deCONZ - Official thread

Rdoull · January 2, 2020, 7:07pm

Gonna get myself a powered adaptor and see if it works. I hadn’t given it a thought as I’m using a pi3+ and a 3a power supply, but it’s worth a shot thank you.

xAPPO · January 2, 2020, 8:51pm

Early IKEA Fyrtur blinds user. Initially only the down and stop button were enabled and worked and then following IKEA firmware update and HA /Deconz everything worked including real-time slider. But now I’m back to the down arrow, stop and the slider controls but does not update. Remote changes to blinds don’t update. My control is 100 dependable and instant though every time.

Tried restarts of HA and Deconz and reinstalled Deconz and re-paired blinds (have an Ikea repeater it connects via). Nothing changes. All latest versions.

How can I get all the UI buttons working and synched and tracking remote changes too ? As I had once a few versions ago.

ronnyandre · January 2, 2020, 9:29pm

Anyone experiencing issues with deCONZ (Phoscon)? I cannot read http://[IP]:40850/pwa/ to login to Phoscon anymore, however Hass.io has noe issues with communicating with deCONZ and controlling lights and sensors.

Dixey · January 2, 2020, 9:38pm

I’m on the latest and mine works when I just use http://[IP]:40850 and not the /pwa/ thing.

Robban · January 2, 2020, 9:46pm

I just added one of my Fyrtur blinds myself and AFAIK the I don’t get the websocket signalling updating the states of the blinds. It could be that the setup with deCONZ didn’t succeed to a 100% according to a discussion on deCONZ GitHub. Im investigating this.

Dixey · January 2, 2020, 9:52pm

Almost all of my weird Conbee 2 Zigbee stick issues disappeared when I stuck the stick on the end of a 3 meter USB extension cable. $5 and problem solved. I took the liberty of hanging the stick up on the wall also just to help with range issues.

I’m running HA on a PI3B+.

ronnyandre · January 3, 2020, 6:15am

@Dixey

I’m also at the latest. All addons updated, Hass.io is updated, HassOS is updated. When I try to reach http://[IP]:40850/ I get connection refused error.

If I try to reach http://phoscon.de/pwa/ it presents my gateway, but with an private IP of 172.30.33.XX and I am not able to log in with any password, as the browser console reports lots of 404 requests to 172.30.33.XX/api/config

Pirol62 · January 3, 2020, 9:02am

Hmmm…never did that before. I will try that

Burningstone · January 3, 2020, 9:05am

That would be great, it’s also a good learning experience in my opinion. Let me know in case you get stuck or need some assistance.

Rdoull · January 3, 2020, 5:26pm

Thank you Dixey,

I got an extention cable and connected it all up, still nothing worked so I uninstalled everything, reset the ConBee 2 and started from scratch… now it appears to all be working… time will tell if it stays that way though…

Thank you !

kurtj · January 3, 2020, 10:36pm

@ronnyandre

could you try this? I just found out after messing around in vnc

deconz-vnc

