-
Notifications
You must be signed in to change notification settings - Fork 47
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
Devices timing out with 0.9.2 and 0.9.1 #209
Comments
Can confirm rolling back to .8.6 and all devices respond and turn off and on correctly (instantly). Back to .9.2 and sometimes it's instant but often it's 15-30 seconds if they respond to a command if at all. |
I also have a significant number of lights (19) that are still unavailable after updating from 0.9.0 to 0.9.1. These include both zigbee and zwave devices. Rolling back to 0.8.6 resolves this issue. |
Please try enabling debug logging and see if anything shows up there. Is there anything different/special about the 19 lights that aren’t responding? Like, are they all rgbw and other lights aren’t? |
Mine are all zwave. On Apr 13, 2023, at 7:10 PM, Jason Cheatham ***@***.***> wrote:
Please try enabling debug logging and see if anything shows up there.
Is there anything different/special about the 19 lights that aren’t responding? Like, are they all rgbw and other lights aren’t?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hmmm...a lot of those devices don't seem like they should be event emitters. Currently, the only things that are (or should be) added as event emitters are devices that can act as button controllers -- ones with PushableButton, HoldableButton, DoubleTapableButton, or ReleasableButton. Are they added as HubitatEventEmitter when you're running v0.8.6, or only with v0.9.x? |
I'm having similar issues and I didn't test .9.x but it works perfectly with .8.6 |
They were added as HubitatEventEmitter only with v0.9.x. Version .0.9.4 seems to have resolved this issue. |
.9.4 seems to be working a lot better, I'm still getting random timeouts but nothing that is atrocious. .8.6 still seems to be rock solid and always responding. |
Hmmm… without more information, I’m really not sure what might be going on here. I haven’t been able to reproduce that locally, and there’s nothing in 0.9.x that should have affected the ability to connect to devices. There’s definitely nothing in 0.9.4 that should have changed the behavior from 0.9.3. The only disruptive change (that I’m aware of) in 0.9 was switching HA device names to use the Hubitat Of course, that doesn’t mean there isn’t an issue, we just need to nail down what it is. 🙂 Are you actually seeing any sort of timeout error in the logs, or are devices just slow to respond when issuing commands from HA? When issuing commands from HA, does the log show commands being immediately sent to Hubitat? |
Is this issue still happening? |
Still need time to test but I'm getting device not responding to commands calling from HA to hubitat, seems to run fine when calling from hubitat directly, I was on 0.8.6 and that was fine (upgrading to 0.9.2 and .1 also messed with some of my device names but easily fixed fyi). HA on 2023.4.4 and hubitat on 2.3.5.125.
The text was updated successfully, but these errors were encountered: