All my SAMSUNG MULTIPURPOSE SENSORS are giving problems since (I think) this new DRIVER was released and installed on my Hub on the 11th August 2024 @11:15am
Most need re-installing and when I have re-installed the CONACT OPEN /CLOSE is not updating but the temperature is being updated. HISTORY shows regular Temperature changes but nothing else … no OPEN/CLOSE and NO VIBRATION data.
Anyone else having problems ???
UPDATE
Had to Re-paired ALL my ZIGBEE devices and move my HUB to a more favourable position. There seems to have been a distance/signal quality change with the new Driver ?
Think I’ve got everything working again but it’s taken 4 hours
I hope this isn’t going to be required everytime I power on/off (loose connection) of my HUB.
No, you are correct. A change was rolled up from beta to production and the driver package was rebuilt. The change on that day seems to have added support for reading min and max temperature values from devices.
This is the first time I experienced these problems … EVERY ZIGBEE device I have had to be repaired … Some not easy because they’re inline switches and required me going into the Garage Loft space !!!
Can’t understand why suddenly I’ve got this distance problem … also the new Contact Driver is missing OPEN/CLOSE operation on some SAMSUNG MULTIPURPOSE SENSORS (now sold by Aerotec)
I see exactly the same issue with two eWelink DS01 Contact Sensors using driver ZigBee Contact dated 2024-07-22T20:07:44.891506019. Most often the devices drop offline - a few times each day. Usually open/close action brings the device back online. Occasionally, the disconnect seems more permanent and I have to re-pair, or reset and re-add to get them to work.
I’ve tried everything, reboot, clean up unused drivers to free memory… Thought I was going crazy.
Has anyone else come up with an actual fix for this??
My Sonoff contact sensors identify as eWeLink DS01 and you’ve just described what I experienced for a few months. However that was from day one with the Edge drivers and it stopped being a problem after that.
I bought one device specifically to see what was happening with this device and this is what I saw:
When sending the configuration to the IASZone cluster, attribute ZoneStatus, the device returns an attribute not supported error.
I had seen this in logs sent by other users. It must be a firmware error, since it answers correctly with that attribute when reporting the open or closed status. This error is maintained in the latest versions, since I bought it new this spring.
The stock driver configures the battery to report every 600 sec instead of 21600 sec to prevent it being marked offline.
This should work if the device accepts the configuration correctly on initial pairing. It does not always happen, you have to reset device and pair it near the hub
My zigbee Contact Mc driver also configures the battery with 600 sec intervals, but I removed the monitoring of the IASZone cluster so that the hub does not perform the healthCheck when the periodic reports are not received.
Also at the request of a user, I introduced a routine that keeps it always online, the problem is that when the battery runs out it will not show offline either.
It is important that you do not make a driver change, you must reset it and pair it directly with the driver so that the configuration is sent to the device
