I’ve had a door contact stop sending open/close status since dec 8 . Multiple delete and rediscoveries, driver changes battery changes and I can’t get the thing to send an open/close status. Shows battery level. But no other info. Ok so I bought new contact sensor. Both sensors are EWeLink branded. Try getting the new one to work. Same issue. Struggled with it for a couple nights now. Came across a post about devices going online and offline. So looked into my setup more. Will if the sensor is a EWeLink Zigbee, it doesn’t send info anymore. They all quit working on dec 8. Door contacts, water leak, temperature sensors, and lights. These are critical devices, not having them work is very concerning. Anyone have any ideas or should I just move away from smartthings.
A little bit more info. Water contact. Model SNZB-03, door contact DS01. Temperature TS0201, light ZB-CL01. They are sending no info, or more than likely, smartthings is not reading anything.
Any ideas? I’m trying beta but hasn’t downloaded yet.
Other question is, how do I roll back the firmware update, worked prefect before the update. I’m really starting to hate updates.
There is no new Beta. 59.8 was the last Beta released.
Are there any Zigbee devices that remain working?
Any Zigbee routing devices such as mains/USB powered smart plugs that can be power cycled but haven’t been?
My Zigbee setup include a significant number of Sonoff/Weblink devices, including the DS01, TH01 and WB01. 59.8 doesn’t seem to have freshly broken anything for them, but neither has it fixed a serious issue that has been plaguing me since 58.x, and probably before that. I effectively lose all communication with routed Zigbee devices and only power cycling a routing device seems to fix the issue (which one, or ones, varies).
Well found the problem and fixed it. Went through smartthings advance and found one thing that was common to all the devices that stoped sending data. It was Default clusters driver. I had 3 drivers, default clusters, default cluster beta and tuya driver. None would work. A few things I found though. I had 8 EWeLink devices not reporting and found one that was. That one had different driver. The 8 not reporting were either connecting directly to hub or through repeaters. All repeaters had other sensors that were working fine, a couple repeaters were ones that were not working, but still had good sensors on them. I ended up using the Mariano Shared Beta Driver for these devices in the end. Hopefully this helps some else with the same issue.