This is why you should never buy into a proprietary hub/ecosystem. Just buy a sbc + zigbee/thread dongle with home assistant and you’re golden. Compatible with way more than any big company ecosystem and won’t get bricked.
I can’t believe this is legal… I understand that they might not find it worthwhile to support it anymore after 10 years. But why the need to actively brick them? Should at least go the other way around too, they brick the device. We get to ‘brick’ the money they got for it.
Homeassistant is everything “smart homes” were supposed to be. Why would you use a cloud service to turn on a lightbulb, or even worse check your security cameras, that are connected to your same WiFi?
Completely overhaul the complex configuration, it’s incredibly difficult to do simple things like creating a button on my dashboard to stop my fish tank pump for 15 minutes. Or to take photos when unifi protect camera AI detects a human, and display that on the dashboard. They are already sensors but building controls for any of these actions and automations relies on bizarre hacks and insanely complex yaml. Or creating morning routines for my lights based on a number of factors, you need countless plugins for basic configurability or basing lighting on sunrise/set times. It should be easy to create controls to do things like disable a routine for a few days.
The programmability is poor, it’s like it was built by a bunch of hobbyists instead of software engineers.
And stop deprecating built in features with extremely short notice.
Not sure how that would conflict with anything… Maybe a schedule? Then just add an override toggle helper that you check in your schedule.
I feel like you’re trying to use it in your specific way. Instead of using home assistant as intended. Sure that’s a valid criticism for your use cases. But it doesn’t make home assistant objectively terrible imho.
You can either directly disable an automation e.g. automation.turn_off: ... or set/read the state of a helper entity that you use to disable certain functionality in another automation. There are probably more tricks too. Though I try to make my automations as atomic as possible so they don’t need to be connected this way.
This is why you should never buy into a proprietary hub/ecosystem. Just buy a sbc + zigbee/thread dongle with home assistant and you’re golden. Compatible with way more than any big company ecosystem and won’t get bricked.
I can’t believe this is legal… I understand that they might not find it worthwhile to support it anymore after 10 years. But why the need to actively brick them? Should at least go the other way around too, they brick the device. We get to ‘brick’ the money they got for it.
Homeassistant is everything “smart homes” were supposed to be. Why would you use a cloud service to turn on a lightbulb, or even worse check your security cameras, that are connected to your same WiFi?
They likely use a ec2 instance that costs Logitech 10s of dollars/month to keep working. Can’t have that now, so into the bin all of these go.
deleted by creator
Home assistant is horrible from a software and configurability perspective but it’s the best tool out there in its class
Genuine question: what makes you label it as “horrible” - which is quite a strong word - and what should it be doing differently, in your opinion?
Completely overhaul the complex configuration, it’s incredibly difficult to do simple things like creating a button on my dashboard to stop my fish tank pump for 15 minutes. Or to take photos when unifi protect camera AI detects a human, and display that on the dashboard. They are already sensors but building controls for any of these actions and automations relies on bizarre hacks and insanely complex yaml. Or creating morning routines for my lights based on a number of factors, you need countless plugins for basic configurability or basing lighting on sunrise/set times. It should be easy to create controls to do things like disable a routine for a few days.
The programmability is poor, it’s like it was built by a bunch of hobbyists instead of software engineers.
And stop deprecating built in features with extremely short notice.
Sure it can improve in some places but saying it is horrible is really over stating it… It was never meant to be ‘programmable’ but configurable.
Now for your fish tank issue… That seems like the easiest automation to make…
And then just add it to dashboard. Not really sure how that’s horrible or difficult?
Ran into issues with it conflicting with other routines that control the fish tank pump too
Not sure how that would conflict with anything… Maybe a schedule? Then just add an override toggle helper that you check in your schedule.
I feel like you’re trying to use it in your specific way. Instead of using home assistant as intended. Sure that’s a valid criticism for your use cases. But it doesn’t make home assistant objectively terrible imho.
How do you build controls to toggle automations as you described?
You can either directly disable an automation e.g.
automation.turn_off: ...or set/read the state of a helper entity that you use to disable certain functionality in another automation. There are probably more tricks too. Though I try to make my automations as atomic as possible so they don’t need to be connected this way.What? The first time I started homeassistant it autodiscovered 90% of my IoT stuff
Same for me, but any real automations are a massive pain. Like I said, nothing is better though
Ah yeah, YAML is definitely not the best tool to do that. I resorted to Node-RED for any more convoluted flows
How does node red integrate with HA?
https://flows.nodered.org/node/node-red-contrib-home-assistant
Alternatively, you can run Node-RED directly in HACS