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

ZY-M100-24G - Unable to change presence sensitivity setting. #21282

Closed
DuncanRae opened this issue Feb 7, 2024 · 13 comments
Closed

ZY-M100-24G - Unable to change presence sensitivity setting. #21282

DuncanRae opened this issue Feb 7, 2024 · 13 comments
Labels
problem Something isn't working

Comments

@DuncanRae
Copy link

DuncanRae commented Feb 7, 2024

What happened?

When changing the Presence Sensitivity value for the ZY-M100-24G Presence Sensor from the default 2.5, it changes for a few seconds then goes back to 2.5.

There is no indication as to why in the logs. The value just changes back to 2.5.

The other slider values like Motion Sensitivity and Radar range are exhibiting the same behavior, so it’s not just one setting.

This setting used to work, (in the last two or 2 months) but now doesn't. I don't often change these settings and have done a few Z2M updates so can't be sure which update broke it. It was definitely working in the mid-January time frame though.

What did you expect to happen?

The Presence Sensitivity value would be set to what I tried to set it to.

How to reproduce it (minimal and precise)

Move the Presence Sensitivity value to anything other than 2.5

Zigbee2MQTT version

1.35.3

Adapter firmware version

20230507

Adapter

Sonoff Zigbee 3.0 USB

Setup

Addon to Home Assistant

Debug log

Debug 2024-02-07 13:41:46Received MQTT message on 'zigbee2mqtt/Main Bedroom Presence Sensor/set/presence_sensitivity' with data '4'
Debug 2024-02-07 13:41:46Publishing 'set' 'presence_sensitivity' to 'Main Bedroom Presence Sensor'

Debug 2024-02-07 13:41:53Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":1,"dp":2}],"seq":62464}' from endpoint 1 with groupID 0
Debug 2024-02-07 13:41:53Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":4,"dp":105}],"seq":62720}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:53MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":693,"linkquality":47,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":4,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:53Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0],"type":"Buffer"},"datatype":4,"dp":112}],"seq":62976}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:53MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":693,"linkquality":43,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":4,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:53Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,0],"type":"Buffer"},"datatype":2,"dp":109}],"seq":63232}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:53MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":693,"linkquality":47,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":4,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:54Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,2,178],"type":"Buffer"},"datatype":2,"dp":104}],"seq":63488}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:54MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":690,"linkquality":43,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":4,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:54Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,20],"type":"Buffer"},"datatype":2,"dp":106}],"seq":63744}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:54MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":690,"linkquality":47,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":4,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:54Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,25],"type":"Buffer"},"datatype":2,"dp":111}],"seq":64000}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:54MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":690,"linkquality":43,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":2.5,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:54Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,1,94],"type":"Buffer"},"datatype":2,"dp":107}],"seq":64256}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:54MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":690,"linkquality":40,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":2.5,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'
Debug 2024-02-07 13:41:54Received Zigbee message from 'Main Bedroom Presence Sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,10],"type":"Buffer"},"datatype":2,"dp":110}],"seq":64512}' from endpoint 1 with groupID 0
Info 2024-02-07 13:41:54MQTT publish: topic 'zigbee2mqtt/Main Bedroom Presence Sensor', payload '{"detection_distance_max":3.5,"distance":0,"fading_time":10,"illuminance_lux":690,"linkquality":43,"motion_sensitivity":2,"move_sensitivity":2,"presence":false,"presence_sensitivity":2.5,"presence_state":"none","presence_timeout":10,"radar_range":3.5,"state":"none","target_distance":0}'

@DuncanRae DuncanRae added the problem Something isn't working label Feb 7, 2024
@AlfAlex
Copy link

AlfAlex commented Feb 7, 2024

