Z-Wave.me integration does not show multi sensor values

[Pkiri]

The problem

After the upgrade to 2023.5 from 2023.3 I have an issue with reading the values of Z-Wave.me multilevel sensors. The values of temperature, humidity and other measured values are not reported anymore. When going to the device it self, there is an error that this kind of device is not supported.

After investigation, I

What version of Home Assistant Core has the issue?

core-2023.5.3

What was the last working version of Home Assistant Core?

core-2023.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Z-Wave.me

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

After investigation I suspect the upgrade of the library zwave-me-ws is causing this issue. There has been a fix in this library, that has not yet been released. If I apply these changes to my local home assistant environment, then the values are available again and the issue is fixed.

So I think a release of zwave-me-ws is needed and after it is available it should by updated in the z-wave.me manifest.json

[home-assistant]

Hey there @lawfulchaos, @Z-Wave-Me, @PoltoS, mind taking a look at this issue as it has been labeled with an integration (zwave_me) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_me 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_me Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[PoltoS]

Thanks for the report. Indeed, this was fixed. We are testing this fix and will release it soon to becomes available in 2023.6

[PoltoS]

Fixed by #93348