It's Halloween so it's a good time to put this one out for consideration.
The Device: C-8 non-Pro. Latest updates. Every device is Zigbee except for a few Lutron plug-in dimmers run through Lutron's PRO hub.
Setting the Table: I recently had a water leak in my home that caused a lot of damage, including the room in which I had my modem, router, and C-8. Everything was running like a top; no real issues except with Third Reality bulbs not liking to shut off.
The Problems Started... The problems started when I moved the entire installation to a spare room. Modem, router, C-8, Lutron. Same setup as before.
The Problems: It is mostly a Third Reality bulb issue but now and then one of my Inovelli wall dimmers acts up. Third Reality bulbs: mysteriously turning themselves on, sometimes an entire fixture-full, then going out in anywhere from 30 seconds to a couple of minutes. The times are not consistent. Inovelli Wall Dimmers: I will see one or another with the "stripe" barely showing, meaning it might be feeding 5% or so power to a fixture.
The Lutron stuff has behaved itself.
What I have tried: Powering down and waiting 30 minutes. Re-boots.
I would have thought that would have been enough. I would re-include a few zigbee devices closest to your hub by resetting them. They will rejoin them as known devices and you won’t loose anything. Might give your zigbee mesh a jumpstart.
I can understand a hub location change causing missed commands, but I don't see how it could cause ghost commands.
Alexa hunches being on can cause this if you share the devices with Alexa. What do the bulbs report as the source of the On events in Events tab on the device page? If it was Alexa, you should see it there. Either way, checking the source of the ghost events should tell you something.
I will say that I see something similar when I have power outages. It takes a day or two for the network to settle in. Additionally, many of my bulbs will come back on in a weird state (barely dimmed on) and I have to send a command to them to turn them on fully (or, walk in front of a motion sensor that triggers the same.)
As to the "ghost" actions, I figured out that with the mesh messed up, the commands sometimes execute a REALLY long time after they had been sent. This was usually caused by me walking by a motion sensor, and the light it was supposed to trigger not coming on. Then, minutes (sometimes almost an hour) later, the action executes. It took a while for me to put it together what was actually going on.
One thing I forget to do after every outage is to open a community app (Zigbee map) and run a new map. That almost always gets my mesh back more quickly. It can also identify problem children:
