Z-Wave Fibaro Button (FGPB-101)

dimmanramone · October 26, 2016, 8:06am

Last week I bought a fibaro button and I’ve been having trouble to set it up.

Pairing the button with the aeon labs z-wave stick went well, but both HA and OZWCP at first detected the button just as a generic z-wave device, then I found the XML for the button and both HA and OZWCP detected it like a fibaro button when I manually changed the configuration. The XML is the following:

<Node id="5" name="" location="" basic="4" generic="24" specific="1" type="Basic Wall Controller" listening="false" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Probe">
	<Manufacturer id="10f" name="FIBARO System">
		<Product type="f01" id="1000" name="FGPB101" />
	</Manufacturer>
	<CommandClasses>
		<CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1">
			<Instance index="1" />
			<Value type="byte" genre="config" instance="1" index="1" label="Scenes sent to the controller" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="127" value="127">
				<Help>This parameter determines which actions result in sending scene IDs and attributes assigned to them. 1 - Key Pressed 1 time. 2 - Key Pressed 2 times. 4 - Key Pressed 3 times. 8 - Key Pressed 4 times. 16 - Key Pressed 5 times. 32 - Key Held Down. 64 - Key Released. Note: Values of parameter 1 may be combined, e.g. 1+2=3 means that scenes will be sent after pressing the button once or twice. Default: 127 All.</Help>
			</Value>
			<Value type="byte" genre="config" instance="1" index="3" label="Associations in Z-Wave network security mode" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="7" value="7">
				<Help>This parameter defines how commands are sent in specified association groups: as secure or non-secure. Parameter is active only in Z-Wave network security mode. It does not apply to 1st Lifeline group. 1 - 2nd group sent as secure. 2 - 3rd group sent as secure. 4 - 4th group sent as secure. Default: 3 All.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="10" label="Key Pressed 1 time – command sent to 2nd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="3" size="1">
				<Help>This parameter defines commands sent to devices associated in 2nd association group after a single click</Help>
				<Item label="No action" value="0" />
				<Item label="Switch ON" value="1" />
				<Item label="Switch OFF" value="2" />
				<Item label="Switch ON/OFF - alternately" value="3" />
			</Value>
			<Value type="short" genre="config" instance="1" index="11" label="Key Pressed 1 times – value of SWITCH ON command sent to 2nd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
				<Help>This parameter defines value of SWITCH ON command sent to devices in 2nd association group after a single click.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="12" label="Key Pressed 2 time – command sent to 2nd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
				<Help>This parameter defines commands sent to devices associated in 2nd association group after a double click</Help>
				<Item label="No action" value="0" />
				<Item label="Switch ON" value="1" />
				<Item label="Switch OFF" value="2" />
				<Item label="Switch ON/OFF - alternately" value="3" />
			</Value>
			<Value type="short" genre="config" instance="1" index="13" label="Key Pressed 2 times – value of SWITCH ON command sent to 2nd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="99">
				<Help>This parameter defines value of SWITCH ON command sent to devices in 2nd association group after a double click.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="14" label="Key Pressed 3 time – command sent to 2nd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
				<Help>This parameter defines commands sent to devices associated in 2nd association group after a triple click</Help>
				<Item label="No action" value="0" />
				<Item label="Switch ON" value="1" />
				<Item label="Switch OFF" value="2" />
				<Item label="Switch ON/OFF - alternately" value="3" />
			</Value>
			<Value type="short" genre="config" instance="1" index="15" label="Key Pressed 3 times – value of SWITCH ON command sent to 2nd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
				<Help>This parameter defines value of SWITCH ON command sent to devices in 2nd association group after a triple click.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="20" label="Key Pressed 1 time – command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="3" size="1">
				<Help>This parameter defines commands sent to devices associated in 2nd association group after a single click</Help>
				<Item label="No action" value="0" />
				<Item label="Switch ON" value="1" />
				<Item label="Switch OFF" value="2" />
				<Item label="Switch ON/OFF - alternately" value="3" />
			</Value>
			<Value type="short" genre="config" instance="1" index="21" label="Key Pressed 1 times – value of SWITCH ON command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
				<Help>This parameter defines value of SWITCH ON command sent to devices in 3rd association group after a single click.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="22" label="Key Pressed 2 time – command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
				<Help>This parameter defines commands sent to devices associated in 3rd association group after a double click</Help>
				<Item label="No action" value="0" />
				<Item label="Switch ON" value="1" />
				<Item label="Switch OFF" value="2" />
				<Item label="Switch ON/OFF - alternately" value="3" />
			</Value>
			<Value type="short" genre="config" instance="1" index="23" label="Key Pressed 2 times – value of SWITCH ON command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="99">
				<Help>This parameter defines value of SWITCH ON command sent to devices in 3rd association group after a double click.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="24" label="Key Pressed 3 time – command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
				<Help>This parameter defines commands sent to devices associated in 3rd association group after a triple click</Help>
				<Item label="No action" value="0" />
				<Item label="Switch ON" value="1" />
				<Item label="Switch OFF" value="2" />
				<Item label="Switch ON/OFF - alternately" value="3" />
			</Value>
			<Value type="short" genre="config" instance="1" index="25" label="Key Pressed 3 times – value of SWITCH ON command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="1" max="255" value="255">
				<Help>This parameter defines value of SWITCH ON command sent to devices in 3rd association group after a triple click.</Help>
			</Value>
			<Value type="list" genre="config" instance="1" index="29" label=" Key Held Down – command sent to 3rd association group" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="3" size="1">
				<Help>This parameter defines commands sent to devices associated in 3rd association group after holding the button down.</Help>
				<Item label="No action" value="0" />
				<Item label="Brightening" value="1" />
				<Item label="Dimming" value="2" />
				<Item label="Brightening/Dimming - alternately" value="3" />
			</Value>
			<Value type="byte" genre="config" instance="1" index="30" label=" Alarm frame triggers" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="127" value="127">
				<Help>Parameter determines which actions result in sending alarm frames to 4th association group. 1 - Key Pressed 1 time. 2 - Key Pressed 2 times. 4 - Key Pressed 3 times. 8 - Key Pressed 4 times. 16 - Key Pressed 5 times. 32 - Key Held Down. 64 - Key Released. Default: 127 All.</Help>
			</Value>
		</CommandClass>
		<CommandClass id="133" name="COMMAND_CLASS_ASSOCIATION" version="1" request_flags="2">
			<Instance index="1" />
			<Associations num_groups="4">
				<Group index="1" max_associations="1" label="Lifeline" auto="true" />
				<Group index="2" max_associations="5" label="On/Off" auto="false" />
				<Group index="3" max_associations="5" label="Dimmer" auto="false" />
				<Group index="4" max_associations="5" label="Alarm" auto="false" />
			</Associations>
		</CommandClass>
	</CommandClasses>
