3 ms·
I don’t think the fault is in Home Assistant. Ultimately, if the smart home device doesn’t cooperate by providing a standards-compliant local interface such as
by Nextgrid 5y ago
I don’t think the fault is in Home Assistant. Ultimately, if the smart home device doesn’t cooperate by providing a standards-compliant local interface such as MQTT or similar there’s not much you can do. HA tries to do its best with integrations that reverse-engineer proprietary APIs but obviously the reliability is variable.
When it comes to devices that do cooperate I’ve found Home Assistant to be extremely reliable. Every update I’ve applied has gone through flawlessly, but the truth is that once something is set up you don’t really need to update. I’ve set one up for friends with only local devices (WIFI switches and relays) and it’s been rock-solid for a couple years now. It’s probably severely outdated now but it works fine and being behind a firewall means outside security threats aren’t an issue.
It’s been working perfectly. They don’t even know nor care how it works behind the scenes, from their perspective light switches will toggle their corresponding light, some basic automations like turning off lights after 10 minutes in common areas such as the hallway and the heating will pause in any room that has windows open.
- jeroenhd 5y agoI don't think the fault is in Home Assistant either, the fault is in the mountain of shitty hardware thag just won't cooperate. Home Assistant does its best to compensate for the bullshit and they're doing an amazing job. Autodiscovery is a godsent and when it works, it's easily the best way to get any home automation system set up. But if autodiscovery fails, honestly, the process is unnecessarily painful. You need to enter a lot of information and mess with settings to get things working reliably because the vendor decided to change the API between hardware revision or send invalid JSON at random.