Open b2un0 opened 1 year ago
+1
+1
+1
I believe that the contact sensor is working as expected buy not the tamper sensor?
Is it possible to integrate the sensor via zha in the meantime?
I believe that the contact sensor is working as expected buy not the tamper sensor?
My experience with LIDL devices is that the tamper is being sent but (Z)HA is not using it and if temper is open and one alarm is being triggered and then the tamper is being retested the alarm reset is being lost and is staying in alarm mode in the HA GUI. I think ZHA need implanting the tamper and fixing the logic of the reset of it and the alarm for getting it working OK.
All my LIDL devices is working OK if getting the tamper being in sync for not braking the alarm commands sent.
+1
+1
I believe that the contact sensor is working as expected buy not the tamper sensor?
That's the exact issue i'm facing with my ZD08 sensors. Anyway, I think the op problem is with slightly different devices, since those of the aliexpress page linked above don't have the tamper sensor. They seems to appear always as "TS0203" though.
I added two TS0203 _TZ3000_au1rjicn contact sensors roughly 6 months ago without any issues and they have been working flawless since. Today I tried to add a new one (bought from the same vendor) and it's not showing the ias_zone sensor anymore just two 'Opening' sensors which are not responding. I get a "failed to bind the 'ias_zone' cluster" in the Debug. Any idea why this might be the case or how to approach the issue @MattWestb? If you need more informations I'll try to provide it.
@cramer52 @b2un0 I had the same issue, also with a Skyconnect. Just today I stumbled across this fix, which made all my pairing problems vanish. A firmware update did the trick.
See more here: https://github.com/home-assistant/core/issues/98624#issuecomment-1688222346
@cramer52 @b2un0 I had the same issue, also with a Skyconnect. Just today I stumbled across this fix, which made all my pairing problems vanish. A firmware update did the trick.
See more here: https://github.com/home-assistant/core/issues/98624#issuecomment-1688222346
Add: The pairing issues have been resolved, but I've been a bit overly excited. The door sensor still drops out of the network after some time.
@MaxMSchneider Look what parent is having in the network it can that is not liking it and trying jumping to one other that also is not working well (like Philips HUE motions is doing all the time).
@MaxMSchneider @MattWestb I use a sonoff cc2652p dongle and with the latest firmware update I paired it (didn't work right away but with a few tries it finally paired) and it seems to be working fine for the past day with several restarts etc.
I used ZHA Toolkit rejoin with success. Just run it until blinking stops several times. I had the same issue after upgrade from Conbee II to III.
I'm using the Sonoff Dongle E with EmberZnet NCP 7.4.1.0 and having still problems to add the TS0203 _TZ3000_au1rjicn. It's been detected but the initial configuration fail.
With Z2M and an conbee II it work out of the box!
Any solution or alternativ door/windows sensors for ZHA with EZSP?!
After forgot to configure it again it works. I put some batteries instead of battery packs in it. Maybe that's a big problem...
Is your feature request related to a problem? Please describe. The mentioned device above joined the network and than leave the network after a seconds
https://www.aliexpress.com/item/1005004984273100.html
Describe the solution you'd like working Contact Senor
Device signature
```yaml Paste the device signature here. Don't remove the extra line breaks outside the ``` marks. ```Additional logs
[home-assistant_zha_2023-04-24T12-26-36.672Z.log](https://github.com/zigpy/zha-device-handlers/files/11310402/home-assistant_zha_2023-04-24T12-26-36.672Z.log)