sampsyo
commented
5 years ago That's a very good question! If I were in your position and I had some time to do a little hacking, I'd probably avoid using Home Assistant and try to build a new HomeBridge plugin that uses wideq directly. This seems like it couldn't be too hard... I know that HomeBride is a JavaScript thing, but it couldn't be too hard to communicate with a Python subprocess to do monitoring and control, right? Surely there must be other HomeBridge plugins that similarly need to interface with a library in another language?
Barring that, it wouldn't be too bad to run HA just for SmartThinQ stuff, without converting your entire setup. There's no particular reason that both couldn't coexist on the same Raspberry Pi. There's even a HomeBridge-to-Home Assistant plugin I've used with some success in the past.
kafeg
I have a full-blown HomeKit environment here consisting of over 30 devices. I also have HomeBridge running on a Rpi3B+ supporting 5 other “non-homekit” devices.
Wideq works pretty well for me from the command line but I would like to get my new LG A/C visible to HomeKit Right now the only way seems to be via Home Assistant (hass.io) which I know little to nothing about. Are there any compelling reasons to convert my entire setup to HomeAssistant? Right now my current setup is very stable and I am not to keen on re-inventing this particular wheel. Can I run Homebridge and Home Assistant at the same time on my Rpi3B+ ?
Thanks in advance for any insight you are able to provide…..