Hello –
After a power loss (or router restart), all of my Devices are turning on unexpected and on their own.
This is unsafe as we have our fireplace connected. Last night the fireplace was on for 8 hours on its own. How do I prevent the Device from turning on unexpectedly?
Specifically:
- Bond controls our fireplace and creates a Fireplace device
- When the Fireplace device is switched to “On” a special automation runs
- After a power cycle or router restart, the Fireplace is turning on automatically
Here is an image showing what happend:
Thanks,
Brandon
Doesn’t identify the real problem, but for safety’s sake could you add modify your automation so that it doesn’t run when the fireplace goes from unavailable to on, but only when it goes from off to on?
1 Like
Thank you, very good idea.
I also did an automation that reverses it just in case. I’ll leave the question open to try to get to root cause.
This happened to me with Wemo only, but I noticed at one point that after a router reboot, that automations that were supposed to turn one one device would turn on a cpompletely unrelated one instead. (Motion in den turning on a living room light, etc.) It turned out the HA integration for Wemo at that time was not driven by the wemo device mac addresss, but it’s IP address, and upon reboot my router was sometimes reassigning a different IP to different devices than before the router reboot. I made all the devices in my home have static ip addresses (assigned by the router) which resolved the issue. Maybe something similar?
Also for the fireplace, I would suggest when it goes FROM unavailable (to anything), there should be an automation when that happens, to: 1. Turn if OFF and 2. Send you an alert - ?
Thank you Kruse. I’d wondered if it was the Bond integration, but nearly all of my devices are turning On.
I’ve added the FROM/TO - it’s a great recommendation and fixed the safety problem. Really appreciaet you all!
1 Like
Sure, I’ve gotten a great amount of information here, so it’s only fair to give back
1 Like