Z-Wave Fibaro Button (FGPB-101)


#4

When I set my logging to debug, yes, I see logs


#5

Anything that you can post and can help me?


#6

Maybe when I get home later. You got debug on?


#7

No, I’ll do that when I get back home and check it.


#8

Here’s a part of my debug log when I’m pressing the button, I cannot really see something that helps me :confused:

16-10-26 20:29:03 libopenzwave: notif_callback : new notification
16-10-26 20:29:03 libopenzwave: notif_callback : Notification type : 2, nodeId : 5
16-10-26 20:29:03 libopenzwave: addValueId : ValueID : 72057594128105473
16-10-26 20:29:03 libopenzwave: addValueId : GetCommandClassId : 128, GetType : 1
16-10-26 20:29:03 libopenzwave: addValueId : Notification : {‘nodeId’: 5, ‘valueId’: {‘nodeId’: 5, ‘commandClass’: ‘COMMAND_CLASS_BATTERY’, ‘instance’: 1, ‘homeId’: 3469775918, ‘label’: ‘Battery Level’, ‘units’: ‘%’, ‘type’: ‘Byte’, ‘value’: 100, ‘id’: 72057594128105473, ‘readOnly’: True, ‘index’: 0, ‘genre’: ‘User’}, ‘notificationType’: ‘ValueChanged’, ‘homeId’: 3469775918}
16-10-26 20:29:03 libopenzwave: notif_callback : call callback context
16-10-26 20:29:03 openzwave: zwcallback args=[{‘nodeId’: 5, ‘valueId’: {‘nodeId’: 5, ‘commandClass’: ‘COMMAND_CLASS_BATTERY’, ‘instance’: 1, ‘homeId’: 3469775918, ‘label’: ‘Battery Level’, ‘units’: ‘%’, ‘type’: ‘Byte’, ‘value’: 100, ‘id’: 72057594128105473, ‘readOnly’: True, ‘index’: 0, ‘genre’: ‘User’}, ‘notificationType’: ‘ValueChanged’, ‘homeId’: 3469775918}]
16-10-26 20:29:03 openzwave: Z-Wave Notification ValueChanged : {‘nodeId’: 5, ‘valueId’: {‘nodeId’: 5, ‘commandClass’: ‘COMMAND_CLASS_BATTERY’, ‘instance’: 1, ‘homeId’: 3469775918, ‘label’: ‘Battery Level’, ‘units’: ‘%’, ‘type’: ‘Byte’, ‘value’: 100, ‘id’: 72057594128105473, ‘readOnly’: True, ‘index’: 0, ‘genre’: ‘User’}, ‘notificationType’: ‘ValueChanged’, ‘homeId’: 3469775918}
16-10-26 20:29:03 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_alarm_type_5_0, new_state=<state sensor.fibaro_system_fgpb101_button_alarm_type_5_0=0; friendly_name=FIBARO System FGPB101 Button Alarm Type, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.629989+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_alarm_type_5_0=0; friendly_name=FIBARO System FGPB101 Button Alarm Type, node_id=5 @ 2016-10-26T20:28:12.629989+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 FORWARDING <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_alarm_type_5_0, new_state=<state sensor.fibaro_system_fgpb101_button_alarm_type_5_0=0; friendly_name=FIBARO System FGPB101 Button Alarm Type, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.629989+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_alarm_type_5_0=0; friendly_name=FIBARO System FGPB101 Button Alarm Type, node_id=5 @ 2016-10-26T20:28:12.629989+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 WRITING data: {“data”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_alarm_type_5_0”, “new_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_alarm_type_5_0”, “state”: “0”, “last_updated”: “2016-10-26T18:29:03.708592+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button Alarm Type”, “battery_level”: 100, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.629989+00:00”}, “old_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_alarm_type_5_0”, “state”: “0”, “last_updated”: “2016-10-26T18:28:12.629989+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button Alarm Type”, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.629989+00:00”}}, “event_type”: “state_changed”, “origin”: “LOCAL”, “time_fired”: “2016-10-26T18:29:03.708834+00:00”}
16-10-26 20:29:03 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_alarm_level_5_1, new_state=<state sensor.fibaro_system_fgpb101_button_alarm_level_5_1=0; friendly_name=FIBARO System FGPB101 Button Alarm Level, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.677196+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_alarm_level_5_1=0; friendly_name=FIBARO System FGPB101 Button Alarm Level, node_id=5 @ 2016-10-26T20:28:12.677196+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 FORWARDING <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_alarm_level_5_1, new_state=<state sensor.fibaro_system_fgpb101_button_alarm_level_5_1=0; friendly_name=FIBARO System FGPB101 Button Alarm Level, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.677196+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_alarm_level_5_1=0; friendly_name=FIBARO System FGPB101 Button Alarm Level, node_id=5 @ 2016-10-26T20:28:12.677196+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 WRITING data: {“data”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_alarm_level_5_1”, “new_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_alarm_level_5_1”, “state”: “0”, “last_updated”: “2016-10-26T18:29:03.737008+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button Alarm Level”, “battery_level”: 100, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.677196+00:00”}, “old_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_alarm_level_5_1”, “state”: “0”, “last_updated”: “2016-10-26T18:28:12.677196+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button Alarm Level”, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.677196+00:00”}}, “event_type”: “state_changed”, “origin”: “LOCAL”, “time_fired”: “2016-10-26T18:29:03.737292+00:00”}
16-10-26 20:29:03 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2, new_state=<state sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2=0; friendly_name=FIBARO System FGPB101 Button SourceNodeId, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.776994+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2=0; friendly_name=FIBARO System FGPB101 Button SourceNodeId, node_id=5 @ 2016-10-26T20:28:12.776994+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 FORWARDING <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2, new_state=<state sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2=0; friendly_name=FIBARO System FGPB101 Button SourceNodeId, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.776994+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2=0; friendly_name=FIBARO System FGPB101 Button SourceNodeId, node_id=5 @ 2016-10-26T20:28:12.776994+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 WRITING data: {“data”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2”, “new_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2”, “state”: “0”, “last_updated”: “2016-10-26T18:29:03.771140+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button SourceNodeId”, “battery_level”: 100, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.776994+00:00”}, “old_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_sourcenodeid_5_2”, “state”: “0”, “last_updated”: “2016-10-26T18:28:12.776994+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button SourceNodeId”, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.776994+00:00”}}, “event_type”: “state_changed”, “origin”: “LOCAL”, “time_fired”: “2016-10-26T18:29:03.771464+00:00”}
16-10-26 20:29:03 homeassistant.core: Bus:Handling <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_burglar_5_10, new_state=<state sensor.fibaro_system_fgpb101_button_burglar_5_10=254; friendly_name=FIBARO System FGPB101 Button Burglar, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.830660+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_burglar_5_10=254; friendly_name=FIBARO System FGPB101 Button Burglar, node_id=5 @ 2016-10-26T20:28:12.830660+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 FORWARDING <Event state_changed[L]: entity_id=sensor.fibaro_system_fgpb101_button_burglar_5_10, new_state=<state sensor.fibaro_system_fgpb101_button_burglar_5_10=254; friendly_name=FIBARO System FGPB101 Button Burglar, battery_level=100, node_id=5 @ 2016-10-26T20:28:12.830660+02:00>, old_state=<state sensor.fibaro_system_fgpb101_button_burglar_5_10=254; friendly_name=FIBARO System FGPB101 Button Burglar, node_id=5 @ 2016-10-26T20:28:12.830660+02:00>>
16-10-26 20:29:03 homeassistant.components.api: STREAM 1990875064 WRITING data: {“data”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_burglar_5_10”, “new_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_burglar_5_10”, “state”: “254”, “last_updated”: “2016-10-26T18:29:03.811231+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button Burglar”, “battery_level”: 100, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.830660+00:00”}, “old_state”: {“entity_id”: “sensor.fibaro_system_fgpb101_button_burglar_5_10”, “state”: “254”, “last_updated”: “2016-10-26T18:28:12.830660+00:00”, “attributes”: {“friendly_name”: “FIBARO System FGPB101 Button Burglar”, “node_id”: 5}, “last_changed”: “2016-10-26T18:28:12.830660+00:00”}}, “event_type”: “state_changed”, “origin”: “LOCAL”, “time_fired”: “2016-10-26T18:29:03.811599+00:00”}
16-10-26 20:29:03 libopenzwave: notif_callback : end
16-10-26 20:29:03 libopenzwave: notif_callback : new notification
16-10-26 20:29:03 libopenzwave: notif_callback : Notification type : 26, nodeId : 5
16-10-26 20:29:03 libopenzwave: notif_callback : call callback context
16-10-26 20:29:03 openzwave: zwcallback args=[{‘nodeId’: 5, ‘notificationCode’: 3, ‘notificationType’: ‘Notification’, ‘homeId’: 3469775918}]
16-10-26 20:29:03 openzwave: Z-Wave Notification : {‘nodeId’: 5, ‘notificationCode’: 3, ‘notificationType’: ‘Notification’, ‘homeId’: 3469775918}
16-10-26 20:29:03 libopenzwave: notif_callback : end
16-10-26 20:29:03 libopenzwave: notif_callback : new notification
16-10-26 20:29:03 libopenzwave: notif_callback : Notification type : 28, nodeId : 0
16-10-26 20:29:03 libopenzwave: notif_callback : call callback context
16-10-26 20:29:03 openzwave: zwcallback args=[{‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘Starting’, ‘controllerStateInt’: 1, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The command is starting.’}]
16-10-26 20:29:03 openzwave: Z-Wave ControllerCommand : {‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘Starting’, ‘controllerStateInt’: 1, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The command is starting.’}
16-10-26 20:29:03 libopenzwave: notif_callback : end
16-10-26 20:29:03 libopenzwave: notif_callback : new notification
16-10-26 20:29:03 libopenzwave: notif_callback : Notification type : 28, nodeId : 0
16-10-26 20:29:03 libopenzwave: notif_callback : call callback context
16-10-26 20:29:03 openzwave: zwcallback args=[{‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘InProgress’, ‘controllerStateInt’: 6, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The controller is communicating with the other device to carry out the command.’}]
16-10-26 20:29:03 openzwave: Z-Wave ControllerCommand : {‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘InProgress’, ‘controllerStateInt’: 6, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The controller is communicating with the other device to carry out the command.’}
16-10-26 20:29:03 libopenzwave: notif_callback : end
16-10-26 20:29:03 libopenzwave: notif_callback : new notification
16-10-26 20:29:03 libopenzwave: notif_callback : Notification type : 28, nodeId : 0
16-10-26 20:29:03 libopenzwave: notif_callback : call callback context
16-10-26 20:29:03 openzwave: zwcallback args=[{‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘Completed’, ‘controllerStateInt’: 7, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The command has completed successfully.’}]
16-10-26 20:29:03 openzwave: Z-Wave ControllerCommand : {‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘Completed’, ‘controllerStateInt’: 7, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The command has completed successfully.’}
16-10-26 20:29:03 libopenzwave: notif_callback : end
16-10-26 20:29:03 libopenzwave: notif_callback : new notification
16-10-26 20:29:03 libopenzwave: notif_callback : Notification type : 28, nodeId : 0
16-10-26 20:29:03 libopenzwave: notif_callback : call callback context
16-10-26 20:29:03 openzwave: zwcallback args=[{‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘Starting’, ‘controllerStateInt’: 1, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The command is starting.’}]
16-10-26 20:29:03 openzwave: Z-Wave ControllerCommand : {‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘Starting’, ‘controllerStateInt’: 1, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The command is starting.’}
16-10-26 20:29:03 libopenzwave: notif_callback : end
16-10-26 20:29:04 libopenzwave: notif_callback : new notification
16-10-26 20:29:04 libopenzwave: notif_callback : Notification type : 28, nodeId : 0
16-10-26 20:29:04 libopenzwave: notif_callback : call callback context
16-10-26 20:29:04 openzwave: zwcallback args=[{‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘InProgress’, ‘controllerStateInt’: 6, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The controller is communicating with the other device to carry out the command.’}]
16-10-26 20:29:04 openzwave: Z-Wave ControllerCommand : {‘nodeId’: 0, ‘notificationType’: ‘ControllerCommand’, ‘homeId’: 3469775918, ‘controllerError’: ‘None’, ‘controllerState’: ‘InProgress’, ‘controllerStateInt’: 6, ‘controllerErrorInt’: 0, ‘controllerErrorDoc’: ‘None.’, ‘controllerStateDoc’: ‘The controller is communicating with the other device to carry out the command.’}
16-10-26 20:29:04 libopenzwave: notif_callback : end


#9

Did you had time to look at your debug? I’m stuck, i cannot see anything in my debug that can help me.


#10

Since I moved house, it turns out I haven’t set my switches back up yet. However there were definitely SCENE debug messages of which you have none. So I’m not sure how your buttons function or how to use them, sorry.


#11

It seems that fibaro button is unable to control scenes right now with the version of OZW, so no way to make work. OZW 1.6 as I read in domoticz forum will fix that. So either I wait for the 1.6 release or return the button and buy something else :slight_smile:


#12

Has anybody else had any luck getting the FGPB-101 to work with HA? Struggling here as well.


#13

Right now there is no full support for Central Scene Command Class on OZW. I read somewhere that is coming on version 1.6. So you have to wait until then to make it work properly. I returned mine back.


#14

Have anyone found any workarounds or are the FGPB-101 useless with HA?
(I was stupid enough to impulse buy one…)


#15

No workarounds I think until OZW 1.6 comes out, then will probably work with HA too.


#16

I saw they were ~80% done with that milestone, hopefully it will be released soon.
But I also saw this in the comments of the “improve support for CentralScene Command Class”-PullRequest on GitHub.


nechry commented 12 days ago
we also work on the Central Scene CC https://github.com/jeedom/plugin-openzwave/blob/beta/resources/python-openzwave/openzwave/cpp/src/command_classes/CentralScene.cpp

We need do more tests, but is actually working very well.


I wounder if we could take that file and recompile the current version OZW somehow?
Everything used for the compile at first install is still in the /srv/hass/src/ so I guess we should be able to do it?


#17

Well you should be able to clone the beta branch in github and build it. I returned my buttons so I cannot test it. I bought some dash buttons instead. Flic is an alternative if you want a button that can do more than one click in case you are thinking about return it.


#18

So I got the button to work semi stable, without double tabs being recognized yet.

First change your zwcfg config as stated here:
https://home-assistant.io/docs/z-wave/device-specific/

Note: Make sure that home assistant is switched off. Turning off the zwave network is not enough as some articles suggest. If you forget this home assistant will overwrite your changes. I also realized that my changes were overwritten at a later stage.

Then you got to write an automation to pick up changes:

- action:
  - data:
      entity_id: input_boolean.button1_button
    service: input_boolean.turn_on
  alias: Trigger Button
  condition: []
  id: '1515230231092'
  trigger:
  - event_data: {}
    event_type: zwave.scene_activated
    platform: event
- action:
  - data:
      entity_id: input_boolean.button2_button
    service: input_boolean.turn_on
  alias: Trigger Button 1 time
  condition: []
  id: '1515231355136'
  trigger:
  - event_data:
      entity_id: zwave.redbutton
      scene_id: 1
      scene_data: 0
    event_type: zwave.scene_activated
    platform: event

Note:

  • I would use the new automation manager to create the automations. This checks for errors. Also IDs are now needed
  • I use the first automation for debugging, that is to check if I pick up any scene changed event. I have it quite often that I press the button, the button reacts but does not send a scence changed.
  • Note the above article suggests values for the scene_data, however my values are different (also an article below has my values). You can find your values in the open zwave log:

2018-01-06 13:08:06.553 Info, Node005, Received Central Scene set from node 5: scene id=1 in 7800 seconds. Sending event notification.
2018-01-06 13:08:06.554 Detail, Node005, Refreshed Value: old value=7740, new value=7800, type=int

Current issues:

At the moment I am still debugging the set up. The button does not always send scene changes for whatever reason. I have no idea why. It wakes up, reports the battery state, but the central scene line is missing from the logs.

I am also not able yet to get the double triggers to work. The log mentions “new value=7800” which I put into the scene data, yet it does not trigger. So far only the most general automation (ignoring the scene_data) and the long push trigger.

Articles which helped:

https://community.home-assistant.io/t/scene-data-on-fibaro-system-fgpb101-button/28008/7

https://community.home-assistant.io/t/aeotec-wallmote-quad-zw130/12100/19


#19

My Button works fine, even with multiple triggers. I followed the adjustment as described here https://home-assistant.io/docs/z-wave/device-specific/

Afterwards, I could use the different triggers within the automation:

trigger:
platform: event
event_type: zwave.scene_activated
event_data:
entity_id: zwave.fibaro_button_black
scene_id: 1
scene_data: 7680 # 1-click 7680, 2-click 7860, 3-click 7920, 4-click 7980, 5-click 8040, long-click 7800, release-7400

I hope this helps


#20

Thanks for the note.

I guess mine might be broken. Whenever I click I receive something into the stack. When I receive a scene I get a 13 bits long message, when nothing happens then I get a message shorter than this with varying length.
Cannot really be a range issue as I stand next to the stick. Battery is reported 100%. Could then only be that the button does not like the Aeotec Gen 5. But then others should have the same issue.

So I might get it replaced.


#21

What is wrong here ? Nothing happens and it looks similar to your code ?

- alias: Druk Zwarte knop
  hide_entity: true
  trigger:
    event_type: zwave.scene_activated
    platform: event
    event_data:
      entity_id: zwave.zwarte_knop_4
      scene_id: 1
      scene_data: 7680
  action:
    service: media_player.turn_off
    entity_id: media_player.viera_dt60_series

this is my log

2018-02-19 16:37:30.242 Info, Node004, Received Central Scene set from node 4: scene id=1 in 7860 seconds. Sending event notification.
2018-02-19 16:37:30.242 Detail, Node004, Refreshed Value: old value=7680, new value=7860, type=int
2018-02-19 16:37:30.242 Detail, Node004, Changes to this value are not verified
2018-02-19 16:37:30.242 Detail, Node004, Notification: ValueChanged
2018-02-19 16:37:31.109 Detail, Node004,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0x07, 0x82, 0x01, 0x2d
2018-02-19 16:37:31.109 Detail,
2018-02-19 16:37:31.109 Info, Node004, Received Central Scene set from node 4: scene id=1 in 7800 seconds. Sending event notification.
2018-02-19 16:37:31.109 Detail, Node004, Refreshed Value: old value=7860, new value=7800, type=int
2018-02-19 16:37:31.109 Detail, Node004, Changes to this value are not verified
2018-02-19 16:37:31.109 Detail, Node004, Notification: ValueChanged
2018-02-19 16:37:32.445 Warning, WARNING: Out of frame flow! (0x00).  Sending NAK.
2018-02-19 16:37:32.448 Detail, Node004,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0x08, 0x81, 0x01, 0x21
2018-02-19 16:37:32.448 Detail,
2018-02-19 16:37:32.448 Info, Node004, Received Central Scene set from node 4: scene id=1 in 7740 seconds. Sending event notification.
2018-02-19 16:37:32.448 Detail, Node004, Refreshed Value: old value=7800, new value=7740, type=int
2018-02-19 16:37:32.448 Detail, Node004, Changes to this value are not verified
2018-02-19 16:37:32.448 Detail, Node004, Notification: ValueChanged
2018-02-19 16:37:35.291 Detail, Node004,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0x09, 0x80, 0x01, 0x21
2018-02-19 16:37:35.291 Detail,
2018-02-19 16:37:35.291 Info, Node004, Received Central Scene set from node 4: scene id=1 in 7680 seconds. Sending event notification.
2018-02-19 16:37:35.291 Detail, Node004, Refreshed Value: old value=7740, new value=7680, type=int
2018-02-19 16:37:35.291 Detail, Node004, Changes to this value are not verified
2018-02-19 16:37:35.291 Detail, Node004, Notification: ValueChanged
2018-02-19 16:37:36.651 Detail, Node004,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0x0a, 0x80, 0x01, 0x22
2018-02-19 16:37:36.651 Detail,
2018-02-19 16:37:36.651 Info, Node004, Received Central Scene set from node 4: scene id=1 in 7680 seconds. Sending event notification.
2018-02-19 16:37:36.651 Detail, Node004, Refreshed Value: old value=7680, new value=7680, type=int
2018-02-19 16:37:36.651 Detail, Node004, Changes to this value are not verified
2018-02-19 16:37:36.651 Detail, Node004, Notification: ValueChanged
2018-02-19 16:37:37.990 Detail, Node004,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0x0b, 0x80, 0x01, 0x231

#22

Try this:

- alias: "Druk Zwarte knop"
  hide_entity: true
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.zwarte_knop_4
      scene_id: 1
      scene_data: 7680
  action:
    -  service: media_player.turn_off
       data:
         entity_id: media_player.viera_dt60_series

#23

solution

it looks like I have a media_player.panasonic_viera_tv and a media_player.viera_dt60_series

and I was using the wrong. But it’s nowhere defined …