Any time you upgrade to a version that isn't supported, you run the risk that a change to the Home Assistant APIs won't be handled properly by the HassController class in MSR. In the last six months, there have been two changes that have changed their API significantly enough to cause issue, and in one of those two cases, it was total shutdown.
I know we talked about this a while back, but wondered if anyone has any ideas at all? It's still a 5-10 second pause between initiating a TTS event and getting the output.
This is using either a direct Luup call or the most excellent VeraTTS plug in.
I noticed that executing from reactor using the little 'run' icon, I'm getting an occasional '0 timeout undefined' error (even though the event eventually happens
Any thoughts, anyone?
Years after having installed and implemented the homekit integration to the vera through the verahomekitbridge which later became the homebridge:rafale77/VeraHomeKitBridge rafale77/VeraHomeKitBridge
Contribute to rafale77/VeraHomeKitBridge development by creating an account on GitHub.
(I just implemented a few updates I discovered were outdated for the garage door which were meant for older vera firmwares)
I just recently came to the realization that I can do a lot more with Hey Siri with devices I already own. I have therefore a renewed interest and have been configuring my homekit installation to match my alexa capability. Unfortunately a lot of things are still pretty far behind in terms of integration but... I found homebridge and all its plugins. I just wanted to share the alternative I pursued: Home Assistant. I implemented the Homekit component for it and have been able to bridge Sonos and Harmony while my openLuup devices are still bridged into homekit through the VeraHomekitBridge. If you already have home assistant, homebridge is potentially redundant...
The probability of taking down alexa and its cloud dependency completely is increasing...