Looking for Help With RATGDO DISCO?

[Jimrpa]

Admins, please move if appropriate but I did see other discussions of RATGDO in this sub.
I’m looking for anyone who might be able to help me diagnose problems with RATGDO or point me in the right place. I posted the below to the RATGDO sub on Reddit a few days ago, and did not get a response.


I have a Chamberlain 41AB050-2M (Security 1.0+, Purple Learn Button, Manufactured July 2009). I replaced the original wall control panel with the 889LM panel, as recommended. After putting in the new panel (and before installing the RATGO DISCO), everything was working fine. The outside keypad opened and closed the garage door, the 889LM panel opened and closed the garage door, and the motion sensor turned on the opener lights whenever there was motion (such as walking into the garage from the house).

I received my RATGO DISCO with parking assistance laser module. I use Apple HomeKit, and was able to configure it with Firmware 3.0.7 using Chrome on my MacBook Air M2 without any issues. I used the pass-through ports and the 3-wire (Red/White/Black) pigtail to connect it to the garage door opener.

There are two sets of wires (4 total) coming from my obstacle sensors up to the GDO. For each obstacle sensor, there is a white wire and a white wire with a black stripe. When connected to the GDO, a white wire and a black wire were twisted together and inserted into the white port on the GDO. The other white wire and black wire were also twisted together, then inserted into the black port on the GDO. The wiring diagram for the RATGDO DISCO shows two white wires from the obstacle detectors going to the second terminal labeled "W" on the bank of 4 pass-through terminals, and the two black wire going to the terminal labled "B" on the bank of 4 pass-through terminals, so I went ahead and wired the obstacle sensors that way.

Here's what works:

I'm able to access the status webpage from Chrome on my MacBook by going to the IP address assigned to the RATGDO DISCO.

I'm able to open the garage door from the status webpage by clicking the "Open Door" button. it usually takes clicking 2-3 times on that button before it responds.

I can both open and close the garage door using the 889LM control panel.

I can turn on and off the GDO light using the 889LM control panel.

I can turn on and off the GDO light using the control in HomeKit.

I can turn on and off the parking assistance laser using the control in HomeKit.

I can open the garage door using the control in HomeKit.

I can open and close the garage door using the remotes.

Here's what doesn't work:

The motion detector on the 889LM no longer turns on the lights. (Note: I DO have the wall panel motion trigger checked in the settings webpage.)

I am NOT able to close the garage door from the status webpage by clicking on the "Close Door" button. All that happens is, each time the "Close Door" button is pressed, the beeper on the RATGDO DISCO beeps several times, and the GDO light flashes, as if there is an obstacle blocking the sensors (there is no obstacle).

