Z-Wave JS UI: Event "CAN" was sent to stopped service "serialAPICommand"

domibarton commented 1 year ago

The problem

Hello

I've upgraded my Home Assistant today and had to move from zwavejs2mqtt to zwave-js-ui.
Everything works as expected and I could migrate everything, but I have some issues with the new Z-Wave JS server.

I've 7 similar Z-Wave switches (Aeotec WallMote Quad) and some of them have issues.

When I press a button, it works. However, when I press the next button (within a couple of seconds), it starts to blink and the event doesn't work.

At the Z-Wave JS UI server I suddenly see a lot of Timeout ACK, Dropped TX and Dropped RX. When I open the debug log I can see this:

<<< Me pressing the first button >>>
2023-05-18 19:31:26.480 INFO Z-WAVE: [Node 007] Is now awake
2023-05-18 19:31:26.536 INFO Z-WAVE: [Node 007] Value notification: 91-0-scene-003 0
<<< Me pressing the second button 1s later; no output in the log but 4s later the node goes to sleep >>>
2023-05-18 19:31:30.835 INFO Z-WAVE: [Node 007] Is now asleep
Warning: Event "CAN" was sent to stopped service "serialAPICommand". This service has already reached its final state, and will not transition.
Event: {"type":"CAN"}
Warning: Event "ACK" was sent to stopped service "serialAPICommand". This service has already reached its final state, and will not transition.
Event: {"type":"ACK"}
Warning: Event "ACK" was sent to stopped service "serialAPICommand". This service has already reached its final state, and will not transition.
Event: {"type":"ACK"}

I didn't had these issues before the upgrade and I didn't change anything on the configuration / setup. It is more than one WallMote which is now experiencing these issues.

Do you've any idea how to fix that or where I can start debugging?

What version of Home Assistant Core has the issue?

core-2023.1.7

What was the last working version of Home Assistant Core?

core-2022.7.2

What type of installation are you running?

Home Assistant Core

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?

<<< Me pressing the first button >>>
2023-05-18 19:31:26.480 INFO Z-WAVE: [Node 007] Is now awake
2023-05-18 19:31:26.536 INFO Z-WAVE: [Node 007] Value notification: 91-0-scene-003 0
<<< Me pressing the second button 1s later; no output in the log but 4s later the node goes to sleep >>>
2023-05-18 19:31:30.835 INFO Z-WAVE: [Node 007] Is now asleep
Warning: Event "CAN" was sent to stopped service "serialAPICommand". This service has already reached its final state, and will not transition.
Event: {"type":"CAN"}
Warning: Event "ACK" was sent to stopped service "serialAPICommand". This service has already reached its final state, and will not transition.
Event: {"type":"ACK"}
Warning: Event "ACK" was sent to stopped service "serialAPICommand". This service has already reached its final state, and will not transition.
Event: {"type":"ACK"}



### Additional information

I'd like to help finding the root cause for this problem, but I'm not sure where to start yet.

home-assistant[bot] commented 1 year ago

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.

_{^{(message by CodeOwnersMention)}}

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

domibarton commented 1 year ago

Btw if it matters:

zwave-js-ui: 8.16.1
zwave-js: 10.20.0

kpine commented 1 year ago

Looks like an issue for https://github.com/zwave-js/zwave-js-ui or https://github.com/zwave-js/node-zwave-js. Based on the logs listed, which are from Z-Wave JS UI (not zwave-js-server), HA is not involved in the problem?

Also, for these sorts of issues, driver logs are necessary.

domibarton commented 1 year ago

Looks like an issue for https://github.com/zwave-js/zwave-js-ui or https://github.com/zwave-js/node-zwave-js. Based on the logs listed, which are from Z-Wave JS UI (not zwave-js-server), HA is not involved in the problem?

Also, for these sorts of issues, driver logs are necessary.

Thanks, I'll enable the driver logs and see what I can detect.
I'll ping the other projects / repos as well.

I think HA is not involved, because HA won't get the event at all - but I'm not 100% sure yet.
Thanks for the tip with the driver log and the links to the other repos! :)

domibarton commented 1 year ago

Closing issue if favour of https://github.com/zwave-js/node-zwave-js/issues/5854

home-assistant / core