Open skykep opened 2 months ago
Try and reflash with full erase to see if a new randomly generated client ID fixes the problem.
Try and reflash with full erase to see if a new randomly generated client ID fixes the problem.
Yep, did that and it works for a few days, but ultimately ends up losing control again. This is on reddit with several others experiencing the same issue. Only appears to be with the MQTT firmware.
Any way I can pull logs off it to help? Just seems like it's losing the rolling code for control because the status hasn't stopped working at all.
I dont think its losing the rolling code, its just using a bad seed. There is some difference in the way the random rolling code is initialized between the esphome version and this version that I have to look into.
Until I figure it out, the only way to get a new random code with the mqtt firmware is to do a full erase and reflash.
Alternatively you can enable MQTT support in the esphome version and use that instead.
Oh, that's some good news. I'll give that a shot for now and report back.
2 of my 4 units are on Craftsman belt-driven overhead units. Flashed with 2.57 MQTT firmware and set for security + 2.0 (yellow buttons). Worked for a bit, but today I discovered that these two Craftsman units are no longer responding to commands. They still report status of door and light (although very delayed), and the wall-mounted door openers still work fine.