@nebulon Sure, tags are nice for filtering. I just thing those 3 specific tags could be labels for better visual review scrolling the whole list. Also, bear in mind they should be "OR" labels, so maybe it is a separate field to tags?
For those that don't know, LoRaWAN is an IoT networking technology. The main features are:
The sensors or things are generally very low power, with battery-lives of 10+ years.
The data bandwidth is very low, often a few bytes a second.
The connection range can be very high, 10+ kilometres.
The sensors or things can go in places where there's no wiring, power or wifi, and they can relay messages for almost unlimited distance coverage.
Car park sensors - is there something in this space?
Sonic sensors - how much fluid is in this tank?
Current sensors - how much power is this thing using?
Location sensors - where's my thing?
Movement sensors - is my thing being hit?
Weight sensors - how full is my thing?
The common use case would be to hook up to something like Prometheus or Influx time-series databases for recording measurements over time, then Grafana for charting time-series data, and NodeRED for reacting to measurements as required, perhaps with alerts or responses.
As you can see, we have 2 of the 4 components (Prometheus & Grafana) to make Cloudron a rapid IoT development platform stack.
I can think of many use-cases, the easier this is made, the more things people can come up with?
It's Thursday, did I put the bins/trash out?
Did I leave the oven/lights on?
Where's my kid?
Then for businesses:
How many people walked through my doors?
What's being used?
What needs replacing?
Hopefully that helps explain, and Chirpstack does seem to be the de-facto in this areas, as much as Prometheus, Grafana and NodeRED seem to be the de-facto apps in their areas.
Plus, this is another reason why Cloudron on Raspberry Pii etc is good, as it can give another use-case for off-grid servers that only have a need within a building or property but no need for the outside world to access.
For anyone else following this thread and app - Portals are a killer feature - get to know how they work, they will add massive value to partner communications!
For interest, the way permissions management works in EspoCRM
"Roles" you set all the permissions for what users with that Role cannot see, so opt-out permissions.
"Portal Roles" you set all the permissions for what users with that Portal Role can see, so opt-in. Which is very fast to setup.
Create an Entity called "Brand Assets", add some multi-attachment fields for things like Icons, Logos, Fonts, Banners, Biographies, etc.
Create a Portal called "Marketing" with the custom URL as marketing.example.com.
Create Portal Role for "Marketing" with access to the " Brand Assets" Entity, and maybe some others once you get used to permissions sharing.
Hey-presto! Your own live data sharing portal for that Entity. Once you've done one, you have a model for all external partnership types to share Entities and all or some records for their access to the latest single source of truth.
@humptydumpty Mostly agreed. The changes suggested are just renaming what's already there.
"Help Offered or Wanted" I think should be a top-level section. I think it was, so not sure why that changed. I also think "Worked Offered or Wanted" would be more appropriate, as that was the hoped intention of that section. I know Girish said he doesn't want it to become a jobs board - but I kinda see that as inevitable as there's so many skills needed online nowadays that we can't all know or do everything but often can network those skills and needs on our travels.
I think it you're looking at self-hosting apps, whether for home or business, you're already very technically competent, so I can't see it ever being SaaS level easy, but maybe as time goes by it will, and certainly a good community of contributors is essential to that.
It's hard to know usage and user-needs without the passage of time and watching what happens, so I'm sure that's being studied and learned from as we go. I can only suggest as it's not my product, but then the best products are usually ones that customers feel an affinity close to ownership.
Growth is always a blessing and a challenge, so just hoping my suggestions can make it more scaleable without getting unhealthy for time-needs, and please most of the people most of the time.