I think you have enough evidence that your Z-Stick is faulty, if your a tinkerer you could try cracking it open and make sure an antenna wire or something obvious did not break loose.
but that might render it inoperable, might just go ahead and pull the trigger on the gen5
Trouble with z-wave hangs after some time.
Moderator: leecollings
- nayr
- Posts: 354
- Joined: Tuesday 11 November 2014 18:42
- Target OS: Linux
- Domoticz version: github
- Location: Denver, CO - USA
- Contact:
Re: Trouble with z-wave hangs after some time.
Debian Jessie: CuBox-i4 (Primary) w/Static Routed IP and x509 / BeagleBone with OpenSprinkler / BeagleBone Planted Aquarium / 3x Raspbery Pi2b GPIO Slaves
Elemental Theme - node-domoticz-mqtt - Home Theatre Controller - AndroidTV Simple OSD Remote - x509 TLS Auth
Elemental Theme - node-domoticz-mqtt - Home Theatre Controller - AndroidTV Simple OSD Remote - x509 TLS Auth
- StephaneG
- Posts: 19
- Joined: Tuesday 17 November 2015 10:10
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: France
- Contact:
Re: Trouble with z-wave hangs after some time.
Hello,
There seems to be a "transfer primary controller role" feature in Dz.
But in your case I wouldnt do that, because if this ends up transferring the messed-up network config from your old to your new controller, this wont be much of a progress.
Even if this sounds very boring, I would advise to exclude and hard-reset each node, then include them from scratch in the new controller.
I still very much doubt that your old controller is at fault, imho it's rather its internal network config which is messed up ; a hard / factory reset may fix it. So in order to better our understanding of the issue, I would suggest:
- exclude and factory reset each node
- then hard / factory reset the old controller
- then re include each node with the old controller
- then observe for a while; and redo the whole thing switching to the new controller only if trouble arises
Regards,
--
Stéphane
There seems to be a "transfer primary controller role" feature in Dz.
But in your case I wouldnt do that, because if this ends up transferring the messed-up network config from your old to your new controller, this wont be much of a progress.
Even if this sounds very boring, I would advise to exclude and hard-reset each node, then include them from scratch in the new controller.
I still very much doubt that your old controller is at fault, imho it's rather its internal network config which is messed up ; a hard / factory reset may fix it. So in order to better our understanding of the issue, I would suggest:
- exclude and factory reset each node
- then hard / factory reset the old controller
- then re include each node with the old controller
- then observe for a while; and redo the whole thing switching to the new controller only if trouble arises
Regards,
--
Stéphane
Who is online
Users browsing this forum: No registered users and 1 guest