Scenes Very Slow when Triggered from Zooz Switches

Configuration Z-Wave
,
1

I have several Zooz switches such as the ZEN30. On some of them, I have enabled Scene Control in the configuration and I use Down 3x to trigger HA scenes. It works but it is really really really slow. For example, it takes 35 seconds to activate the “RB” scene which sets the state of 21 devices in the house. If I activate that scene from with HA, it is instantaneous; under 1 second.

I have this HA automation attached to the ZEN30:

alias: Living Room Light Down 3x
description: RB
triggers:
  - device_id: 9f86efb0f8f06d8f094fb340faef5df3
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    property_key: "002"
    endpoint: 0
    command_class: 91
    subtype: Endpoint 0 Scene 002
    trigger: device
    value: 4
conditions: []
actions:
  - action: scene.turn_on
    metadata: {}
    data: {}
    target:
      entity_id: scene.rb
mode: single

It triggers the HA scene “rb” but it takes about 35 seconds to run after I press the down paddle 3x.

I also have a card on a dashboard that has an entry to activate the scene. The card is nothing fancy but here is the code:

type: entities
entities:
  - <snip>
  - entity: scene.rb
title: Scenes
show_header_toggle: false

When I activate the scene from the card, it is instantaneous.

Why is that happening?

– Art Z.

2

I have zooz switches and gesture recognitions are fast, like almost instant.

Are you using HA scenes or Zwave scenes - this are two complete different things? Do you have an HA automation? Please update the question with that so we can see.

You’ll need to separate the problem out. Is the delay the switch sending the scene control and triggering the automation or is it the execution of the automation that is taking the time.

3

@PeteRage I updated the question. I am using a HA scene. I’ll appreciate any insight that you have.

4

The automation trace should show the delay.

So if you are looking at your phone clock (I’m assuming the HA clock is synced), when it hits the top of the minute, do the triple press. Then go look at the automation trace. If it triggers close to 00 seconds or closer to 25 seconds,

If the later the next stop is looking at the zwavejs debug log files to see when the message for the node is delivered.

At this point we’ll know if the delay is from the device to zwavejs, zwavejs to ha automation, or executing the scene.

5

@PeteRage Thank you for the pointers.

  1. I tapped down 3x at 8:51:00
  2. At 8:51:26, Z-Wave JS UI events for the device shows the Value Notification for
    property: scene
    propertyKey: 002
  3. HA logged that the the automation triggered at 8:51:26
  4. HA logged that the scene was triggered by the automation at 8:51:26

Looking through the configuration parameters for the ZEN77, I don’t see anything which would account for any delay in sending the value notification. I did download the configuration “download diagnostics” JSON file. Maybe you will see something in it?

I tried to upload it here but apparently I can only upload images. Here is a link to the file: zwave_js_zen77_hall_light.json

6

@PeteRage One more thing: From looking at the network graph in Zwave JS UI, the Hall Light ZEN77 is talking directly to the controller (Zooz ZST39 LR) over a Z-Wave 100 kbit/s edge.

7

Did you set parameter 13 to on?

8

Yes, param 13 Scene Control is on.

9

What are you running ha on? I experienced the exact same issue when running on low end hardware.

10

I’m running Home Assistant OS on a Raspberry Pi 4. I don’t think that that is the problem, though. CPU load hovers between 1% and 2% when the system is idle. I tapped down 3x on the switch and watched the CPU. It stayed at 2% until the automation ran. When that happened, I saw a spike to 8% and then it dropped immediately back to 2%.

Memory stays right at 23%, 0.9 / 4 GB.