Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add double-tap support for Jasco 14318 via "Basic CC event on Endpoint 0" #3437

Closed
nmpu opened this issue Nov 25, 2023 · 1 comment
Closed
Assignees
Labels
enhancement New feature or request

Comments

@nmpu
Copy link

nmpu commented Nov 25, 2023

I currently use the following automations to control a secondary switch by double-tap up/down on a Jasco 14318. This required a manual Z-Wave group association for the hub.

alias: Bath1 Shower On
trigger:
  - platform: device
    device_id: 99a2268aeb554c812f8d42141688b566
    domain: zwave_js
    type: zwave_js.value_updated.value
    command_class: 32
    property: currentValue
    to: 255
action:
  - service: switch.turn_on
    target:
      entity_id: switch.bath1_shower
mode: single

alias: Bath1 Shower Off
trigger:
  - platform: device
    device_id: 99a2268aeb554c812f8d42141688b566
    domain: zwave_js
    type: zwave_js.value_updated.value
    command_class: 32
    property: currentValue
    to: 0
action:
  - service: switch.turn_off
    target:
      entity_id: switch.bath1_shower
mode: single

The above worked fine initially, but now fails with the following error:

Error setting up trigger Bath1 Shower On
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/device_automation/trigger.py", line 64, in async_attach_trigger
    return await platform.async_attach_trigger(hass, config, action, trigger_info)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/device_trigger.py", line 453, in async_attach_trigger
    return await trigger.async_attach_trigger(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/trigger.py", line 45, in async_attach_trigger
    return await platform.async_attach_trigger(hass, config, action, trigger_info)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/triggers/value_updated.py", line 205, in async_attach_trigger
    _create_zwave_listeners()
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/triggers/value_updated.py", line 187, in _create_zwave_listeners
    value = node.values[value_id]
            ~~~~~~~~~~~^^^^^^^^^^
KeyError: '58-32-0-currentValue'

It's not clear why 58-32-0-currentValue intermittently goes AWOL. 58 is the 14318 node. When it's broken, I see a similar error in the Home Assistant YAML editor which prevents me from saving.

Other similar-era switches have built-in support for "Basic CC event on Endpoint 0". Can this same functionality be enabled for the Jasco 14318? Otherwise, I'll need to pursue a formal bug report for the above error.

@nmpu nmpu added the enhancement New feature or request label Nov 25, 2023
@robertsLando
Copy link
Member

@nmpu you should open that issue on HA core repository https://github.com/home-assistant/core/issues/new/choose

Unfortunately I don't have any control on that side, sorry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants