zlacker

>>pictur+(OP)
This enshittifcation is endemic. Corporations cannot just release a good product and support it. The better the product is and the larger the customer base becomes, the higher the likelihood that some business planner is going to see dollar signs and try to squeeze the product for everything it’s worth. And every time this ruins the product. And we’re here with a proprietary phone OS and proprietary apps. Proprietary firmwares on proprietary hardware. And we are completely at the whim of these companies.

And the option is what, buy a Zigbee dongle and a raspberry pi run some code written by unpaid enthusiasts? 3D print a case for it and mount it on the wall, running updates and fixing it ever few months when some package update breaks it?

I like the concept of lights that run from an app. I don’t have any of the physical Hue switches for my system and it’s fine. But I do not want an app that abuses me, and I do not want to maintain some fragile project made from slapped together code. I want robust open hardware with open source software.

I’m convinced that we can achieve this, but it won’t be with the current model of business and engineering we have today.

>>Taylor+We
The Home Assistant team has a full company behind them, and they sell cloud services for the app for people who want it. Zigbee2MQTT has 113 sponsors. If you run them both with docker then updating is pretty simple with no package breaks.

I do get your point though. Fixing the lack of a privacy focused option that works well for people who aren't familiar with systems administration would be nice.

>>tedivm+8h
“If you run them both with docker then updating is pretty simple with no package breaks.”

Do you realize how insane this sounds for non-technical people who want to turn on a light in their livingroom?

>>uptown+3k
Your grandma doesn’t know how to run containers as k8s services?

Don’t tell me she still manually SSHes to each box to run the apps in the background using nohup?!