Open up vnc to your deconz
start the rest app plugin (plugins > rest

and while plugin active, try again to open the web interface?

Bergh2 · January 4, 2020, 9:12am

Thank you, I’ve tried that and even setup a completly new testing machine in docker without any luck. After some more googling on this topic I came to realize that the discovery will not work as the main HA is on a different subnet from the deconz-HA machine. However, this have not changed recently at it used to work before these updated. But since discovery will not work I guess I need to setup this manually? I’ve tried adding it straight to configuration.yaml file but that did not help.
deconz:
host: 192.168.x.x
port: 40850

Do anyone have any more ideas?

tosion · January 4, 2020, 10:48am

Hi there,

I have a little problem with Deconz I try to solve - not a big deal - but any help would be appreciated?

I have couple Deconz (Raspbee) systems running in RPI 3B+, HassIo, HassOS 3.7, HA 1.103.4, Deconz 5.0. I have been very pleased with these systems and I feel I can rely on them. In my systems I have nodes between 70-40.

Far away in my summer cabin I have that 40 nodes divided to 4 buildings and some sensors are outside also. Some nodes are located around 70 meters from the Coordinator (Raspbee). Now and then some nodes have dropped but mostly I have managed to recover remotely using “Reboot” from VNC

Now one Aqara motion sensor has started to act the way I do not exactly understand. The group below is located in my “Boathouse” and VV2Liike is the one which does not show in Phoscon/HA. On the other hand it looks to act live in the VNC mesh, just like VV1Liike, which acts normally also in Phoscon/HA?

Reeboot Device does not help? I do hesitate to reboot Hassos, just in case, system is far away and it is also taking care of some heating preventing water pipes and pumps to freeze.

I can easily live thru the winter without that sensor, but as a learning perspective all the ideas are very well come - how to wake it up remotely?

Boulder · January 4, 2020, 12:11pm

TL:DR All lights gone from Phoscon, no switches working, deCONZ seems normal. Wierd login behavior in Phoscon

Hi everyone! I’m quite new to most of this, so I hope you can have some patience with me (atleast some more than my girlfriend is having right now, having no functional switches).

My setup is a laptop running Ubuntu and Hassio. I started out using a hue bridge, but recently bought a ConBee II stick and set up the add-on.
I then migrated all devices from hue to phoscon:

Added all my lights: mostly Trådfri GU10.
Added all my switches: hue dimmer sticks, Niko Friends of Hue, Trådfri
Added all my sensors: hue motion, several aqara multi
I set up the groups and switch functionality I needed to mimick my hue-setup, and everything was working just fine.

Then suddenly at some point last night it all stopped working. No switches respond. Trying to log in to Phoscon now prompts me with a “new password” screen when clicking the GW-tile. Entering my current password produces a login error. A small “pairing” icon in the upper right of the GW-tile comes and goes (what is this?). It also seems as if the GW changes names for a microsecond sometimes, but reverts to quick to read.

If i keep trying (at random) to click the GW-tile after a while it suddely behaves normal and I’m able to log in.
When logged in the following is the situation:

All my lights are gone from Devices, but the groups are still in the main view
Sensors are still present under Devices, though not refreshed
The firmware info says “not connected”.

The deCONZ GUI desktop app looks “OK” to a total noob, it seems to be building a network, looking similar to before. Clicking random nodes, they all have quite recent “Last seen” values.

I have tried rebooting the computer, starting/stopping the addon and hassio.

ANY suggestions as to why everything is non responsive is GREATLY appreciated! My gf is “mildly” irritated at this point

Below is the log from a restart of deCONZ add-on, please inform me to what other information may be needed to understand this issue.

starting version 237

[12:51:00] INFO: Waiting for device...
[12:51:02] INFO: Starting the deCONZ gateway...
libpng warning: iCCP: known incorrect sRGB profile
12:51:02:337 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
12:51:02:351 CTRL. 3.22.012:51:02:400 COM: /dev/ttyACM1 / serialno: DE2131052
12:51:02:400 COM: --dev: /dev/ttyACM1 (ConBee II)
12:51:02:400 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
12:51:02:459 parent process bash
12:51:02:459 gw run mode: docker/hassio
12:51:02:459 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
12:51:02:459 DB sqlite version 3.22.0
12:51:02:460 DB PRAGMA page_count: 45
12:51:02:460 DB PRAGMA page_size: 4096
12:51:02:460 DB PRAGMA freelist_count: 1
12:51:02:460 DB file size 184320 bytes, free pages 1
12:51:02:460 DB PRAGMA user_version: 6
12:51:02:460 DB cleanup
12:51:02:460 DB create temporary views
12:51:02:471 don't close database yet, keep open for 900 seconds
12:51:02:471 started websocket server at port 8081
12:51:02:475 GW firmware update not supported on x86 linux headless
12:51:02:506 found node plugin: libde_rest_plugin.so - REST API Plugin
12:51:02:507 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
[12:51:02] INFO: Starting Nginx...
[12:51:02] INFO: Running Hass.io discovery task...
2020/01/04 12:51:02 [notice] 393#393: using the "epoll" event method
2020/01/04 12:51:02 [notice] 393#393: nginx/1.14.0 (Ubuntu)
2020/01/04 12:51:02 [notice] 393#393: OS: Linux 5.1.15-surface-linux-surface
2020/01/04 12:51:02 [notice] 393#393: getrlimit(RLIMIT_NOFILE): 1048576:1048576
2020/01/04 12:51:02 [notice] 393#393: start worker processes
2020/01/04 12:51:02 [notice] 393#393: start worker process 401
[12:51:02] INFO: Running the deCONZ OTA updater...
[12:51:02] INFO: Running the IKEA OTA updater...
[12:51:02] INFO: deCONZ is set up and running!
12:51:03:094 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
12:51:03:108 COM: /dev/ttyACM1 / serialno: DE2131052
12:51:03:108 COM: --dev: /dev/ttyACM1 (ConBee II)
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
12:51:03:424 wait reconnect 15 seconds
12:51:03:439 COM: /dev/ttyACM1 / serialno: DE2131052
12:51:03:439 COM: --dev: /dev/ttyACM1 (ConBee II)
12:51:04:470 wait reconnect 14 seconds
12:51:05:469 wait reconnect 13 seconds
12:51:06:469 wait reconnect 12 seconds
12:51:07:469 wait reconnect 11 seconds
12:51:08:113 Announced to internet https://phoscon.de/discover
12:51:08:468 wait reconnect 10 seconds
12:51:09:469 wait reconnect 9 seconds
12:51:10:468 wait reconnect 8 seconds
12:51:11:468 wait reconnect 7 seconds
12:51:12:468 wait reconnect 6 seconds
[12:51:12] INFO: Successfully send discovery information to Home Assistant.
12:51:13:468 wait reconnect 5 seconds
12:51:13:885 New websocket 172.30.32.1:52930 (state: 3) 
12:51:14:469 wait reconnect 4 seconds
12:51:15:469 wait reconnect 3 seconds

Changed USB port, to same as title line from deCONZ GUI, same issue:

14:32:00:181 wait reconnect 13 seconds
14:32:01:181 wait reconnect 12 seconds
14:32:02:181 failed to reconnect to network try=2
14:32:02:181 wait reconnect 11 seconds
172.30.32.2 - - [04/Jan/2020:14:32:02 +0100] "GET /api/23DCFEF171/sensors/new?_=1578143876531 HTTP/1.1" 200 34 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-sensors.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
14:32:03:181 wait reconnect 10 seconds
14:32:04:181 wait reconnect 9 seconds
14:32:04:670 Websocket disconnected 172.30.32.1:56712 (state: 0) 
172.30.32.2 - - [04/Jan/2020:14:32:04 +0100] "GET /pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C HTTP/1.1" 200 12662 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-sensors.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
172.30.32.2 - - [04/Jan/2020:14:32:04 +0100] "GET /pwa/developer.js HTTP/1.1" 404 142 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
172.30.32.2 - - [04/Jan/2020:14:32:04 +0100] "GET /api/23DCFEF171/config?_=1578144724786 HTTP/1.1" 200 2622 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
172.30.32.2 - - [04/Jan/2020:14:32:04 +0100] "GET /api/23DCFEF171/config?_=1578144724787 HTTP/1.1" 200 2622 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
172.30.32.2 - - [04/Jan/2020:14:32:04 +0100] "GET /api/23DCFEF171/lights?_=1578144724788 HTTP/1.1" 200 12 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
172.30.32.2 - - [04/Jan/2020:14:32:04 +0100] "GET /api/23DCFEF171/lights?_=1578144724789 HTTP/1.1" 200 12 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
14:32:05:181 wait reconnect 8 seconds
14:32:05:831 New websocket 172.30.32.1:33588 (state: 3) 
172.30.32.2 - - [04/Jan/2020:14:32:05 +0100] "GET /api/23DCFEF171/sensors/new HTTP/1.1" 200 34 "http://127.0.0.1:8123/api/hassio_ingress/SrcAnqCiAPgUDMxgwMFnSGfbbRUh8h_XkP1Iu-OIfRE/pwa/devices-lights.html?_v=bb47cdbc19c257e3000fdb8475aa456830e6df94,0,6,14&gwid=00212EFFFF04FF0C" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0"
14:32:06:181 wait reconnect 7 seconds
14:32:07:181 failed to reconnect to network try=3
14:32:07:181 wait reconnect 6 seconds
14:32:08:181 wait reconnect 5 seconds
14:32:09:181 wait reconnect 4 seconds
14:32:09:264 Websocket disconnected 172.30.32.1:33588 (state: 0) 
14:32:10:180 wait reconnect 3 seconds
14:32:11:181 wait reconnect 2 seconds
14:32:12:181 failed to reconnect to network try=4
14:32:12:181 wait reconnect 1 seconds
14:32:12:200 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:12:200 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:13:181 wait reconnect 15 seconds
14:32:13:212 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:13:212 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:14:181 wait reconnect 14 seconds
14:32:15:181 wait reconnect 13 seconds
14:32:16:181 wait reconnect 12 seconds
14:32:17:181 failed to reconnect to network try=5
14:32:17:181 wait reconnect 11 seconds
14:32:18:181 wait reconnect 10 seconds
14:32:19:181 wait reconnect 9 seconds
14:32:20:181 wait reconnect 8 seconds
14:32:21:181 wait reconnect 7 seconds
14:32:22:181 failed to reconnect to network try=6
14:32:22:181 wait reconnect 6 seconds
14:32:23:181 wait reconnect 5 seconds
14:32:24:181 wait reconnect 4 seconds
14:32:25:181 wait reconnect 3 seconds
14:32:26:181 wait reconnect 2 seconds
14:32:27:181 failed to reconnect to network try=7
14:32:27:181 wait reconnect 1 seconds
14:32:27:227 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:27:227 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:28:181 wait reconnect 15 seconds
14:32:28:201 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:28:201 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:29:181 wait reconnect 14 seconds
14:32:30:181 wait reconnect 13 seconds
14:32:31:181 wait reconnect 12 seconds
14:32:32:181 failed to reconnect to network try=8
14:32:32:181 wait reconnect 11 seconds
14:32:33:181 wait reconnect 10 seconds
14:32:34:181 wait reconnect 9 seconds
14:32:35:180 wait reconnect 8 seconds
14:32:36:181 wait reconnect 7 seconds
14:32:37:181 failed to reconnect to network try=9
14:32:37:182 wait reconnect 6 seconds
14:32:38:181 wait reconnect 5 seconds
14:32:39:181 wait reconnect 4 seconds
14:32:40:181 wait reconnect 3 seconds
14:32:41:181 wait reconnect 2 seconds
14:32:42:181 failed to reconnect to network try=10
14:32:42:181 wait reconnect 1 seconds
14:32:42:232 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:42:232 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:43:181 wait reconnect 15 seconds
14:32:43:220 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:43:220 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:44:181 wait reconnect 14 seconds
14:32:45:181 wait reconnect 13 seconds
14:32:46:181 wait reconnect 12 seconds
14:32:47:181 reconnect network failed, try later
14:32:47:181 wait reconnect 11 seconds
14:32:47:181 start reconnect to network
14:32:48:181 wait reconnect 10 seconds
14:32:49:181 wait reconnect 9 seconds
14:32:50:181 wait reconnect 8 seconds
14:32:51:181 wait reconnect 7 seconds
14:32:52:181 failed to reconnect to network try=1
14:32:52:182 wait reconnect 6 seconds
14:32:53:181 wait reconnect 5 seconds
14:32:54:181 wait reconnect 4 seconds
14:32:55:181 wait reconnect 3 seconds
14:32:56:181 wait reconnect 2 seconds
14:32:57:181 failed to reconnect to network try=2
14:32:57:181 wait reconnect 1 seconds
14:32:57:227 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:57:227 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:58:181 wait reconnect 15 seconds
14:32:58:234 COM: /dev/ttyACM0 / serialno: DE2131052
14:32:58:234 COM: --dev: /dev/ttyACM0 (ConBee II)
14:32:59:181 wait reconnect 14 seconds

CrocMonster · January 4, 2020, 7:14pm

A bit late maybee…are you running /boot of sd and have /root on ssd (as I have) then you get that problem with ssd in usb3 port on rpi4.
Ssd has to be moved to usb2 port then you get conbee II and not raspbee in settings/gateway and with firmware id in deconz add-on phoscon web app.
Jup, losing the ssd/usb3 speed but sd-cards are lousy harddrives which is the main reason for my setup. Waiting for real usb boot option for rpi4.

jdbrookes · January 6, 2020, 2:41pm

I’m currently on Home Assistant (hassio) 0.102.2 and running Deconz add-on 3.9

What is my upgrade path to minimise disruption? Update hassio or the addon first? Remove the integration and re-add? The posts here over Christmas have me wary!

I don’t mind a bit of troubleshooting but I want to absolutely minimise the risk of losing my deconz config, devices, entity names etc because I’ve something like 60 sensors and lights from xiaomi, hue, ikea

Thanks in advance

Pirol62 · January 6, 2020, 3:11pm

I’m absolutely in the same situation but on version 103.4 and 3.8.
Everything works so far and I cannot allow to loose my functionality.
My complete house illumination works via deconz and I don’t have enough time to reconfigure the complete system.
In addition I have the issue of ID00000000… which isn’t really a functional issue so far.

stigvi · January 7, 2020, 9:42am

I upgraded 2 days ago. First HA to 0.103.5 and then deConz to 5. Took me less than 3 minutes and everything worked as usual.

Philip_Embleton · January 7, 2020, 6:15pm

If you have HA snapshots and Phoscon backups then it’s highly unlikely you’ll find youreself in a position where you can’t recover your system.

jdbrookes · January 7, 2020, 8:25pm

Sounds promising, thanks.