It first happened a few months back and I thought that it was just a one off glitch. Now it has happened four times and I have no idea how to troubleshoot.
An automation is triggered, via button press or schedule so far. Random devices then change state in addition to the expected action.
Automation from a switch press to turn off three lights on the kitchen triggered, but randomly turned on/off lights throughout the house.
Schedule to close one set of blinds, also closed two unrelated blinds and turned a bunch of lights on and others off.
Other examples are the same but different. There’s no single device or action that appears to cause if, each time it has been different. Some devices are groovy, some edge and some integrated (ie Philips Hue)
I have no idea how to troubleshoot or where to really start.
In particular, Zigbee handheld buttons and remotes, as well as battery powered, wall-mounted, remotes, have been known to trigger other Zigbee devices in the same Zigbee group. that’s because many of these devices have the option to be used without a hub at all, just the remote and the smart bulb, so they have the ability to broadcast directly to the group.
I asked for the model numbers because that’s what matters for troubleshooting. Just as an example, the GE switches and the Schlage locks come in both Zigbee and zwave models. Each can get glitchy, but for different reasons. So especially when asking for troubleshooting help on the internet in the future please give specific model numbers.
That said, you have enough variety in your setup that it doesn’t look like a protocol issue.
Most likely either SmartThings platform glitches, delayed automations, or Alexa hunches.
Alexa hunches are easiest to troubleshoot, so I’d start by looking there.
I’m not feeling well this morning so I’ll leave it to others to answer questions on that, but here’s a good thread, with a lot of details from someone who got hit by the problem:
I will go pull all the exact model numbers for you.
It’s not an Alexa issue, from what I can tell. Alexa does not have any routines that call SmartThings devices, we only connect it to Harmony Hub, which is not integrated with ST. There was nothing in the logs for Alexa calls recorded. We only have the Alexa Show in our bedroom too, and it is disabled in all the other smart devices, like the TV, and soundbar.
I had a similar, but not exact issue as OP some time ago. I turned off Alexa Hunches, (it is on by default), and the problem stopped. It is an easy troubleshoot. I actually had no idea Hunches was even a thing…
I’m not sure about regions, but I searched endlessly to find out why a device was turning OFF at random times without any interaction. I found nothing in the event list or any logs that showed the device state was changed. It was weird. Then someone suggested Hunches. Never had the problem again. It was hard to locate in the app. I think I read that you can speak the command to Alexa to turn it off.
EXCERPT FROM ONLINE:
Last year, Amazon rolled out an Alexa feature called Hunches. It allows the assistant to proactively complete house tasks for you without having to ask permission . Alexa will perform hunches - like automatically turn off your lights - all based on your past habits and requests.
You mentioned it started about a month ago. Did anything happen around that time… add new device/edit any devices/hub firmware update that may occurred around that time? Nothing shows in History for any of the devices affected?
I ask because about a month ago, smartthings updated the firmware in the V3 hub to turn on the thread radio. Which is actually the same radio as the Zigbee radio, but the two are now taking turns. This caused a bunch of issues for some community members with their Zigbee devices, including some random turning on and off. They tried to fix it with a new hub firmware update, which didn’t fix it right away, although I think it’s supposed to be fixed now after yet another update.
Anyway, the point of all that is that quite a few people were having problems with Zigbee Devices in November, and December, But of course that doesn’t explain the other issues unless there was a triggering issue with the Zigbee device.
There were a number of different threads about the issue, the following was typical:
the issue was also mentioned in the official release notes for the hub Firmware updates.