Probably a bit technical, but I MISS cookie-based authentication, as opposed to basic auth on home.myopenhab.org. Would solve a lot of problems with PWA features of the UI
Also an idea I had, not directly related to openHAB Cloud the software, but could be within the myopenHAB “brand”: the service could offer a dynamic DNS feature which would set up the TXT records necessary to perform a Let’s Encrypt DNS-01 challenge, in order to ultimately provide users with a valid TLS certificate to use on their LAN (and automatically assigned to the openHAB instance and renewed whenever appropriate). Home Assistant has something like that which uses an external service (duckdns.org), but in our case it would be something like bobsawesomehome.myopenhab.org pointing to 192.168.1.102 or whatever the local IP for the server is. Ideally the server would respond to those queries only for a select range of source IP addresses, so that it does not divulge an internal IP address to the internet at large.
Serving the web app over HTTPS by default unlocks a lot of useful features, but setting it up on your LAN is painful.
I LOVE: How myopenhab.org is run on donations and not a monthly fee that each user has to pay. Instead of 1,000’s of people all paying for their own hosted cloud which still costs for certificates and the upkeep. The power of sharing and being in a community.
As someone who does not work or connected in any way to the foundation, please consider subscribing at the link below so we all benefit from @digitaldan’s (and any other volunteers involved) hard work. Thank you.
Last year I set up my own cloud server. I setup correctly notifications in Firebase for Android and IOS, everything works perfectly. The code is quite easy to understand and can be modified as you like. I think the founders did an excellent job and each one could install it and adapt the functionalities to their needs