deCONZ - Official thread

myle · June 6, 2020, 6:32am

Did try changing the USB port

xbmcnut · June 6, 2020, 7:01am

Restart HA

Matt_Barnes · June 6, 2020, 7:10am

It’s connected via the serial pins

meremortal · June 6, 2020, 9:06am

Sorry let me be more specific. They appear in the Integration in HA but not in the Phoscon/GUI add in. When this happens the names I set in HA Integration are not persistent. Everytime Deconz is restarted the names reset. Unless the names are changed in the GUI add in the names are not changed in Deconz

xbmcnut · June 6, 2020, 10:49am

What device is it? Some don’t show in the Phoscon GUI in HA like the Xiaomi smoke detectors. If you add a device using Phoscon, the name you give it will become the name of the entity in HA too but not the entity ID. That will be some random ID you ideally have to change. These changing should stick after a restart.

xbmcnut · June 8, 2020, 1:02am

How to get deCONZ working again after a reboot or supervisor upgrade.
_{*This is based on my experience with a Conbee II connected to a USB port on an Intel NUC}

Check if add-on is running
If stopped, adjust config to other port (say to /dev/ttyACM0 from /dev/ttyACM1 ) and restart add-on. Note that your port may differ.
Check the deCONZ logs to see if your Zigbee device was detected but note that even though the logs may report that it has found your hardware, this is no guarantee that deCONZ is running and you may need to try another port to get the next step working.
Check deCONZ in sidebar and go to ‘Gateway’ and make sure is does not say “Not Connected”. If it does, switch the port back and restart add-on again (yes I know, that sounds silly)
Check deCONZ > Gateway and ensure it’s reporting the firmware version and that under ‘Advanced’ you have a channel assigned.
in deCONZ, check lights, sensor and switches. Note that some sensors and switches may not immediately appear until they have ‘checked-in’ again.
There is a chance that your Zigbee devices are still not controllable in HA even though they are in deCONZ.
Restart HA to complete the process.
Store this guide somewhere safe as you’re going to need it a lot!

N.B The device by ID serial port (/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_xxxxx) has not worked for me for some time so this is why you have to jump through hoops when your hardware reboots as the ports /dev/ttyACMx are randomly assigned on boot.

meremortal · June 8, 2020, 8:32am

Thanks for the advice, I have been using the Deconz add I for 12 months. These are not the issues, if they were no Zigbee devices would be working

Robban · June 8, 2020, 9:05am

You can use the refresh device service as an alternative to restart hass at the end

xbmcnut · June 8, 2020, 9:40am

Thanks for the tip.

meremortal · June 8, 2020, 10:00am

Yes I have setup an automation to refresh devices so I go and execute that when I need to

bernhard · June 8, 2020, 10:21am

Would you care sharing that? Sounds useful. Thanks!

WhistleMaster · June 8, 2020, 11:06am

Try the following on the wiki. Sometimes, the network configuration changes between updates.

meremortal · June 8, 2020, 11:17am

Matt_Barnes · June 8, 2020, 3:56pm

Just trying this now but still does not seem to work.

I notice in the logs even though its a clean install of deconz and I have added /dev/ttyS0 in my config that its still mentioning /dev/ttyAMA0 each time its retrying?

capstan1 · June 8, 2020, 4:25pm

Then probably it didn’t apply the change. Try to restart the add-on. Also you can check for possible ports in the hardware page under the supervisor page. Maybe you got another one than ttyS0

kurniawan77 · June 11, 2020, 9:53am

That did the trick except for the groups. After rebooting ha it all came back

sender · June 13, 2020, 5:01pm

I have this very strange behaviour… I run hass core in an esxi with usb passthrough to usb conbee2. It works very well!

But… if I reboot complete hassos I cannot start container (addon). I can only do that if I first physically unplug usb stick, place back and start addon. That always works…

But this is not desirable e.g. when I am away from home and need to reboot hassos remote (rarely though but…).

Any tips?

patfelst · June 13, 2020, 10:03pm

I got a chance to try the Stitchy zigbee modules out yesterday, and you guys were right, they just worked out of the box. A switch and a dimmer. Little report and photos on this thread.

sender · June 15, 2020, 10:08pm

Sorry, I really needs some tip on this. Today I had a power outage. All came up fine but deconz not. Can’t start it remote. Have to physically take out and in usb stick then it works immediately.

s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
starting version 237
[23:56:44] INFO: Waiting for device…
[23:59:45] FATAL: No device /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2194613-if00 found!
[cmd] /run.sh exited 1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal

juhaa · June 16, 2020, 7:58pm

After the update. deCONZ don’t work… What to try?
It was fine before the HA and deCONZ update for hassio RPi with Conbee II

deCONZ
Current version: 5.3.5

After the update what I’ve tried so far… few different firmware updates with Windows PC.

GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
\\.\COM3         | 0x1CF1 | 0x0030  | xxxxxxxxx  | ConBee II

..\deCONZ\bin>GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26580700.bin.GCF
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
deCONZ firmware version 264A0700
action: update firmware after 6822 ms
flashing 160930 bytes: |==============================|
verify: .
SUCCESS

\deCONZ\bin>GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26580700.bin.GCF
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
deCONZ firmware version 26580700
action: update firmware after 6761 ms
flashing 160930 bytes: |==============================|
verify: .
SUCCESS

\deCONZ\bin>GCFFlasher -d COM3 -t 60 -f ../firmware/deCONZ_ConBeeII_0x26490700.bin.GCF
GCFFlasher V3_05 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
deCONZ firmware version 26580700
action: update firmware after 6823 ms
flashing 158985 bytes: |==============================|
verify: .
SUCCESS

22:59:59:531 wait reconnect 10 seconds
22:59:59:582 dev /dev/ttyAMA0
23:00:00:531 wait reconnect 9 seconds
23:00:01:531 wait reconnect 8 seconds
23:00:02:531 failed to reconnect to network try=8
23:00:02:531 wait reconnect 7 seconds
23:00:03:531 wait reconnect 6 seconds
23:00:04:531 wait reconnect 5 seconds
23:00:05:532 wait reconnect 4 seconds
23:00:06:531 wait reconnect 3 seconds
23:00:07:531 failed to reconnect to network try=9
23:00:07:531 wait reconnect 2 seconds
23:00:08:531 wait reconnect 1 seconds
23:00:08:580 dev /dev/ttyAMA0
23:00:08:580 COM: /dev/ttyAMA0 / serialno: 
23:00:08:580 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:08:659 device disconnected reason: 4, index: 0
23:00:09:531 wait reconnect 15 seconds
23:00:09:578 dev /dev/ttyAMA0
23:00:09:578 COM: /dev/ttyAMA0 / serialno: 
23:00:09:578 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:09:615 dev /dev/ttyAMA0
23:00:10:531 wait reconnect 14 seconds
23:00:11:531 wait reconnect 13 seconds
23:00:12:531 failed to reconnect to network try=10
23:00:12:531 wait reconnect 12 seconds
23:00:13:531 wait reconnect 11 seconds
23:00:14:531 wait reconnect 10 seconds
23:00:15:532 wait reconnect 9 seconds
23:00:16:531 wait reconnect 8 seconds
23:00:17:531 reconnect network failed, try later
23:00:17:531 wait reconnect 7 seconds
23:00:18:031 start reconnect to network
23:00:18:531 wait reconnect 6 seconds
23:00:19:531 wait reconnect 5 seconds
23:00:19:575 dev /dev/ttyAMA0
23:00:20:531 wait reconnect 4 seconds
23:00:21:531 wait reconnect 3 seconds
23:00:22:531 wait reconnect 2 seconds
23:00:23:282 failed to reconnect to network try=1
23:00:23:531 wait reconnect 1 seconds
23:00:23:576 dev /dev/ttyAMA0
23:00:23:576 COM: /dev/ttyAMA0 / serialno: 
23:00:23:576 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:23:622 device disconnected reason: 4, index: 0
23:00:24:530 wait reconnect 15 seconds
23:00:24:575 dev /dev/ttyAMA0
23:00:24:575 COM: /dev/ttyAMA0 / serialno: 
23:00:24:575 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:25:531 wait reconnect 14 seconds
23:00:26:530 wait reconnect 13 seconds
23:00:27:531 wait reconnect 12 seconds
23:00:28:531 failed to reconnect to network try=2
23:00:28:531 wait reconnect 11 seconds
23:00:29:531 wait reconnect 10 seconds
23:00:29:573 dev /dev/ttyAMA0
23:00:30:532 wait reconnect 9 seconds
23:00:31:531 wait reconnect 8 seconds
23:00:32:531 wait reconnect 7 seconds
23:00:33:530 failed to reconnect to network try=3
23:00:33:530 wait reconnect 6 seconds
23:00:34:530 wait reconnect 5 seconds
23:00:35:531 wait reconnect 4 seconds
23:00:36:531 wait reconnect 3 seconds
23:00:37:531 wait reconnect 2 seconds
23:00:38:531 failed to reconnect to network try=4
23:00:38:531 wait reconnect 1 seconds
23:00:38:576 dev /dev/ttyAMA0
23:00:38:576 COM: /dev/ttyAMA0 / serialno: 
23:00:38:576 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:38:598 device disconnected reason: 4, index: 0
23:00:39:531 wait reconnect 15 seconds
23:00:39:585 dev /dev/ttyAMA0
23:00:39:585 COM: /dev/ttyAMA0 / serialno: 
23:00:39:585 COM: --dev: /dev/ttyAMA0 (RaspBee)
23:00:39:622 dev /dev/ttyAMA0
23:00:40:531 wait reconnect 14 seconds
23:00:41:531 wait reconnect 13 seconds
23:00:42:531 wait reconnect 12 seconds
23:00:43:531 failed to reconnect to network try=5
23:00:43:531 wait reconnect 11 seconds
23:00:44:531 wait reconnect 10 seconds
23:00:45:531 wait reconnect 9 seconds
23:00:46:531 wait reconnect 8 seconds
23:00:47:531 wait reconnect 7 seconds
23:00:48:531 failed to reconnect to network try=6
23:00:48:531 wait reconnect 6 seconds
23:00:49:531 wait reconnect 5 seconds
23:00:49:580 dev /dev/ttyAMA0
23:00:50:531 wait reconnect 4 seconds
23:00:51:531 wait reconnect 3 seconds
23:00:52:531 wait rec172.30.32.2 - - [16/Jun/2020:23:00:54 +0300] "GET /api/E463615D64/config?_=1592337172836 HTTP/1.1" 200 2854 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0"
172.30.32.2 - - [16/Jun/2020:23:00:59 +0300] "GET /api/E463615D64/config?_=1592337172837 HTTP/1.1" 200 2854 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0"