-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long time no operation causes failure of the first operation of home assistant devices #722
Comments
I'm a new ha-bridge user. This issue seems to be the same as Which user @kmdm has posted a "fix" i am yet to try. (Last comment contain his fix download link) |
thanks to @tryingwebguy and @kmdm, it seems that the problem was solved by using the |
Solved it for me initially but it seams I'm now back at square 1 |
I've tested several times and it worked like a charm. |
Which version of Home Assistant are you using? I'm now on 0.51.1 maybe this is causing it.. And to apply the jar fix your renaming the file "ha-bridge-4.5.6.jar" and replacing the existing one? |
@tryingwebguy I have 0.51.1 - working fine for me. |
Looks like restarting my docker container after replacing the jar file was resorting it back to the original. Just replaced the file and re-initialised within ha-bridge and I'm so far so good. Thanks for the fix @kmdm |
@tryingwebguy I ran habridge on ubuntu, just placed the fix file there and enabled auto starting, no renaming needed. btw i saw you have solved this. cong. |
Fixing with #671 |
After quite a while without any operation, when clicking the TEST_ON or TEST_OFF button on the devices page, the first click would not succeed, also not controllable by smart speaker.
Maybe habridge should send keep alive packages to HomeAssistant API to maintain connection.
HaBridge version 4.5.6, running on ubuntu 16.10, with java version 1.8.0_131.
Hope to fix it soon. Thanks.
The text was updated successfully, but these errors were encountered: