Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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 Water Sensor 6 (ZW122) multiple issues #6466

Closed
kpanchen opened this issue Oct 30, 2023 · 0 comments
Closed

Aeotec Water Sensor 6 (ZW122) multiple issues #6466

kpanchen opened this issue Oct 30, 2023 · 0 comments

Comments

@kpanchen
Copy link

Hi, I'm currently switching to zwaver-js-ui and moving all my devices along the way encountered some issues particularly with this Water Leak Sensor (not using HA, just MQTT functionality):

  1. I have device on USB power / always awake, configuration is reflecting this but main dashboard indicates that device is sleeping and only receive commands / configuration updates upon button press. Similar device Multisensor 6 which could be powered by battery or USB works correctly and indicates that device is awake.
  2. Attempt to include device is S0 secure mode only interviewed endpoint_0 securely and endpoint_1 and 2 non-securely which made them inoperable (not able to tell which probe sensor detected a leak). Non-secure inclusion worked fine.
  3. I also noticed that bitmasked parameters not always set configuration correctly, this goes for both devices ZW122 and Multisensor 6 ZW100. As an example if parameter has higher bytes temperature scale and lower bytes recovery limit and scale set first it will set lower part incorrectly to some strange value, manual calculation and parameter set up will set it properly.

Both devices are currently out of support / end of life so 2 and 3 are not that important, non-secure works and params need to set only once. But 1 is interesting issue and probably can be fixed judging that the other device does not behave this way.

Thank you and thank you for your great work!! I can provide more information if needed.
K.

@zwave-js zwave-js locked and limited conversation to collaborators Oct 30, 2023
@AlCalzone AlCalzone converted this issue into discussion #6467 Oct 30, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant