Zen14 seems to lose track of end points above 0

[TheKorn2]

Checklist

• I am not using Home Assistant. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog and my problem is not mentioned there.

Deploy method

Snap

Z-Wave JS UI version

9.9.0.09b107a

ZwaveJS version

12.4.4

Describe the bug

This seems to be a very latent bug. (happy happy joy joy)

Occasionally zwave-js / zwave-js-ui seems to lose track of Zen14 end points above 0. (I'm not sure if it happens with other items, I've just noticed it with my Zen14s.)

See attached screenshot. Device was interviewed correctly a couple of months ago, and was working perfectly for those couple months using mqtt commands to any and all end points (0, 1, 2). All of a sudden, zwave-js/zwave-js-ui insist that end points 1 and 2 don't exist, despite clearly being there for the interview and also working previously.

Note that while in the failure state, end point 0 continues to function normally. In this device's case, a command to end point 0 makes that change to end points 1 and 2. So if I send a command to turn on end point 0, the device itself turns on end points 1 and 2 and then update their states in the UI! But if I then go into the UI and try to issue a command directly to end point 1 or 2, I'll get the "end point 1 (or 2) doesn't exist" message.

Moreso, this is not the first time I've run into this bug. Previously I've "fixed" it by re-interviewing the device, and the zen14 will come back exactly the same and it'll work again for a few weeks using end points 1 and 2. But re-interviewing is not fixing the bug it's just papering over it, so I'm raising it at this point as this has the hallmarks of being an ugly one to track down and fix.

To Reproduce

• Add Zen14 to zwave-js
• Use for a few weeks/months
• Notice end points 1 or 2 are not working, while end point 0 continues to work

Expected behavior

Commands to end points 1 and 2 should continue to function as in the past.

Additional context

Given the long times between occurrences of this bug, I'm reticent to restart zwave-js/zwave-js-ui because I'm unsure if it'll come back in the failed state and we'll lose the opportunity for useful debugging.

Again, this can be "fixed" by re-interviewing the device, but considering I've encountered this same bug a few times now I'm willing to forego this working for a while to try and debug, just not exactly sure where/how to proceed from here and what would be useful.

[robertsLando]

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).

[TheKorn2]

OK so fun times!

The act of turning on debugging caused end points 1 and 2 to disappear.

Tried turning on end point 0, which then caused end points 1 and 2 to re-appear in the UI.

Fortunately (well, kind-of), it's still in the failure state so I was able to grab a driver log. It's 512KB raw, so zipping it up to drop here.

zwavejs_2024-03-26.zip

[TheKorn2]

(more info... turned on driver log. saw end points 1 & 2 missing. turned on end point 0, saw end points 1 & 2 reappear in on state. Then went to end points 1 and 2 and tried to turn them off, got end points not found messages as shown. Then copied log, and returned debugging to normal settings.)

[TheKorn2]

@AlCalzone Any ideas? I can't keep holding off on resetting this thing forever. (And it's still happening.)

[TheKorn2]

@AlCalzone @robertsLando What do I have to do to even get someone to take a look at this? There's been no eyes on this since it's been moved off of UI.

[AlCalzone]

I'll try to find some time next week. Have been pretty busy since I came back from parental leave.

[robertsLando]

@TheKorn2 I'm sorry for that but there is nothing I can do and @AlCalzone has been busy as he said 🙏🏻

[TheKorn2]

I'll try to find some time next week. Have been pretty busy since I came back from parental leave.

Thanks Al!