I have a very strange problem with the deConz plugin. I can import devices to Domoticz, and they do work for a while after an initial installation, but then they suddenly stop working. I still have communication with deConz, everything is fine except when I turn a switch on/off, then I get this error:
-
2022-09-27 00:27:29.448 Error: PhosCon: deCONZ error :{'error': {'address': '/lights/3/state', 'description': 'resource, /lights/3/state, is not modifiable. Device is not reachable.', 'type': 202}}
I have another issue as well, I can't start the GUI in deConz to debug the problem from that end either. It works after a fresh install with a manual start from the menu in Raspbian GUI (which is required to get access to deConz from Domoticz as well), but as soon as I try to make a service out of it (with or without GUI), communication for devices with deConz stops to work from the Domoticz side. It is working from deConz towards Domoticz though.
I have reinstalled deConz from scratch three times, the same with the plugin. The only time I got the plugin to work when communicating to deconz was after a reboot when RFXTRX plugin stopped working instead. After another reboot (no changes at all), the deConz plugin stopped working again and RFXTRX was working again.
I have gone back to a fresh installation of the previous Raspbian release after huge issues with Python on the latest one (together with plugins). I however ended up in having the same problems with the Daikin plugin also on this older release, so I am not running that plugin at all (it anyway ended up better with my own integration). I had to update to the latest beta to avoid other issues with Python and the deConz plugin and here I am with something that works, kind of, but not at all...
I saw something about issues with websockets, can this be it in this case?
The reason I was going down the deConz path again was that several of my devices stopped working in SmartThings (that I've been using for ZigBee up until now, as they used to have more custom integrations than deConz and it was much easier to patch broken integrations there up until now). Maybe I need to start developing my own edge drivers on SmartThings instead?
Does anyone have any idea in what ditch to start digging?
I have full debugging and the only strange thing is the error message above. All other deConz communication seems to work as it is supposed to.
2022-09-27 00:52:15.023 PhosCon: Pushing 'onHeartbeatCallback' on to queue
2022-09-27 00:52:15.073 PhosCon: Processing 'onHeartbeatCallback' message
2022-09-27 00:52:15.073 PhosCon: Acquiring GIL for 'onHeartbeatCallback'
2022-09-27 00:52:15.073 PhosCon: Calling message handler 'onHeartbeat' on 'module' type object.
2022-09-27 00:52:15.073 PhosCon: onHeartbeat called
2022-09-27 00:52:15.073 PhosCon: Acquiring GIL for 'onHeartbeatCallback'
2022-09-27 00:52:25.040 PhosCon: Pushing 'onHeartbeatCallback' on to queue
2022-09-27 00:52:25.090 PhosCon: Processing 'onHeartbeatCallback' message
2022-09-27 00:52:25.090 PhosCon: Acquiring GIL for 'onHeartbeatCallback'
2022-09-27 00:52:25.090 PhosCon: Calling message handler 'onHeartbeat' on 'module' type object.
2022-09-27 00:52:25.090 PhosCon: onHeartbeat called
2022-09-27 00:52:25.090 PhosCon: Acquiring GIL for 'onHeartbeatCallback'
Restarting the deConz plugin gives this chunk of data that looks OK:
2022-09-27 00:54:13.198 PhosCon: ### Groupe > 1 Name:Farstu
2022-09-27 00:54:13.198 PhosCon: ### Groupe > 2 Name:Ute
2022-09-27 00:54:13.198 PhosCon: Acquiring GIL for 'onHeartbeatCallback'
2022-09-27 00:54:13.198 PhosCon: Processing 'ProtocolDirective' message
2022-09-27 00:54:13.198 PhosCon: Acquiring GIL for 'ProtocolDirective'
2022-09-27 00:54:13.198 PhosCon: Protocol set to: 'None'.
2022-09-27 00:54:13.198 PhosCon: Acquiring GIL for 'ProtocolDirective'
2022-09-27 00:54:13.198 PhosCon: Processing 'ConnectDirective' message
2022-09-27 00:54:13.198 PhosCon: Acquiring GIL for 'ConnectDirective'
2022-09-27 00:54:13.198 PhosCon: Transport set to: 'TCP/IP', 127.0.0.1:8088.
2022-09-27 00:54:13.199 PhosCon: Connect directive received, action initiated successfully.
2022-09-27 00:54:13.199 PhosCon: Acquiring GIL for 'ConnectDirective'
2022-09-27 00:54:13.199 PhosCon: Acquiring GIL for 'CPluginTransportTCP::handleAsyncResolve'
2022-09-27 00:54:13.199 PhosCon: Acquiring GIL for 'CPluginTransportTCP::handleAsyncResolve'
2022-09-27 00:54:13.199 PhosCon: Pushing 'onConnectCallback' on to queue
2022-09-27 00:54:13.249 PhosCon: Processing 'onConnectCallback' message
2022-09-27 00:54:13.249 PhosCon: Acquiring GIL for 'onConnectCallback'
2022-09-27 00:54:13.249 PhosCon: Calling message handler 'onConnect' on 'module' type object.
2022-09-27 00:54:13.249 PhosCon: onConnect called
2022-09-27 00:54:13.249 PhosCon: Pushing 'WriteDirective' on to queue
2022-09-27 00:54:13.249 PhosCon: Acquiring GIL for 'onConnectCallback'
2022-09-27 00:54:13.249 PhosCon: Processing 'WriteDirective' message
2022-09-27 00:54:13.249 PhosCon: Acquiring GIL for 'WriteDirective'
2022-09-27 00:54:13.249 PhosCon: Sending 217 bytes of data
2022-09-27 00:54:13.249 PhosCon: 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a 48 6f 73 74 GET./.HTTP/1.1..Host
2022-09-27 00:54:13.249 PhosCon: 3a 20 31 32 37 2e 30 2e 30 2e 31 3a 38 30 38 38 0d 0a 55 73 :.127.0.0.1:8088..Us
2022-09-27 00:54:13.249 PhosCon: 65 72 2d 41 67 65 6e 74 3a 20 44 6f 6d 6f 74 69 63 7a 2f 31 er-Agent:.Domoticz/1
2022-09-27 00:54:13.249 PhosCon: 2e 30 0d 0a 53 65 63 2d 57 65 62 53 6f 63 6b 65 74 2d 56 65 .0..Sec-WebSocket-Ve
2022-09-27 00:54:13.249 PhosCon: 72 73 69 6f 6e 3a 20 31 33 0d 0a 4f 72 69 67 69 6e 3a 20 68 rsion:.13..Origin:.h
2022-09-27 00:54:13.249 PhosCon: 74 74 70 3a 2f 2f 31 32 37 2e 30 2e 30 2e 31 0d 0a 53 65 63 ttp://127.0.0.1..Sec
2022-09-27 00:54:13.249 PhosCon: 2d 57 65 62 53 6f 63 6b 65 74 2d 4b 65 79 3a 20 71 71 4d 4c -WebSocket-Key:.qqML
2022-09-27 00:54:13.249 PhosCon: 42 78 79 79 6a 7a 39 54 6f 67 31 62 6c 6c 37 4b 36 41 3d 3d Bxyyjz9Tog1bll7K6A==
2022-09-27 00:54:13.249 PhosCon: 0d 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b 65 65 70 2d 61 ..Connection:.keep-a
2022-09-27 00:54:13.249 PhosCon: 6c 69 76 65 2c 20 55 70 67 72 61 64 65 0d 0a 55 70 67 72 61 live,.Upgrade..Upgra
2022-09-27 00:54:13.250 PhosCon: 64 65 3a 20 77 65 62 73 6f 63 6b 65 74 0d 0a 0d 0a .. .. .. de:.websocket....
2022-09-27 00:54:13.250 PhosCon: Acquiring GIL for 'WriteDirective'
2022-09-27 00:54:13.251 PhosCon: Acquiring GIL for 'CPluginTransportTCP::handleRead'
2022-09-27 00:54:13.251 PhosCon: Pushing 'ReadEvent' on to queue
2022-09-27 00:54:13.300 PhosCon: Processing 'ReadEvent' message
2022-09-27 00:54:13.300 PhosCon: Acquiring GIL for 'ReadEvent'
2022-09-27 00:54:13.300 PhosCon: Received 349 bytes of data
2022-09-27 00:54:13.300 PhosCon: 48 54 54 50 2f 31 2e 31 20 31 30 31 20 53 77 69 74 63 68 69 HTTP/1.1.101.Switchi
2022-09-27 00:54:13.300 PhosCon: 6e 67 20 50 72 6f 74 6f 63 6f 6c 73 0d 0a 55 70 67 72 61 64 ng.Protocols..Upgrad
2022-09-27 00:54:13.300 PhosCon: 65 3a 20 77 65 62 73 6f 63 6b 65 74 0d 0a 43 6f 6e 6e 65 63 e:.websocket..Connec
2022-09-27 00:54:13.300 PhosCon: 74 69 6f 6e 3a 20 55 70 67 72 61 64 65 0d 0a 53 65 63 2d 57 tion:.Upgrade..Sec-W
2022-09-27 00:54:13.300 PhosCon: 65 62 53 6f 63 6b 65 74 2d 41 63 63 65 70 74 3a 20 56 30 68 ebSocket-Accept:.V0h
2022-09-27 00:54:13.300 PhosCon: 74 45 62 6e 35 46 68 49 41 31 78 66 51 52 79 47 33 79 55 31 tEbn5FhIA1xfQRyG3yU1
2022-09-27 00:54:13.300 PhosCon: 61 47 39 63 3d 0d 0a 53 65 72 76 65 72 3a 20 64 65 63 6f 6e aG9c=..Server:.decon
2022-09-27 00:54:13.300 PhosCon: 7a 0d 0a 41 63 63 65 73 73 2d 43 6f 6e 74 72 6f 6c 2d 41 6c z..Access-Control-Al
2022-09-27 00:54:13.300 PhosCon: 6c 6f 77 2d 43 72 65 64 65 6e 74 69 61 6c 73 3a 20 66 61 6c low-Credentials:.fal
2022-09-27 00:54:13.300 PhosCon: 73 65 0d 0a 41 63 63 65 73 73 2d 43 6f 6e 74 72 6f 6c 2d 41 se..Access-Control-A
2022-09-27 00:54:13.300 PhosCon: 6c 6c 6f 77 2d 4d 65 74 68 6f 64 73 3a 20 47 45 54 0d 0a 41 llow-Methods:.GET..A
2022-09-27 00:54:13.300 PhosCon: 63 63 65 73 73 2d 43 6f 6e 74 72 6f 6c 2d 41 6c 6c 6f 77 2d ccess-Control-Allow-
2022-09-27 00:54:13.300 PhosCon: 48 65 61 64 65 72 73 3a 20 63 6f 6e 74 65 6e 74 2d 74 79 70 Headers:.content-typ
2022-09-27 00:54:13.300 PhosCon: 65 0d 0a 41 63 63 65 73 73 2d 43 6f 6e 74 72 6f 6c 2d 41 6c e..Access-Control-Al
2022-09-27 00:54:13.300 PhosCon: 6c 6f 77 2d 4f 72 69 67 69 6e 3a 20 68 74 74 70 3a 2f 2f 31 low-Origin:.
http://1
2022-09-27 00:54:13.300 PhosCon: 32 37 2e 30 2e 30 2e 31 0d 0a 44 61 74 65 3a 20 4d 6f 6e 2c 27.0.0.1..Date:.Mon,
2022-09-27 00:54:13.300 PhosCon: 20 32 36 20 53 65 70 20 32 30 32 32 20 32 32 3a 35 34 3a 31 .26.Sep.2022.22:54:1
2022-09-27 00:54:13.300 PhosCon: 33 20 47 4d 54 0d 0a 0d 0a .. .. .. .. .. .. .. .. .. .. .. 3.GMT....
2022-09-27 00:54:13.300 PhosCon: Pushing 'onMessageCallback' on to queue
2022-09-27 00:54:13.300 PhosCon: Acquiring GIL for 'ReadEvent'
2022-09-27 00:54:13.300 PhosCon: Processing 'onMessageCallback' message
2022-09-27 00:54:13.300 PhosCon: Acquiring GIL for 'onMessageCallback'
2022-09-27 00:54:13.301 PhosCon: Calling message handler 'onMessage' on 'module' type object.
2022-09-27 00:54:13.301 PhosCon: onMessage called
2022-09-27 00:54:13.301 PhosCon: WebSocket Handshake : HTTP/1.1 101 Switching Protocols ***Upgrade: websocket ***Connection: Upgrade ***Sec-WebSocket-Accept: V0htEbn5FhIA1xfQRyG3yU1aG9c= ***Server: deconz ***Access-Control-Allow-Credentials: false ***Access-Control-Allow-Methods: GET ***Access-Control-Allow-Headers: content-type ***Access-Control-Allow-Origin:
http://127.0.0.1 ***Date: Mon, 26 Sep 2022 22:54:13 GMT *** ***
2022-09-27 00:54:13.301 PhosCon: Acquiring GIL for 'onMessageCallback'
