r/ratgdo•
crazy4dogs

Reboot loop after successful install

I thought I somehow bricked my Ratgdo, but I didn't. Here's what happened to me.

I loaded the serial driver, flashed the firmware (Mac), and entered my Wi-Fi credentials; the whole process was fairly seamless. I saw someone mention that the Apple Multiport Adapter would not work, so I did buy another USB adapter. After doing the flash, I checked the web status page and saw it was connected to my Wi-Fi. Home Assistant found it using ESPHome, and everything looked great.

The next day, when I returned to my laptop where I had left the Ratgdo plugged into my USB port, the device appeared to be in a reboot loop. There was a JavaScript error, and the web page for Ratgdo now looked like it had crashed, showing only a partial status page. I couldn't access it over the serial port to reset or re-flash the firmware, even after rebooting my laptop and power cycling the Ratgdo. My router's Wi-Fi page indicated that it had a new IP address. I believe that was due to the router rebooting last night (but that should not cause a problem). So, I unplugged the Ratgdo from my Mac and installed it on my garage opener. It worked. So, after flashing the firmware, it seems there's a reboot bug if you don't install it right away.

Here's the stack from the JavaScript console

www.js:3 Uncaught (in promise) Error: invalid template strings array
    at Ct (www.js:3:335)
    at Mt (www.js:3:1057)
    at new T (www.js:3:1221)
    at R._$AC (www.js:3:4731)
    at R.g (www.js:3:4433)
    at R._$AI (www.js:3:4089)
    at zt (www.js:3:7409)
    at yt.update (www.js:3:7811)
    at yt.performUpdate (www.js:1:6064)
    at yt.scheduleUpdate (www.js:1:5716)

and I believe that corresponds to this throw

function Ct(r, t) {
    if (!Array.isArray(r) || !r.hasOwnProperty("raw"))
        throw Error("invalid template strings array");
    return dt !== void 0 ? dt.createHTML(t) : t
}

The device is Ratgdo 2.5i and the firmware is 2024.10.0 Oct 21 2024, 21:47:47

I have no idea if this bug is triggered by something about my setup, but it's working now so I thought I'd mention this in case someone else also they've also bricked their device.

Posted Oct 24, 2024, 6:35 AM UTC

30
Loading comments…