Contribute to Open Source. Search issue labels to find the right project for you!

Z-Wave devices stop responding/network failure occurs

athombv/homey

What is your Homey version (Settings → System)?

1.5.3

What did you try to achieve?

Control Z-Wave devices with Homey.

What was the result?

After a variable amount of time (even directly after reboot) Z-Wave devices stop responding to commands, and probably also stop sending reports.

Any other remarks

This is an issue summarizing various other issues: - https://github.com/athombv/com.fibaro/issues/174 - https://github.com/athombv/com.fibaro/issues/164

The issue is common and known in our community, someone who can (almost) always reproduce is m-ruiter.

Updated 16/10/2017 15:34

Fibaro Motion Sensor suddenly not connected anymore

athombv/homey

What is your Homey version (Settings → System)?

1.5.2

What did you try to achieve?

My Fibaro Motion Sensor did not report anything anymore. When looking at the zwave network graph it was not ‘connected’ to Homey anymore. Never had problems with this. The sensor is about 2 meters away from Homey.. Restarted Homey and still the same

What was the result?

No communication with the sensor anymore

What did you expect as result?

A nicely working sensor which communicates with Homey

Any other remarks

Please attach a Homey System log (Settings -> System -> Send Log) It’s about node 18 in the logs: zwave logs.txt

Homey log file code: D55285419F

Updated 26/09/2017 09:57 1 Comments

Stillt got: ProcessSendData[3715]: Error: TRANSMIT_COMPLETE_NO_ACK

athombv/homey

What is your Homey version (Settings → System)?

1.5.0-rc.2

Fibaro:v1.5.5

What did you try to achieve?

Removed the Z-Wave device Node 6 (Motion sensor). But i can’t add it anymore. I tried it with an other motion sensor (same model) and i got the same issue. Changed power measure report intervals of all power plugs.

Please include detailed steps how we can reproduce the issue

What was the result?

What did you expect as result?

Any other remarks

Please attach a Homey System log (Settings -> System -> Send Log)

I got still get so many z-wave delays:

And i can’t readd my Danalock (timeout)!

[2017-08-04T17:46:44.229Z] ProcessSendData[3715]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-08-04T17:46:48.862Z] ProcessSendData[3717]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-08-04T17:46:53.513Z] ProcessSendData[3716]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-08-04T17:47:07.792Z] ProcessSendData[3719]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-08-04T17:51:44.724Z] ProcessSendData[3731]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-08-04T17:51:50.494Z] ProcessSendData[3732]: Error: TRANSMIT_COMPLETE_NO_ACK

[2017-08-04T17:46:39.298Z] ProcessSendData[3715]: To node: 6 with data: 0x98803500d1876ef497db and txOptions: ACK,AUTO_ROUTE [2017-08-04T17:46:44.229Z] ProcessSendData[3715]: Error: TRANSMIT_COMPLETE_NO_ACK

Updated 11/09/2017 16:02 7 Comments

z-wave devices don't show status / energy / power after power down

athombv/homey

What is your Homey version (Settings → System)? Homey Firmware Versie: 1.3.2

What did you try to achieve? use the devices Fibaro FGS-221 and Qubino ZMNHBD1 (Both 2-relay modules) and be able to monitor the momentairy-power use

Please include detailed steps how we can reproduce the issue After Pairing these devices, the power/energy is displayed, status change by connected switch is not shown on Homey

What was the result? Added the device, then the “Energy” was shown and updated while it was changing. The switch-status was updated when it was changed by a connected switch/pushbutton. Then I did a power down for 5 minutes of the device, and powered it up again, then there was no update of the “Energy” it stays on 0W , several times switching the device on/off does work for the load but no energy indication.

What did you expect as result? indication of the power data

Any other remarks when pairing the Qubino device, the default on the display says “pushbutton” but the function is “switch”, if you need “pushbutton” then you first have to change the parameters to “switch” and then back to “pushbutton”, then it works.

Homey_ZWAVE.txt

see also https://forum.athom.com/discussion/3461/multichannel-nodes-not-updating-status#latest https://forum.athom.com/discussion/3427/z-wave-devices-dont-show-energy-power-after-power-down#latest

Updated 16/10/2017 14:48 1 Comments

Z-wave inclusion doesn't work - stuck at Exchanging security key and other issues

athombv/homey

What is your Homey version (Settings → System)?

1.3.2

What did you try to achieve?

Include a Philio device

Please include detailed steps how we can reproduce the issue

Tried 3 times to include and everytime it gets stuck at the phase it showing “exchanging security key” after a while (timeout?) it asked again to put it into inclusion mode as it is paired, it gives error that it is already paired. Then first delete it through Z-wave settings and tried to include again. After 3 times I decided to reboot and then it worked directly. I have seen this behaviour on 1.3 RCs as well and then also reboot fixed the issue. Errors like Error: queue_full are visible in the Z-wave log

Then performed reboot. Then tried again, it got further when retrieving classes it stopped and showing that it could not reach despite the fact the device is 5 cm from Homey After Homey seems to be very busy. When trying to add a device again it it slower and when Z-wave device creation starts it shows for a long period of time waiting z-wave to be ready Then I had to remove node again (twice… ) and after that it was succesfull included

Please attach a Homey System log (Settings -> System -> Send Log)

After 3 times and before reboot: FDA8C0F1E2 After reboot, other issues and succesful inclusion: 308CE686C3

Updated 12/08/2017 09:55 10 Comments

Z-Wave Device creation - invalid_commandClass_COMMAND_CLASS_NOTIFICATION

athombv/homey

What is your Homey version (Settings → System)?

1.3.2

What did you try to achieve?

Add a Fibaro Motion Sensor (Z-wave Plus)

Please include detailed steps how we can reproduce the issue

What was the result?

Device card was created but when you click on the device card instead of values it showed a broken link icon with the text “Motion Sensor (Z-Wave Plus) invalid_commandClass_COMMAND_CLASS_NOTIFICATION” (see photo)

After a while the whole device card showed a broken link icon (see photo) What did you expect as result?

Any other remarks

I deleted the device as it was not updating its values anymore. Deletion was also giving issues and when trying to add it was also having issue. Finally I first had to reboot

Please attach a Homey System log (Settings -> System -> Send Log)

9CC28C50E4

Photos:

1 2

Updated 17/10/2017 09:17 11 Comments

Z-Wave many timeout and ack errors

athombv/homey

What is your Homey version (Settings → System)?

1.3.2

What did you try to achieve? Reset the complete Z-Wave Network, exclude and include all z-wave devices after that.

Please include detailed steps how we can reproduce the issue

3x NEO Switches, 3x Fibaro Motion Sensors, 3x Fibaro Sensors, 2x Aeotec Smart Switch V2

What was the result? Same issue like before.

The first timeout comes with the first devices. (Aeotec & FIbaro Motion Sensors)

What did you expect as result?

Any other remarks

Please attach a Homey System log (Settings -> System -> Send Log)

Log Key: 210B7D42D8

[2017-06-28T19:42:01.670Z] ProcessSendData[138]: Error: senddata_timeout [2017-06-28T19:42:03.726Z] ProcessSendData[139]: Error: senddata_timeout [2017-06-28T19:42:05.955Z] ProcessSendData[137]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:42:06.147Z] ProcessSendData[136]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:42:06.323Z] ProcessSendData[135]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:42:06.429Z] ProcessSendData[134]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:42:06.607Z] ProcessSendData[133]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:42:06.786Z] ProcessSendData[132]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:45:38.531Z] ProcessSendData[151]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:45:38.729Z] ProcessSendData[153]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:45:38.907Z] ProcessSendData[154]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:45:39.117Z] ProcessSendData[152]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:45:42.028Z] ProcessSendData[155]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:21.338Z] ProcessSendData[156]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:21.497Z] ProcessSendData[159]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:21.627Z] ProcessSendData[158]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:21.787Z] ProcessSendData[157]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:39.722Z] ProcessSendData[160]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:39.897Z] ProcessSendData[163]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:40.057Z] ProcessSendData[162]: Error: TRANSMIT_COMPLETE_NO_ACK [2017-06-28T19:46:40.177Z] ProcessSendData[161]: Error: TRANSMIT_COMPLETE_NO_ACK

