Closed MHerbst closed 1 year ago
Faced this night the same issue. Running OH 3.3 on Windows with Zulu and Conbee 2 on Raspberry 4. Before update to 3.3 never had this issue.
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/deconz-binding-show-error-after-oh-3-3-restart/137699/1
This issue has been mentioned on openHAB Community. There might be relevant details there:
I got this problem last night without restarting OpenHAB (for months). I don't find a log message but the deconz bridge thing was offline with COMMUNICATION ERROR and "Error while connecting: Destroyed container cannot be restarted". Deactivating and activating the bridge thing solved that problem (so an automatic reconnect should also be possible... ;-)).
I hope this can get improved/fixed soon. It's very annoying when the lights randomly aren't working anymore...
Hi, just noticed that de-/activating helps, how do you automate this?
Sven Strohschein @.***> schrieb am Sa., 3. Sept. 2022, 21:39:
I got this problem last night without restarting OpenHAB (for months). I don't find a log message but the deconz bridge thing was offline with COMMUNICATION ERROR and "Error while connecting: Destroyed container cannot be restarted". Deactivating and activating the bridge thing solved that problem (so an automatic reconnect should also be possible... ;-)).
I hope this can get improved/fixed soon. It's very annoying when the lights randomly aren't working anymore...
— Reply to this email directly, view it on GitHub https://github.com/openhab/openhab-addons/issues/13141#issuecomment-1236187864, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFDAWAHCBI4RBRTYKUSJ2QLV4OSQFANCNFSM535BJQZQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I haven't automated it. I mean it should be possible to fix the binding, that the binding do the reconnect automatically. Unfortunately the binding seem to have no maintainer, therefore this ticket isn't assigned and nobody seems to fix that... :-(
I haven't automated it. I mean it should be possible to fix the binding, that the binding do the reconnect automatically. Unfortunately the binding seem to have no maintainer, therefore this ticket isn't assigned and nobody seems to fix that... :-(
Script should look like this:
Thread::sleep(45000)
sendHttpPutRequest("http://user:password@openhabhost:8080/rest/things/deconz%3Adeconz%3A00212E06B3E4/enable", "text/plain", 'false')
Thread::sleep(10000)
sendHttpPutRequest("http://user:password@openhabhost:8080/rest/things/deconz%3Adeconz%3A00212E06B3E4/enable", "text/plain", 'true')
Just replace the thing path with your UID and "user" and "password" with your admin user. This will de- and reactivate the deconz bridge thing on startup and on thing becoming offline.
I am using this script which I started in a screen session for now. I am trying to get this working also as a systemd service but wasnt successful sofar.
#!/usr/bin/env bash
set -x
set -e
export COMPOSE_INTERACTIVE_NO_CLI=1
while :
do read line
echo "==> found error pattern ${line}"
docker-compose exec -T openhab /openhab/runtime/bin/client -p habopen bundle:restart org.openhab.binding.deconz
done < <(tail -F /srv/openhab3/openhab_userdata/logs/openhab.log | grep --line-buffered -F "Get full state failed")
I have exactly the same issue here, after a reboot the conee gateway is offline, clicking on "Pause" and "Play" it goes immediately online. But additionally all my sensors (Xiaomi OpenClose, Presence, Temperature, Pressure, Humidity, ...) stay offline too. After some minutes/hours of waiting to go online again sometimes the OpenClose and Presence sensors are back online, but the rest need also a click on "Pause" and "Play" in PaperUI to get back online immediately.
Any idea how to workaround till a bugfix is available? I am pretty new to scripting in openhab, and did not get how and where to put them and to run them, perhaps there is a good tutorial?
Hi, clearing the openhanded cache has helped me and the issue is gone now.
On my setup this didn't help. Error came also after clearing cache :(
@MHerbst - are you planning on back porting the smarthomej fixes? I'd be happy to review.
@jlaur Please excuse my late answer. I am a bit busy at the moment. I will try to find allocate time in the next days to compare both source version. As far as I remember, the SmarthomeJ implementation contains not only fixes but only some enhanced settings with regard to the websocket handling.
Fixed with #14622
Sweet! :+1: Thank you.
After I have updated OH to version 3.3 the deCONZ binding hast start problems. After OH is restarted the gateway stays offline and the log file contains logs of these messages.
After manually stopping and starting the gateway thing the binding works fine again and the Websocket message no longer appears.
There are also some these interesting messages in openhab.log (maybe not related to the problem):
There were not problems with OH 3.2
Steps to Reproduce (for Bugs)
Stop and start openHAB
Your Environment
I have attached a log file with DEBUG messages openhab.log