OK, I may be mis-understanding but, if a switch (smart or otherwise) does not operated as a switch, surely that is an issue with the swtich?
I know what you mean.
However this has happened twice, both times when the switch has gone āofflineā with other devices.
The switch is a touch sensitive panel which contains electronics and a circuit board which i believe controls a mechanical relay.
Somehow it gets into a state where the touch sensor switch wont throw the relay.
To be clear, it wasnāt just this device i had the issue with, Ikea control outlets were offline and movement sensors too.
@nayelyz
Is this released to all v3 HUBās?, or only affected hubs, as stated in status update.
Can you or a staff member of this topic elaborate what specific zigbee incident has been resolved?
Just adding to this that my v2 hub on 45.11 firmware is broken for Zigbeeā¦ my devices are either offline or not communicating to the hub. Iāve removed and re-added both and they work for a few days and then stop.
This happened before moving to Edge drivers and hasnāt improved since.
Particularly annoying that the Hughes Doorbell sensor that notifies my phone when my traditional doorbell is pressed is one of the devices. When Iām in the loft I donāt always hear it.
Would be nice if there was acknowledgment of this issue at the leastā¦
Definitely it has NOT been resolved. My Zigbee devices still go offline randomly, ~3-4 times a day. Automations canāt be trusted anymore.
So far mitigating with a Hubitat system running in parallel. This is not a long term solution obviously. I can: a)completely switch to Hubitat, b) replace all my Zigbee sensors and plugs with Z-wave ones, or c) wait for Thread/Matter to become a reality -assuming they will work and they will sell them in the near future-.
Iām hoping there is an option d) SmartThings just fix the bug. I had no issues with Zigbee until a month ago!
After 2-3 months of this Zigbee instability and seeing that Thread and Zigbee share the 2.4Ghz band, Iām thinking they are prioritizing Thread and they just donāt know how to fix this Zigbee mess without rolling back their Thread/Matter compatibility.
You may be right. I have a v2 hub which did NOT get Thread capability and I have had no significant ZigBee problems
My HUB Aeotec I had problems with constant offline again, having to turn the hub off and on again to get back to normal. Damn Smartthings, when are you going to fix this crap with zigbee failing and going offline and that is harming automations and routines. Making clear the example of Automations and routines failing and leaving late. Apparently Iām not the only one who is experiencing problems with the Hub going offline constantly. When are you going to release the new firmware that fixes this zigbee instability?
Same.
Nobody seems to remember that this note was in the release notes for 45.9. ZigBee issues started then.
Upgraded the Zigbee Stack for the SmartThings Hub 2018 and the Aeotec Smart Home Hub. There is no new functionality added.
This is disappointing.
I have had issues since 45.11 that were not there before.
Twice lots of devices have gone offline requiring a reboot.
Does the above message suggest samsung reckon 45.11 has no issues
Unlikely. The next beta cycle is in progress.
What zigbee channel are you using?
Iām in a very congested wi-fi area (townhome complex) and also have numerous zigbee hubs and devices active.
I have SmartThings on 25, devices are once again working normally (had issues with some ikea devices after the zigbee stack upgrade).
I also have Hubitat on 20, and Home Assistant on 15 (no idea what channels my Echo 4 or Ikea Dirigera hubs use).
Channels 25 and 20 have always been good for me.
Iām using Channel 24, that was the default and I have never changed it.
Ive had a V3 hub running for around a year now and never had lots of devices dropping offline together until 45.11
I do have a WIFI mesh system in the house but have had that for ages so itās not new.
I also donāt think there is much likelihood of interference from neighours ( Detached house)
Giving this a nudge as I do t want the thread to auto close yet
I see that the 0.45.11 firmware has been marked as āsolvedā in the Status. Not sure this is the case. Iāve been experiencing issues with Zigbee connected devices almost daily since the latest patches.
Today all Zigbee connected sensors are reporting as offline
Same here, my hubs memory is almost full, but I managed to get a stable setup, but yesterday I changed a community driver on 3 light sources to an official Smartthings driver (a Smartthings driver that was already installed on my hub), about 12 hours later my hub began to disconnect/connect constantly. I had to change back to that community driver and nearly instantly, stable hub again !!!
So yeah, itās defintly not solved yet
And no official response to my earlier post:
I wonder if SmartThings is having the same issue in the Aeotec/V3 hubs with Zigbee/Thread multi protocol as Home Assistantā¦
The bug is that Zigbee end-devices cannot rejoin the network through the coordinator: it kicks them and asks them to re-join, over and over. Normal EmberZNet firmware does not behave this way. It only affects end devices joined directly to the coordinator, not ones joining through an intermediate router, and only those that attempt to re-join the network.
Interestingly, all my Zigbee devices have been 100% stable the last 48hrs. Before that they would go offline several times a day. Some devices that stayed offline since the beginning of this ZigBee v. Thread fiasco 2-3months ago that I didnāt even bother reconnecting manually, now I reconnected them and are very stable. Iām turning back on some routines, automations and monitoring closely. Still keeping some ācriticalā devices and automations with Hubitat. If people are still having problems this issue hasnāt been completely fixed then.
Unlikely that itās exactly the same issue, since the Home Assistant device is using one radio to handle two protocols, Zigbee and thread. My understanding, which may be incorrect, was that SmartThings was going to use two different radios.
Historically MultiPAN (thatās the two on one architecture) was mostly used to run multiple Zigbee networks on one radio, or zigbee and Bluetooth, but SI Labs has recently been promoting it for Zigbee/thread combinations. (If itās not obvious, in a multiPAN setup both networks must run on the same channel.)
There are a couple of known bugs in the current implementation:
Thereās also been an ongoing issue with Tuya Zigbee devices for a couple of years with their weird proprietary format which sends multiple values in one frame where the two values donāt get processed together in a multiPAN setup. See the āSend Commands (0x04)ā section of the Tuya docs.
Does anyone know if ST is using a multiPAN setup?