search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.89k stars 496 forks source link

Restore raspbee backup in conbee #1300

Closed Wyphorn closed 5 years ago

Wyphorn commented 5 years ago

Hi, I switched from RaspBee to Conbee and tried to load my raspbee backup in conbee. But the startup routine loops with these logs: Feb 26 21:32:28 server systemd[1]: Started deCONZ: ZigBee gateway -- Initialisation. Feb 26 21:32:28 server systemd[1]: Started ACPI event daemon. Feb 26 21:32:28 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Feb 26 21:32:28 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Feb 26 21:32:28 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Feb 26 21:32:28 server systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation... Feb 26 21:32:28 server deCONZ[24643]: QXcbConnection: Could not connect to display Feb 26 21:32:28 server deCONZ-init.sh[24644]: cat: /sys/block/mmcblk0/device/cid: No such file or directory Feb 26 21:32:28 server deCONZ-init.sh[24644]: stopping deconz-wifi.service Feb 26 21:32:28 server systemd[1]: Stopped deCONZ: ZigBee gateway -- WIFI Service. Feb 26 21:32:28 server systemd[1]: Reloading.

Is there a nice way to migrate? My server where conbee is attached has no display. So it won't be connectable, but I thought to start the headless version. I have 30 hue devices, multiple sensors and remotes and all is connected to fhem with its names. I don't want to reset all, learn them to new network and set all up again..

Best

etique57 commented 5 years ago

I'm planning to do the exact same thing (sick of the fragility of the raspberry... moving to x86 proxmox) so I'm interested in the answer!

etique57 commented 5 years ago

Any idea or piece of advice?

manup commented 5 years ago

Is there a nice way to migrate?

The simplest way is to load the backup of the old installation (created in the Phoscon App).

However keep in mind that the RaspBee shouldn't be powered afterwards since two clones (via mac address) would fight over the network.

But the above log looks a bit like the ConBee/ deCONZ installation isn't working for some reason. What kind of system is this?

Wyphorn commented 5 years ago

This is an ubuntu debian 16.04 lts 64bit without x11 with deconz-2.05.59-qt5.deb and deCONZ_Rpi_0x26300500.bin.GCF. After I installed deconz first time, I was able to browse to phoscon webpage. Then I created the backup of my phoscon running on raspbee (raspberian image of dresden electronics) with x11. Then I uploaded this backup to deconz with conbee and it was imported, but no lights were displayed. So I restarted the server and deconz was not longer able to start. I always get the error messages.

I tried to reinstall deconz on my server but it is still failing with the provided errors. What files do I have to delete for a full deinstallation? I would test to run deconz on raspbee headless to before I create the backup.

Wyphorn commented 5 years ago

So, I tried again to remove all deconz folders, but it's still like this: Mar 6 21:28:42 server systemd[1]: Stopped deCONZ: ZigBee gateway -- WIFI Service. Mar 6 21:28:42 server systemd[1]: Reloading. Mar 6 21:28:42 server systemd[1]: Started ACPI event daemon. Mar 6 21:28:42 server systemd[1]: Started deCONZ: ZigBee gateway -- Initialisation. Mar 6 21:28:42 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 6 21:28:42 server systemd[1]: deconz.service: Unit entered failed state. Mar 6 21:28:42 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 6 21:28:42 server systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation... Mar 6 21:28:42 server deCONZ-init.sh[10754]: cat: /sys/block/mmcblk0/device/cid: No such file or directory Mar 6 21:28:42 server deCONZ-init.sh[10754]: stopping deconz-wifi.service Mar 6 21:28:42 server systemd[1]: Stopped deCONZ: ZigBee gateway -- WIFI Service. Mar 6 21:28:42 server systemd[1]: Reloading. Mar 6 21:28:42 server systemd[1]: Started ACPI event daemon. Mar 6 21:28:42 server systemd[1]: Started deCONZ: ZigBee gateway -- Initialisation. Mar 6 21:28:42 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Mar 6 21:28:42 server systemd[1]: Starting deCONZ: ZigBee gateway -- Initialisation... Mar 6 21:28:42 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Mar 6 21:28:42 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Mar 6 21:28:42 server deCONZ[10790]: QXcbConnection: Could not connect to display Mar 6 21:28:42 server deCONZ-init.sh[10789]: cat: /sys/block/mmcblk0/device/cid: No such file or directory Mar 6 21:28:42 server deCONZ-init.sh[10789]: stopping deconz-wifi.service Mar 6 21:28:42 server systemd[1]: Stopped deCONZ: ZigBee gateway -- WIFI Service. Mar 6 21:28:42 server systemd[1]: Reloading.

I think there are three problems. I marked the lines bold. First is a wrong path in the file "/usr/bin/deCONZ-init.sh". There is a line: THIS_SDCARD=$(cat /sys/block/mmcblk0/device/cid) On my raspbee I have this path. On my ubuntu server I haven't. Do I have to change something there?

€: I was able to stop the first error message with comment the THIS_SDCARD lines. But the "Could not connect to display" is still active. For running deconz headless, I did "sudo systemctl enable deconz" after installation and using "service deconz start/stop" to start and stop the service. Trying to get the services with ps I get this results: root@server:~# ps aux | grep deconz root 25319 0.0 0.0 15608 1100 ? S 21:43 0:00 /lib/systemd/systemd-cgroups-agent /system.slice/deconz-init.service root 25320 0.0 0.0 15608 1128 ? S 21:43 0:00 /lib/systemd/systemd-cgroups-agent /system.slice/deconz.service root 25323 0.0 0.0 14228 972 pts/0 S+ 21:43 0:00 grep --color=auto deconz and sometimes this: root 28954 0.0 0.0 26300 3408 ? S 21:43 0:00 systemctl disable deconz-wifi

The journal entries are: Mar 06 22:26:15 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 06 22:26:15 server systemd[1]: deconz.service: Unit entered failed state. Mar 06 22:26:15 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 06 22:26:15 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Mar 06 22:26:15 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:15 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:16 server deCONZ[10222]: QXcbConnection: Could not connect to display Mar 06 22:26:16 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 06 22:26:16 server systemd[1]: deconz.service: Unit entered failed state. Mar 06 22:26:16 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 06 22:26:16 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Mar 06 22:26:16 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:16 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:16 server deCONZ[10298]: QXcbConnection: Could not connect to display Mar 06 22:26:16 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 06 22:26:16 server systemd[1]: deconz.service: Unit entered failed state. Mar 06 22:26:16 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 06 22:26:16 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Mar 06 22:26:16 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:16 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:16 server deCONZ[10371]: QXcbConnection: Could not connect to display Mar 06 22:26:16 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 06 22:26:16 server systemd[1]: deconz.service: Unit entered failed state. Mar 06 22:26:16 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 06 22:26:16 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Mar 06 22:26:16 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:16 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:17 server deCONZ[10413]: QXcbConnection: Could not connect to display Mar 06 22:26:17 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 06 22:26:17 server systemd[1]: deconz.service: Unit entered failed state. Mar 06 22:26:17 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 06 22:26:17 server systemd[1]: deconz.service: Service hold-off time over, scheduling restart. Mar 06 22:26:17 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:17 server systemd[1]: Started deCONZ: ZigBee gateway -- REST API. Mar 06 22:26:17 server deCONZ[10489]: QXcbConnection: Could not connect to display Mar 06 22:26:17 server systemd[1]: deconz.service: Main process exited, code=dumped, status=6/ABRT Mar 06 22:26:17 server systemd[1]: deconz.service: Unit entered failed state. Mar 06 22:26:17 server systemd[1]: deconz.service: Failed with result 'core-dump'. Mar 06 22:26:17 server systemd[1]: Stopped deCONZ: ZigBee gateway -- REST API.

Wyphorn commented 5 years ago

Okay, I found this command for start up in another issue: deCONZ --dbg-info=1 --dbg-aps=1 --dbg-zcl=1 --dbg-zdp=1 --http-port=80 -platform minimal This one works for me. I was able to start phoscon with that and was able to import my backup. After that I had again the QXcbConnection: Could not connect to displayin my logs. But I was able to restart deconz with same parameters again. The command "deCONZ -platform minimal --http-port=81" in the "/lib/systemd/system/deconz.service" fails with the QXcbConnection error. Running the same command in terminal works nice. I have no idea for this.

Wyphorn commented 5 years ago

After starting the deconz with imported files, I have the next problem. On Phoscon landing page, I am able to use the imported network; the conbee itself keeps greyed out. In the imported network I see all my bulbs, strips, switches and sensors. But I cannot use them. I tried to search for new lights and turn them off for 10 seconds but I still can not use them. And yes, the raspbee is offline. How to "migrate" them to new hardware?

Wyphorn commented 5 years ago

Is here any news how to use a restored backup? The problem is still: I can import the raspbee phoscon backup in deconz and I see all devices, rules and scenes, but I cannot use them. The status of the devices is wrong too.

I tried just a new light search, but without any result. I tried to cut off the power of the devices for multiple seconds and after turning on I still can't find them. What's the provided way to restore a backup on different hardware? The wiki page is very basically: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Backup-&-Restore

Wyphorn commented 5 years ago

I'm planning to do the exact same thing (sick of the fragility of the raspberry... moving to x86 proxmox) so I'm interested in the answer!

I will swap back to hue bridge as main zigbee host. The idea of deconz is nice, but deconz (phoscon) is not nice to handle and I think dresden electronics don't know the onus of a smart home interface. I forced my switches to homematic, so there is no need for zll support for gira or busch jaeger. My few xiaomi devices will stay with conbee. With the hue bridge, I had never losing switch devices after updates. They have a much better qa department and with hue bridge, I will be able to get firmware updates and have the "correct hue way" of scenes. I use fhem as smart home server and there I had to create the light scenes at the moment, because deconz gone its own way. And the bad way of configurig motion sensors. Just as a small exchange of my experiences with deconz. One of the biggest benefits was the possibility to make a backup of the config. But when I can't restore it like I learned here, this is no benefit. The support of dresden electronics just stopped my case and hadn't answered last emails.