›
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 and/or no response for WALLC-S devices and fast battery drain

home78home78 Member
edited July 2017 in Devices

I have Homey 1.3.1 and ZWave.ME 0.1.1 installed and since release 1.3.1 of Homey experiencing the following issues:

  1. Switches are directly associated with Fibaro dimmers, but after a few (10-20) days not functioning any more. That is, when someone presses one of the buttons nothing happens.
  2. There is no low battery report in Homey.
  3. Sometimes, when pressing a switch it takes a while (2-10 seconds) before the dimmers respond.
  4. Also, sometimes the dimmers respond the first time a switch is pressed but don't respond to any presses after the first time it was presses.
  5. After replacing the battery I'm able to make the switches operate normally again.
  6. Some switches (either close or far away from Homey) do not display this behaviour.

My guess is that Z-Wave message handling is currently not being handled very efficiently. In the Homey "Network Graph" it is shown that nodes which are relatively far away from Homey communicate with Homey directly while it would be more efficient to communicate via another node. But this may not be the root cause, since some switches that are located in close vicinity of Homey (only 3 meters away) also display the same behaviour.

I'm not sure wheter this effect should be contributed to Homey version 1.3.1 and its changed Z-Wave implementation or the ZWave.ME app in particular. However, I'm currently only experiencing issues with the WALLC-S and WALLC-S v2 switches while my Fibaro and Aotec multisensors (also battery operated devices) are working without problems at this moment (knock on wood).

I think this may require much more investigating to find the cause of the problem. Any suggestions on how to proceed are very much welcome!

Comments

  • lubbertkramerlubbertkramer Member
    Think one of the ways to go is to use the topic from the z-wave me app from the developer of the app and contact the developer
  • bvbbvb Member
    @home78 I had the same issue and changed the battery from the switch and it was working again. I set the "wake up" of the Switch to 86400 Seconds (24 hours) instead 1600 seconds (30 Minutes). I hope the battery will now survive longer...
  • home78home78 Member
    bvb said:
    @home78 I had the same issue and changed the battery from the switch and it was working again. I set the "wake up" of the Switch to 86400 Seconds (24 hours) instead 1600 seconds (30 Minutes). I hope the battery will now survive longer...
    This is exactly what I did, however not all devices seem to have picked up the new settings (they should automatically be picked up, right?) I'm now closely monitoring the insights page to see which devices are behaving correctly and have a spreadheet to keep track of battery replacements. Its becoming very painfull when the family is unable to operate the lights... but still work in progress I guess.

    I think we need a better way to analyze ZWave logging. So that you can see device activity over a longer period of time.
  • TobiasETobiasE Member
    Hi,

    Just bought this switch to use at home but im having problem to get it to work properly.
    At first i got 2 out of 4 buttons to work but now none of the work (i see the switch trannsmit in the logging)
    Could any of you using these switch please share your settings for the switch ?

    Thanks !
  • phil_sphil_s Member
    would this thread help you?
    https://forum.athom.com/discussion/2949/how-to-double-click-zwave-me-wallc-s-wallc-2-makes-8-possible-options#latest

    greedings
  • TobiasETobiasE Member
    Hi, thanks that helped to get the buttons to work separatly but.......

    Im having huge problem to get this switch to work properly, when pushin the buttons i can see in the zwave log in Homey that it receives the signal but it only intermitent activates the flows i´ve created linked to the button. 
    I can´t understand why (i tried to change the battery).

    Example when button 2 was pressed:

    Log button 2;

    [2017-10-03T05:38:20.555Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40

    [2017-10-03T05:38:20.556Z] Node[4]: sendData to COMMAND_CLASS_SECURITY, params 0x800f3d3f5e7aa159c6

    [2017-10-03T05:38:20.557Z] Command[53] start: sendData

    [2017-10-03T05:38:20.559Z] ProcessSendData[53]: To node: 4 with data: 0x98800f3d3f5e7aa159c6 and txOptions: ACK,AUTO_ROUTE

    [2017-10-03T05:38:20.717Z] Command[53] end: sendData

    [2017-10-03T05:38:20.768Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0xc18eecdf691ebd36cda5ba534a87380f2d6e9f26f9048cdb

     

    {"zw_state":{"stats":{"processmanager":{"processQueue":0},"commands":{"commandsQueue":0}},"ver":5,"capabilities":{"api":"controller","timerSupported":false,"controllerType":"primary"},"nodes":[1,2,4,5,6],"chip_type":5,"chip_version":0,"homeId":4142704806,"nodeId":1,"nvr":[1,5,0,21,13,27,120,32,1,0,32,0,64,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,24,19,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,11,91],"CONTROLLER_IS_SECONDARY":false,"CONTROLLER_ON_OTHER_NETWORK":false,"CONTROLLER_NODEID_SERVER_PRESENT":true,"CONTROLLER_IS_REAL_PRIMARY":true,"CONTROLLER_IS_SUC":true,"NO_NODES_INCUDED":false,"sucId":1,"powerLevel":0,"version":"Z-Wave 3.99","networkKey":"c003ef9b980c9c7735f6c3ab065971d4","methodsAsync":["factoryReset","addNodeAbort","removeNodeAbort","replaceFailedNodeAbort","sendData","isFailedNode","getFailedNodes","ping"]},"zw_ready":true,"_stateTimestamp":1507009120946}

     

    Example when button 3 was pressed

     

    [2017-10-03T05:40:59.502Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40

    [2017-10-03T05:40:59.503Z] Node[4]: sendData to COMMAND_CLASS_SECURITY, params 0x8013c3ffe3fdb64345

    [2017-10-03T05:40:59.504Z] Command[57] start: sendData

    [2017-10-03T05:40:59.505Z] ProcessSendData[57]: To node: 4 with data: 0x988013c3ffe3fdb64345 and txOptions: ACK,AUTO_ROUTE

    [2017-10-03T05:41:00.039Z] Command[57] end: sendData

    [2017-10-03T05:41:00.099Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0xc130b0b2508655d1683e7e07904664130a50bc0cf03aaea5

     

    {"zw_state":{"stats":{"processmanager":{"processQueue":0},"commands":{"commandsQueue":0}},"ver":5,"capabilities":{"api":"controller","timerSupported":false,"controllerType":"primary"},"nodes":[1,2,4,5,6],"chip_type":5,"chip_version":0,"homeId":4142704806,"nodeId":1,"nvr":[1,5,0,21,13,27,120,32,1,0,32,0,64,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,24,19,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,11,91],"CONTROLLER_IS_SECONDARY":false,"CONTROLLER_ON_OTHER_NETWORK":false,"CONTROLLER_NODEID_SERVER_PRESENT":true,"CONTROLLER_IS_REAL_PRIMARY":true,"CONTROLLER_IS_SUC":true,"NO_NODES_INCUDED":false,"sucId":1,"powerLevel":0,"version":"Z-Wave 3.99","networkKey":"c003ef9b980c9c7735f6c3ab065971d4","methodsAsync":["factoryReset","addNodeAbort","removeNodeAbort","replaceFailedNodeAbort","sendData","isFailedNode","getFailedNodes","ping"]},"zw_ready":true,"_stateTimestamp":1507009260053}



     


  • TobiasETobiasE Member
    I missed to post pictures from the flows liked to the buttons.


Sign In or Register to comment.