-
-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aeotec Multisensor 6 temperature threshold parameter reported incorrectly #16941
Comments
Could you provide some logs please? |
There was nothing relevant in the homeassistant.log but I can supply it if you need it. Below is a snippet from the ozw log. Setting parameter 41 to 5 (0.5°C) then to 2 (0,2°C):
|
Ok, this is either a problem with the device itself, or the settings of the config parameters in OZW. |
Home Assistant release with the issue:
0.78.3
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio, pi3b
Component/platform:
https://www.home-assistant.io/docs/z-wave/
Description of problem:
For a newly connected Aeotec Multisensor 6 zwave device the default temperature threshold value (parameter 41) displays as 20, but if something is written to the value (e.g. 10, or 5) after a short delay it displays 1310976 as the set value. I have tried this with both secure and insecure connections. I have tried and found this behaviour with two new devices.
All other parameter values display correctly when edited.
I’m pretty sure this is just a parameter value display bug as the device behaves as expected for the value entered.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: