search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.77k stars 1.64k forks source link

SEA802 Lock state report #6826

Closed bublikOff closed 3 years ago

bublikOff commented 3 years ago

There is something wrong with SEA802 lock state report. I can lock or unlock from HA and I can see that state change in HA and in z2m "State" tab. In z2m "Expose" tab is always showing "Unlocked" in any actual state locked or unlocked. There is also problem with lock state reporting when I do lock or unlock thermostat using buton on it (not from HA GUI)

PS z2m version is 1.18.1-2

salopette commented 3 years ago

so with me the satus is transmitted

bublikOff commented 3 years ago

im not sure wghat is actually wrog ... as for eg on my test thermostat child_lock shows "locked" but if I press button on thermostat it shows themperature instead of LC But in any case it does not change switch state on Expose tab

bublikOff commented 3 years ago

Video about GUI problem https://www.youtube.com/watch?v=LOR0fug2SWw

github-actions[bot] commented 3 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Chekedaudau commented 2 years ago

This issue schouldn't be closed. For me the lock/unlock switch has no function for the SEA802-Zigbee in zigbee2mqtt. The state is always unlocked.

maz3max commented 2 years ago

I think I found something: If I set the state exposed in z2m to "unlocked" it really disables the child lock function. If the device is currently locked, it is unlocked and cannot be locked again until I enable it via z2m.

Chekedaudau commented 2 years ago

I think I found something: If I set the state exposed in z2m to "unlocked" it really disables the child lock function. If the device is currently locked, it is unlocked and cannot be locked again until I enable it via z2m.

Do you think this is a z2m problem or a problem with the radiator?

maz3max commented 2 years ago

I think I found something: If I set the state exposed in z2m to "unlocked" it really disables the child lock function. If the device is currently locked, it is unlocked and cannot be locked again until I enable it via z2m.

Do you think this is a z2m problem or a problem with the radiator?

I wonder if we are reading/writing the wrong Data ID. It's also possible that tuya/saswell made an error in their implementation and that is just how the device operates.

Chekedaudau commented 2 years ago

I've just testet it with TuYa and it's working fine. So there must be an issue in z2m. I'm quite new to github. Is there a way to reopen this ticket?