I am NOT able to close the garage door using the control in HomeKit. Again, all that happens is that each time I slide the garage door control down (to the "closed" position, the beeper on the RATGDO DISCO beeps several times, and the GDO light flashes, as if there is an obstacle blocking the sensors (there is no obstacle).

To summarize: I can only CLOSE the garage door using the wall panel or a hand-held remote. I can't close it from HomeKit or the web interface. The motion sensor on the 889LM panel no longer turns on the garage lights.

I've rebooted the device a few times, and no change in behavior.

Any ideas?

Sponsored

 

[AliRafiee]

I have an idea. Send them an email.

Very bottom of this page.
https://ratcloud.llc/pages/frequently-asked-questions

 

[Jimrpa]

I have an idea. Send them an email.

Very bottom of this page.
https://ratcloud.llc/pages/frequently-asked-questions

Thanks so much! That’s what I get for not reading the “fine print”.

 

[DevSecOps]

The Homekit firmware is in beta still isn't it? Aren't you also supposed to flash ESPHome on it first?

I use the base model with HA and the same wall controller, only I have a yellow button GDO. Works flawlessly. I have no issues with occupancy sensor or control.

I'd try a stable firmware without HomeKit and see if everything works. Then maybe create an issue on GitHub with your findings.

 

[Jimrpa]

The Homekit firmware is in beta still isn't it? Aren't you also supposed to flash ESPHome on it first?

I use the base model with HA and the same wall controller, only I have a yellow button GDO. Works flawlessly. I have no issues with occupancy sensor or control.

I'd try a stable firmware without HomeKit and see if everything works. Then maybe create an issue on GitHub with your findings.

Hey, it’s so great to see you again! I thought you had moved on.

I’m not sure about the HomeKit software being “beta”. They speak about HomeKit support as “a thing” in all their documentation, and the software version is 3.0.7.
I thought about going with HA, but it seems pretty complex to set up an HA server when I already have almost everything working the way I want with HomeKit and I don’t want to do anything super complicated.
I do have an email into the address and will report any response I get from that.

 

[Jiji]

Any ideas?

I run a pair of the older RATGDO hardware with the HomeKit firmware and it has been flawless. But here are some ideas:
1. My 889LM modules are crap, even after getting them replaced by Chamberlain mine have terrible sensitivity. But to solve the motion detection I would unplug the RATGDO from the motor and see if they work as expected. My gut feeling is the RATGDO should not impact the motion detection on the wall switches but who knows.

2. Check the system log file and the status, you will need these to create an issue on GitHub. Sure sounds like it thinks there is an obstruction and I would expect the status to show this. Here is my current status (I assume the ESP32 firmware has something similar):

RATGDO device status...
{
"upTime": 1004848817,
"deviceName": "Baba Garage Door",
"userName": "admin",
"paired": true,
"firmwareVersion": "1.8.3",
"accessoryID": "DC:32:D6:C7:01:58",
"clients": 1,
"GDOSecurityType": 1,
"garageDoorState": "Closed",
"garageLockState": "Unsecured",
"garageLightOn": false,
"garageMotion": false,
"garageObstructed": false,
"passwordRequired": false,
"rebootSeconds": 0,
"freeHeap": 23544,
"minHeap": 20256,
"minStack": 1120,
"crashCount": 3,
"wifiPhyMode": 0,
"wifiPower": 20,
"staticIP": false,
"syslogEn": false,
"syslogIP": "0.0.0.0",
"syslogPort": 514,
"TTCseconds": 0,
"motionTriggers": 0,
"LEDidle": 0,
"lastDoorUpdateAt": 11898514,
"enableNTP": true,
"serverTime": 1741565474,
"timeZone": "America/New_York;EST5EDT,M3.2.0,M11.1.0",
"checkFlashCRC": true
}

 

[Jiji]

I’m not sure about the HomeKit software being “beta”. They speak about HomeKit support as “a thing” in all their documentation, and the software version is 3.0.7.

The GitHub repo is your friend. Very much a work in progress for now.

Important

This firmware is for the ratgdo32 and ratgdo32-disco series boards. It will not work with the ratgdo v2.5xi boards. HomeKit support for for the original v2.5xi devices can be found here

THIS IS EARLY FIRMWARE still under test. Future updates MAY include breaking changes requiring a flash erase and re-upload.

Firmware for the new DISCO device is under development. The following features, documented in this README, are not currently available in this version and may never be implemented

• Locking WiFi to specific WiFi access point.
• Setting WiFi protocol version.
• Setting WiFi transmit power.

 

[DevSecOps]

Hey, it’s so great to see you again! I thought you had moved on.

I’m not sure about the HomeKit software being “beta”. They speak about HomeKit support as “a thing” in all their documentation, and the software version is 3.0.7.

I have moved on but this weekend I was quoted and referenced on this board a bit so I decided to drop in and respond. While I cant really help with the MME anymore, there are other things that I know something about that I might be able to help with so I chimed in.

I'm fairly certain the base model works well with HomeKit, but the Disco is a work in progress. I'd be interested to see how it works out for you and if you ever decide to go with HA and need help send me a DM. I'd be more than happy to help! I just moved my HA server from a RPi4 (where it was for 5 years) to an Asus NUC last month and couldn't be happier.

Take care!

 

[Jimrpa]

I have moved on but this weekend I was quoted and referenced on this board a bit so I decided to drop in and respond. While I cant really help with the MME anymore, there are other things that I know something about that I might be able to help with so I chimed in.

I'm fairly certain the base model works well with HomeKit, but the Disco is a work in progress. I'd be interested to see how it works out for you and if you ever decide to go with HA and need help send me a DM. I'd be more than happy to help! I just moved my HA server from a RPi4 (where it was for 5 years) to an Asus NUC last month and couldn't be happier.

Take care!

Thanks so much for the offer. I just may take you up on it!
It’s puzzling that it works very reliably from the basic infrastructure (control panel, keypad remote, handheld remotes), fairly reliably from the webpage, but pretty unreliable from HomeKit.
I’ll also check around on GitHub.

 

[AhardFSU]

Thanks so much for the offer. I just may take you up on it!
It’s puzzling that it works very reliably from the basic infrastructure (control panel, keypad remote, handheld remotes), fairly reliably from the webpage, but pretty unreliable from HomeKit.
I’ll also check around on GitHub.

I was going to mention that you should check the GitHub. But you’ll need the logs from your system in order to open a ticket.

Im using the yellow button security 2.0 RatGDO but I’m using it with Home Assistant. It’s been working flawlessly for the last 3 weeks.

 

[Jiji]

To summarize: I can only CLOSE the garage door using the wall panel or a hand-held remote. I can't close it from HomeKit or the web interface. The motion sensor on the 889LM panel no longer turns on the garage lights.

Save yourself time by ignoring HomeKit for now and focus on getting the web interface working (HomeKit will likely work when you sort out the web interface controls).

For what it’s worth, here is a close door operation using the web interface button in an OG RATDGO log. Hopefullly your log has some info on why the GDI can’t be closed.

[2025-03-10T13:13:26.828Z] RATGDO: close door request
[2025-03-10T13:13:26.834Z] RATGDO: SetGDO Complete
[2025-03-10T13:13:26.840Z] RATGDO: Writing user configuration to file: user_config
[2025-03-10T13:13:27.003Z] RATGDO: sending DOOR button press
[2025-03-10T13:13:27.384Z] RATGDO: sending DOOR button release
[2025-03-10T13:13:27.434Z] RATGDO: sending DOOR button release
[2025-03-10T13:13:27.686Z] RATGDO: 0x3A val upper nible not 5: 38
[2025-03-10T13:13:29.727Z] RATGDO: status DOOR: Closing
[2025-03-10T13:13:29.796Z] HomeKit: [Client 1073698180] Got characteristic 1.11 GARAGE_DOOR_OPENER Current Door State change event 3
[2025-03-10T13:13:29.803Z] HomeKit: [Client 1073698180] Got characteristic 1.12 GARAGE_DOOR_OPENER Target Door State change event 1
[2025-03-10T13:13:29.831Z] RATGDO: Current Door State changing from 0 to 3
[2025-03-10T13:13:29.837Z] RATGDO: Writing user configuration to file: user_config
[2025-03-10T13:13:29.966Z] RATGDO: SSE send to client 192.168.1.243 on channel 0, data: { "lastDoorUpdateAt": 0, "garageDoorState": "Closing", "upTime": 1051785117 }
[2025-03-10T13:13:29.982Z] RATGDO: SSE send to client 192.168.1.243 on channel 1, data: { "lastDoorUpdateAt": 0, "garageDoorState": "Closing", "upTime": 1051785117 }
[2025-03-10T13:13:30.658Z] HomeKit: [Client 1073698180] Requested characteristic info for 1.6 ACCESSORY_INFORMATION Firmware Revision 1.8.3
[2025-03-10T13:13:40.799Z] RATGDO: status DOOR: Closed
[2025-03-10T13:13:40.854Z] HomeKit: [Client 1073698180] Got characteristic 1.11 GARAGE_DOOR_OPENER Current Door State change event 1
[2025-03-10T13:13:40.875Z] RATGDO: Current Door State changing from 3 to

 

[AhardFSU]

Save yourself time by ignoring HomeKit for now and focus on getting the web interface working (HomeKit will likely work when you sort out the web interface controls).

For what it’s worth, here is a close door operation using the web interface button in an OG RATDGO log. Hopefullly your log has some info on why the GDI can’t be closed.

[2025-03-10T13:13:26.828Z] RATGDO: close door request
[2025-03-10T13:13:26.834Z] RATGDO: SetGDO Complete
[2025-03-10T13:13:26.840Z] RATGDO: Writing user configuration to file: user_config
[2025-03-10T13:13:27.003Z] RATGDO: sending DOOR button press
[2025-03-10T13:13:27.384Z] RATGDO: sending DOOR button release
[2025-03-10T13:13:27.434Z] RATGDO: sending DOOR button release
[2025-03-10T13:13:27.686Z] RATGDO: 0x3A val upper nible not 5: 38
[2025-03-10T13:13:29.727Z] RATGDO: status DOOR: Closing
[2025-03-10T13:13:29.796Z] HomeKit: [Client 1073698180] Got characteristic 1.11 GARAGE_DOOR_OPENER Current Door State change event 3
[2025-03-10T13:13:29.803Z] HomeKit: [Client 1073698180] Got characteristic 1.12 GARAGE_DOOR_OPENER Target Door State change event 1
[2025-03-10T13:13:29.831Z] RATGDO: Current Door State changing from 0 to 3
[2025-03-10T13:13:29.837Z] RATGDO: Writing user configuration to file: user_config
[2025-03-10T13:13:29.966Z] RATGDO: SSE send to client 192.168.1.243 on channel 0, data: { "lastDoorUpdateAt": 0, "garageDoorState": "Closing", "upTime": 1051785117 }
[2025-03-10T13:13:29.982Z] RATGDO: SSE send to client 192.168.1.243 on channel 1, data: { "lastDoorUpdateAt": 0, "garageDoorState": "Closing", "upTime": 1051785117 }
[2025-03-10T13:13:30.658Z] HomeKit: [Client 1073698180] Requested characteristic info for 1.6 ACCESSORY_INFORMATION Firmware Revision 1.8.3
[2025-03-10T13:13:40.799Z] RATGDO: status DOOR: Closed
[2025-03-10T13:13:40.854Z] HomeKit: [Client 1073698180] Got characteristic 1.11 GARAGE_DOOR_OPENER Current Door State change event 1
[2025-03-10T13:13:40.875Z] RATGDO: Current Door State changing from 3 to

Totally. Get the web interface working and then circle back to Homekit.

Sponsored