I have the same problem with device "[ZY-M100-24G]" (I have this device twice, the other one does not have this problem.

@DuncanRae
Copy link
Author

I also have 2 devices. Both exhibit the same behavior. They sometimes take a few seconds to go back to 2.5, and I had it once on one device seem to stick for a few minutes, but then went back to 2.5 again.

@DuncanRae
Copy link
Author

I’ve done a bit more testing. All of the sliders are behaving in the same way. Presence Sensitivity, Move Sensitivity and Radar Range. They are all returning to default values a few seconds after changing them.

@DuncanRae
Copy link
Author

Not sure if I'm barking up the wrong tree here, and would appreciate input from someone more experienced, but when comparing the converter file (tuya.ts) in an older version that worked (pretty sure) to now, I see the following difference:

Worked (from version 18.10.0 of Herdsman)
e.numeric('presence_sensitivity', ea.STATE_SET).withValueMin(1).withValueMax(10).withValueStep(1).withDescription('Presence sensitivity'),

Doesn't work (18.28.3 of Herdsman):
e.numeric('presence_sensitivity', ea.STATE_SET).withValueMin(1) .withValueMax(10) .withValueStep(1) .withDescription('Presence sensitivity'),

The not working one seems to be missing the withValueMin piece. I don't have a way to make this change and test so if this helps point someone who can in the right direction, that is great.

@AlfAlex
Copy link

AlfAlex commented Feb 8, 2024

For me these lines do look identical... ;)

I did not recongize any problem with version 1.34.0 besides frequently crashes (the reason why I did the upgrade, also I had some prblems with another sensor).
I do have these problems now with version 1.35.2 and also with 1.35.1.
I will try 1.35.0 and 1.35.3 now

@DuncanRae
Copy link
Author

DuncanRae commented Feb 8, 2024

For me these lines do look identical... ;)

I did not recongize any problem with version 1.34.0 besides frequently crashes (the reason why I did the upgrade, also I had some prblems with another sensor). I do have these problems now with version 1.35.2 and also with 1.35.1. I will try 1.35.0 and 1.35.3 now

You're right! Sorry. They were laid out differently, and I missed it. Wrong tree. :(

There is also this line:

multiEndpoint: true,

Seems to be in the one that doesn't work and not in the one that does. Not sure what this does.

Thanks for the help.

@AlfAlex
Copy link

AlfAlex commented Feb 8, 2024

1.35.3: same bug
1.35.0: same bug
1.34.0: same bug

So it looks like I had this problem before but did not reconize it

@gustjoha
Copy link

gustjoha commented Feb 9, 2024

Same problem for me - values revert to default after a few seconds.

@SonTypda
Copy link

SonTypda commented Feb 9, 2024

Almost the same problem for me. I also mentioned it here: #21180

For me, the Presence sensitivity value always jumps back to the highest level (10)

As a result, my network is completely spammed because someone in the room is constantly and erroneously detected at this sensitivity level

@DuncanRae
Copy link
Author

See #19448 Once I switched to the external converter in Fehuz's comment all my issues were resolved regarding not being able to change any settings as well as the many issues running multiple presence sensors at the same time. Would definitely recommend giving it a try and hope that it can be added natively within Z2M

Thanks. I have done this and is seems to be all good now. I change presence sensitivity from 2.5 to 4, and it went to 0.4, but then changed to 4 a few seconds later and it seems to have stuck!

@AlfAlex
Copy link

AlfAlex commented Feb 9, 2024

Working for me too.
For me it looks like a serious bug in this deviiveBy10 converter stuff.

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Feb 10, 2024
@Koenkk
Copy link
Owner

Koenkk commented Feb 10, 2024

Integrated the fix!

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

@monqui-ulia
Copy link

It seems that in version z2m 1.39.1 (zigbee-herdsman-converters version
19.72.0) the error persists. If you set the presence sensitivity parameter to 8 it changes to 0.8. Same behavior with move sensitivity.

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

7 participants
@AlfAlex @Koenkk @gustjoha @DuncanRae @SonTypda @monqui-ulia and others