</Node>

After restarting the HA assistant I could see the button under States in the Developer Tools

and I could see it in the logbook too

Then in OZWCP I could the following:

and when I’m pressing the button the following shows up in the OZWCP log

It seems that the button works and that OZWCP recognize when I press the button but I’m not really sure what to do with all this info, becuase when I’m pressing the button I cannot see any state changing in HA.

Anyone that can guide me how to make it work in HA?

fearoffish · October 26, 2016, 1:26pm

With my NODON switches, they send a Scene ID. In my config I capture this like so:

automation:
- alias: Living Room Switch Button 1 Pressed
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: nodon_crc3100_octan_remote_22
      scene_id: 10
  action:
    service: light.turn_on
    entity_id: light.living_room
    data:
      rgb_color: [255,255,255]
      brightness: 255

Maybe this is the route to go.

dimmanramone · October 26, 2016, 1:33pm

Thanks I’m going to take a look in the scenes.

When you are pressing the button can you see anywhere in HA that you pressed the button i.e Logbook? or a change in the states?

How does the nodon xml look like? and what about in the OZWCP?

fearoffish · October 26, 2016, 1:34pm

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

dimmanramone · October 26, 2016, 1:35pm

Anything that you can post and can help me?

fearoffish · October 26, 2016, 1:39pm

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

dimmanramone · October 26, 2016, 1:44pm

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

dimmanramone · October 26, 2016, 6:35pm

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

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

dimmanramone · October 28, 2016, 7:33am

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

fearoffish · October 28, 2016, 9:54am

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.

dimmanramone · October 28, 2016, 3:04pm

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

ollie · November 24, 2016, 6:11pm

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

dimmanramone · November 29, 2016, 3:46pm

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.

ZyberSE · December 19, 2016, 10:28pm

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

dimmanramone · December 20, 2016, 8:00am

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

ZyberSE · December 20, 2016, 8:11am

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?

dimmanramone · December 20, 2016, 8:23am

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.

CoolKau · January 6, 2018, 12:37pm

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

lithium · January 9, 2018, 9:13pm

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

CoolKau · January 20, 2018, 8:04pm

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.