Setting scenes on Z-Wave Wall Switch ZHC5010

I bought this Z-Wace Wall Switch ZHC5010 and added it to my Z-Wave network (AEON LABS Z-Stick GEN5 USB on RPI2 running HA 0.28.1.

http://products.z-wavealliance.org/products/1779/configs
http://products.z-wavealliance.org/products/1779/assoc?noFilename=True

The device is added, recognized and appears in the HA GUI. From the GUI I can control the Wall Switch (toggle the relay and LEDs). But going the other way!!! NO CONNECTION!

  1. HA won’t trigger on state changes:

    • alias: Turn on kitchen lights OFF button
      trigger:

      • platform: state
        entity_id: switch.unknown_id0234_unknown_type0003_id010a_switch_5_3
        to: ‘off’
        action:
        service: light.turn_off
        entity_id: light.lamp9
    • alias: Turn on kitchen lights ON button
      trigger:

      • platform: state
        entity_id: switch.unknown_id0234_unknown_type0003_id010a_switch_5_3
        to: ‘on’
        action:
        service: light.turn_on
        entity_id: light.lamp9
  2. And HA won’t catch events/scenes:

    • alias: A1_ON
      trigger:
      platform: event
      event_type: zwave.scene_activated
      event_data:
      object_id: switch.unknown_id0234_unknown_type0003_id010a_switch_5
      scene_id: 1
      action:
      service: light.turn_on
      entity_id: light.lamp1

    • alias: A1_OFF
      trigger:
      platform: event
      event_type: zwave.scene_activated
      event_data:
      object_id: switch.unknown_id0234_unknown_type0003_id010a_switch_5
      scene_id: 2
      action:
      service: light.turn_off
      entity_id: light.lamp1

The log reads on button pressed (first on, the off):
2016-09-12 09:01:20.900 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0x6c, 0x00, 0x02, 0xc6
2016-09-12 09:01:20.900 Detail,
2016-09-12 09:01:20.900 Info, Node005, Received Central Scene set from node 5: scene id=2 in 0 seconds. Sending event notification.
2016-09-12 09:01:20.901 Warning, Node005, No ValueID created for Scene 2
2016-09-12 09:01:23.761 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0x6d, 0x00, 0x02, 0xc7
2016-09-12 09:01:23.761 Detail,
2016-09-12 09:01:23.780 Info, Node005, Received Central Scene set from node 5: scene id=2 in 0 seconds. Sending event notification.
2016-09-12 09:01:23.780 Warning, Node005, No ValueID created for Scene 2

What am I doing wrong? Do I need to define scenes manually?

Thanks in advance!
Tonkin

make sure that your zwave controller (rpi) has its node ID added to the group of the button that you want the receive updates on.

Pardon my ignorance (Im new at this). How is this done? Do I use HA, another tool or do I alter files directly on the rpi?

Best regards,
Tonkin

Do you mean like this? (Using Domoticz)

/Tonkin

Button press on, then off now yields:

2016-09-12 14:49:50.766 Detail, Node005, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x5b, 0x03, 0xce, 0x00, 0x02, 0x64
2016-09-12 14:49:50.766 Detail,
2016-09-12 14:49:50.766 Info, Node005, Received Central Scene set from node 5: scene id=2 in 0 seconds. Sending event notification.
2016-09-12 14:49:50.766 Warning, Node005, No ValueID created for Scene 2
2016-09-12 14:49:50.790 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x20, 0x03, 0x00, 0xd7
2016-09-12 14:49:50.790 Detail,
2016-09-12 14:49:50.790 Info, Node005, Received Basic report from node 5: level=0
2016-09-12 14:49:50.790 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x4d, 0xad
2016-09-12 14:49:50.790 Detail,
2016-09-12 14:49:50.791 Info, Node005, Sending (Send) message (Callback ID=0x4d, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x4d, 0xad
2016-09-12 14:49:50.800 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-09-12 14:49:50.800 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2016-09-12 14:49:50.814 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x20, 0x01, 0x00, 0xd5
2016-09-12 14:49:50.814 Detail,
2016-09-12 14:49:50.814 Info, Node005, Response RTT 23 Average Response RTT 36
2016-09-12 14:49:50.814 Info, Node005, Received Basic set from node 5: level=0. Sending event notification.
2016-09-12 14:49:50.815 Detail, Node005, Notification: NodeEvent
2016-09-12 14:49:50.841 Detail, Node005, Received: 0x01, 0x07, 0x00, 0x13, 0x4d, 0x00, 0x00, 0x05, 0xa3
2016-09-12 14:49:50.841 Detail, Node005, ZW_SEND_DATA Request with callback ID 0x4d received (expected 0x4d)
2016-09-12 14:49:50.841 Info, Node005, Request RTT 50 Average Request RTT 49
2016-09-12 14:49:50.841 Detail, Expected callbackId was received
2016-09-12 14:49:50.854 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x25, 0x01, 0x00, 0xd0
2016-09-12 14:49:50.855 Detail,
2016-09-12 14:49:50.855 Info, Node005, Response RTT 64 Average Response RTT 50
2016-09-12 14:49:50.855 Detail, Node005, Expected reply and command class was received
2016-09-12 14:49:50.855 Detail, Node005, Message transaction complete
2016-09-12 14:49:50.855 Detail,
2016-09-12 14:49:50.855 Detail, Node005, Removing current message
2016-09-12 14:49:50.878 Detail, Node005, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x05, 0x02, 0x28, 0x01, 0xdd
2016-09-12 14:49:50.879 Detail,
2016-09-12 14:49:50.902 Detail, Node005, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x05, 0x04, 0x26, 0x01, 0x00, 0x00, 0xd7
2016-09-12 14:49:50.903 Detail,
2016-09-12 14:49:50.927 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x25, 0x03, 0x00, 0xd2
2016-09-12 14:49:50.928 Detail,
2016-09-12 14:49:50.928 Info, Node005, Received SwitchBinary report from node 5: level=Off
2016-09-12 14:49:50.928 Detail, Node005, Refreshed Value: old value=false, new value=false, type=bool
2016-09-12 14:49:50.928 Detail, Node005, Changes to this value are not verified
2016-09-12 14:49:50.929 Detail, Node005, Notification: ValueChanged

Don’t these devices work similar to a Minimote? It sends events that you have to listen for in order to trigger the actions? I don’t have one of these devices, so I’m not sure.

Shutdown Open Zwave Control Panel, then start up Home Assistant, and from the terminal, type:

sudo journalctl -u home-assistant -f

Then when Home Assistant is fully booted up, click a button on the wall switch and see what the log in the journal says. If it is sending an event, it will have the event name you should be listening for along with any event data that was sent.

If that is the case, then you should use a trigger on that event:

automation:
  trigger:
    platform: event
    event_type: zwave.my_event_name
    event_data:
      switch_id: button_1

Obviously this is an example, so the event name and data being transfered would be different

sudo journalctl -u [email protected] -f worked for me!

On/Off press yields:
Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=255
Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=0

Enabling the following automation to toggle a HUE light! So far so good!

- alias: Lights Test - ON
  trigger:
     platform: event
     event_type: zwave.node_event
     event_data:
       object_id: unknown_id0234_unknown_type0003_id010a_5
       basic_level: 0
  action:
    service: light.turn_on
    entity_id: light.sofabord

- alias: Lights Test - OFF
  trigger:
     platform: event
     event_type: zwave.node_event
     event_data:
       object_id: unknown_id0234_unknown_type0003_id010a_5
       basic_level: 255
  action:
    service: light.turn_off
    entity_id: light.sofabord

But each of the four buttons give the same result!

In the Home Assistant Dev-State, the following are listed under “Current Entities”

switch.unknown_id0234_unknown_type0003_id010a_switch_5
switch.unknown_id0234_unknown_type0003_id010a_switch_5_2
switch.unknown_id0234_unknown_type0003_id010a_switch_5_3
switch.unknown_id0234_unknown_type0003_id010a_switch_5_4
switch.unknown_id0234_unknown_type0003_id010a_switch_5_5

From the “States” pane, under “Switch” I can toggle each node on and off (the LED on the device turns on and off)

The manual says:
“In order to better represent the various functions of ZHC5010 and provide a better visualization of the different Z-Wave network control, then ZHC5010 support for Multi Channel Command Class, which makes ZHC5010 will be presented as multiple logical units (End Points), in instead of only one device in the network control that supports Multi Channel Command Class.
For example. Fibaro Home Center 2 will ZHC5010 be displayed as 6 units, a Master and 5 Slave units where the Master is the Z-Wave device (Root Device) (shown as a cardboard box), a base unit (End Point 0) and 4 logical units (End Point 1 to 4).
In other systems simply acting ZHC5010 with a base unit 4 and the logical units. The base unit is a kind of intersection of the logical units and to some systems, only the basic unit in which to link units into association groups in which the other systems can also be (should) be done in the logical units (for example in Fibaro Home Center 2).
If the Z-Wave network controller does not support Multi Channel Command Class will ZHC5010 only be represented as a single unit, which corresponds to the base unit containing the full functionality.
The logical units 4 represents a division of the ZHC5010 in 4 switches each of which may be independent of one another.”

Is HA capable of handling Multi Channel Command Class?
Any suggestions for next step?

I have attached the log from journalctl below as described by JBARDI.

– Logs begin at Wed 2016-09-14 06:58:51 UTC. –
–Button #2
–Press 1
07:27:55 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=255>
07:27:55 hass[560]: INFO:hass.components.automation:Executing Lights Test - OFF
07:27:55 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - OFF, domain=automation>
07:27:55 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Running script
07:27:55 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Executing step call service
07:27:55 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_off, domain=light, service_call_id=1978693712-13, service_data=entity_id=[‘light.sofabord’]>
07:27:55 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state light.sofabord=off; supported_features=127, friendly_name=Sofabord @ 2016-09-14T09:27:55.502941+02:00>, old_state=<state light.sofabord=on; supported_features=127, brightness=123, xy_color=[0.2926, 0.224], friendly_name=Sofabord, color_temp=153, rgb_color=(203, 175, 253) @ 2016-09-14T09:26:58.994968+02:00>, entity_id=light.sofabord>
07:27:55 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-13>
07:27:55 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:27:55.529405+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, old_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:26:56.050294+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, entity_id=automation.lights_test__off>
–Press 2
07:28:04 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=0>
07:28:04 hass[560]: INFO:hass.components.automation:Executing Lights Test - ON
07:28:04 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - ON, domain=automation>
07:28:04 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Running script
07:28:04 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Executing step call service
07:28:04 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_on, domain=light, service_call_id=1978693712-14, service_data=entity_id=[‘light.sofabord’]>
07:28:04 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state light.sofabord=on; supported_features=127, brightness=123, xy_color=[0.2926, 0.224], friendly_name=Sofabord, color_temp=153, rgb_color=(203, 175, 253) @ 2016-09-14T09:28:04.538593+02:00>, old_state=<state light.sofabord=off; supported_features=127, friendly_name=Sofabord @ 2016-09-14T09:27:55.502941+02:00>, entity_id=light.sofabord>
07:28:04 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-14>
07:28:04 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:04.556458+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, old_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:26:59.013274+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, entity_id=automation.lights_test__on>

–Button #3
–Press 1
07:28:10 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=0>
07:28:10 hass[560]: INFO:hass.components.automation:Executing Lights Test - ON
07:28:10 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - ON, domain=automation>
07:28:10 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Running script
07:28:10 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Executing step call service
07:28:10 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_on, domain=light, service_call_id=1978693712-15, service_data=entity_id=[‘light.sofabord’]>
07:28:10 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-15>
07:28:10 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:10.670782+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, old_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:04.556458+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, entity_id=automation.lights_test__on>
–Press 2
07:28:13 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=255>
07:28:13 hass[560]: INFO:hass.components.automation:Executing Lights Test - OFF
07:28:13 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - OFF, domain=automation>
07:28:13 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Running script
07:28:13 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Executing step call service
07:28:13 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_off, domain=light, service_call_id=1978693712-16, service_data=entity_id=[‘light.sofabord’]>
07:28:13 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state light.sofabord=off; supported_features=127, friendly_name=Sofabord @ 2016-09-14T09:28:13.228651+02:00>, old_state=<state light.sofabord=on; supported_features=127, brightness=123, xy_color=[0.2926, 0.224], friendly_name=Sofabord, color_temp=153, rgb_color=(203, 175, 253) @ 2016-09-14T09:28:04.538593+02:00>, entity_id=light.sofabord>
07:28:13 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-16>
07:28:13 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:28:13.245239+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, old_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:27:55.529405+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, entity_id=automation.lights_test__off>

–Button #4
–Press 1
07:28:17 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=255>
07:28:17 hass[560]: INFO:hass.components.automation:Executing Lights Test - OFF
07:28:17 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - OFF, domain=automation>
07:28:17 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Running script
07:28:17 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Executing step call service
07:28:17 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_off, domain=light, service_call_id=1978693712-17, service_data=entity_id=[‘light.sofabord’]>
07:28:17 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-17>
07:28:17 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:28:17.600723+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, old_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:28:13.245239+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, entity_id=automation.lights_test__off>
–Pres2
07:28:19 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=0>
07:28:19 hass[560]: INFO:hass.components.automation:Executing Lights Test - ON
07:28:19 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - ON, domain=automation>
07:28:19 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Running script
07:28:19 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Executing step call service
07:28:19 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_on, domain=light, service_call_id=1978693712-18, service_data=entity_id=[‘light.sofabord’]>
07:28:19 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state light.sofabord=on; supported_features=127, brightness=123, xy_color=[0.2926, 0.224], friendly_name=Sofabord, color_temp=153, rgb_color=(203, 175, 253) @ 2016-09-14T09:28:19.604495+02:00>, old_state=<state light.sofabord=off; supported_features=127, friendly_name=Sofabord @ 2016-09-14T09:28:13.228651+02:00>, entity_id=light.sofabord>
07:28:19 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-18>
07:28:19 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:19.624285+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, old_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:10.670782+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, entity_id=automation.lights_test__on>

–Button #1
–Press 1
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=255>
07:28:24 hass[560]: INFO:hass.components.automation:Executing Lights Test - OFF
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - OFF, domain=automation>
07:28:24 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Running script
07:28:24 hass[560]: INFO:hass.helpers.script:Script Lights Test - OFF: Executing step call service
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_off, domain=light, service_call_id=1978693712-19, service_data=entity_id=[‘light.sofabord’]>
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state switch.unknown_id0234_unknown_type0003_id010a_switch_5=on; friendly_name=Unknown: id=0234 Unknown: type=0003, id=010a Switch, node_id=5 @ 2016-09-14T09:28:24.437636+02:00>, old_state=<state switch.unknown_id0234_unknown_type0003_id010a_switch_5=off; friendly_name=Unknown: id=0234 Unknown: type=0003, id=010a Switch, node_id=5 @ 2016-09-14T09:26:58.907806+02:00>, entity_id=switch.unknown_id0234_unknown_type0003_id010a_switch_5>
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state light.sofabord=off; supported_features=127, friendly_name=Sofabord @ 2016-09-14T09:28:24.516294+02:00>, old_state=<state light.sofabord=on; supported_features=127, brightness=123, xy_color=[0.2926, 0.224], friendly_name=Sofabord, color_temp=153, rgb_color=(203, 175, 253) @ 2016-09-14T09:28:19.604495+02:00>, entity_id=light.sofabord>
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-19>
07:28:24 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:28:24.530471+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, old_state=<state automation.lights_test__off=on; last_triggered=2016-09-14T09:28:17.600723+02:00, friendly_name=Lights Test - OFF @ 2016-09-14T09:25:59.233739+02:00>, entity_id=automation.lights_test__off>
–Press 2
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event zwave.node_event[L]: object_id=unknown_id0234_unknown_type0003_id010a_5, basic_level=0>
07:28:27 hass[560]: INFO:hass.components.automation:Executing Lights Test - ON
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event logbook_entry[L]: message=has been triggered, name=Lights Test - ON, domain=automation>
07:28:27 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Running script
07:28:27 hass[560]: INFO:hass.helpers.script:Script Lights Test - ON: Executing step call service
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event call_service[L]: service=turn_on, domain=light, service_call_id=1978693712-20, service_data=entity_id=[‘light.sofabord’]>
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state switch.unknown_id0234_unknown_type0003_id010a_switch_5=off; friendly_name=Unknown: id=0234 Unknown: type=0003, id=010a Switch, node_id=5 @ 2016-09-14T09:28:27.431557+02:00>, old_state=<state switch.unknown_id0234_unknown_type0003_id010a_switch_5=on; friendly_name=Unknown: id=0234 Unknown: type=0003, id=010a Switch, node_id=5 @ 2016-09-14T09:28:24.437636+02:00>, entity_id=switch.unknown_id0234_unknown_type0003_id010a_switch_5>
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state light.sofabord=on; supported_features=127, brightness=123, xy_color=[0.2926, 0.224], friendly_name=Sofabord, color_temp=153, rgb_color=(203, 175, 253) @ 2016-09-14T09:28:27.508651+02:00>, old_state=<state light.sofabord=off; supported_features=127, friendly_name=Sofabord @ 2016-09-14T09:28:24.516294+02:00>, entity_id=light.sofabord>
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event service_executed[L]: service_call_id=1978693712-20>
07:28:27 hass[560]: INFO:hass.core:Bus:Handling <Event state_changed[L]: new_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:27.530793+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, old_state=<state automation.lights_test__on=on; last_triggered=2016-09-14T09:28:19.624285+02:00, friendly_name=Lights Test - ON @ 2016-09-14T09:25:59.223023+02:00>, entity_id=automation.lights_test__on>

Best regards,
Tonkin

FIXED!

A complete reinstall of HA and extra focus on the install guide of python-OpenZwave is important. The folder for the manufacturer_specific.xml i located according to the guide.

/Tonkin

Hi Tonkin,

Can you be a bit more specific about what you did to make the 4 switches act independently?

I have all 4 switches visible in HASS, but they all respond with the same object_id: logic_soft_zhc5010_wall_switch_2

Best, Soren

Hi Soren (Hej Søren)

The trick was to place the ZCH5010 config file (ZHC5010.xml) in the right place. There are two - or even three !? - places to drop the config file and then think you are good to go.

After reinstalling HA to correct all my messing around and placing the config file in the open z-wace configuration folder.

In my case:
/usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config/logicsoft

My automation look like this (for key 2):

  trigger:
    platform: state
    entity_id: switch.logic_soft_zhc5010_wall_switch_switch_4_0_3
    to: 'on'
  action:
    service: light.turn_on
    entity_id: light.room001

I hope this will help you!
Otherwise, write again.

//Tonkin

1 Like