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.

Binary sensor does not always work

OGSOGS Member
I use the binary sensor (fibaro) multiple times in my house and I notice that Homey does not always execute the flow
I use both inputs and sometimes only 1 flow is activated sometimes both
I looked in the log of the z-wave and I see the message comes in Homey just doesn't do anything with it.
[2017-07-09T15:06:49.933Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0101200100
[2017-07-09T15:06:49.978Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
[2017-07-09T15:06:50.100Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010bff
[2017-07-09T15:06:51.681Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
[2017-07-09T15:06:51.718Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
[2017-07-09T15:06:51.760Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff
[2017-07-09T15:07:33.267Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0101200100
[2017-07-09T15:07:33.337Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
[2017-07-09T15:07:33.347Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010bff

It is Node 39 and as you can see it sends out 3 times the message Command_Class_Multi_Channel but I can hear and see (flow contains speech and push notification) only 2 times.
This happens regularly on at least 2 of the binary sensors I have.

Is this a known problem?


Comments

  • casedacaseda Member
    there are not 3 signals... wel actually there is,
    but it is 2 "off" commands, and 1 "on" command, so that it only triggers twice is exactly how it is supposed to.

    if one doesn't trigger, it will probably be the range that is the factor, but that does not show in your log at the moment.
  • OGSOGS Member
    Hi Caseda,

    This morning I had the situation I have seen a couple of times
    The Z-Wave log form node 39
    [2017-07-11T06:18:26.721Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    [2017-07-11T06:18:26.760Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:18:26.768Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0114ff
    [2017-07-11T06:18:39.983Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
    [2017-07-11T06:18:40.041Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:18:40.043Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff

    Both inputs send the same status (open or closed) but only 1 flow has been triggered (1 times speech) 1 time push notification
    The Recent only showed 1 push message but in the Z-Wave both "Voordeur wordt geopend" and "Voordeur slot wordt geopend"


    This is the image as it should have been




    And the Z-wave messages
    [2017-07-11T06:31:01.788Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0202200100
    [2017-07-11T06:31:01.821Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
    [2017-07-11T06:31:01.846Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0115ff
    [2017-07-11T06:31:06.468Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    [2017-07-11T06:31:06.502Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:31:06.520Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0114ff
    [2017-07-11T06:31:09.151Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
    [2017-07-11T06:31:09.201Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:31:09.214Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff
    [2017-07-11T06:31:11.281Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0101200100
    [2017-07-11T06:31:11.352Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
    [2017-07-11T06:31:11.369Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010bff

    I locked and unlocked the door and opened and closed the door (so 4 messsages as it should be)

    I hope you see what I mean?
    I don't think it is an app problem more of a Homey problem, If so I can raise a Git question but want to be sure before doing that


  • OGSOGS Member
    And again with the front door
    [2017-07-11T06:50:30.532Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    [2017-07-11T06:50:30.566Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:50:30.650Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0114ff
    [2017-07-11T06:50:33.679Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
    [2017-07-11T06:50:33.709Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:50:33.839Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff
    [2017-07-11T06:50:39.414Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0101200100
    [2017-07-11T06:50:39.445Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
    [2017-07-11T06:50:39.580Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010bff

    2 times open door/lock and 1 time close door so 3 messages
    But only 1 time push/speech
    pictures similar to previous post
    In this case only the first message was activated

    And the same for the backdoor (also binary sensor)
    [2017-07-11T06:53:57.576Z] Node[9]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
    [2017-07-11T06:53:57.612Z] Node[9]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:53:57.912Z] Node[9]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff
    [2017-07-11T06:54:03.526Z] Node[9]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    [2017-07-11T06:54:03.560Z] Node[9]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:54:03.564Z] Node[9]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0114ff

    I can attach the pictures but they are similar only 1 push message
    In the last case only the last message was activated



  • casedacaseda Member
    edited July 2017
    you only give very tiny snippets, now it is searching a needle in a haystack...

    only see a few commands come by: (we only use scene activation, that was the only way to distinguish between input 1 and 2 when i created the driver)

    node 39 - 0114ff - input 2 close
    node 39 - 010aff - input 1 close
         
    node 39 - 0115ff - input 2 open
    node 39 - 010aff - input 1 close
    node 39 - 010bff - input 1 open
         
    node 39 - 0114ff - input 2 close
    node 39 - 010aff - input 1 close
    node 39 - 010bff - input 1 open
         
    node 9 - 010aff - input 1 close
    node 9 - 0114ff - input 2 close

    given in order as you give them in the logs until now
    homey just doesn't receive more signals... or you are just not giving them here.

    if they are different then you expect, them something else is wrong in your workings, maybe you connected your binary sensors wrong?

    so it might even be some flow mistakes, as the signals do come in, and they will trigger your flows (100% sure about that)

    good to see now the other commands coming in too though... that was not when i was writing the driver.
    might update the driver for that when we are going to update to sdk v2
  • OGSOGS Member
    Indeed this are just snippets but that whats coming in for that specific node, I can attach the complete Z-wave log but that is (I think) not relevant for this problem.
    But When I look at the first (made it Bolt and Italic) I can see both messages coming in, so there is no distance or connection (sensor) problem.
    For this test I only opened the lock and opened the door and left it at that status so only 2 messages should come in
    Input 2 is Voordeur slot status --> message: Voordeur slot wordt geopend
    Input 1 is Voordeur status --> message: Voordeur wordt geopend
    Only the flow linked to "Voordeur status" is started and the flow linked to "voordeur slot" is not triggered.
    As seen on the Recent part of the picture
    OGS said:
    Hi Caseda,

    This morning I had the situation I have seen a couple of times
    The Z-Wave log form node 39
    [2017-07-11T06:18:26.721Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    [2017-07-11T06:18:26.760Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:18:26.768Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0114ff
    [2017-07-11T06:18:39.983Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
    [2017-07-11T06:18:40.041Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:18:40.043Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff

    Both inputs send the same status (open or closed) but only 1 flow has been triggered (1 times speech) 1 time push notification
    The Recent only showed 1 push message but in the Z-Wave both "Voordeur wordt geopend" and "Voordeur slot wordt geopend"


    This is the image as it should have been




    And the Z-wave messages
    [2017-07-11T06:31:01.788Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0202200100
    [2017-07-11T06:31:01.821Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
    [2017-07-11T06:31:01.846Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0115ff
    [2017-07-11T06:31:06.468Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    [2017-07-11T06:31:06.502Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:31:06.520Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x0114ff
    [2017-07-11T06:31:09.151Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01012001ff
    [2017-07-11T06:31:09.201Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
    [2017-07-11T06:31:09.214Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010aff
    [2017-07-11T06:31:11.281Z] Node[39]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0101200100
    [2017-07-11T06:31:11.352Z] Node[39]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
    [2017-07-11T06:31:11.369Z] Node[39]: Received application command for COMMAND_CLASS_SCENE_ACTIVATION, data: 0x010bff

    I locked and unlocked the door and opened and closed the door (so 4 messsages as it should be)

    I hope you see what I mean?
    I don't think it is an app problem more of a Homey problem, If so I can raise a Git question but want to be sure before doing that


    When I do it a second time both flows are triggered (see the lower part of the quote with the picture above)
    The incoming messages are the same
    I can repeat opening and closing the door and I have mostly a 100% correct response from Homey so there are no flow problems (flow is very simple --> input 1 (or 2) is closed --> speech (Voordeur (slot) wordt geopend) and push with the same message. Both speech and push are not executed

    I detect it normally when the unit is not used for a longer time (so no messages from that specific node) so when opening the door in the morning.

    Note, I only have flows on the closing of the contacts
  • OGSOGS Member
    Any news
Sign In or Register to comment.