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.

Slow or no response in z-wave & unsuccesful pairing

cbhcbh Member
edited July 2017 in Questions & Help
Hi,
Looking through the forum, I'm obviously not the first having problems with long delays or unresponsive units in the z-wave mesh.
During the last days, both the delay and the "no-response" rate has increased - especially for my Fibaro units (???).
When toggling on/off on the units, the delay eventually "wears off" as if the system "wake up"/prioritize traffic/find the most efficient route for signals.

Further, I'm experiencing some strange pattern when pairing devices:
Most of the times (especially Fibaro and ZHC5010 units), they are recognised initially, but then the process fails at some point, often it stops during "Exchaning security keys", sometimes when it has exchanged almost all unit specific parameters - or the pairing pop-up either disappears or return to "Press button three times".
However, when trying again, the result is is inevitably "This unit is already paired, try to remove etc.".
Removing the unit has a succes rate of 100%!

Sometimes I have to re-pair 5-10-15 times until succes.
However, some units pairs at first try - like, always! - Greenwave Powernode, e.g. is almost paired before it is plugged in ;-)

Have tried rebooting the Homey, have placed the Homey close to units, have waited to the next day to let the mesh "settle down", but the problem persists.
Also tried with removing/re-pairing units (after resetting the unit manually inbetween), but it doesn't change the pattern :-(

The mesh looks like:
All units with prefix "L" are stationary units with repeaters, all units are z+.



Although I think I've been through most of the forum, I might have missed some advice somewhere, of course - but:
Any ideas?

Comments

  • bvdbosbvdbos Member
    What does the log under settings-zwave-stuff for geeks say, are there any errors?
  • cbhcbh Member
    If I filter the log for "error", I get:

    [2017-07-01T12:38:26.614Z] ProcessSendData[1728]: Error: queue_full
    [2017-07-01T12:38:30.190Z] ProcessSendData[1746]: Error: queue_full
    [2017-07-01T12:38:32.167Z] ProcessSendData[1750]: Error: queue_full

    Each of these seems to be preceeded with something like:
    [2017-07-01T12:38:31.616Z] ProcessSendData[1750]: To node: 79 with data: 0x600d4f01320100 and txOptions: ACK,AUTO_ROUTE,EXPLORE

    All to node 79, which is a Greenwave Powernode - the one most recently added (near the Homey), but now placed probably the farthest away in the house.

    Noticed another thing:
    There is a lot of traffic directed from the Homey to one of the sensors (Fibaro Motion Sensor) - a little of the log pasted below - is this a "normal" load? It seems like a lot I think (especially, as I have no flows associated to it right now - it is associated directly to a lamp).

    [2017-07-01T12:49:23.930Z] Node[48]: sendData to COMMAND_CLASS_WAKE_UP, params 0x08
    [2017-07-01T12:49:30.431Z] Node[48]: Marked as offline
    [2017-07-01T12:50:20.389Z] Node[48]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-07-01T12:50:20.392Z] Node[48]: sendData to COMMAND_CLASS_SECURITY, params 0x80575f566cf5aade09
    [2017-07-01T12:50:20.413Z] ProcessSendData[1827]: To node: 48 with data: 0x9880575f566cf5aade09 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-07-01T12:50:20.568Z] Node[48]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81a0a75cf04631d07c9c2f7a57996bb4a2abf7f22e
    [2017-07-01T12:50:20.603Z] Node[48]: Marked as online
    [2017-07-01T12:50:20.605Z] Node[48]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_WAKE_UP, data 0x07
    [2017-07-01T12:50:24.110Z] Node[48]: sendData to COMMAND_CLASS_WAKE_UP, params 0x08
    [2017-07-01T12:50:30.614Z] Node[48]: Marked as offline
    [2017-07-01T12:51:20.500Z] Node[48]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
    [2017-07-01T12:51:20.502Z] Node[48]: sendData to COMMAND_CLASS_SECURITY, params 0x8058823a69978337ff
    [2017-07-01T12:51:20.521Z] ProcessSendData[1831]: To node: 48 with data: 0x988058823a69978337ff and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-07-01T12:51:20.680Z] Node[48]: Received application command for COMMAND_CLASS_SECURITY, data: 0x819fabd791fafcd0bc3d548b589a005f4e83436e38
    [2017-07-01T12:51:20.712Z] Node[48]: Marked as online
    [2017-07-01T12:51:20.715Z] Node[48]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_WAKE_UP, data 0x07
    [2017-07-01T12:51:24.219Z] Node[48]: sendData to COMMAND_CLASS_WAKE_UP, params 0x08

    Thanks,
    Chr.
  • @cbh at which Homey SW version are you running?
  • cbhcbh Member
    Homey Firmware Version: 1.3.1
  • cbhcbh Member
    archarm
    boot_id
    cpus[{"model":"ARMv7 Processor rev 10 (v7l)","speed":996,"times":{"user":9375700,"nice":7857600,"sys":18525000,"idle":127881500,"irq":0}}]
    date2017-07-01T15:17:59.472Z
    date_dsttrue
    date_humanSaturday 1st July 2017 17:17:59
    devmodefalse
    freemem26189824
    freemem_human5%
    homey_version1.3.1
    hostnameHomey
    loadavg[0.37255859375,0.38671875,0.36767578125]

    node_versionv4.8.3
    platformlinux
    release4.7.2-gcff857e
    timezoneEurope/Copenhagen
    totalmem511541248
    uptime16898
    wifi_ssid

    And only 14 apps :-)
  • Can you try to manually wake up the motion sensor; 3x pressing the B-button?
  • cbhcbh Member
    Removed it from totally and rebooted to see what would happen - only one association to be re-assigned, when adding it again later.
    Definitely changed something, now I could even add another component - and units are reacting within 1/2 of a second.
    Still have some instances of "queue full", however (although not as many). All are related to two PowerNode 6 (but not to the third I have), which have a central role in the mesh, when looking at the graphics.
    Think this could be related to the "problem", that if units are paired with Homey nearby and then moved (?)

    It seems there is no way to initiate a rebuild of the mesh manually - how long should it take for the system to rebuild after adding unit(s)?

    Regards,
    Chr.
  • Best advice I still can give is to move Homey close to the position where the new device is going to be used and include it there... and move Homey back to his original location..

    did you change the polling interval of the PN-6 sockets?
  • cbhcbh Member
    Will do so in the future - move Homey to the mountain ;-)
    Haven't changed anything on the PN-6's.

    Could try to remove and re-pair them, when on their final location one of the days, if they are not "sent" to a more peripheral role in the system automatically (if it makes sense to do so, of course?)
  • cbhcbh Member
    Removed and re-paired the PN-6-sockets - helped quite a lot on the delays.

    However, still have the strange behavior when adding new components: Goes through a cycle of pairing, not succeding, removing, pairing, and after a 3-4-5 times through this finally succes...  Weird (but as most components are now added, I'll live with it ;-)).

    Thanks for all the help!
    Chr.
Sign In or Register to comment.