643
Philips Hue will force users to upload their data to Hue cloud
(www.home-assistant.io)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Sep 2023
643 points (99.2% liked)
Technology
60130 readers
2790 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
I bough a TP-Link smart bulb once. It was very nice - I could just download a "tp link bulb client" written for everyone by some third-party dude. If I wanted to, I could add a desktop shortcut to turn on/off the bulb.
Then TP-Link decided to automatically update the firmware of the bulb without my knowledge. The update turned off the REST API that made the third-party client to work. I could only use the shitty MOBILE app from then on.
The update was impossible to revert (though TP-Link said "Ok write to our support and we'll give you the downgrade file" no fuck you).
Ever since I've vowed to heavily think whether I want to buy a non-open-source firmware smart device ever again. Recently I bought a smart bulb and two smart sockets that come pre-flashed with "Tasmota" and "WLED" firmware out of the factory and they work great.
And I OWN them too
Many years ago i bought an RGB LED and naively thought the remote signal must have some standard protocol, because it is so simple commands that would allow for some cool shit if automated. Oh boy was i wrong. Proprietary smart home software is the most insane. How on earth should your home become "smart" when it is locked into some ideology (manufacturer) or worse yet you have multiple "parties" fighting over the government causing a shutdown.
NGL you kinda went into left field at the end there, but I still agree.
i wanted to compare the issue with the principles of government and the structures needed,because that what smart home should be, organizing your home to certain effect.
And like with state government that requires transparent and consistent rules, cooperation of the different branches and accountability.
That doesn't sound like it was impossible, it sounds like you just didn't want to do it.
Factually, it was how you described. Poetically, it was making my life as a customer unnecessarily difficult to the point where the word "impossible" is a valid form of artistic expression. I didn't want to have to beg anybody to please unlock the device I paid for.
https://community.home-assistant.io/t/tp-link-offers-way-to-add-local-api-back
Please be advised that I intentionally cherry-picked the comments that support my point, as I was just skimming the thread.
There is esphome too, it's not used a lot by fabricant yet, but still exist and compatiblr with all devices using an esp as chip.
Pi-hole.
My two top-blocked domains are related to TP-Link.
While I can’t always get local-only devices, I can at least separate their traffic and block the shit out of them.
Why do they do this shit? Is "User A turned their lights on at 9 AM" that valuable of data that they'd disable third party shit?
I guess it's because it's "insecure". Any device on the network could control the lights. Tasmota allows setting a password for the control panel though.
Tasmota is great but I've found the number of available devices is limited. For instance Tasmota smart dimmer plugs do not exist, nor could I find a stand alone controller.
Z-wave or Zigbee integration dramatically expand the number of available options and work with local controllers.
I too get the feeling that the selection of devices with Tasmota pre-flashed is rather limited. Due to the nature of Tasmota, those devices will only be Wi-Fi devices, which further causes problems with battery usage (contrary to Zigbee/Z-wave etc.) 15 minutes ago I was looking at smart buttons that can run Tasmota, and I've only found the Shelly Button 1. And funnily enough, it's possible to connect it with microUSB (!) so it stays charged.
All zigbee devices' firmware is proprietary though, no? This is why I'm willing to suffer for Tasmota
The device list seems larger if you're willing to flash Tasmota yourself: https://templates.blakadder.com/
Zigbee does work with a generic controller on Home Assistant and other platforms, and there are >3100 devices that are compatible with zigbee2mqtt, a Zigbee to MQTT bridge that exists to bypass the need for proprietary Zigbee bridges. No proprietary app or Internet access required either, but it was not easy to set up. Here's a list of supported devices: https://www.zigbee2mqtt.io/supported-devices/
The list of Tasmota devices is extremely limited if you don't want to flash it yourself, but a bit less so if you use Tuya Convert which is done via WiFi. It seems the device list is getting shorter all the time as vendors switch to other hardware implementations, but I seem to remember reading that a new Tasmota version will be coming that supports additional hardware.
To get plug-in dimmer and smart button functionality (Shelly Button 1 didn't exist at the time) I had to put in Z-Wave. and I've since added a few new devices. Z-wave works pretty well, but not flawlessly. My Tasmota stuff just works and works much better than the original firmware on my smart bulbs and plugs.
Just getting my feet wet with Zigbee because I need yet another dimmer plug for a different location, but my understanding is most (but not all) Zigbee devices are not proprietary and work with most controllers. I'll know next week.