Skip to content
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

Tuya ZY-M100-24GV2 _TZE204_7gclukjs presence sensitivity and move sensitivity are divided by 10 #23582

Closed
monqui-ulia opened this issue Aug 10, 2024 · 2 comments
Labels
problem Something isn't working

Comments

@monqui-ulia
Copy link

monqui-ulia commented Aug 10, 2024

What happened?

For example, if you set move sensitivity to 8, the value that is updated and displayed is 0.8

Captura de pantalla 2024-08-10 a las 10 55 42 Captura de pantalla 2024-08-10 a las 10 42 58 Captura de pantalla 2024-08-10 a las 11 35 02 WhatsApp Image 2024-08-11 at 10 54 56

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.39.1

Adapter firmware version

20230507

Adapter

Sonoff Zigbee 3.0 USB Dongle Plus

Setup

Add-on on HAOS on miniPC

Debug log

Captura de pantalla 2024-08-10 a las 11 41 44
@monqui-ulia monqui-ulia added the problem Something isn't working label Aug 10, 2024
@Koenkk
Copy link
Owner

Koenkk commented Aug 12, 2024

Fixed!

Changes will be available in the dev branch in a few hours from now.

@alexk7110
Copy link

I believe the fix was applied backwards. After days of frustration I've come to the conclusion that the device move and presence sensitivity should be in the 0.1 to 0.9 range and home assistant should expect decimal values instead of integers that the error message on the logs suggests.
I've manually entered 0.8 to both move and presence sensitivity and for the first time the values stick and not zero out after a few seconds and the move and presence detection actually work as expected. Also the distance reported must be in meters so it shouldn't be divided by 10 and instead be presented as raw number.
I've been testing the dev branch the past few days and either this specific device has a few revisions that work differently or the error message in home assistant was wrong and decimals under 1 till 0 should be used on the sensitivity settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants