Smartwings Top Down/Bottom Up Zwave Shade level reporting issue

[djw1191]

The problem

I've got a top down/bottom up shade with a zwave motor from smartwings that is having issues with consistent reporting of position. It's easily observed when doing a StartLevelChange and stopping midway, as the shade loses track of the current position inside of HA.

From observing the device in zwavejs, it appears the window covering command class doesn't properly keep track of level changes and instead the current level is properly tracked via the MultiLevel Switch command class. I'm not sure what the zwave spec says is supposed to happen, but that is the behavior observed.

From the device debug, 2-38-2-currentValue and 2-38-1-currentValue are the multilevel CC I see with the proper level tracked. While 2-106-1-currentValue-13 and 2-106-2-currentValue-13 which only stays accurate when a specific SetLevel is set.

What version of Home Assistant Core has the issue?

2024.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

zwave_js

Link to integration documentation on our website

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

Diagnostics information

zwave_js-97af15baf470eaee4676c01d316bec80-sr_front_window_shades-534777af8ca562d3aab8dc0e99a1454d.json

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

[kpine]

The behavior you observe means this isn't an HA issue, it's probably a device issue, or driver. You'll want to submit an issue to node-zwave-js for further help. I don't see your device in the Z-Wave JS device database, but if this is anything like the other Smartwing/ZVIDAR product, it sounds an awful like issue https://github.com/zwave-js/node-zwave-js/issues/5975.

[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.