Ratgdo Homekit Sec+ Stops after 1/2 second

[cjwyche95]

Installed Ratgdo on two garage openers:

1. Newer Sec+ 2.0 door and works perfectly
2. Older Sec+ 1.0 door and it stops after 1/2 second either opening or closing which is baffling me on how to get working correctly.

Wiring triple-checked and is 100%. Door goes up and down without issue with wall-panel button. Also have MYQ HomeKit bridge and problem does not occur when using either. Checked obstruction sensors and all checks out. Even unlatched the door from the opener trolly and same issue happens. Switched Ratgdo board and wiring harness with door that works perfectly, but issue still present in same door.

Any ideas would be appreciated.

[dkerr64]

I deleted the post from @ghost as it looks highly suspicious. The user is deleted. Who knows what the zip file at the link contains, but I strongly suspect bad things might happen if you unzipped it.

[dkerr64]

@cjwyche95 Thanks for reporting this. I've not decoded the stack trace but with lots of zeros it looks like the known problem in MDNS responder. We're not sure how to fix it, but it usually stabilizes after a reboot.

The log immediately before the crash shows multiple HomeKit clients trying to connect. What we need is to see a log once the ratgdo has stabilized and then you request to open or close the door. Can you do that please? See the README file for the command line to run to capture the logs in real time.

Thanks

[dkerr64]

That is the same crash log as your first post, you can delete it now... there will be a link at the bottom of the web page to delete.

Do you have Windows, Mac or Linux computer? If you have Mac or Linux then we have a command you can run that will connect to the device and display the log, it is described here. If you are able to run that then you should see the message log, and your screen will update with any activity... so with that connected, try and open/close the door (you will see messages appear) and when finished copy the entire log from your screen and post it here.

Thanks

[dkerr64]

I am now running firmware 1.7.1 which shows more logs than 1.7.0, including System Log, Status Log, Reboot Log, and Crash Log. Would one of those do the job?

Yes, watch the system log tab, it is the same as the command I suggested.

[cjwyche95]

Anything else needed to help resolve this issue? Also, should I delete the logs I've uploaded? Appreciate your assistance.

[dkerr64]

Sorry for going quiet. I am traveling so have not been able to look at this yet.

[dkerr64]

@cjwyche95 yes you can delete the logs that you uploaded here.

Looking at the most recent log you posted, can you tell me at exactly which point you requested the door open... it will be somewhere after timestamp 98000. And are you triggering the request by using Apple Home or by using the door open button on the web interface. Thanks.

[cjwyche95]

Not sure how to pinpoint exactly when I requested the door to open per the log... I can tell you it was within a minute after a reboot, and I requested it through HomeKit. I had to close the door through the wall button after since it always gets stuck after requesting through HomeKit.

[dkerr64]

ok, so I think it occurs at 98 seconds (timestamp 98897) where HomeKit is requesting an update characteristic to set door state to 0 (zero equals open, one equals close). It is interesting that this is sent four times in the space of half a second. The actual request to open the door is triggered at 99350 with a press and release of the sec+ 1.0 door button.

But then your log ends... is there anything more logged? I am not seeing anything that would notify when the door finished opening.

[dkerr64]

@mitchjs looping you into this discussion... anything you can assist with?

[dkerr64]

Please don't keep rebooting the device, it doesn't help. And you need to open up the system logs page before you start to do any testing... you can watch the log messages appear as you request open/close.

Your log shows multiple door press/release actions and that feels odd. Not sure why it is occurring. The Sec+ 1.0 support was provided by @mitchjs so we really need his help to diagnose.

[mitchjs]

sorry guys, been busy, now doing hurricane prep... i actually have my ratgdo disconnected right now, due to mess in garage and with hurricane coming directly on me this Wednesday... I prob cant set back up till next week

@cjwyche95, what kind of wall plate do you have? you could try, with the wall keypad disconnected too if you do that, just reboot the ratgdo, so it goes in to emulation mode give it a min before trying, prob best to use the buttons on the webpage for now and keep homekit out of it (kinda)

[cjwyche95]

It is the Liftmaster 889LM MyQ Control Panel.

[cjwyche95]

I will give your suggestion a try. I had the LiftMaster 78LM Control Panel before replacing with the 889LM Control Panel and it still had the same problem. I'll update with results. Hope you and family are okay from the hurricane.

[mitchjs]

@cjwyche95, also did you make any changes to "settings"? specifically the close door delay.

[cjwyche95]

No, no changes were made to the close door delay.

[mitchjs]

@cjwyche95 , i use the 889LM and no isssues (of course) for sure test it with the web page buttons... lets keep homekit out of it for a bit

also, confirm that the web page shows proper status closed, open etc (can use wall plate to change state, and make sure web updates)

[cjwyche95]

Issue fixed. Turns out, MYQ related devices connected to the garage door was causing the problem. Unplugged all things MYQ and all works perfectly! Problem solved. Guess I should have known to try that a while back.

[mitchjs]

@cjwyche95, out of curiosity what did/do you have connected? and how they connected? to the 2 wires for the wall plate (spot where ratgdo connected). maybe the could be reproduced and i could look at the raw messages coming into the ratgdo my setup is super simple, the gdo and myq digital wall plate (889LM) and that connects to the MYQ internet gateway

[cjwyche95]

I had the MyQ HomeKit bridge and the wireless hub and sensor still running on the door itself. After unplugging all, the problem disappeared. Been working perfectly since. My setup is exactly like yours now, except no MyQ internet gateway.

[mitchjs]

@cjwyche95, if you had the homeKit bridge why need ratgdo? just wondering

[cjwyche95]

The Chamberlain HomeKit Bridge had lots of issues where a reboot was needed often. When it worked and was connected it was fine... but frustrating. Chamberlain also discontinued the product and no longer supported it, so it was sure to stop working eventually. I see the ratgdo as a more permanent solution. I still will have the HomeKit bridge as a backup if Ratgdo has issues.

[dkerr64]

Thank you for reporting this. We should add to documentation/readme a caution about having other devices connected to the garage door.