Starting to lose patience with Z-Wave

[garethhowell]

See below
Device 22 has been behaving nicely for over a week. It's permanently powered, as are its neighbouring switches, and is working quiet nicely with device 14, the thermostat.
Suddenly, this morning, it's marked as DEAD.
However, look at the Last seen time. It's still sending updates that are being received by Domoticz. The snapshot was taken at 13:42 and taken after a reboot.
I give up.

Screenshot 2016-11-29 13.41.59.png (236.81 KiB) Viewed 2959 times

[emme]

start healing your zwave network and wait few hours...
I had the same problem with an AEON Switch that results dead mut it was working fine...
I made the heal and it came back

[korniza]

I had strange issues when I update open-wave.
I removed ALL devices (what a painful procedure) and add them again!

[garethhowell]

Thanks for the advice. Healing made no difference.
I could remove and re-add all the devices, but this is not a realistic option in the long term. I've already done that twice to cover earlier problems. The root of the problem seems to be that either: a) the Z-Wave protocol itself is inherently unreliableI, or b) the implementation in the Aeotec and/or Open Z-wave is unreliable.
If you create a reliable network (in the sense of surviving untouched for more than a few days), then the system, by definition, cannot be relied upon and is just another experimental technology that is too fragile for real life.

[emme]

I have 34 devices in my network and more will come...
In almost 1 year I only had a problem with 1 device last week due to a power outage (I made)
For my experience, the network is stable and the controller works exactely as it is supposed to...

Protocol is stable and safe (safe no more than any other wireless system)... since you work inside its cloud... example: using a aeon stick GEN5 is different than using a razberry

[Egregius]

What version of Domoticz/Openzwave are you using?
I've seen versions where nodes are marked as dead without a reason.
Just recently I tried to update from stable to beta on my Syno, all of the sudden 6 devices marked as dead. Reboot, same thing.
Restored previous version and all nodes were back OK.
Here also very stable with 52 nodes of wich approx half battery powered. If something doesn't work it's either because I messed up, or because of an update.
If it's because of an update I restore previous version and wait several weeks to update. Mostly then it's good.

[Westcott]

I had exactly these problems while I too was using an Aeotec S2 stick.
Plus, some nodes only reported very intermittently.
Recently I switched to a Sigma Gen5 stick, and the network is now very stable.
Downside? Had to rebuild from scratch.

[Egregius]

Mine is a Aeotec S2 stick.
So you think that has something to do with it?
I'd like to see that confirmed by other members, otherwise I would buy another stick.
Rebuilding is not such a big deal. The biggest problem is getting all the devices excluded/reset.
Inclusion is quite fun

[emme]

I'm using a Gen5 Aeon Stick with no problems.

moving to another gateway wouldn't be so difficult since you can transfer its configuration from the OZWCP....
ciao
M

[Egregius]

I guess you'll need 2 domoticz installations for that.
The 'old' one with the stick and all the nodes. And a new one with an empty stick.
And then the send and receive configuration option? Is that a good way to go?

Oh, and don't get me wrong. Most of the time the S2 stick is performing really well. Just with updates sometimes troubles.

[emme]

not sure you need 2 installation...
I think you would just need the other gateway (stick) reachable within the range on your existing zwave network, than you activate the "transfer role" option from the hardware/Zwave configuration menu

[garethhowell]

What version of Domoticz/Openzwave are you using? ...

Domoticz is 3.5985
OpenZwave is 1.4_2247
Not sure what firmware the Aeotec S2 is running, but as it hasn't been updated for years, I guess its the latest

[Egregius]

I don't know wich latest beta caused the dead nodes but could be that one.
Now it's 3.5989 on yadahl's Syno repository.
With 3.5877 (openzwave 1.4-2246-ga583ba8-dirty) I don't have it.

[Derik]

I did resell the tkb switches...
They are in the list.
http://www.openzwave.com/device-database
So it is not the same like popp...
Remove the TKB and you network will run stable...

Edit..
It is in the list.. [ in my time not.. ]

Only when i did remove this sensors my network was acting very stable...

[evertide]

Hi.

Have you tried the new S2 firmware released 3rd of April 2016. I have not yet since I am afraid it will loose configuration and I have to rebuild the network.

Hence I am also interested in how to migrated easy to a new controller.

Regards


Verzonden vanaf mijn iPhone met Tapatalk

[Egregius]

What version is that? Is that 3.08? Wich isn't officially on their site?

[evertide]

Hi,

Yes version 3.08 but it is onbthere support site.
https://aeotec.freshdesk.com/support/so ... are-update

Regards

[Egregius]

Yep, forgot the site. But that's the one that I'm already running for months.
I still believe the biggest problems are Openzwave related. Part of the reverse engineering stuff.

[garethhowell]

Hi,

Yes version 3.08 but it is onbthere support site.
https://aeotec.freshdesk.com/support/so ... are-update

Regards

I hadn't realised there was a new firmware release. I'll give that a try


Sent from my iPhone using Tapatalk

[garethhowell]

Remove the TKB and you network will run stable...
...

Only when i did remove this sensors my network was acting very stable...

I guess I'll have to try that. I noticed that the switches have differing firmware versions, so that could be part of it.
They're not cheap though, so it will have to wait until after Christmas.


Sent from my iPhone using Tapatalk