Today the automation that turns my garage lights on when I walk into the garage because the garage door opener sensor sees me stopped working. All other automations that use the ratgdo and my lights work.
I saw this message:
Motion:
This entity is no longer being provided by the esphome integration.
Is there another option? What gives?
device_class: motion still works fine, no recent changes. Show us your yaml, also have you. restarted the device, what were any recent changes etc.
alias: Motion garage lights on
description: “”
triggers:
I doubt your issue is with the automation, since you have already shown us the device is showing as unavailable. More likely you have an issue with the ESPHome device, either a comms or config issue.
When posting code use the preformatted text </> tag around it.
Failure to to do so will make the forum remove important indentations and bug hunting becomes hard then.
Code must be properly aligned and using the correct syntax. Also, when you’re in a specific forum like this one, Esphome. Its not very helpful to us or useful for you to put in here because, that is syntax specific to Homeassistant and not Esphome. When your Esphome entity isnt even being integrated into HA from your Esp device then if you think about it then its easier to recognize the Esphome part is the problem and if it’s not even being recognized in HA then messing around with your HA automation code for that sensor isn’t very helpful because HA shows your sensor as “Unavailable” which means the automation doesn’t comprehend the name of a non working entity so we need to focus elsewhere with our troubleshooting, if that makes sense?? Its kind of like if i were to get irritated because I cant find my favorite Backstreet Boys mix tape but, my wife is still using my car to do shopping so there’s not even a reason to stress over the mix tape because I wouldn’t be able to listen to it anyway…
I am guessing (because it is not clearly stated) that you are using this GitHub - ratgdo/esphome-ratgdo: ratgdo for ESPHome · GitHub
I (and others) are also guessing at what the real problem is. You seem to be saying that only one of the multiple sensors that the device/integration provides is missing, is the others are present. If that is true, I would start by restarting the ratgdo device (cycle power on it, or if it has a reboot button on its web UI).
If others are missing, it points to the device not communicating anymore.
Another option might be that the sensor got recreated with a _2 in the end and the original one is then unavailable.
It happens from time to time with some entities in HA.
You can delete the unavailable one then and rename the _2 to the original name.
I’m having the exact same issue. Over the past week or two, I noticed that my garage lights—triggered by motion via the ratgdo32—stopped working. After doing some digging, it seems the ratgdo32 no longer shows motion status at all on its web interface. Previously, I could see motion events there, but now nothing shows up.
As a workaround, I modified my setup so that when the garage door opener’s built-in light (which is internally triggered by motion) turns on, it also triggers my actual garage lights.
Something definitely changed. I’m wondering if the Chamberlain garage door opener received an OTA firmware update. While troubleshooting, I also updated my ratgdo32 to the latest firmware, but the problem persists.
Everything was working fine before, and then suddenly it stopped. I’m still trying to figure out what changed and why.