Updated 15/08/2017 18:03 3 Comments

[Z-Wave] Wake Up Interval value: 0 should be possible

athombv/homey

What did you try to achieve? Have a battery device’s wake-up interval on 0 but the range starts from the minimal step size (in this case (ZW074) 240 seconds, but have seen more devices use this)

What was the result? The setting save button disables since 0 is not in the specified range even though 0 was the default wake up time.

What did you expect as result? 0 should be possible according to the specs, though it’s not really a good thing, it shouldn’t disable the save settings button causing confusion.

Any other remarks Version 1:

Values in the range 1..16777215 MUST indicate the time between Wake Up periods. The value 0 MUST indicate that the receiving node MUST Wake Up when initiated by an event determined by the application e.g. a pushbutton activation.

Version 2 (and up) there is an extra addition to this rule:

A receiving node SHOULD accept the value 0, even if the Minimum Wake Up Interval advertised by the Wake Up Interval Capabilities Report Command is larger than 0. If accepted, the value 0 MUST disable the timer-based transmission of Wake Up Notification Commands.

Updated 30/08/2017 16:35 2 Comments

zwave devices marked as invalid_node

athombv/homey

What is your Homey version (Settings → System)?

1.2.2

What did you try to achieve?

Removed some zwave devices and tryed to repair. Repair worked couple of times, after that no more. Last repaired devices are all marked as invalid_node. Even one older device (fabro roller shutter) is now marked as invalid_node. Removing zwave from settings is working, but the device is still here. Removing with the cross from devices and timeout is working. Removed devices now unpossible to pair.

What was the result?

Dead devices, zwave unusable, pairing not possible, removing old devices problematic.

What did you expect as result?

Working zwave

Any other remarks

Zwave IDs are over 200 atm, maybe i have the max. IDs used? Is Homey not restarting with the zwave ID Nummbers? PTP and Rebooted many times, not better

Please attach a Homey System log (Settings -> System -> Send Log)

557E168C2B is a new one, 3F06DE6438 older (better) one

Updated 16/08/2017 06:23 17 Comments

[Z-wave] Multi Channel association not possible (input validation NOK)

athombv/homey

What is your Homey version (Settings → System)? 1.1.2

What did you try to achieve? Add a multi channel end-point (Light connected to one of the Greenwave Powernode-6 sockets) node ID to the association group of a Fibaro Dimmer-2 (supporting COMMAND_CLASS_MULTI_CHANNEL and COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION) to switch on the light simultaneously with the light connected to the Dimmer-2

What was the result? Input validation of the association groups field does not accept non integer input (e.g. 10.1) to indicate the node ID of the multi channel end point (light connected to the greenwave powernode) <img width=“655” alt=“schermafbeelding 2017-01-21 om 10 45 31” src=“https://cloud.githubusercontent.com/assets/17163431/22173528/096a5f7a-dfc7-11e6-9c88-df6379bf4f6d.png”>

What did you expect as result? Able to add it to the association groups.

Has the COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION been fully implemented and is this only an input validation issue or is the COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION not (fully) implemented yet?

Any other remarks Work around is to create a flow within Homey to do this. But this is not the desired situation. Specifically in case of Z-wave sensors with alarm capability (e.g. motion or smoke sensors) it should be possible to directly switch on (or off) any other Z-wave devices by creating a direct association

In addition, new Z-wave Multi-channel sockets are currently under development by different parties…

Updated 11/09/2017 14:50 19 Comments

Fork me on GitHub