Automation works occasionally + other things that I'm confused about

maykino · June 26, 2019, 10:48pm

Hello everyone, I have some basic knowledge of this technology but I may be missing some important things so pardon me for any mistakes and please point me in the right direction.

I recently helped a friend and installed a set up a Fibaro automation with the super expensive unit to manage it. I was pretty happy how everything worked out however as a software engineer I always try to find new ways to improve things. That is why the super expensive home unit seemed to be obsolete in my own setup when I decided to automate my house.

I bought a raspberry pi unit and I flashed the memory card with a Hassbian OS. I started adding devices one by one:

Garage:

Aoetec Dual Switch: https://amzn.to/2Yhan5t
Dome motion sensor: https://amzn.to/2X6MCR4
Raspberry PI with Aotec Z Stick
Hallway 1:
Aotec nano dimmer
Fibaro motion sensor

I added the same cookbook automation template for both rooms: turn_on_light_for_10_minutes_when_motion_detected

Issues:

The garage automation works perfectly in 90% cases however sometimes it takes even 5 seconds to turn the lights on. It’s completely random.
The hallway automation almost never works. I’m actually surprised when the lights get turned on.
The interface seem to be showing old information from time to time. For example when I added a new dimmer it became visible in the system after I rebooted the whole unit. Also after each reboot the HA interface is not showing any devices until a few mins later.
Why the same device is showing under different names in the system. For example it’s showing it under Light, Z-Wave and Switch. Changing the name of one doesn’t change it for the others. I feel like I’m missing something here:

How to properly add a new Z-Wave device to Home Assistant? Should I unplug the Z-Stick from Raspberry PI and walk up to the new module and pair it? Do I have to click on “Add node” in HA before or after I perform the above steps?
What is this button in the Z-Wave panel for?
While adding a new device is there a way to see the live log of exchanging information? That is one part that I liked about Fibaro that it showed right away that it found the device.

Thank you in advance.

M.

petro · June 27, 2019, 12:20pm

Sometimes zwave networks have latency. It depends on the device and how much traffic is currently happening on the network. You may have a device that wont stfu and is crowding the network. That’s the first place I would look.

Post the automation.

Zwave network can take up to 2 minutes to intialize. This is normal. Also, you are running on a pi, pi’s are slow. I moved to a intel NUC i5 and my startup is ~15 seconds. On the pi, my startup was 3-5 minutes.

Many zwave devices have more than 1 sensor built into it. I don’t have that dimmer so I cant speak for the light & the switch being created. I can tell you that the zwave section is purely to show you the status of the zwave node and it’s information. At a minimum every device will have a z-wave node device and the actual device it creates (switch, sensor, light, etc).

I typically:

shut down home assistant & the system.
Walk around the house and add the device.
Start up home asssitant. Typically don’t even have to add the node, it’s already discovered because it’s included on the z-wave network. (unless that process has changed, in which You’d then press the ‘add a node’ button).

I haven’t added a node in about a year so this process may have changed beyond step 3. But step 1 and 2 would not have changed.

It does nothing. It’s a byproduct of groups. You can adjust your interface to remove it. I believe the property is show_header_toggle or something of that nature.

There is a zwave log at the bottom of the zwave page.

maykino · June 28, 2019, 2:50am

Thank you so much for your time and I appreciate explaining everything.

- alias: Turn on garage light when there is movement
  trigger:
    platform: state
    entity_id: binary_sensor.elexa_consumer_products_inc_dome_motion_detector_sensor
    to: 'on'
  action:
    service: homeassistant.turn_on
    entity_id: switch.aeon_labs_zw132_dual_nano_switch_switch

- alias: Turn off garage light 2 minutes after last movement
  trigger:
    platform: state
    entity_id: binary_sensor.elexa_consumer_products_inc_dome_motion_detector_sensor
    to: 'off'
    for:
      minutes: 2
  action:
    service: homeassistant.turn_off
    entity_id: switch.aeon_labs_zw132_dual_nano_switch_switch

- alias: Turn on staircase 1 light when there is movement
  trigger:
    platform: state
    entity_id: binary_sensor.fibaro_system_fgms001_zw5_motion_sensor_sensor
    to: 'on'
  action:
    service: homeassistant.turn_on
    entity_id: switch.aeon_labs_zw111_nano_dimmer_switch

- alias: Turn off staircase 1 light 2 minutes after last movement
  trigger:
    platform: state
    entity_id: binary_sensor.fibaro_system_fgms001_zw5_motion_sensor_sensor
    to: 'off'
    for:
      minutes: 2
  action:
    service: homeassistant.turn_off
    entity_id: switch.aeon_labs_zw111_nano_dimmer_switch

However when I take the sensor off the wall and put it on my desk the automation works perfectly fine. For some reason it doesn’t work when it’s hanging on the wall. I tried to use the built in Fibaro range feature and it shows that it’s connecting directly to the main unit so it doesn’t seem like a range issue. Also there are two other z-wave devices nearby that work perfectly fine. Also, the above automation doesn’t seem to work when the light gets turned on manually by using the switch. What could be wrong?

Everything else I was able to figure out from your answers above but there is one more thing. It seems like the HA control panel doesn’t show the right state of the switches. Sometimes it shows that the light is on when it’s turned off and vice versa.

Thanks again!

petro · June 28, 2019, 11:54am

That should be switch.turn_on and switch.turn_off.

This can be a number of things. First thing I would check is the states page and verify that Home assistant sees the correct state. If it does, it’s just a refresh issue, refresh the browser and you’ll be good to go. If home assistant doesn’t see the correct state, investigate your zwave mesh and find where the drop outs are.

maykino · July 3, 2019, 4:14am

Are you sure?

I’m ready to give up. I have been playing with this for a week now and I can’t get it to the state where everything works as expected. Since day 1 I have issues with automation working randomly. Then when somehow I fix one automation the other one stops working. For example the garage automation doesn’t work at all but it worked before. There are currently 3 Fibaro motion sensors triggering the hallway light. This is the only one that works 2-3 times a day totally randomly.

I just checked the log and it looks like there are plenty of errors there:

2019-07-03 05:06:58.835 Info, Node001, Sending (Command) message (Callback ID=0x3c, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x3c, 0x8f
2019-07-03 05:06:59.835 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-03 05:06:59.835 Detail, Node001, Removing current message
2019-07-03 05:06:59.836 Detail, Node001, Notification: Notification - TimeOut
2019-07-03 05:06:59.837 Detail, Notification: ControllerCommand - Error - Failed
2019-07-03 05:06:59.838 Info, Requesting Neighbor Update for node 2
2019-07-03 05:06:59.838 Detail,
2019-07-03 05:06:59.838 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:06:59.838 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:06:59.838 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:06:59.839 Info, Requesting Neighbor Update for node 3
2019-07-03 05:06:59.839 Detail,
2019-07-03 05:06:59.839 Detail, Node003, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:06:59.839 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:06:59.839 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:06:59.839 Info, Requesting Neighbor Update for node 4
2019-07-03 05:06:59.839 Detail, Node004, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=4): 0x01, 0x05, 0x00, 0x48, 0x04, 0x3f, 0x89
2019-07-03 05:06:59.839 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:06:59.840 Detail,
2019-07-03 05:06:59.840 Info, Node004, Sending (Command) message (Callback ID=0x3f, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=4): 0x01, 0x05, 0x00, 0x48, 0x04, 0x3f, 0x89
2019-07-03 05:07:00.840 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-03 05:07:00.840 Detail, Node004, Removing current message
2019-07-03 05:07:00.840 Detail, Node004, Notification: Notification - TimeOut
2019-07-03 05:07:00.843 Detail, Notification: ControllerCommand - Error - Failed
2019-07-03 05:07:00.844 Info, Requesting Neighbor Update for node 6
2019-07-03 05:07:00.844 Detail, Node006, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=6): 0x01, 0x05, 0x00, 0x48, 0x06, 0x40, 0xf4
2019-07-03 05:07:00.844 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:00.844 Detail,
2019-07-03 05:07:00.844 Info, Node006, Sending (Command) message (Callback ID=0x40, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=6): 0x01, 0x05, 0x00, 0x48, 0x06, 0x40, 0xf4
2019-07-03 05:07:01.845 Error, Node006, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-03 05:07:01.845 Detail, Node006, Removing current message
2019-07-03 05:07:01.845 Detail, Node006, Notification: Notification - TimeOut
2019-07-03 05:07:01.847 Detail, Notification: ControllerCommand - Error - Failed
2019-07-03 05:07:01.848 Info, Requesting Neighbor Update for node 7
2019-07-03 05:07:01.848 Detail,
2019-07-03 05:07:01.848 Detail, Node007, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:01.848 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:01.848 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:01.849 Info, Requesting Neighbor Update for node 8
2019-07-03 05:07:01.849 Detail, Node008, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=8): 0x01, 0x05, 0x00, 0x48, 0x08, 0x42, 0xf8
2019-07-03 05:07:01.849 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:01.849 Detail,
2019-07-03 05:07:01.849 Info, Node008, Sending (Command) message (Callback ID=0x42, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=8): 0x01, 0x05, 0x00, 0x48, 0x08, 0x42, 0xf8
2019-07-03 05:07:02.849 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-03 05:07:02.850 Detail, Node008, Removing current message
2019-07-03 05:07:02.850 Detail, Node008, Notification: Notification - TimeOut
2019-07-03 05:07:02.852 Detail, Notification: ControllerCommand - Error - Failed
2019-07-03 05:07:02.853 Info, Requesting Neighbor Update for node 9
2019-07-03 05:07:02.853 Detail,
2019-07-03 05:07:02.853 Detail, Node009, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.853 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.853 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.853 Info, Requesting Neighbor Update for node 10
2019-07-03 05:07:02.853 Detail,
2019-07-03 05:07:02.853 Detail, Node010, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.854 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.854 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.854 Info, Requesting Neighbor Update for node 12
2019-07-03 05:07:02.854 Detail,
2019-07-03 05:07:02.854 Detail, Node012, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.854 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.854 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.854 Info, Requesting Neighbor Update for node 13
2019-07-03 05:07:02.855 Detail,
2019-07-03 05:07:02.855 Detail, Node013, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.855 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.855 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.855 Info, Requesting Neighbor Update for node 14
2019-07-03 05:07:02.855 Detail,
2019-07-03 05:07:02.855 Detail, Node014, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.855 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.855 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.856 Info, Requesting Neighbor Update for node 15
2019-07-03 05:07:02.856 Detail,
2019-07-03 05:07:02.856 Detail, Node015, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.856 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.856 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.856 Info, Requesting Neighbor Update for node 16
2019-07-03 05:07:02.856 Detail,
2019-07-03 05:07:02.856 Detail, Node016, Queuing (Controller) Request Node Neighbor Update
2019-07-03 05:07:02.856 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.856 Detail, Notification: ControllerCommand - Sleeping
2019-07-03 05:07:02.857 Info, Requesting Neighbor Update for node 17
2019-07-03 05:07:02.857 Detail, Node017, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=17): 0x01, 0x05, 0x00, 0x48, 0x11, 0x4a, 0xe9
2019-07-03 05:07:02.857 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:02.857 Detail,
2019-07-03 05:07:02.857 Info, Node017, Sending (Command) message (Callback ID=0x4a, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=17): 0x01, 0x05, 0x00, 0x48, 0x11, 0x4a, 0xe9
2019-07-03 05:07:03.857 Error, Node017, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-03 05:07:03.857 Detail, Node017, Removing current message
2019-07-03 05:07:03.857 Detail, Node017, Notification: Notification - TimeOut
2019-07-03 05:07:03.859 Detail, Notification: ControllerCommand - Error - Failed
2019-07-03 05:07:03.860 Info, Requesting Neighbor Update for node 18
2019-07-03 05:07:03.860 Detail, Node018, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=18): 0x01, 0x05, 0x00, 0x48, 0x12, 0x4b, 0xeb
2019-07-03 05:07:03.860 Detail, Notification: ControllerCommand - Starting
2019-07-03 05:07:03.860 Detail,
2019-07-03 05:07:03.860 Info, Node018, Sending (Command) message (Callback ID=0x4b, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=18): 0x01, 0x05, 0x00, 0x48, 0x12, 0x4b, 0xeb
2019-07-03 05:07:04.861 Error, Node018, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-03 05:07:04.861 Detail, Node018, Removing current message
2019-07-03 05:07:04.861 Detail, Node018, Notification: Notification - TimeOut
2019-07-03 05:07:04.863 Detail, Notification: ControllerCommand - Error - Failed

My current automations.yaml:

- alias: Turn on garage lights when there is movement
  trigger:
  - platform: state
    entity_id: binary_sensor.elexa_consumer_products_inc_dome_motion_detector_sensor, binary_sensor.elexa_consumer_products_inc_dome_motion_detector_sensor_2 
    to: 'on'
  action:
  - service: homeassistant.turn_on
    data:
      entity_id:
        - switch.aeon_labs_zw132_dual_nano_switch_switch
  - service: timer.start
    data:
      entity_id: timer.garage
- alias: Turn off garage lights 1 minutes after trigger
  trigger:
    platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.garage
  action:
    service: homeassistant.turn_off
    data:
      entity_id:
        - switch.aeon_labs_zw132_dual_nano_switch_switch

- alias: Turn on hallway lights when there is movement
  trigger:
  - platform: state
    entity_id: sensor.fibaro_system_fgms001_zw5_motion_sensor_burglar_3, sensor.fibaro_system_fgms001_zw5_motion_sensor_burglar_2, sensor.fibaro_system_fgms001_zw5_motion_sensor_burglar
    to: '8'
  action:
  - service: homeassistant.turn_on
    data:
      entity_id:
        - light.hallway1
  - service: timer.start
    data:
      entity_id: timer.hallway1
- alias: Turn off hallway 1 lights 1 minutes after trigger
  trigger:
    platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.hallway1
  action:
    service: homeassistant.turn_off
    data:
      entity_id:
        - light.hallway1

The timers are in the configuration.yaml:

tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
timer:
  hallway1:
    duration: '00:01:00'
  garage:
    duration: '00:01:00'
  living_room:
    duration: '00:01:00'

maykino · July 3, 2019, 5:36am

Okay, I think I found something. I have two motion sensors in the garage that are set to trigger the light when they their status changes to “on”. I’m looking at the stats of the sensor that almost never triggers anything and it looks like it rarely turns off during the day:

It’s in the garage so there is no chance that there is constant motion there.

sparkydave · July 3, 2019, 6:09am

check the device settings in the z-wave panel. Using the devices user manual, check the parameters in the section circled below

maykino · July 3, 2019, 4:32pm

Thanks. I’m going to check it shortly.

Now, I’m trying to get to work room by room. The garage seems to work fine now after I’m using the burglar entity to trigger the lights but for some reason I’m having issues getting everything else to work. In the garage I use the https://amzn.to/2X6MCR4 motion sensor and everywhere else I use the Fibaro motion sensors https://amzn.to/2LA96TM

It makes me think I’m doing something wrong with Fibaro motion sensors. The following Living Room automation doesn’t work at all now although I see that there is a burglar alert in the logs. The first part of the code is the garage automation and then there is the living room that doesn’t work.

- alias: Turn on garage lights when there is movement
  trigger:
  - platform: state
    entity_id: sensor.elexa_consumer_products_inc_dome_motion_detector_burglar, sensor.elexa_consumer_products_inc_dome_motion_detector_burglar_2
    to: '8'
  action:
  - service: homeassistant.turn_on
    data:
      entity_id:
        - switch.garage_light
  - service: timer.start
    data:
      entity_id: timer.garage
- alias: Turn off garage lights 1 minutes after trigger
  trigger:
    platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.garage
  action:
    service: homeassistant.turn_off
    data:
      entity_id:
        - switch.garage_light

