Unhandled exceptions during bunding init (OH3)
kpanchen opened this issue · 6 comments
Updated to OH+binding 3.1.0. Unhandled exceptions on binding startup / things discovery. Seems fine after, no crashes.
Let me know if debug logging would require.
Please provide debug logging for this, and also advise what the devices are that might be causing this.
Unfortunately I can't really see what is happening with this. There must be an attribute that is incorrectly cast. Normally this happens if a device has an attribute configured incorrectly. The library tries to normalise such things, but there's always the possibility that there's one I've not covered. Unfortunately the log doesn't show this as there's no communications with the device.
I'd suggest to remove the XML for the device (in the "userdata / bridge name" folder) and then start discovery again and see if we can log the issue.
Unfortunately I can't really see what is happening with this. There must be an attribute that is incorrectly cast. Normally this happens if a device has an attribute configured incorrectly. The library tries to normalise such things, but there's always the possibility that there's one I've not covered. Unfortunately the log doesn't show this as there's no communications with the device.
I'd suggest to remove the XML for the device (in the "userdata / bridge name" folder) and then start discovery again and see if we can log the issue.
openhab.log
This time all five detected fine but only 3 xml files were recreated:
I really need to see the full debug logs to understand what is happening. Please take a look at the binding documentation on how to configure this - currently there is no zigbee information being logged, and as the error is in the zigbee framework it's not possible to see what's happening if this isn't enabled.