Deconz - Please Help - RPI/Raspbee -> NUC/Conbee

Elcahon · May 8, 2020, 2:11pm

Zigbee configuration in deconz doesn’t seem to do much. But I did end up with two Phoscon integrations. With different number of devices and entities.

There are two lines with exactly the same info, just different Id’s.

In the login page for Phoscon I have two instances of Phoscon-GW. One is greyed out.

I guess this is what happens when I do something I don’t know about and should not do…

I do get some errors in the system log:

20-05-08 13:52:51 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-05-08 13:52:51 INFO (MainThread) [supervisor.addons] Phase 'application' start 0 add-ons
20-05-08 13:52:51 INFO (MainThread) [supervisor.tasks] All core tasks are scheduled
20-05-08 13:52:51 INFO (MainThread) [supervisor.hwmon] Started Supervisor hardware monitor
20-05-08 13:52:51 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-05-08 13:52:51 INFO (MainThread) [supervisor.host.info] Update local host information
20-05-08 13:52:51 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-05-08 13:52:51 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-05-08 13:52:51 INFO (MainThread) [supervisor.host.services] Update service information
20-05-08 13:52:51 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-05-08 13:52:52 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-05-08 13:52:52 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-05-08 13:52:52 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-05-08 13:53:04 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:04 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:04 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:04 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:08 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:08 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:08 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:08 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:10 WARNING (MainThread) [supervisor.api.ingress] Ingress for G_FJm4a_DqNXhpjTfSITAhPt6Ry6xTctGitdawvVlj4 not available
20-05-08 13:53:33 ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
20-05-08 13:54:32 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 13:54:42 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 13:54:52 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 13:55:02 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 13:55:12 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 13:55:35 INFO (SyncWorker_13) [supervisor.docker.interface] Stop addon_core_deconz application
20-05-08 13:55:36 INFO (SyncWorker_13) [supervisor.docker.interface] Clean addon_core_deconz application
20-05-08 13:55:38 INFO (SyncWorker_7) [supervisor.docker.addon] Start Docker add-on homeassistant/armhf-addon-deconz with version 5.3.2
20-05-08 13:55:50 INFO (MainThread) [supervisor.discovery] Send discovery to Home Assistant deconz from core_deconz
20-05-08 13:55:50 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-05-08 13:55:50 INFO (MainThread) [supervisor.discovery] Discovery a2255922bad94dc0b28b07f231c64a4f message send
20-05-08 13:55:54 ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
20-05-08 14:01:42 ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
20-05-08 14:04:35 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:04:45 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:04:55 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:05:05 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:05:15 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:05:25 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:05:34 ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
20-05-08 14:05:35 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:05:45 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:05:54 ERROR (MainThread) [supervisor.api.ingress] Ingress error: None
20-05-08 14:05:55 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:06:05 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket
20-05-08 14:06:06 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url='http://172.30.33.0:8099/websocket

tosion · May 8, 2020, 2:49pm

I think those two Phoscon GW:s are because in your LAN has been two different raspbees or conbees. When I had one additional conbee in win10 PC I also had one greyed GW. I think I was able to delete it or something from the Phoscon GUI …

I have understood that loading this configuration to second raspbee has to be done in same computer with the first raspbee and it should somehow make a clone of the first raspbee. But you should not keep the both raspbees powered after ( there is a conflict if you have two identical raspbees in same location)

Elcahon · May 8, 2020, 3:16pm

I think I tried the Raspbee in my existing Pi. But it shouldn’t matter, since it should be possible to move to a new Pi with a new Raspbee. My primary and secondary Pi are never powered at the same time, so there haven’t been any conflict there.

I tried my first (primary) Raspbee on the new Pi board, and that worked without any problems.

tosion · May 8, 2020, 6:21pm

Ok - thanks for this valuable information …

tosion · May 9, 2020, 7:04pm

Someone has succeeded - not with Home Assistant supervised & Deconz addon but still. Take a look of the last post of the thread. Looks promising.
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2749

Elcahon · May 10, 2020, 5:51pm

I’ve tried to change the MAC-address and different other settings (among others extended PAN ID) so they have exactly the same setting. This was done in the deCONS configuration program via VNC. No luck…

Interesting though, in the node map 2 entities are seen: configuration tool 1 and an on/off sensor. But some 20 other sensors/lights/switches are out of reach. Hmm…

This is moving from (RPi 4B, Raspbee II) to (RPi 4B, Raspbee II). The same hardware as you can see.

I’ve tried many of the solutions presented in different foras, but I still can’t figure out how to make myself a backup controller witch I can easily power up if the main one fails.

This is beyond my knowledge, and maybe I should give up for now, and try again later…

tosion · May 11, 2020, 11:20am

Sorry to hear you were not able to get it work.

The good news is that I was successful - so I can confirm you are able to clone the Raspbee/Conbee and make a remotely controlled backup system with Deconz.

Petter, I am not sure did I follow exactly what you did but I think that cloning with Phoscon GUI (Not Deconz GUI) is the key. Somehow I got the idea that you mostly adjusted things in Deconz GUI?

I did not do this with NUC yet (it is on the way) but I had an extra RPI3B+ and extra Conbee.

I created a backup in Phoscon in existing system
Shut down the host
Pulled Raspbee out
Installed Conbee
Power on
Changed the device address in deconz addon (device: /dev/ttyUSB0)
Loaded the backup in Phoscon
In hidden config loaded the last network configuration
Rebooted the host

I think at some point I had to manually change in Phoscon the zigbee channel to 25 (from 20 which the new Conbee had)

Now I was able to control existing system with new Conbee. So the Conbee was cloned with Raspbee data. I shut down the old system and installed the cloned Conbee to new RPI3B+. When old system was shut down I started the new and it worked perfectly; all my 66 nodes were there and worked.

Now I have a clone Conbee ready for my NUC when it arrives on Wednesday.

Another very interesting observation:

When running my existing system with Conbee instead of Raspbee the system temperature was around 10 C lower - quite a lot - that encourages using Conbee instead of Raspbee

Elcahon · May 12, 2020, 9:12am

Yes, I did the Phoscon route, but did not load the last network configuration at that stage. The deCONZ GUI (via VNC) I used later, trying to set similar MAC-address etc.

But thank you very much for your update here, I will try this today and report back.

BTW, I have to use /dev/ttyAMA0 on my Raspbee II.

Elcahon · May 12, 2020, 11:12am

Now it works !!!

Thank you tosion for keeping me trying

I did the Phoscon method again, and now it worked. I didn’t need to load my last network configuration in the hidden Phoscon menu. Maybe that has something to do with the settings I changed in the deCONZ (VNC) configuration tool previously. IDK.

Here is what I did:

Made a new installation SC card and powered up my secondary RPi
Installed deCONZ add-on
Restored the Phoscon Backup (backed up from my primary RPi)
Checked if deCONZ could control my lights. It could.
Installed Samba add-on
Put my last snapshot (from the primary RPi) to the “backup” folder.
Restored the snapshot (had to reboot to gain access to the snapshot)
Exception: I did not restore deCONZ from the snapshot (not Samba either)

I do not know why this worked now and not the last time I tried it. I guess I had a slight variation in the order of things, and that it was enough to break the system.

But at least I now have a functioning “manual failover system” I can get up and running in a matter of minutes with no configuring. Just plug and play.

tosion · May 12, 2020, 12:23pm

Petter,

Great to hear you got it working.

All the time we talk about the software backup - that’s important - but I have been worried about what happens when my deconz (or host) hardware breaks.

My plan is to use NUC7CJYH2 Celeron J4005 (109 € in Amazon.de) as a primary system and backup it with RPI3B+ (they sold them in local store 17 € a piece, I promise I have my share of those ). Both behind UPS and wifi smart plugs. Also one extra RPI3B+ with rasbian using VNC to have a local access.

I just have to be sure I have the latest snapshots and Phoscon backups - with these arrangements I have system I can leave for longer period (my summer cabin) knowing the system is pretty reliable …

Hey - Great we solved this!

tosion · May 13, 2020, 8:01pm

Short update - I got this the NUC this evening and I can confirm the new Conbee works also there. So now I have a working backup for the hardware also.

Elcahon · May 13, 2020, 8:15pm

Nice Backup is always good