›
This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to https://community.athom.com.

This forum is now read-only for archive purposes.
Solved

When Pairing Z-Wave Devices, I Encountered All Sorts Of Errors

lesterchanlesterchan Member
edited September 2017 in Questions & Help
My Z-Wave devices are pretty much standard, TKH Smart Energy Plug, Aeotec  Smart Switch 6, Fibaro Motion Sensor, Aeotec Motion Sensor.

I keep having problems pairing devices after like paring 20 devices. Here are my paired devices
  • 1x MCO Touch Panel 1 Gang
  • 1x MCO Touch Panel 4 Gang
  • 11x Aeotec Smart Switch 6
  • 4x TKB Smart Meter Switch
  • 3x Aeotec Motion Sensor
  • 3x Fibaro Window Sensor
  • 1x Fibaro Motion Sensor
As I add more devices, I get all sorts of error for just 1 device the one same device (doesn't matter which one):
  • Could not reach the device anymore
  • Cannot find Z-Wave device
  • vdevice.drivers.zwavebasic.pair.senddata_timeout
  • vdevice.drivers.zwavebasic.pair.Operation canceled
  • vdevice.drivers.zwavebasic.pair.ALREADY_ACTIVE

It is so frustrating. Not sure if I unpair and pair everything too fast in a go. 
Tagged:

Comments

  • StefanStefan Member
    Hi @lesterchan . Sorry to hear that you have these errors. How do you try to pair the devices? Do you pair them as 'basic Z-Wave devices' under Homey, or do you search for and install the App for the relevant brand? The second option is the way to go, the other options is just for basic switches which are not supported yet.

    Best,

    Stefan
  • addwindtanaddwindtan Member
    Hi @Stefan . Yes, I believe Lester is using the respective Apps. Is there a log file which we can extract for analysis?

  • lesterchanlesterchan Member
     Hi @Stefan, thanks for the reply. I am using the respective apps. I came across https://github.com/athombv/homey/issues/1678 and https://forum.athom.com/discussion/3405/manager-vdevice-drivers-zwavebasic-pair-senddata-timeout which is similar to mine.

    I might reset to factory settings tonight and try again, starting with MCO Touch Panel.

    @addwindtan: The log ID is 80B4F97B01

  • lesterchanlesterchan Member
    Just an update. It seems to be due to a z-wave congestion on my network. Despite my Fibaro HCL crashed and data is gone. I did not go around unpairing 20+ other devices and that causes it (I am guessing) to flood the network.

    Once I went around unpairing, I factory reset Homey and it works now!
  • TedTolboomTedTolboom Member
    Hi @lesterchan
    Thanks for the feedback and good to hear that your issue has been solved!

    A good thing to learn out of this is that Z-wave congestion can also be caused by devices that were never part of Homey’s network... and that it is essential to unpair device’s not in use / formally belonging to another (crashed / replaced) controller...

    enjoy your Homey!
Sign In or Register to comment.