

5·
3 months agoIt is exactly my case, as HomeKit by itself is way too limited for automations.
All of my HomeKit devices are actually exposed through HomeBridge, so I can still use HomeKit stuff if needed, and devices that do not support HomeKit can still be added to HomeKit.
My current challenge is on the Smart Dashboard side, I don’t really want to buy a Google Pixel Tablet for this, and the Nest Hubs I have don’t really integrate with HomeAssistant except through Google cloud services.
HomeKit dashboard is fine but too basic.
For me what generally happens if I stop at 9PM, I will work through the problem in my sleep (and it will prevent me from getting a good night sleep), but I will often find a breakthrough the next morning during shower time.
I’m talking about those hard, multi-days debugging problems that nobody can figure out, but as someone else raised, that’s why I get paid good money for it.
It still sucks though. That first response in the thread rings so true, ok now I get it, no you don’t…