›
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.

Fibaro Binary Sensor settings?

slashrootslashroot Member
in Devices
Hi,

I have been playing with my Fibaro binary sensor and somehow cannot use it in any flow, at least nothing is triggered.
My goal is to use it for my doorbell which looks according to google quite easy to do :)

Do you need specific parameters set for this device. I had this device working on Vera without issues, though it had trigger sensors in that system like a motion sensor.

I powered the sensor using the P & GND (one next to ANT) wires and did not set any parameters. Associations are 1=1 ,  2=1  , 3 = blanc.

fgbs


When IN1 & IN2 are in contact with each other you will see that back in the logs in Homey.  I also attached a small ledstrip on the out part and that reacts (powers on) when i connect IN1 with IN2.



TimeEntry
2018-01-13T16:58:04.053Z
Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
2018-01-13T16:58:04.054Z
Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[255]}}
2018-01-13T16:58:04.067Z
Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
2018-01-13T16:58:10.715Z
Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0202200100
2018-01-13T16:58:10.716Z
Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[0]}}
2018-01-13T16:58:10.727Z
Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
2018-01-13T16:58:18.974Z
Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
2018-01-13T16:58:18.975Z
Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[255]}}
2018-01-13T16:58:18.985Z
Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
2018-01-13T16:58:27.983Z
Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0202200100
2018-01-13T16:58:27.984Z
Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[0]}}
2018-01-13T16:58:27.997Z
Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
2018-01-13T16:58:41.186Z
Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0202200100
2018-01-13T16:58:41.187Z
Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[0]}}
2018-01-13T16:58:41.205Z
Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
2018-01-13T16:58:51.250Z
Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0202200100
2018-01-13T16:58:51.251Z
Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[0]}}
2018-01-13T16:58:51.261Z
Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x0100
I hope someone will be able to help Thanks

Comments

  • Oy1974Oy1974 Member
    edited January 2018
    Maybe i read it wrong, but you need to conect IN1 or IN2 with the GND
  • slashrootslashroot Member
    I followed the "Rob-shop" manual with one thing different, i do not use the OUTPUT as I don't have a doorbell
    My explanation was a bit wrong. I tried blue (GND) and Green and also blue (GND) Yellow
    I see in logs that something is happening but the Flow does not do anything., I tried on IN1 and IN2  open,close, switched but no message send to my phone.

    Z-wave deurbel op basis van FIBARO binaire sensor
  • slashrootslashroot Member
    I connected the Gnd also to the Out and when i connect blue (GND)) with Green the ledstrip conencted will light up and following is logged:

    2018-01-14T10:27:02.660Z
    		Node[65]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d02022001ff
    2018-01-14T10:27:02.661Z
    		Node[65]: [COMMAND_CLASS_MULTI_CHANNEL] {"Properties1 (Raw)":{"type":"Buffer","data":[2]},"Properties1":{"Source End Point":2,"Res":false},"Properties2 (Raw)":{"type":"Buffer","data":[2]},"Properties2":{"Destination End Point":2,"Bit address":false},"Command Class (Raw)":{"type":"Buffer","data":[32]},"Command Class":32,"Command (Raw)":{"type":"Buffer","data":[1]},"Command":1,"Parameter":{"type":"Buffer","data":[255]}}
    2018-01-14T10:27:02.673Z
    		Node[65]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_BASIC, data 0x01ff
  • Oy1974Oy1974 Member
    is the in the card switchinbg from closed to open? 


    And maybe post to your flow here?
  • slashrootslashroot Member
    Hi,

    The FLOW is quite basic:

    IF Input xxx , AND is not used, THEN Send message to mobile phone

    xxx i tried ( when connecting Blue and Green) with Open 1, Closed 1, Switched 1 , Open 2, Closed 2, Switched 2

    I do not see the status changed if i look in Homey on device status



  • slashrootslashroot Member

  • casedacaseda Member
    edited January 2018
    there is a bug in homey where in certain cases a setting during pairing is not send, fixed in the upcoming experimental release.
    you can fix it by adding this expert parameter:
    14,1,1

    want to read more about it, here is a github issue about this issue:
    https://github.com/athombv/com.fibaro/issues/193

    the commands you see come in where not there when i created the driver a year ago

  • slashrootslashroot Member
    Thanks, I changed the settings but only changed is that device status is different, no response to any open,close,switched in a flow yet.


  • slashrootslashroot Member
    There is no need to create a flow like: IF Input 2 switched, and INPUT 2 Open, THEN send phone message?
  • Oy1974Oy1974 Member
    slashroot said:
    There is no need to create a flow like: IF Input 2 switched, and INPUT 2 Open, THEN send phone message?

    nope

  • slashrootslashroot Member
    So IF Input 2 switched the send message to mobile is enough
  • slashrootslashroot Member
    I am able to trigger the flow now by using IF INPUT2 switched. Is it normal that you need to wait quite long before trigegring again, as it does not always trigger if you try multiple times
  • mikronmikron Member
    I borrow this if it´s ok.

    I'm trying to include my universal binary sensor to homey. Has reset the sensor, but it refuses to be included. What is wrong?
  • JPeJPe Member
    edited February 2018
    When a Z-Wave device cannot be included, always remove the device from Homey (even if it was never included) via the Tab Settings/Z-Wave/ and choose "Remove device".
  • mikronmikron Member
    Thank you! It solved the problem.
  • VeldkornetVeldkornet Member
    edited March 2018
    @slashroot Any problems after the update to Homey 1.5.8?

    My doorbell doesn't work anymore now :neutral:
Sign In or Register to comment.