Skip to content
This repository has been archived by the owner. It is now read-only.

Paring and/or removing Z-Wave nodes fails due to time out #2333

Open
cbho opened this Issue Mar 14, 2018 · 19 comments

Comments

@cbho
Copy link

cbho commented Mar 14, 2018

Metadata

  • Homey Version: 1.5.8

  • Homey Log Code: 03443B0A46

  • Affected Devices (preferably product codes):
    Several manufacturers and types, e.g.
    Neo Coolcam Door Window Sensor (NAS-DS01ZE)
    Neo Coolcam Motion Sensor V1 (NAS-PD01ZE)
    Fibaro Motion Sensor (Z-Wave Plus) (FGMS-001-PLUS)
    Fibaro Door/Window Sensor (Z-Wave Plus) (FGK-10x)
    Copenhagen Blinds (no app, work in progress)

What did you try to achieve?
Add devices in z-wave network.
When failed, remove them again via "Settings -> Z-Wave -> Remove a device"

What did you expect as result?
That devices were added without problems as they were in Homey fw 1.5.x up until 1.5.7
And if pairing failed, removal via "Settings -> Z-Wave -> Remove a device"

What was the result?
Since updating to 1.5.8 adding and removing z-wave nodes have deteriorated severely.

Adding devices fail
When trying to add e.g. the blinds I'm trying to make an app for, pairing fails something like 9 out of 10 times now, the last couple of weeks, it has been totally opposite - fail rate has been something like 1 out of 25 - and that due to problems in my code.

Now, most of the times the pairing stops at some point (mostly while retrieving command class versions, not at any specific point, can be after retrieving 9, 12, 15, or 16 of 17 classes when it's the blinds).
Resulting error messages are:
vdevice.drivers.zwavebasic.pair.senddata_timeout or
No Z-Wave device has been found.

An example from the z-wave log could be:
2018-03-14T22:42:51.791Z | ProcessSendData[306]: To node: 55 with data: 0x86138e and txOptions: AUTO_ROUTE,ACK,EXPLORE
2018-03-14T22:43:01.804Z | ProcessSendData[306]: Error: senddata_timeout

Removing devices fail
After failed pairing, removing the node via "Settings -> Z-Wave -> Remove a device" now also fails most of the times - although the device is set in "Learn mode" removal fails and error message No device for removal found shows.
Edit 18.3.2018:
New error message appeared: Could not remove a device; the device could however be removed on next attempt.

Furthermore, when removal finally results in "Device succesfully removed", the next pairing attempt may still result in a message stating the device is already paired with Homey.

Any other remarks
Initially I thought the reason was heavy polling on some Powernode 6 devices, but this seems not to be the case afterall (nothing really changes when disabling the app and physically unplugging the devices).

As I thought this was post probably something with my code for the blinds, I tried adding the Neo and Fibaro devices mentioned above (had some unused) with the devices mentioned above. All have been paired with Homey before and worked flawlessly.

All pairing attempts have been done, re-done, re-re-done at different distances from five cm to 0,5-1-2 meters.
Homey has been rebooted a conutless number of times, PTP has been tried as well.

The result stays more or less unchanged.
As mentioned, during the last weeks I have paired and un-paired the same devices litterally hundreds of times - and something has definitely changed - and disabling apps and flows trying to minimise traffic load on the z-wave mesh has not solved the time outs experienced.

I have noticed a behavior similar to that described in #2326 with "Unknown node" but have not been checking this systematically and cannot say for certain that it is in fact the same pattern.

@jaimevisser

This comment has been minimized.

Copy link

jaimevisser commented Apr 26, 2018

Also fails with Benext P1 dongle on 1.5.3

@Rocodamelshe

This comment has been minimized.

Copy link

Rocodamelshe commented May 13, 2018

Same issue here. Cannot delete a device anymore from devices page.
vdevice.drivers.zwavebasic.pair.response_timeout is what i get.
Device was removed ok with the zwave-delete device but is still on devices page.
1.5.11

@razorfish79

This comment has been minimized.

Copy link

razorfish79 commented May 16, 2018

Having the very same issue as @Rocodamelshe.

Removing of Z-Wave device went OK but device is still shown. When trying to remove from the device page the error occures.
vdevice.drivers.zwavebasic.pair.response_timeout

1.5.11

@philsniff

This comment has been minimized.

Copy link

philsniff commented May 20, 2018

Same problems here! Firmware 1.5.11

@Mikro007

This comment has been minimized.

Copy link

Mikro007 commented Jun 9, 2018

Same for me! Firmware 1.5.11

I think I have 3-4 devices in homey gui that shouldnt be there...

@Eternity-again

This comment has been minimized.

Copy link

Eternity-again commented Jun 12, 2018

Same problem here!
Homey Firmware Versie: 1.5.11

Successfully removed a device via the z-wave menu. However, device is still shown in device page and can't be removed:

schermafbeelding 2018-06-12 om 14 29 38

@korkmazk

This comment has been minimized.

Copy link

korkmazk commented Jun 29, 2018

Same issue here, tried to remove a device and same timeout error.

@lesterchan

This comment has been minimized.

Copy link

lesterchan commented Jul 14, 2018

Having the same exact issue. My MCO TouchPanel died. So I have to forcefully remove the Z-Wave device but I’m unable to do it. After 30s, this error will show up and Homey doesn’t remove it. It worked before.

9a6rlx5x3pzg

@depeej

This comment has been minimized.

Copy link

depeej commented Aug 4, 2018

homey

I have the same error, the device is excluded. But it stays in the devices menu.

@Patrikgolfer

This comment has been minimized.

Copy link

Patrikgolfer commented Aug 4, 2018

Same problem i 1.5.12

@AdyRock

This comment has been minimized.

Copy link

AdyRock commented Aug 12, 2018

Same for me also in 1.5.12

@akke911

This comment has been minimized.

Copy link

akke911 commented Sep 9, 2018

2 devices I cannot add: (Timeout retrieving command class versions)
Fibaro wallplug FGWPE/F-102
Aoeotec Wallmote Quad

Homey Firmware Version: 1.5.11
Aeotec app v1.6.7
Fibaro app v1.5.18

@Inversion-NL

This comment has been minimized.

Copy link

Inversion-NL commented Sep 11, 2018

Same for me on Firmware 1.5.13-RC9 on a Neo CoolCam plug.

Was unable to remove it (in the Android Homey Preview app) so used Settings > Zwave to remove the device.
However the device is still on Homey and have been unable to remove it resulting in a message: "vdevice.drivers.zwavebasic.pair.response_timeout"
The Android Preview app, however, a different message appears:
"Missing required parameter: driverId"

Homey log: 71E13EB194

@Inversion-NL

This comment has been minimized.

Copy link

Inversion-NL commented Sep 14, 2018

Tried with Homey firmware 1.5.13.RC11 and both types of unknown nodes (one visible in Homey while the other was visible only in developer tools) were removed succesfully! 👍

@chixxi

This comment has been minimized.

Copy link

chixxi commented Sep 14, 2018

Oh yes, this finally works by using the "remove" button in the developer section when you have 1.5.13.RC11 installed.

Thanks for the hint @Inversion-NL !

@AdyRock

This comment has been minimized.

Copy link

AdyRock commented Sep 16, 2018

Works for me but (possibly a different topic) the range seems to be reduced now. To communicate with a Quibino shutter dc I now need to have Homey in the same room. Move it to the next room (about 10m away and one wall) and it's No longer communicates.

@jeroenvano

This comment has been minimized.

Copy link

jeroenvano commented Sep 21, 2018

I am on stable 1.5.12 so it looks that I need to have a little more patience.

@LesPaul1962

This comment has been minimized.

Copy link

LesPaul1962 commented Sep 27, 2018

Same problem on 1.5.12 vdevice.drivers.zwavebasic.pair.response_timeout

@Shadowz7

This comment has been minimized.

Copy link

Shadowz7 commented Oct 28, 2018

vdevice.drivers.zwavebasic.pair.response_timeout
Homey Firmware Version: 1.5.12
When i go to Athom Developer then "This page requires that the selected Homey matches firmware version >=2.0.0.
The selected Homey Homey is version 1.5.12."

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.