Works well but unreliable

Discussions about Z-Way software and Z-Wave technology in general
Eagle
Posts: 90
Joined: 18 Jun 2017 19:04

Re: Works well but unreliable

Post by Eagle » 21 Feb 2018 18:01

i had some problems but after some reorganizations und mostly since the update to 2.3.6 im very happy. i got some automated lights; some hue lights (around 15 to 20), which are controlled through zwave.me wallc-s and some normal light bulbs with fibaro double switches, dimmers and relais, everything switches instant. of course there are some movement sensors for lights etc..

im including every device on the place where the device will be used, so the device will be reliably included in my mesh network.
when i started, i included every device next to my UZB Stick, even the main powered devices.. but that didnt work well, maybe because the older versions of zway for the wd nas didnt work well or maybe zway didnt set up a reliable mesh network. reorganizations were somewhat broken on the older versions, so i had no mesh network and mostly only one connection, only to the uzb stick

Guybrush
Posts: 1
Joined: 21 Feb 2018 23:23

Re: Works well but unreliable

Post by Guybrush » 21 Feb 2018 23:30

What makes mine reliable is that I eventually managed to directly associate the switches with the nodes, so the controller could be off and it still works. Doing this was a lot harder than it should have been due to faulty software and incompatibilities.

Also, I placed the nodes no further than 4 metres from each other, so they always have a good link between each other. I use it for all the lights in the flat and some smoke alarms, so with the switches and the secondary controller that makes about 40 nodes.

piet66
Posts: 86
Joined: 04 Feb 2017 17:00

User reset to factory defaults Z-Wave device ID: 14

Post by piet66 » 24 Feb 2018 12:57

Since my last post in this thread I made the ZWave network tighter by adding more ZWave+ devices to minimize the likelihood of' dead' devices.

But now I again have such a case.
In notifications I found a message which I have never seen before:
User reset to factory defaults Z-Wave device ID: 14

And the lines in the log:

Code: Select all

[2018-02-24 09:04:00.378] [I] [core] ---  ZWayVDev_zway_14-1-37 performCommand processing: {"0":"off"}
[2018-02-24 09:04:00.378] [I] [zway] Adding job: SwitchBinary Set
[2018-02-24 09:04:00.378] [I] [zway] Adding job: SwitchBinary Get
...
[2018-02-24 09:04:00.634] [I] [zway] Job 0x13 (SwitchBinary Set): Delivered
[2018-02-24 09:04:00.634] [I] [zway] Removing job: SwitchBinary Set
[2018-02-24 09:04:00.931] [I] [zway] Job 0x13 (SwitchBinary Get): Delivered
[2018-02-24 09:04:00.931] [I] [zway] Waiting for job reply: SwitchBinary Get
[2018-02-24 09:04:01.101] [I] [core] Notification: device-info (device-OnOff): {"dev":"EN-Bad Pumpe Ein-Aus","l":"off","location":8}
...
[2018-02-24 09:04:05.393] [I] [core] ---  ZWayVDev_zway_14-1-37 performCommand processing: {"0":"update"}
[2018-02-24 09:04:05.394] [I] [zway] Adding job: SwitchBinary Get
[2018-02-24 09:04:05.647] [I] [zway] Job 0x13 (SwitchBinary Get): Delivered
[2018-02-24 09:04:05.647] [I] [zway] Waiting for job reply: SwitchBinary Get
[2018-02-24 09:04:07.790] [W] [zway] Reply not received before timeout for job (SwitchBinary Get)
[2018-02-24 09:04:09.904] [I] [core] Notification: error (connection): User reset to factory defaults Z-Wave device ID: 14
The notification message clearly is wrong, cause no user has done anything.
I tried to switch the device manually from Web UI. But after that the device is marked as 'dead'.
log:

Code: Select all

[2018-02-24 10:29:21.916] [I] [core] ---  ZWayVDev_zway_14-1-37 performCommand processing: {"0":"on","1":{}}
[2018-02-24 10:29:21.916] [I] [zway] Adding job: SwitchBinary Set
[2018-02-24 10:29:21.916] [I] [zway] Adding job: SwitchBinary Get
[2018-02-24 10:29:30.155] [I] [zway] Job 0x13 (SwitchBinary Set): Not delivered to recipient
[2018-02-24 10:29:37.363] [I] [zway] Job 0x13 (SwitchBinary Set): Not delivered to recipient
[2018-02-24 10:29:44.559] [I] [zway] Job 0x13 (SwitchBinary Set): Not delivered to recipient
[2018-02-24 10:29:44.559] [I] [zway] Job 0x13 (SwitchBinary Set): Removing job due to too much retransmitions
[2018-02-24 10:29:44.559] [I] [zway] Adding job: Check if node is failed
[2018-02-24 10:29:44.559] [I] [zway] Removing job: SwitchBinary Set
[2018-02-24 10:29:44.569] [I] [zway] Job 0x62 (Check if node is failed): Node 14 is failed
[2018-02-24 10:29:44.569] [I] [zway] Removing job: Check if node is failed
...
[2018-02-24 10:29:55.128] [I] [zway] Job 0x13 (SwitchBinary Get): Not delivered to recipient
...
[2018-02-24 10:30:02.044] [I] [zway] Job 0x13 (SwitchBinary Get): Not delivered to recipient
[2018-02-24 10:30:09.074] [I] [zway] Job 0x13 (SwitchBinary Get): Not delivered to recipient
[2018-02-24 10:30:09.075] [I] [zway] Job 0x13 (SwitchBinary Get): Removing job due to too much retransmitions
[2018-02-24 10:30:09.082] [I] [zway] Waiting for job reply: SwitchBinary Get
[2018-02-24 10:30:09.413] [I] [core] Notification: error (connection): Connection lost to Z-Wave device ID: 14
[2018-02-24 10:30:11.205] [W] [zway] Reply not received before timeout for job (SwitchBinary Get)
Zway version 2.3.6 running on raspbian with razberry.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 9 (stretch)
ZMEERAZ 2016, SDK Version: 6.51.03, Serial API Version: 05.00
Z-Way version v3.0.0 from 2019-07-18 02:13:01 +0300 (build 146fa9b44605907737b17032131987cab573da1f)

Post Reply