Has anyone been successful in controlling the Sonoff TX Ultimate with this?
Successfully setup my Ratgdo yesterday, using the current esphome drivers, however I noticed that there are several attributes/capabilities that could be added. (I have the Disco Version) before I start adding them, wondering if anyone else has already done the work.
FWIW I did it all within Hubitat, no need for MQTT or HA to be in the mix.
Thanks!
2 Likes
So I have been using a ratgdo 2.5i mostly flawlessly for about 6 months with ESPHome drivers. For some reason over the last month or so it has begun being unresponsive. Some days it works, and for the most part it will go a couple of days not responding to commands. Then it will respond to commands again.
Is anyone else having similar issues as of late? Firmware on the ratgdo is the October 2024 firmware for ESPHome.
Sorry for your troubles. I have had mine up and running since April 2024 and have had no issues. I havenāt updated the firmware since that time either given it has been working.
How is your wireless connectivity in your garage? A weak signal might be causing your troubles.
Wireless is good, I have a backhauled mesh router in the garage connected via Ethernet. Signal is strong.
The odd thing is it just started happening out of the blue? Everything has been fine for months and then suddenly it just starts dropping off. And I should add that I can still access the ratgdo via browser&its IP address when it becomes unresponsive in Hubitat.
Might just have to integrate it to HA and bring it over to Hubitat for more reliability.
Strange. You might try a continuous ping from a computer to see if you get a no response at the same time it falls off your HE hub.
With your mesh do you use the same SSID for both 2.4 and 5ghz? I have a separate dedicated 2.4 SSID for my IoT devices such at RATGDO.
Huh I didnāt think about the ping, Iāll try that.
And just like you, itās a separate dedicated 2.4ghz for all my iot devices.
1 Like
Try re-booting the devices. I found them to be sensitive to issues in my own environment. To the extent I added a controllable plug and re-cycle them nightly.
1 Like
I have an Eero mesh and find that it needs to be rebooted occasionally as devices start dropping if I donāt. I suspect a similar issue here.
Rebooted ratgdo, WiFi, and it fell off again tonight. Unfortunately when I opened it I didnāt have debugging enabled so the photo is all I got. Opening the garage door did wake the device and its rules attached (garage lights turning on when opening and off when closing) worked flawlessly.
And in events I see it attempting to connect and not doing so until I opened the garage door.
@wyn.carlton thanks for posting your logs, seeing this rings a bell:
Look at your past logs to and click dev:37 to filter on your GDO device. Do you see this error happening daily? I recall modifying my driver to get past that error and to successfully reconnect.
After researching the primary reason mine was failing was because of a nighttime routine of mine where I was invoking a close on the garage door when it was already closed. The RATGDO or driver didn't handle that very well and errored out and thus disconnected.
1 Like
I am seeing a HealthCheck, and it has passed/not lost connection so far this morning.
My past logs do show that error happening daily. Do you remember what you modified in the driver to get past the error?
And I'll have to take a look at what routines I have that might be causing the error like you mentioned, but I believe the only thing I have setup for my garage door is nfc tags for open/close.
I just posted my version to Github here. Changed from @ady624's version he posted here:
- Disabled the dry contacts since I don't use them
- Disabled processing the position attribute until the door stops moving - when the door is opening or closing that hammers the hub with events which I personally don't find useful
- Changed obstruction to use the motion attribute instead - believe it originally was based on the wall controller and its motion which again I don't find useful. I am using the obstruction sensor via motion for another automation.
- Put in some additional handling to not invoke the close if the door is already closed
- Added a setPosition function which allows you to close to the door to a certain value
Hopefully this solves your issue. If there is a feature above you want reverted I can help with that too.
Just a heads up, I was running into connection issues daily. I noticed that the driver install via HPM referenced the ApiLibrary Bundle Zip file. That file had not been updated in awhile. Its just a zip of the groovy file.
I opened a PR and moving forward that zip file will be automatically updated if/when there are changes to the groovy file. I don't think the version was bumped so HPM may not be aware of the change.
All that to say, if you have an old copy of espHomeApiHelper in your "libraries code", you should update it and see if it helps.
3 Likes
Thank you! This worked like a charm, and so far Iām going on almost 24 hours (previously it was maybe 8-10 hours max) of it staying connected.
