Messed up my Ratgdo.

[medic165]

I made the horrible mistake of doing an OTA firmware upgrade on my perfectly working Ratgdo32. Now this is what I get.

13:33:04 | [D] | [ratgdo_secplus2:356] | Sending packet: [55:01:00:8A:3D:F6:D8:6D:F6:DF:78:A9:23:87:AC:46:E2:C2:05]
13:33:04 | [D] | [ratgdo_secplus2:356] | Received packet: [55:01:00:8A:3D:F6:D8:6D:F6:DF:00:A9:23:87:AC:06:FE:F8:FE]
13:33:04 | [W] | [ratgdo_secplus2:367] | Decode failed (parity error or invalid frame)
13:33:05 | [D] | [ratgdo_secplus2:444] | Send command: DOOR_ACTION, data: 01:00:01
13:33:05 | [D] | [ratgdo_secplus2:356] | Sending packet: [55:01:00:8A:3D:F6:D8:6D:F6:DF:7C:A9:23:87:AC:46:E2:82:05]
13:33:05 | [W] | [ratgdo_secplus2:343] | Discard incomplete packet, length: 18
13:33:35 | [D] | [api.connection:2409] | Home Assistant 2026.5.0 (10.0.0.103): disconnected
13:33:35 | [W] | [component:389] | api set Warning flag: waiting for client connection
13:33:45 | [D] | [preferences:136] | Writing 1 items: 0 cached, 1 written, 0 failed
13:33:47 | [D] | [api:220] | Accept 10.0.0.103
13:33:47 | [W] | [component:422] | api cleared Warning flag
13:33:47 | [D] | [api.connection:2409] | aioesphomeapi (10.0.0.103): connected
13:33:47 | [D] | [api.connection:2409] | aioesphomeapi (10.0.0.103): disconnected
13:33:47 | [W] | [api.connection:2415] | aioesphomeapi (10.0.0.103): Reading failed CONNECTION_CLOSED errno=128
13:33:47 | [W] | [component:389] | api set Warning flag: waiting for client connection
13:33:47 | [D] | [api:220] | Accept 10.0.0.103
13:33:47 | [W] | [component:422] | api cleared Warning flag
13:33:47 | [D] | [api.connection:2409] | Home Assistant 2026.5.0 (10.0.0.103): connected
13:33:53 | [D] | [ratgdo_secplus2:444] | Send command: DOOR_ACTION, data: 01:01:00
13:33:53 | [D] | [ratgdo_secplus2:356] | Sending packet: [55:01:00:89:02:08:03:00:40:04:07:9A:23:15:75:6A:56:13:4D]
13:33:53 | [D] | [ratgdo_secplus2:356] | Received packet: [55:01:00:89:02:08:03:00:40:04:00:9A:23:15:75:6A:D5:D4:FF]
13:33:53 | [W] | [ratgdo_secplus2:367] | Decode failed (parity error or invalid frame)
13:33:53 | [D] | [ratgdo_secplus2:444] | Send command: DOOR_ACTION, data: 01:00:00
13:33:53 | [D] | [ratgdo_secplus2:356] | Sending packet: [55:01:00:89:02:08:03:00:40:04:03:9A:23:15:75:6A:56:03:4D]
13:33:54 | [W] | [ratgdo_secplus2:343] | Discard incomplete packet, length: 18
13:34:45 | [D] | [preferences:136] | Writing 1 items: 0 cached, 1 written, 0 failed
13:35:52 | [D] | [wifi:2408] | Roam check skipped, signal good (-39 dBm, attempt 3/3)

It's a sears craftsman opener but it's a rebadged Chamberlain opener with security 2.0. I had it working flawlessly before with the Ratgdo32 , Home Assistant and even Alexa. Now this is what I have. Nothing has changed in the wiring. The only change was the stupid firmware update attempt.

[PaulWieland]

Can you elaborate? What happens when you try and control the door from ratgdo or from the wall control panel?

[medic165]

I can operate the door with then wall button just fine. But not within the Ratgdo32 internal page or Home Assistant. The MyQ App is working fine.

I have disconnected the Ratgdeo32 and went through the firmware installation process a couple times (even checking erase on the setup).

[medic165]

I can operate the door with then wall button just fine. But not within the Ratgdo32 internal page or Home Assistant. The MyQ App is working fine. I have disconnected the Ratgdeo32 and went through the firmware installation process a couple times (even checking erase on the setup).

…

On Thu, May 7, 2026 at 1:47 PM Paul Wieland ***@***.***> wrote: *PaulWieland* left a comment (ratgdo/esphome-ratgdo#618) <#618 (comment)> Can you elaborate? What happens when you try and control the door from ratgdo or from the wall control panel? — Reply to this email directly, view it on GitHub <#618 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZ2SY4KGSLQ4OT6ZTCOE2534ZTD3JAVCNFSM6AAAAACYU5WBGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJZGY2DIMJSGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Medic165 ***@***.***

[PaulWieland]

Can you please post a picture of your wiring?

[medic165]

Sent from my iPhoneOn May 7, 2026, at 15:01, Paul Wieland ***@***.***> wrote:PaulWieland left a comment (ratgdo/esphome-ratgdo#618) Can you please post a picture of your wiring? —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[medic165]

Wait…is this door a security 1.0?  I just realized I don’t have a yellow button on it. My other Chamberlain door is a security 2.0 for sure. It works fine btwSent from my iPhoneOn May 7, 2026, at 15:05, Roger Barnes ***@***.***> wrote:<image0.jpeg><image1.jpeg>Sent from my iPhoneOn May 7, 2026, at 15:01, Paul Wieland ***@***.***> wrote:PaulWieland left a comment (ratgdo/esphome-ratgdo#618) Can you please post a picture of your wiring? —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[medic165]

I think I have it fixed. The sears craftsman door opener is a Security 1.0 door. The door to my work shop is a chamberlain security 2.0. I loaded the wrong firmware on the door. Anyway, It's up and running. BUT... The log on the right had side just scrolls and scrolls data. That's why I initially thought about upgrading the firmware thinking it was a bug. But now that I have it restored to the correct and newest version it's still doing it. Is this normal? I've attached a screenshot. Thank you for your help Roger

…

On Thu, May 7, 2026 at 3:01 PM Paul Wieland ***@***.***> wrote: *PaulWieland* left a comment (ratgdo/esphome-ratgdo#618) <#618 (comment)> Can you please post a picture of your wiring? — Reply to this email directly, view it on GitHub <#618 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZ2SY4J7YVLXSDK5YVY7I4D4ZTMRXAVCNFSM6AAAAACYU5WBGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMBQGIYDGMBVGE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Medic165 ***@***.***