thecode Posted September 16, 2022 Share Posted September 16, 2022 (edited) Overview: Support for the deCONZ Community Official docker container Docker: https://hub.docker.com/r/deconzcommunity/deconz Github: https://github.com/deconz-community/deconz-docker This is an unRAID template for the official deCONZ Community container which replaces the marthoc/deconz docker. If you are migrating an existing marthoc/deconz install to deconzcommunity/deconz, Make sure you have the latest backup from Phoscon. To use this container you need to have a a ConBee II USB stick This template is set to run on a custom network and it is better to assign a fixed IP address, it is also possible to use host network with this template, but make sure to change the web ports If you have just one device it will usually be found at: /dev/ttyACM0 Which is the default device path for this template, however it is recommended to update the device path to use serial by id, which makes sure you point to the correct device even if multiple USB devices are plugged into the server or the USB mapping changes, to do it when the stick is plugged into the server run the following command in a terminal window; ls /dev/serial/by-id Copy the id from the result and update the ConBee USB port in the template as follows: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_[SN]-if00:/dev/ttyACM0 Replace the "usb-dresden---if00:" with the result from the "ls" command, keep the ":/dev/ttyACM0" even if the device is mapped to a different port. This will map the USB stick to "dev/ttyACM0" even if it is mapped to a different path on the host OS. The template is set to install the latest stable release, you can modify the release tab by replacing the "stable" in the template repository, available tags: latest - Latest release of deCONZ, stable or beta stable - Stable releases of deCONZ only beta - Beta releases of deCONZ only version - Specific versions of deCONZ, use only if you wish to pin your version of deCONZ, eg 2.13.02 If you enable VNC mode (make sure to change the password), you can also access the deCONZ mesh app using noVNC: http://IP:6080/vnc.html Replace the "IP" with the container IP address if you like my work, Buy me a beer! Edited September 27, 2022 by thecode 1 Quote Link to comment
Mik3 Posted September 17, 2022 Share Posted September 17, 2022 Hi, thanks for your work much appreciated. Probably it's me but the docker is not working. Please find below all the details. OS: Unraid 6.11-rc5 Fresh install of docker, no previous appdata. I change the net to host, change the HTTP and WS port to something not used but when the container is pulled, it still shows port 80 and port 443 in the docker details in unraid. 192.168.1.2:443/TCP192.168.1.2:443 192.168.1.2:5900/TCP192.168.1.2:5900 192.168.1.2:6080/TCP192.168.1.2:6080 192.168.1.2:80/TCP192.168.1.2:80/opt/deCONZ/mnt/user/appdata/deconz Docker logs shows in RED [deconzcommunity/deconz] Using options .......... --http-port=808 --ws-port=4434 Same happens if using the custom network to br0. Even if I leave the standard configurations the red line is still showed in the docker logs. What am I doing wrong? Quote Link to comment
thecode Posted September 17, 2022 Author Share Posted September 17, 2022 8 hours ago, Mik3 said: Hi, thanks for your work much appreciated. Probably it's me but the docker is not working. Please find below all the details. OS: Unraid 6.11-rc5 Fresh install of docker, no previous appdata. I change the net to host, change the HTTP and WS port to something not used but when the container is pulled, it still shows port 80 and port 443 in the docker details in unraid. 192.168.1.2:443/TCP192.168.1.2:443 192.168.1.2:5900/TCP192.168.1.2:5900 192.168.1.2:6080/TCP192.168.1.2:6080 192.168.1.2:80/TCP192.168.1.2:80/opt/deCONZ/mnt/user/appdata/deconz Docker logs shows in RED [deconzcommunity/deconz] Using options .......... --http-port=808 --ws-port=4434 Same happens if using the custom network to br0. Even if I leave the standard configurations the red line is still showed in the docker logs. What am I doing wrong? Unless there is some copy paste error the last line looks strange: 192.168.1.2:80/TCP192.168.1.2:80/opt/deCONZ/mnt/user/appdata/deconz I have tested again HOST mode for the docker and it does work, the only problem is that if you try to open the WebUI from unRAID it will try to open it on port 80 since it is hardcoded in the template, I will check if it is possible to fix it. If you open the WebUI using the port you set it should work. The RED line shows the correct ports that are used, I have moved 80 to 9080 and I can access the WebUI on my server like this: http://server_ip:9080 Can you share a screenshot of your settings? Can you share the output of the following in a terminal: sof -i -P -n | grep deCONZ Quote Link to comment
Mik3 Posted September 19, 2022 Share Posted September 19, 2022 Sorry for the late reply I was busy at work. I tried to setup again using the host mode and changing the port to something else. Maybe he doesn't like 808 XD. Anyway now looks like it's working. I'll do more tests and if anything strange comes up I'll report back. On 9/17/2022 at 9:22 PM, thecode said: I have tested again HOST mode for the docker and it does work, the only problem is that if you try to open the WebUI from unRAID it will try to open it on port 80 since it is hardcoded in the template, I will check if it is possible to fix it. To solve this just change the view from basic to advanced and modify the value "WebUI: http://[IP]:[PORT:80]/". Change 80 to the port you use..in your example 9080. Thanks again for your time and help. Have a nice day! 1 Quote Link to comment
HansPeter Posted October 16, 2022 Share Posted October 16, 2022 Hi, first of all I'd like to thank you for your work! Unfortunatly I fail to run the network type host. I changed the ports as follows: After saving it looks like this: LogFile: The Web UI doesn't work. Do you have any idea? Greetings, HansPeter Quote Link to comment
thecode Posted October 16, 2022 Author Share Posted October 16, 2022 1 hour ago, HansPeter said: Hi, first of all I'd like to thank you for your work! Unfortunatly I fail to run the network type host. I changed the ports as follows: After saving it looks like this: LogFile: The Web UI doesn't work. Do you have any idea? Greetings, HansPeter This usually happens if there is another app using this port. Can you try to change to a different port and check? what else do you see in the log? I have just tested using host network with port 9080 without issues on my test server. Quote Link to comment
JonathanM Posted October 17, 2022 Share Posted October 17, 2022 23 hours ago, HansPeter said: The Web UI doesn't work. Do you have any idea? Where is the mapping for 9080? 23 hours ago, HansPeter said: After saving it looks like this: Quote Link to comment
Cupra-Bo Posted October 26, 2022 Share Posted October 26, 2022 Hi, I just wanted to update Deconz and came up with this version... Unfortunately nothing can be clicked in the web gui in the Gateway tab or the stick is not recognized either. Here are some pictures and the log stat: cannot statx '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxx22-if00:/dev/ttyACM0': No such file or directory stat: cannot statx '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxx22-if00:/dev/ttyACM0': No such file or directory QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-deconz' libpng warning: iCCP: known incorrect sRGB profile This plugin does not support propagateSizeHints() This plugin does not support propagateSizeHints() [deconzcommunity/deconz] Starting deCONZ... [deconzcommunity/deconz] Current deCONZ version: 2.19.01 [deconzcommunity/deconz] Web UI port: 80 [deconzcommunity/deconz] Websockets port: 443 [deconzcommunity/deconz] Using options --auto-connect=1 --appdata=/opt/deCONZ --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-ddf=0 --dbg-dev=0 --dbg-zdp=0 --dbg-ota=0 --dbg-error=0 --dbg-http=0 --http-port=80 --ws-port=443 [deconzcommunity/deconz] Modifying user and group ID [deconzcommunity/deconz] Checking device group ID [deconzcommunity/deconz] VNC Disabled 16:43:47:808 HTTP Server listen on address 0.0.0.0, port: 80, root: /usr/share/deCONZ/webapp/ 16:43:47:822 /opt/deCONZ/config.ini exists and is writeable 16:43:47:823 /opt/deCONZ/zll.db exists and is writeable 16:43:47:838 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxx2-if00:/dev/ttyACM0 16:43:47:867 ZCLDB init file /opt/deCONZ/zcldb.txt 16:43:47:929 DDF enabled for Gold status 16:43:48:012 gw run mode: docker 16:43:48:012 GW sd-card image version file does not exist: /opt/deCONZ/gw-version 16:43:48:013 DB sqlite version 3.34.1 16:43:48:013 DB PRAGMA page_count: 50 16:43:48:013 DB PRAGMA page_size: 4096 16:43:48:013 DB PRAGMA freelist_count: 0 16:43:48:013 DB file size 204800 bytes, free pages 0 16:43:48:014 DB PRAGMA user_version: 9 16:43:48:014 DB cleanup 16:43:48:014 DB create temporary views 16:43:48:019 DB skip loading sensor BZ.Sensor.Temp 9, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor BZ.Sensor.Temp 8, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor BZ.Sensor.Temp 10, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor WZ.Sensor.Temp 12, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor WZ.Sensor.Temp 11, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor WZ.Sensor.Temp 13, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:021 Started websocket server on 0.0.0.0, port: 443 16:43:48:021 [INFO] - Found file containing button maps. Parsing data... 16:43:48:025 [INFO] - Button maps loaded. 16:43:48:026 found node plugin: libde_rest_plugin.so - REST API Plugin 16:43:48:027 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin 16:43:48:031 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin 16:43:48:044 LightNode 1: Configuration tool 1 added 16:43:48:064 LightNode 3: On/Off light 3 added 16:43:48:065 SensorNode 15 set node 0x00158d000276e4c7 16:43:48:066 SensorNode 7 set node 0x00158d000279579c 16:43:48:068 SensorNode 5 set node 0x00158d00045cf0c5 16:43:48:069 SensorNode 18 set node 0x00158d000271b763 16:43:48:069 SensorNode 17 set node 0xccccccfffef01e72 16:43:48:071 LightNode 2: Deko Standlampe added 16:43:48:072 SensorNode 6 set node 0x00158d0002770cc5 16:43:48:073 SensorNode 14 set node 0x00158d000276c14a 16:43:48:080 DEV no DDF for 0xCCCCCCFFFEF01E72, modelId: TRADFRI on/off switch 16:43:48:080 DEV create on-the-fly DDF for 0xCCCCCCFFFEF01E72 16:43:48:080 DEV no DDF for 0x00158D00045CF0C5, modelId: lumi.sensor_motion 16:43:48:080 DEV create on-the-fly DDF for 0x00158D00045CF0C5 16:43:48:080 DEV no DDF for 0x00158D0002770CC5, modelId: lumi.sensor_magnet.aq2 16:43:48:080 DEV create on-the-fly DDF for 0x00158D0002770CC5 16:43:48:080 DEV no DDF for 0x00158D000279579C, modelId: lumi.sensor_wleak.aq1 16:43:48:080 DEV create on-the-fly DDF for 0x00158D000279579C 16:43:48:080 DEV found DDF for 0x00158D000271B763, path: 16:43:48:080 DEV found DDF for 0x00158D000276C14A, path: 16:43:48:080 DEV found DDF for 0x00158D000276E4C7, path: 16:43:48:085 DEV found DDF for 0x00158D00027724CA, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq11lm_temp_hum_press_sensor.json 16:43:48:085 DEV no DDF for 0xEC1BBDFFFEA04F5E, modelId: TRADFRI bulb E27 WW 806lm 16:43:48:085 DEV create on-the-fly DDF for 0xEC1BBDFFFEA04F5E 16:43:48:090 DEV found DDF for 0x00158D0002739BE2, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq11lm_temp_hum_press_sensor.json 16:43:48:095 dlg action: Read binding table 16:43:50:019 New websocket 192.168.177.107:48320 (state: 3) 16:43:51:586 New websocket 192.168.177.3:61097 (state: 3) 16:43:52:867 Announced to internet https://phoscon.de/discover 16:43:52:867 discovery updated announce interval to 45 minutes 16:43:54:888 New websocket 192.168.177.3:61108 (state: 3) 16:43:55:621 DEV Tick.Init: booted after 8000 seconds 16:44:08:113 start reconnect to network 16:44:10:222 Websocket disconnected 192.168.177.3:61097, state: 0, close-code: 1001, reason: 16:44:13:364 failed to reconnect to network try=1 16:44:15:013 created username: 5159C37F23, devicetype: Phoscon#B2560x1218 16:44:16:166 New websocket 192.168.177.3:61123 (state: 3) 16:44:16:917 New websocket 192.168.177.13:35608 (state: 3) 16:44:18:090 Websocket disconnected 192.168.177.3:61123, state: 0, close-code: 1001, reason: 16:44:18:614 failed to reconnect to network try=2 16:44:19:168 New websocket 192.168.177.3:61125 (state: 3) 16:44:19:358 Websocket disconnected 192.168.177.3:61125, state: 0, close-code: 1001, reason: 16:44:20:502 New websocket 192.168.177.3:61129 (state: 3) 16:44:23:613 failed to reconnect to network try=3 16:44:28:614 failed to reconnect to network try=4 16:44:33:614 failed to reconnect to network try=5 16:44:38:613 failed to reconnect to network try=6 16:44:43:613 failed to reconnect to network try=7 16:44:48:614 failed to reconnect to network try=8 16:44:53:614 failed to reconnect to network try=9 16:44:58:614 failed to reconnect to network try=10 16:45:03:613 reconnect network failed, try later 16:45:04:140 start reconnect to network 16:45:09:390 failed to reconnect to network try=1 16:45:14:613 failed to reconnect to network try=2 16:45:16:918 Remove websocket 192.168.177.13:35608 after error Unknown error, close-code: 1000, reason: 16:45:16:919 New websocket 192.168.177.13:58800 (state: 3) 16:45:19:613 failed to reconnect to network try=3 16:45:24:614 failed to reconnect to network try=4 16:45:29:613 failed to reconnect to network try=5 16:45:34:614 failed to reconnect to network try=6 16:45:39:614 failed to reconnect to network try=7 16:45:44:614 failed to reconnect to network try=8 16:45:49:614 failed to reconnect to network try=9 16:45:54:614 failed to reconnect to network try=10 16:45:59:613 reconnect network failed, try later 16:46:00:141 start reconnect to network 16:46:05:392 failed to reconnect to network try=1 16:46:10:614 failed to reconnect to network try=2 16:46:15:614 failed to reconnect to network try=3 16:46:16:920 Remove websocket 192.168.177.13:58800 after error Unknown error, close-code: 1000, reason: 16:46:16:921 New websocket 192.168.177.13:49958 (state: 3) 16:46:20:614 failed to reconnect to network try=4 16:46:25:614 failed to reconnect to network try=5 Think something doesn't fit from the mount point here My mount point on Conbee USB Port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxx22-if00:/dev/ttyACM0 and on deCONZ Device: same Quote Link to comment
thecode Posted October 26, 2022 Author Share Posted October 26, 2022 1 hour ago, Cupra-Bo said: Hi, I just wanted to update Deconz and came up with this version... Unfortunately nothing can be clicked in the web gui in the Gateway tab or the stick is not recognized either. Here are some pictures and the log stat: cannot statx '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxx22-if00:/dev/ttyACM0': No such file or directory stat: cannot statx '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxx22-if00:/dev/ttyACM0': No such file or directory QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-deconz' libpng warning: iCCP: known incorrect sRGB profile This plugin does not support propagateSizeHints() This plugin does not support propagateSizeHints() [deconzcommunity/deconz] Starting deCONZ... [deconzcommunity/deconz] Current deCONZ version: 2.19.01 [deconzcommunity/deconz] Web UI port: 80 [deconzcommunity/deconz] Websockets port: 443 [deconzcommunity/deconz] Using options --auto-connect=1 --appdata=/opt/deCONZ --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-ddf=0 --dbg-dev=0 --dbg-zdp=0 --dbg-ota=0 --dbg-error=0 --dbg-http=0 --http-port=80 --ws-port=443 [deconzcommunity/deconz] Modifying user and group ID [deconzcommunity/deconz] Checking device group ID [deconzcommunity/deconz] VNC Disabled 16:43:47:808 HTTP Server listen on address 0.0.0.0, port: 80, root: /usr/share/deCONZ/webapp/ 16:43:47:822 /opt/deCONZ/config.ini exists and is writeable 16:43:47:823 /opt/deCONZ/zll.db exists and is writeable 16:43:47:838 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxx2-if00:/dev/ttyACM0 16:43:47:867 ZCLDB init file /opt/deCONZ/zcldb.txt 16:43:47:929 DDF enabled for Gold status 16:43:48:012 gw run mode: docker 16:43:48:012 GW sd-card image version file does not exist: /opt/deCONZ/gw-version 16:43:48:013 DB sqlite version 3.34.1 16:43:48:013 DB PRAGMA page_count: 50 16:43:48:013 DB PRAGMA page_size: 4096 16:43:48:013 DB PRAGMA freelist_count: 0 16:43:48:013 DB file size 204800 bytes, free pages 0 16:43:48:014 DB PRAGMA user_version: 9 16:43:48:014 DB cleanup 16:43:48:014 DB create temporary views 16:43:48:019 DB skip loading sensor BZ.Sensor.Temp 9, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor BZ.Sensor.Temp 8, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor BZ.Sensor.Temp 10, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor WZ.Sensor.Temp 12, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor WZ.Sensor.Temp 11, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:019 DB skip loading sensor WZ.Sensor.Temp 13, handled by DDF Aqara temp./hum./press. sensor WSDCGQ11LM 16:43:48:021 Started websocket server on 0.0.0.0, port: 443 16:43:48:021 [INFO] - Found file containing button maps. Parsing data... 16:43:48:025 [INFO] - Button maps loaded. 16:43:48:026 found node plugin: libde_rest_plugin.so - REST API Plugin 16:43:48:027 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin 16:43:48:031 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin 16:43:48:044 LightNode 1: Configuration tool 1 added 16:43:48:064 LightNode 3: On/Off light 3 added 16:43:48:065 SensorNode 15 set node 0x00158d000276e4c7 16:43:48:066 SensorNode 7 set node 0x00158d000279579c 16:43:48:068 SensorNode 5 set node 0x00158d00045cf0c5 16:43:48:069 SensorNode 18 set node 0x00158d000271b763 16:43:48:069 SensorNode 17 set node 0xccccccfffef01e72 16:43:48:071 LightNode 2: Deko Standlampe added 16:43:48:072 SensorNode 6 set node 0x00158d0002770cc5 16:43:48:073 SensorNode 14 set node 0x00158d000276c14a 16:43:48:080 DEV no DDF for 0xCCCCCCFFFEF01E72, modelId: TRADFRI on/off switch 16:43:48:080 DEV create on-the-fly DDF for 0xCCCCCCFFFEF01E72 16:43:48:080 DEV no DDF for 0x00158D00045CF0C5, modelId: lumi.sensor_motion 16:43:48:080 DEV create on-the-fly DDF for 0x00158D00045CF0C5 16:43:48:080 DEV no DDF for 0x00158D0002770CC5, modelId: lumi.sensor_magnet.aq2 16:43:48:080 DEV create on-the-fly DDF for 0x00158D0002770CC5 16:43:48:080 DEV no DDF for 0x00158D000279579C, modelId: lumi.sensor_wleak.aq1 16:43:48:080 DEV create on-the-fly DDF for 0x00158D000279579C 16:43:48:080 DEV found DDF for 0x00158D000271B763, path: 16:43:48:080 DEV found DDF for 0x00158D000276C14A, path: 16:43:48:080 DEV found DDF for 0x00158D000276E4C7, path: 16:43:48:085 DEV found DDF for 0x00158D00027724CA, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq11lm_temp_hum_press_sensor.json 16:43:48:085 DEV no DDF for 0xEC1BBDFFFEA04F5E, modelId: TRADFRI bulb E27 WW 806lm 16:43:48:085 DEV create on-the-fly DDF for 0xEC1BBDFFFEA04F5E 16:43:48:090 DEV found DDF for 0x00158D0002739BE2, path: /usr/share/deCONZ/devices/xiaomi/xiaomi_wsdcgq11lm_temp_hum_press_sensor.json 16:43:48:095 dlg action: Read binding table 16:43:50:019 New websocket 192.168.177.107:48320 (state: 3) 16:43:51:586 New websocket 192.168.177.3:61097 (state: 3) 16:43:52:867 Announced to internet https://phoscon.de/discover 16:43:52:867 discovery updated announce interval to 45 minutes 16:43:54:888 New websocket 192.168.177.3:61108 (state: 3) 16:43:55:621 DEV Tick.Init: booted after 8000 seconds 16:44:08:113 start reconnect to network 16:44:10:222 Websocket disconnected 192.168.177.3:61097, state: 0, close-code: 1001, reason: 16:44:13:364 failed to reconnect to network try=1 16:44:15:013 created username: 5159C37F23, devicetype: Phoscon#B2560x1218 16:44:16:166 New websocket 192.168.177.3:61123 (state: 3) 16:44:16:917 New websocket 192.168.177.13:35608 (state: 3) 16:44:18:090 Websocket disconnected 192.168.177.3:61123, state: 0, close-code: 1001, reason: 16:44:18:614 failed to reconnect to network try=2 16:44:19:168 New websocket 192.168.177.3:61125 (state: 3) 16:44:19:358 Websocket disconnected 192.168.177.3:61125, state: 0, close-code: 1001, reason: 16:44:20:502 New websocket 192.168.177.3:61129 (state: 3) 16:44:23:613 failed to reconnect to network try=3 16:44:28:614 failed to reconnect to network try=4 16:44:33:614 failed to reconnect to network try=5 16:44:38:613 failed to reconnect to network try=6 16:44:43:613 failed to reconnect to network try=7 16:44:48:614 failed to reconnect to network try=8 16:44:53:614 failed to reconnect to network try=9 16:44:58:614 failed to reconnect to network try=10 16:45:03:613 reconnect network failed, try later 16:45:04:140 start reconnect to network 16:45:09:390 failed to reconnect to network try=1 16:45:14:613 failed to reconnect to network try=2 16:45:16:918 Remove websocket 192.168.177.13:35608 after error Unknown error, close-code: 1000, reason: 16:45:16:919 New websocket 192.168.177.13:58800 (state: 3) 16:45:19:613 failed to reconnect to network try=3 16:45:24:614 failed to reconnect to network try=4 16:45:29:613 failed to reconnect to network try=5 16:45:34:614 failed to reconnect to network try=6 16:45:39:614 failed to reconnect to network try=7 16:45:44:614 failed to reconnect to network try=8 16:45:49:614 failed to reconnect to network try=9 16:45:54:614 failed to reconnect to network try=10 16:45:59:613 reconnect network failed, try later 16:46:00:141 start reconnect to network 16:46:05:392 failed to reconnect to network try=1 16:46:10:614 failed to reconnect to network try=2 16:46:15:614 failed to reconnect to network try=3 16:46:16:920 Remove websocket 192.168.177.13:58800 after error Unknown error, close-code: 1000, reason: 16:46:16:921 New websocket 192.168.177.13:49958 (state: 3) 16:46:20:614 failed to reconnect to network try=4 16:46:25:614 failed to reconnect to network try=5 Think something doesn't fit from the mount point here My mount point on Conbee USB Port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxx22-if00:/dev/ttyACM0 and on deCONZ Device: same The USB port is correct, however you need to keep the deCONZ device with /dev/ttyACM0 Quote Link to comment
Cupra-Bo Posted October 26, 2022 Share Posted October 26, 2022 okay Sensors etc react but on the web interface the buttons are not clickable when they are not working and I still have an error in red in the log [deconzcommunity/deconz] Using options --auto-connect=1 --appdata=/opt/deCONZ --dbg-info=1 --dbg-aps=0 --dbg-zcl=0 --dbg-ddf=0 --dbg-dev=0 --dbg-zdp=0 --dbg-ota=0 --dbg-error=0 --dbg-http=0 --http-port=80 --ws-port=443 Quote Link to comment
thecode Posted October 26, 2022 Author Share Posted October 26, 2022 That is not an error, it is just printed in red 🤷♂️ About the UI this happens when switching from older version to a newer version, it should be resolved by clearing the browser cache. If you use Chrome, press F12, right click the reload button and select "Empty Cache and Hard Reload" 1 Quote Link to comment
ub.privat Posted December 13, 2022 Share Posted December 13, 2022 the docker is running fine after installation. Installation method: sudo docker run -d \ --name=deconzgateway \ --net=host \ --restart=always \ -v /volume1/docker/deconz:/opt/deCONZ \ --device=/dev/ttyACM0 \ -e DECONZ_UID=0 \ -e DECONZ_GID=0 \ -e DECONZ_WEB_PORT=8085 \ -e DECONZ_WS_PORT=443 \ deconzcommunity/deconz:stable Now I want to set the DECONZ_VNC_MODE =1 afterwards. I try this in the settings of the container. This fails and Docker tries to restart all the time. Where should I look for the error? Quote Link to comment
thecode Posted December 14, 2022 Author Share Posted December 14, 2022 18 hours ago, ub.privat said: the docker is running fine after installation. Installation method: sudo docker run -d \ --name=deconzgateway \ --net=host \ --restart=always \ -v /volume1/docker/deconz:/opt/deCONZ \ --device=/dev/ttyACM0 \ -e DECONZ_UID=0 \ -e DECONZ_GID=0 \ -e DECONZ_WEB_PORT=8085 \ -e DECONZ_WS_PORT=443 \ deconzcommunity/deconz:stable Now I want to set the DECONZ_VNC_MODE =1 afterwards. I try this in the settings of the container. This fails and Docker tries to restart all the time. Where should I look for the error? This is a support thread for the community app docker template, it doesn't look like you are using the template, the default options in the template has VNC mode already set, please first try it, otherwise try to ask for support in the https://github.com/deconz-community/deconz-docker repo Quote Link to comment
c4coer Posted December 30, 2022 Share Posted December 30, 2022 (edited) hello I'm trying to switch from marthoc/deconz docker. (amd64 2.10.04) with a conbee2 dongle with firmware 26720700, but in fact recognizes it as an unknown hub, and when I connect to the dongle, I don't see its firmware, can you help me? FYI I tested several versions of the new docker nothing to do, I had to reactivate the old one. for info when I connect to the key it asks me for the password again, like when it is blank, I tried your version 2.12.06, I can see the firmware and my devices, but I can't control anything because in the logs appear errors I attach the logs and a screenshot, thanks you and happy new year deconzcommunity-deconz2.html Edited December 30, 2022 by c4coer Quote Link to comment
c4coer Posted December 31, 2022 Share Posted December 31, 2022 i have a solution, i had need driver (section 7 and 8 for me): https://mariushosting.com/synology-how-to-add-usb-support-on-dsm-7/ it run, key conbee2 has firmware connect. lixee (zlinky tic) is connect to deconz, but i no see inside domoticz Quote Link to comment
thecode Posted December 31, 2022 Author Share Posted December 31, 2022 1 hour ago, c4coer said: i have a solution, i had need driver (section 7 and 8 for me): https://mariushosting.com/synology-how-to-add-usb-support-on-dsm-7/ it run, key conbee2 has firmware connect. lixee (zlinky tic) is connect to deconz, but i no see inside domoticz Thanks for updating back, I use Home Assistant but if you can reach the Phoscon UI the docker is working. I would try getting help in Domoticz forums Quote Link to comment
RezzZ Posted January 31 Share Posted January 31 (edited) trying to get deconz to work but when using my custom network bridge I don't get an IP or ports assigned in unraid, and I can't access th gui/novpn. when trying host mode I still see port 80 being assigned while I setup deconz to use a different port via the Web Port variable. Any thoughts? Deconz seems to have started when I check the logs but I can't get access. edit: I used to run deconz in docker on a raspberry pi but wanted to migrate as my Pi keeps crashing due to recent added devices in deconz... edit2: changed it back to bridge mode and added 3 port forwards, 80->185 443->1445 6080->6080 novnc is now accessible, webui / phoscon is still not available Edited January 31 by RezzZ Quote Link to comment
Coxeroni Posted February 25 Share Posted February 25 Is anybody else also having issues with updating deconz recently? The Unraid docker update check is giving me a version "not available" lately and I don't seem to be able to fix this. Help is appreaciated. Quote Link to comment
SimonF Posted February 25 Share Posted February 25 13 minutes ago, Coxeroni said: Is anybody else also having issues with updating deconz recently? The Unraid docker update check is giving me a version "not available" lately and I don't seem to be able to fix this. Help is appreaciated. Have you installed Quote Link to comment
Ancan Posted February 26 Share Posted February 26 Hi all, After swapping my cache-drive for a larger one, I did reinstall of the Deconz container from "old apps" and restored appdata-folder from my backup. After this I've lost control over all my zigbee devices. Checking the logs there's lots of "error ASSPDE-DATA.confirm: 0xE1 on task". I've also noted that in the container, "DECONZ_DEVICE" is set to "0", but in the config screen it says "set same as device", which for me is /dev/ttyACM0. Is this expected? It seems to find the USB-device, because it confirms that the firmware is up to date. Quote Link to comment
Coxeroni Posted February 26 Share Posted February 26 On 2/25/2023 at 9:56 AM, SimonF said: Have you installed Indeed I have not. Sir you are great, as is this community as usual. Installed the patch and now I can update my container again. Cheers! 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.