Unknown action z-wave

[FSHelgeland]

The problem

I have an automation that request battery value from my Danalock with z-wave. I suddenly discovered the node went dead and after looking into the automation I could see that the refresh value for battery was listed as unknown and I couldnt find update battery levels as well in the list for the automation in ui. I deleted the automation and made a new one. Then I could find refresh battery value. I saved and tested, worked fine. The when I checked the automation then again the refresh value had status as unknown action and running the automation again gave me a dead node. I repeated this, and the next time I made the automation it worked 5 or 6 times before the action came as unknown. The original automation has worked for a couple of years so something has happened.

What version of Home Assistant Core has the issue?

core-2024.8.0

What was the last working version of Home Assistant Core?

core-2024.8B7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

z-wave js

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[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)}}

[eliasisrael]

I am seeing this as well. Has anyone come up with an idea what's going wrong?

[FSHelgeland]

I have discovered a couple og things. First og all I lifted my usb-coordinator higher up. It now is about 2 meters over the floor, and is only 7 meters away from the lock. Now I have almost faultless communication with the lock and very seldom I get errors, and lock works fine all time. Second is that I had to run through all my automations, as I discovered some og them sent the same message twice within the same automation, if certain criterias were met. Two messages in the same automation forced aleays a dead lock. This has helped me, hope it will help you too.