-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
tried updating channel <your channel here> although the handler was already disposed #881
Comments
It's hard to know what your system is doing, but this means that there is no handler for this thing - the OH core has either shut it down or not started it yet. This can happen during configuration changes, binding system restarts etc. At the end of the day this is a system/core issue. |
Thanks @cdjackson , |
Well, the error is coming from the core. The core seems unable to find the thing handler for this thing (as per the error). I agree - it seems strange if there are other channels working - maybe there's something strange with your configuration. In any case I don't see how (at the moment anyway) that this can be an issue in the binding given it's the core that manages this and there's nothing here that shows any error in the binding. There is something a little strange here -:
This appears to show the same device updating two different channels, but in the second one it doesn't print the address - it prints |
Thank you Chris, no it’s well better understood. |
Hi @cdjackson , Is this log passage similar?
|
No - it's a completely different log with a very different meaning. This means that you are trying to send commands to a channel that can't be commanded. |
Outline
I see quite often the entry "Handler ZigBeeThingHandler of thing zigbee:device:62ec522f14:a4c1384309cf08d7 tried updating channel A4C1384309CF08D7_1_meteringsumdelivered although the handler was already disposed."
can this be avoided?
Configuration
Logs
The text was updated successfully, but these errors were encountered: