Announcement

Collapse
No announcement yet.

Zwave Wall plug turns on at random

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Zwave Wall plug turns on at random

    I have an issue where a Zwave wall plug turns on by itself. It is only associated with Homeseer and I have checked the logs to confirm there is no manual or timed actions that are turning the device on.

    The device is a TKB Wallplug. I used to have a standard UK version that had the same symptoms and replaced it with a Gen 5 unit but this has made no difference.

    I can go months without an issue, but when the problem starts again it will power on by itself once every 1-3 days. When I had the issue in the past it was associated with Zwave logs saying "Unhandled frame for command class". I mentioned this in the following post and can see that these messages are now meant to be suppressed so I guess I won't know if these messages are still being received.....

    https://forums.homeseer.com/showthread.php?t=178269

    I am slowly tearing my hair out over this... Any ideas on how to troubleshoot this further? The full Zwave Debug log of the device turning on by itself is below but I assume this is just a status frame notifying Homeseer that the device has powered on rather than having any useful information?

    5/04/2017_20:04:28 Z-Wave --------------------------------------------------------------------------------------------------------------------------------------------------------------
    05/04/2017_20:04:31 EBF89EE4-001: S > 06 (ACK)
    05/04/2017_20:04:31 ZNet1: FRAME BEING PLACED IN FramesQ!
    05/04/2017_20:04:31 EBF89EE4-001: RQ < 13-00-49-84-1F-0D-04-11-01-26-8E-85-86-60-27-91-72-77-87-D8
    05/04/2017_20:04:31 ZNet1: PROCESSING - REQUEST - Frame
    05/04/2017_20:04:31 ProcessFrame_STATUS from interface 1 (ZNet1) Type: ZW_APPLICATION_UPDATE, Length: 20, Frame=13-00-49-84-1F-0D-04-11-01-26-8E-85-86-60-27-91-72-77-87-D8
    05/04/2017_20:04:31 ZNet1: REQUEST: ZW_APPLICATION_CONTROLLER_UPDATE, Frame=13-00-49-84-1F-0D-04-11-01-26-8E-85-86-60-27-91-72-77-87-D8
    05/04/2017_20:04:31 Node info frame from node 31
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_SWITCH_MULTILEVEL_V3
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_ASSOCIATION_V2
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_VERSION_V2
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_MULTI_CHANNEL_V3
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_SWITCH_ALL
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_MANUFACTURER_PROPRIETARY
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_MANUFACTURER_SPECIFIC_V2
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_NODE_NAMING
    05/04/2017_20:04:31 ZNet1: Node 31 supports class: COMMAND_CLASS_INDICATOR_V2
    05/04/2017_20:04:32 ZNet2 STARTING API COMMAND: ZW_GET_VERSION
    05/04/2017_20:04:32 ZNet2 ENTERING WaitForFinish (ZW_GET_VERSION/0 of ZWaveAPIThreadProc) with ZW_GET_VERSION/0
    05/04/2017_20:04:32 EBF89EE4-045: S > 01-03-00-15-E9
    05/04/2017_20:04:32 EBF89EE4-045: S > 06 (ACK)
    05/04/2017_20:04:32 ZNet2: FRAME BEING PLACED IN FramesQ!
    05/04/2017_20:04:32 EBF89EE4-045: RS < 10-01-15-5A-2D-57-61-76-65-20-34-2E-30-35-00-01-97
    05/04/2017_20:04:32 ZNet2: PROCESSING - RESPONSE - Frame
    05/04/2017_20:04:32 Process response frame
    05/04/2017_20:04:32 ZNet2: RESPONSE: ZW_GET_VERSION, Frame=10-01-15-5A-2D-57-61-76-65-20-34-2E-30-35-00-01-97
    05/04/2017_20:04:32 ZNet2 LEAVING WaitForFinish TRUE (ZW_GET_VERSION/0 of ZWaveAPIThreadProc) with ZW_GET_VERSION/0
    05/04/2017_20:04:32 EBF89EE4-001: S > 06 (ACK)
    05/04/2017_20:04:32 ZNet1: FRAME BEING PLACED IN FramesQ!
    05/04/2017_20:04:32 EBF89EE4-001: RQ < 09-00-04-00-07-03-25-03-FF-2F
    05/04/2017_20:04:32 ZNet1: PROCESSING - REQUEST - Frame
    05/04/2017_20:04:32 ProcessFrame_STATUS from interface 1 (ZNet1) Type: APPLICATION_COMMAND_HANDLER, Length: 10, Frame=09-00-04-00-07-03-25-03-FF-2F
    05/04/2017_20:04:32 ZNet1: REQUEST: APPLICATION_COMMAND_HANDLER, Frame=09-00-04-00-07-03-25-03-FF-2F
    05/04/2017_20:04:32 ZNet1: ApplicationCommandHandler from node 7 HANDLING: COMMAND_CLASS_SWITCH_BINARY, Payload=25-03-FF-2F
    05/04/2017_20:04:32 ApplicationCommandHandler from node 7 HANDLING: COMMAND_CLASS_SWITCH_BINARY Frame(7)=3

    #2
    I occasionally had devices turning on without any input from events or any manual action. I never got the bottom of it. I had a few problems with my zwave network, I had a few ghost nodes, nodes which were not properly recognised (wrong manufacturer etc). I corrected all this, ran multiple network optimisations, and have had no problems since but its early days for me, so not sure this was the problem. But maybe worth looking into.

    Comment

    Working...
    X