- alias: Turn on living room lights when there is movement
  trigger:
  - platform: state
    entity_id: sensor.fibaro_system_fgms001_zw5_motion_sensor_burglar_3
    to: '8'
  action:
  - service: homeassistant.turn_on
    data:
      entity_id:
        - light.living_room
  - service: timer.start
    data:
      entity_id: timer.living_room
- alias: Turn off living room 1 lights 1 minutes after trigger
  trigger:
    platform: event
    event_type: timer.finished
    event_data:
      entity_id: timer.living_room
  action:
    service: homeassistant.turn_off
    data:
      entity_id:
        - light.living_room

Logs:

2019-07-03 17:39:17.607 Detail, Node016,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x10, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x08, 0x00, 0x69
2019-07-03 17:39:17.607 Detail,
2019-07-03 17:39:17.607 Info, Node016, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:8, status=255
2019-07-03 17:39:17.607 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:17.607 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:17.607 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:17.607 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:17.608 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:17.608 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:17.608 Detail, Node016, Refreshed Value: old value=8, new value=8, type=byte
2019-07-03 17:39:17.608 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:17.608 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:17.627 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:17.647 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:17.666 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:17.827 Detail,   Received: 0x01, 0x07, 0x00, 0x13, 0x98, 0x01, 0x03, 0x79, 0x08
2019-07-03 17:39:17.827 Detail,   ZW_SEND_DATA Request with callback ID 0x98 received (expected 0x00)
2019-07-03 17:39:17.827 Warning, WARNING: Unexpected Callback ID received
2019-07-03 17:39:20.727 Detail, Node016,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x30, 0x03, 0xff, 0x0c, 0x25
2019-07-03 17:39:20.728 Detail,
2019-07-03 17:39:20.728 Info, Node016, Received SensorBinary report: Sensor:12 State=On
2019-07-03 17:39:20.728 Detail, Node016, Refreshed Value: old value=true, new value=true, type=bool
2019-07-03 17:39:20.728 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:20.728 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:23.902 Detail, Node016,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x10, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x08, 0x00, 0x69
2019-07-03 17:39:23.902 Detail,
2019-07-03 17:39:23.902 Info, Node016, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:8, status=255
2019-07-03 17:39:23.902 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:23.902 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:23.902 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:23.902 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:23.903 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:23.903 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:23.903 Detail, Node016, Refreshed Value: old value=8, new value=8, type=byte
2019-07-03 17:39:23.903 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:23.903 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:23.922 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:23.942 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:23.961 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:23.981 Detail, Node016,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x30, 0x03, 0xff, 0x0c, 0x25
2019-07-03 17:39:23.981 Detail,
2019-07-03 17:39:23.981 Info, Node016, Received SensorBinary report: Sensor:12 State=On
2019-07-03 17:39:23.981 Detail, Node016, Refreshed Value: old value=true, new value=true, type=bool
2019-07-03 17:39:23.981 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:23.981 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:55.518 Detail, Node016,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x10, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x00, 0x01, 0x08, 0x74
2019-07-03 17:39:55.519 Detail,
2019-07-03 17:39:55.523 Info, Node016, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:0, status=255
2019-07-03 17:39:55.524 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:55.524 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:55.524 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:55.524 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:55.524 Detail, Node016, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:39:55.524 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:55.524 Detail, Node016, Refreshed Value: old value=8, new value=0, type=byte
2019-07-03 17:39:55.524 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:55.524 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:55.545 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:55.564 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:55.584 Detail, Node016, Notification: ValueChanged
2019-07-03 17:39:55.603 Detail, Node016,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x10, 0x04, 0x30, 0x03, 0x00, 0x0c, 0xda
2019-07-03 17:39:55.604 Detail,
2019-07-03 17:39:55.604 Info, Node016, Received SensorBinary report: Sensor:12 State=Off
2019-07-03 17:39:55.604 Detail, Node016, Refreshed Value: old value=true, new value=false, type=bool
2019-07-03 17:39:55.604 Detail, Node016, Changes to this value are not verified
2019-07-03 17:39:55.604 Detail, Node016, Notification: ValueChanged
2019-07-03 17:40:09.035 Info, Node008, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Dimming Duration - 5 - 1 - 255
2019-07-03 17:40:09.036 Detail, Node008, Refreshed Value: old value=255, new value=255, type=byte
2019-07-03 17:40:09.036 Detail, Node008, Changes to this value are not verified
2019-07-03 17:40:09.036 Detail, Node008, Notification: ValueChanged
2019-07-03 17:40:09.038 Info, Node008, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 0
2019-07-03 17:40:09.038 Info, Node008, SwitchMultilevel::Set - Setting to level 0
2019-07-03 17:40:09.038 Info, Node008,   Duration: Default
2019-07-03 17:40:09.039 Detail, Node008, Queuing (Send) SwitchMultilevelCmd_Set (Node=8): 0x01, 0x0b, 0x00, 0x13, 0x08, 0x04, 0x26, 0x01, 0x00, 0xff, 0x25, 0x9a, 0x8c
2019-07-03 17:40:09.039 Detail, Node008, Queuing (Send) SwitchMultilevelCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x26, 0x02, 0x25, 0x9b, 0x75
2019-07-03 17:40:09.068 Detail,
2019-07-03 17:40:09.069 Info, Node008, Sending (Send) message (Callback ID=0x9a, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=8): 0x01, 0x0b, 0x00, 0x13, 0x08, 0x04, 0x26, 0x01, 0x00, 0xff, 0x25, 0x9a, 0x8c
2019-07-03 17:40:09.077 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-07-03 17:40:09.078 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-07-03 17:40:09.094 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x9a, 0x00, 0x00, 0x02, 0x73
2019-07-03 17:40:09.094 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x9a received (expected 0x9a)
2019-07-03 17:40:09.094 Info, Node008, Request RTT 25 Average Request RTT 99
2019-07-03 17:40:09.094 Detail,   Expected callbackId was received
2019-07-03 17:40:09.094 Detail,   Expected reply was received
2019-07-03 17:40:09.094 Detail,   Message transaction complete
2019-07-03 17:40:09.094 Detail,
2019-07-03 17:40:09.095 Detail, Node008, Removing current message
2019-07-03 17:40:09.095 Detail,
2019-07-03 17:40:09.095 Info, Node008, Sending (Send) message (Callback ID=0x9b, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x26, 0x02, 0x25, 0x9b, 0x75
2019-07-03 17:40:09.103 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-07-03 17:40:09.103 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-07-03 17:40:09.119 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x9b, 0x00, 0x00, 0x03, 0x73
2019-07-03 17:40:09.119 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x9b received (expected 0x9b)
2019-07-03 17:40:09.119 Info, Node008, Request RTT 24 Average Request RTT 61
2019-07-03 17:40:09.120 Detail,   Expected callbackId was received
2019-07-03 17:40:09.131 Detail, Node008,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x26, 0x03, 0x00, 0xdc
2019-07-03 17:40:09.131 Detail,
2019-07-03 17:40:09.131 Info, Node008, Response RTT 36 Average Response RTT 96
2019-07-03 17:40:09.131 Info, Node008, Received SwitchMultiLevel report: level=0
2019-07-03 17:40:09.131 Detail, Node008, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:40:09.131 Detail, Node008, Changes to this value are not verified
2019-07-03 17:40:09.131 Detail, Node008,   Expected reply and command class was received
2019-07-03 17:40:09.131 Detail, Node008,   Message transaction complete
2019-07-03 17:40:09.131 Detail,
2019-07-03 17:40:09.132 Detail, Node008, Removing current message
2019-07-03 17:40:09.132 Detail, Node008, Notification: ValueChanged
2019-07-03 17:40:10.047 Info, mgr,     Refreshing node 8: COMMAND_CLASS_SWITCH_MULTILEVEL index = 0 instance = 1 (to confirm a reported change)
2019-07-03 17:40:10.047 Detail, Node008, Queuing (Send) SwitchMultilevelCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x26, 0x02, 0x25, 0x9c, 0x72
2019-07-03 17:40:10.048 Detail,
2019-07-03 17:40:10.048 Info, Node008, Sending (Send) message (Callback ID=0x9c, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x26, 0x02, 0x25, 0x9c, 0x72
2019-07-03 17:40:10.056 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-07-03 17:40:10.056 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-07-03 17:40:10.072 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x9c, 0x00, 0x00, 0x02, 0x75
2019-07-03 17:40:10.072 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x9c received (expected 0x9c)
2019-07-03 17:40:10.073 Info, Node008, Request RTT 24 Average Request RTT 42
2019-07-03 17:40:10.073 Detail,   Expected callbackId was received
2019-07-03 17:40:10.086 Detail, Node008,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x26, 0x03, 0x00, 0xdc
2019-07-03 17:40:10.086 Detail,
2019-07-03 17:40:10.086 Info, Node008, Response RTT 38 Average Response RTT 67
2019-07-03 17:40:10.087 Info, Node008, Received SwitchMultiLevel report: level=0
2019-07-03 17:40:10.087 Detail, Node008, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:40:10.087 Detail, Node008, Changes to this value are not verified
2019-07-03 17:40:10.087 Detail, Node008,   Expected reply and command class was received
2019-07-03 17:40:10.087 Detail, Node008,   Message transaction complete
2019-07-03 17:40:10.087 Detail,
2019-07-03 17:40:10.087 Detail, Node008, Removing current message
2019-07-03 17:40:10.087 Detail, Node008, Notification: ValueChanged
2019-07-03 17:40:11.053 Info, mgr,     Refreshing node 8: COMMAND_CLASS_SWITCH_MULTILEVEL index = 0 instance = 1 (to confirm a reported change)
2019-07-03 17:40:11.053 Detail, Node008, Queuing (Send) SwitchMultilevelCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x26, 0x02, 0x25, 0x9d, 0x73
2019-07-03 17:40:11.053 Detail,
2019-07-03 17:40:11.053 Info, Node008, Sending (Send) message (Callback ID=0x9d, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x26, 0x02, 0x25, 0x9d, 0x73
2019-07-03 17:40:11.061 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-07-03 17:40:11.062 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-07-03 17:40:11.078 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x9d, 0x00, 0x00, 0x02, 0x74
2019-07-03 17:40:11.078 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x9d received (expected 0x9d)
2019-07-03 17:40:11.078 Info, Node008, Request RTT 24 Average Request RTT 33
2019-07-03 17:40:11.078 Detail,   Expected callbackId was received
2019-07-03 17:40:11.089 Detail, Node008,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x26, 0x03, 0x00, 0xdc
2019-07-03 17:40:11.089 Detail,
2019-07-03 17:40:11.089 Info, Node008, Response RTT 35 Average Response RTT 51
2019-07-03 17:40:11.090 Info, Node008, Received SwitchMultiLevel report: level=0
2019-07-03 17:40:11.090 Detail, Node008, Refreshed Value: old value=0, new value=0, type=byte
2019-07-03 17:40:11.090 Detail, Node008, Changes to this value are not verified
2019-07-03 17:40:11.090 Detail, Node008,   Expected reply and command class was received
2019-07-03 17:40:11.090 Detail, Node008,   Message transaction complete
2019-07-03 17:40:11.090 Detail,
2019-07-03 17:40:11.090 Detail, Node008, Removing current message
2019-07-03 17:40:11.090 Detail, Node008, Notification: ValueChanged

Just by looking at the logs it looks like the Fibaro sensor (Node016) gets triggered and sends a message to the Node008 (Living room switch).

sparkydave · July 3, 2019, 10:18pm

Rather than ‘burgler’ I set an option in my z-wave motion detectors to make them send a ‘basic’ report which then gives you a nice binary_sensor entity. You can do it either way but I have found the binary_sensor to be very stable. Not sure what option number it is for the Fibaro as I have Aeotec devices. It will be in the manual though, worth trying.