Intermittent error with automation for "garage door open" indicator

Configuration
1

I have several Inovellis Black Series dimmers with LED Indicator lights. I would like to use the LED on one of them as an indicator for my garage door being left open. I’ve configured an automation to do this, but it only works some of the time (maybe 20% of the time it works). I’m using a binary contact sensor on my garage door to trigger the automation. When it works, it works. But when it doesn’t work, I get the following error:

Scott's Garage Door Open: Error executing script. Unexpected error for device at pos 1: 'type'

Here is the YAML for the automation:

- id: '1644695761905'
  alias: Scott's Garage Door Open
  description: ''
  trigger:
  - type: opened
    platform: device
    device_id: 269e12598a5c7dec71df986b77f9c5c3
    entity_id: binary_sensor.scotts_garage_door_sensor
    domain: binary_sensor
  condition: []
  action:
  - device_id: ac4bda9aaea038cfb118e930c3da3b40
    domain: zwave_js
    type: set_config_parameter
    parameter: 13
    bitmask:
    subtype: 5-112-0-13 (LED Indicator Color)
    value: 0
  mode: single

I have a similar automation setup for when the garage door closes, but it suffers from the same intermittent behavior. And I have a second garage door and a second Inovelli Black Series Dimmer that I have another set of automations setup for, and they also have the same intermittent behavior. Nothing else in my HA setup is intermittent like this.

I previously had this setup on Hubitat Elevation, and it worked reliably (same dimmers, same firmware, same contact sensors).

Any ideas on why this would only work intermittently? I can literally change nothing and it will just start (or stop) working.

Thanks in advance for any assistance!

2

Is the binary sensor provided by the integration you’re using?

Is there perhaps a firmware update for the device?

3

I’m not exactly sure what you mean.

There is a firmware update available. I was just hoping to not have to do that because it is a pain, and it was working before with Hubitat. I know - apples and oranges. I guess I can give it a shot.

4

I mean, did you do anything to create that binary sensor (e.g. in your YAML config as a template sensor), or whether it was simply there after installing the integration. If the latter, there might be more config we should see in order to help you.

5

Ah, I see. It was simply there after installing the integration. Which part of the config would you need to see? (and thank you for the reply!)

By the way, I upgraded the firmware on one of my Inovelli dimmers to the latest - v1.57. I recreated the automation, and the same thing happens, unfortunately. I still get the error: “Error executing script. Unexpected error for device at pos 1: ‘type’.” I actually haven’t gotten it to work since upgrading the firmware today. So it may no longer be “intermittent,” but instead just “not working.”

6

One more piece of information:

If I go to the Automation and click “Run Actions,” I get the same error in the logs. This would indicate to me that the problem is somewhere in the Actions, not the Trigger. Does that sound right?

Thanks!

7

I don’t know how Zwave works, unfortunately, but that actions section looks strange as it doesn’t contain any service calls.

8

It’s a device action. Here’s what it looks like in the GUI:

action
action1006×625 25.7 KB

9

Your post got me thinking, and I changed it to a Z-wave service call (I didn’t even know you could do that until I looked). Problem solved!!!

For anyone that may have this problem in the future, here’s my updated automation:

- id: '1644695761905'
  alias: Scott's Garage Door Open
  description: ''
  trigger:
  - type: opened
    platform: device
    device_id: 269e12598a5c7dec71df986b77f9c5c3
    entity_id: binary_sensor.scotts_garage_door_sensor
    domain: binary_sensor
  condition: []
  action:
  - service: zwave_js.set_config_parameter
    data:
      parameter: '13'
      value: '0'
    target:
      device_id: 06cc6495476d1df6d8cb528bd0dff23f
  mode: single

And here’s what it looks like in the GUI:

action2
action2990×1139 68 KB

10

Glad you got it working. Annoyed with myself that I didn’t already spot the faulty action section in the first post. :slight_smile: