Homeseer Switch Scene Activation Trouble

I’ve spent the last few days trying to get doubletap working on my Homeseer WD100+ dimmer, and can’t make it work. I’m attempting to use doubletap-off to turn off a group of lights.

I added the segment from the device specific page to my zwcfg file.

This is my automation:

- alias: Homeseer All Off
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.living_room_overhead_18
      scene_id: 2
      scene_data: 3
  action:
    service: homeassistant.turn_off
    entity_id: group.livingspace

My ozw_log has this portion, that I think is the scene activation from the switch, but my action never triggers.

2018-01-08 20:18:36.931 Detail, Node018,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x12, 0x05, 0x5b, 0x03, 0x14, 0x03, 0x02, 0xaa
2018-01-08 20:18:36.931 Info, Node018, Received Central Scene set from node 18: scene id=2 in 3 seconds. Sending event notification.
2018-01-08 20:18:36.931 Detail, Node018, Initial read of value
2018-01-08 20:18:36.931 Detail, Node018, Notification: ValueChanged

Any ideas on why this won’t work?

Just wanted to bump this a little and mention that I’m not seeing scene_data anywhere in my logs when I try to trigger my doubletap, but I’m not sure how to troubleshoot that…

I know that you have to stop home assistant before making those changes to the zwcfg file otherwise they are lost after restart. Are you sure they’re still there?

Yup. Like I say I’ve been doing this over several days, so I’ve probably restarted HA 10-15 times in that period.

After restarting HA does your zwavecfg file keep the changes for the Central scene? If so compare you automation to this one. I think the spacing in yours might be off. I know i just had that issue with this one. I am still new to this so I might be wrong but just trying ideas. The first one is to make sure the changes to the zwavecfg_xxx.xml are staying after a restart.

- alias: North Mud Room On with Porch Switch
  trigger:
   - platform: event  
     event_type: zwave.scene_activated
     event_data:
       entity_id: zwave.northporchlight
       scene_id: 2
       scene_data: 3
  action:
    service: switch.turn_off
    data:
      entity_id: switch.north_mud_room_switch

Yeah, just to confirm my zwcfg absolutely does have the changes in it. I copied the snippet from the device page, and replaced the entire CommandClass 91 snippet in my zwcfg with it.

I don’t see any difference in spacing between our triggers? It looks like our actions might be a little different, but manually triggering the automation performs the action just fine. Also, I ran the configuration validator, and it came back fine.

Are you also missing scene_data in your logs? I think that’s the root of my problem.

This is what my log shows with the double tap. I figured out that the “new value=xx” is the scene data which also matches up to the table on the device specific page. It does look like yours is not getting that information.

2018-01-10 10:26:42.529 Info, Node004, Received Central Scene set from node 4: scene id=1 in 3 seconds. Sending event notification.
2018-01-10 10:26:42.529 Detail, Node004, Refreshed Value: old value=4, new value=3, type=int
2018-01-10 10:26:42.529 Detail, Node004, Changes to this value are not verified
2018-01-10 10:26:42.529 Detail, Node004, Notification: ValueChanged
2018-01-10 10:26:44.848 Detail, Node004, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x04, 0x05, 0x5b, 0x03, 0x01, 0x03, 0x02, 0xa9
2018-01-10 10:26:44.849 Detail,
2018-01-10 10:26:44.849 Info, Node004, Received Central Scene set from node 4: scene id=2 in 3 seconds. Sending event notification.
2018-01-10 10:26:44.849 Detail, Node004, Refreshed Value: old value=4, new value=3, type=int
2018-01-10 10:26:44.850 Detail, Node004, Changes to this value are not verified
2018-01-10 10:26:44.850 Detail, Node004, Notification: ValueChanged

Interesting. I felt like I saw some people’s logs that included scene_data. I have entries similar to that in my logs, but they have both the old and new values as the same. Here’s some lines from an OZW log where I was testing:

2018-01-08 21:12:40.615 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int
2018-01-08 21:12:41.785 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int
2018-01-08 21:12:42.044 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int
2018-01-08 21:12:42.771 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int
2018-01-08 21:12:42.840 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int
2018-01-08 21:12:43.630 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int
2018-01-08 21:12:43.913 Detail, Node018, Refreshed Value: old value=3, new value=3, type=int

I’m not sure which of those is my actual doubletap, but I know I didn’t do that many. This was from a testing session. I’m 70% sure that my process in this one was trying every combo of button press (IE doubletap up, doubletap down, etc) just to make sure that I wasn’t trying to map to the wrong event. For what it’s worth, here’s the whole ozw log. Node018 is my Homeseer switch.

Are you running the latest version of HA? I have multiple of these switches and double and triple taping works on them.

I wonder if the dimmer is a little different than the Switch. I just noticed you have the WD100+ but i have the WS100.

@pmarq2008 I guess anything is possible, but the device specific page lists them as just “homeseer devices”, and you’d think they’d be similar in any event, right?

@Maaniac Yup. These specific logs might have been on .59, but I’m currently on .60.1 with the same issues. I agree though that several people now seem to be using the homeseer devices successfully, so I’m sure it’s something on my end that’s wrong, but I’m not sure what it could be at this point.

More info on my setup: I’m running HA in docker on a synology box, with an aeotec zwave gen5 stick. Zwave works perfectly fine in other respects here. Here’s my full zwcfg. Node 18 is my homeseer switch, and it’s config begins on line 1054.

UGH. I notice that the code snippet on the device specific page is different from what’s in my zwcfg. No idea how this happened, since it was a literal copy and paste from there to my config file.

The third key in the device page reads:

<Value type="int" genre="user" instance="1" index="2" label="Bottom Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />

Where mine has a different “value = 3” at the end:

<Value type="int" genre="user" instance="1" index="2" label="Bottom Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />

I’m going to try repasting in the whole snippet this evening, and will update once I can test. :roll_eyes:

@supagold I’ve pasted my zwcfg file and it also has value 3 for bottom button scene so I don’t think that is the issue. I’ve also included my automation for double click on and off.

		<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
			<Instance index="1" />
			<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="2" />
			<Value type="int" genre="user" instance="1" index="1" label="Top Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />
			<Value type="int" genre="user" instance="1" index="2" label="Bottom Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3" />
		</CommandClass>

- alias: Double tap on - Deck
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.deck
      scene_id: 1
      scene_data: 3
  action:
    - service: light.turn_on
      entity_id: light.under_cabinets_level

- alias: Double tap off - Deck
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.deck
      scene_id: 2
      scene_data: 3
  action:
    - service: light.turn_off
      entity_id: light.under_cabinets_level

So that’s even weirder! Yours has a different value from both mine and the device specific page for the second value. I guess I’ll try that too…