Z-wave fails to properly include Aeotec Smart Dimmer (ZW099)

[anmeie]

The problem

Aeotec Smart Dimmer 6 (ZW099) cannot be controlled and fails to update light status when added with S0 security.

1. Light/dimmer status and control is not working
2. Power meter values are properly updated in HA
3. Everything works properly with Unsecured inclusion
4. Previously (over a year ago) added Smart Dimmers work properly in the same installation with S0 security (identical configuration from what can be seen in the UI, so conf paramters and groups)
5. Have tried to add 3 new Smart Dimmer 6 to the system, all experiencing the exact same behaviour

What version of Home Assistant Core has the issue?

core-2023.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave

Link to integration documentation on our website

No response

Diagnostics information

Debug info from Z-Wave JS. "Working SW099" is from a previously included dimmer which works well. "Not working SW099" is a new dimmer I've added but is not properly working. Both with S0 security.

Working SW099.json Not working SW099.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[anmeie]

Z-wave log when I physically press the button on the dimmer.

Dimmer turned off by physical button.txt

[anmeie]

One difference I noticed between the working and non-working device's debug info is the definition of groups:

Working device (previously added device with S0 security or newly added device without security):

"groups": [ { "text": "Lifeline", "endpoint": 0, "value": 1, "maxNodes": 5, "isLifeline": true, "multiChannel": true }, { "text": "Retransmit", "endpoint": 0, "value": 2, "maxNodes": 5, "isLifeline": false, "multiChannel": true }, { "text": "Lifeline", "endpoint": 1, "value": 1, "maxNodes": 1, "isLifeline": true, "multiChannel": true }, { "text": "Retransmit", "endpoint": 1, "value": 2, "maxNodes": 1, "isLifeline": false, "multiChannel": true }, { "text": "Lifeline", "endpoint": 2, "value": 1, "maxNodes": 1, "isLifeline": true, "multiChannel": false }, { "text": "Retransmit", "endpoint": 2, "value": 2, "maxNodes": 1, "isLifeline": false, "multiChannel": false } ],

Non-working device (newly added device with S0 security):

"groups": [ { "text": "Lifeline", "endpoint": 0, "value": 1, "maxNodes": 5, "isLifeline": true, "multiChannel": true }, { "text": "Retransmit", "endpoint": 0, "value": 2, "maxNodes": 5, "isLifeline": false, "multiChannel": true } ],

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[anmeie]

Appreciate if someone would be able to take a look, happy to provide additional logs and testing.

[oak867]

This same issue has been happening for my ZW099 for a few weeks now. I have one dimmer and 5 switches connected to a vera hub, and Alexa voice commands will not work, and vera controller app says "can't detect device." I can usually manually turn the dimmer on via the app, but this is super annoying.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.