Page 1 of 1

Replace broken z-stick controller

Posted: Thursday 05 November 2020 12:57
by GeneralTgul
Hi,
My Aeotec z-stick gen5 controller did break so I bought a new one.
Is there a way for me to replace the old one without going trough the hassle of including all my devices one by one?
All my devices are still under devices. When I go to Hardware the new z-stick is there but under Setup it doesn't have the nodes.

Hope you understand my question and that there is a way. have so many devices and it would be a huge amount of work to reconnect them one by one and replace them.

Re: Replace broken z-stick controller

Posted: Thursday 05 November 2020 18:18
by GeneralTgul
I found answer on my question.
You need to take backup with software from Aeotec on the old device and restore the backup on the
https://aeotec.freshdesk.com/support/so ... user-guide

This didn't solve my problem however. My problem is that Domoticz stopped responding a few days ago.
When I reboot it it works for a few seconds before it freeze again.
First I thougth it was the memorycard giving up so here is my troubleshoot this far.

1. Reinstalled Raspbian GNU/Linux 9 on a fresh memory card.
2. Installed latest stable Domoticz 2020.2.12554.
3. Restore from database backup. (As soon as I did restore the DB the problem reoccurred, thought it was corrupted DB)
4. Restore from database backup some days before the problem started (Still same issue)
5. Figured out that Domoticz works fine as long as I don't connect my z-stick. (Order a new Z-stick)
6. The new Z-stick didnt freeze Domotics but all devices where missing. Did a backup on the old Z-stick and restored it to my new z-stick (Now the problem reoccurred again!)

So this is where I stand now. I don't have any idéas left but to revert the new z-stick back, and then start including all devices again one by one.
I have 83 devices so it will take some time.
If anyone have any suggestions before I do this I would be glad.

It seams that my problem is either the firmware on my old controller that I wrote to my new controller. Or some node connected to my controller that makes it crash.

I didn't mention that I turned on verbose logging and dig trougth the database without any luck
:o :o :o