This is one of the really old ones with motion sensing, similar to the 398LM that also has compatibility issues. I have not seen many of these out in the wild … it sounds like they were only on the market for a short time and 10+ years ago.
I can’t say for sure, but i strongly suspect it is these much older wall panels that are causing the problem. The 398LM is confirmed known to cause interference with communication, sometimes resulting in unintended door openings.
You can test it by simply removing the wall button from the circuit (disconnecting it). If the GDO blaQ works reliably with the wall button disconnected, then we know it’s the wall button causing interference.
Recommended replacements are the 889LM if you want motion sensing capability and all the bells/whistles or 78LM or generic equivalent if you want a cheaper, basic analog wall button.
I have the same model wall control (41A6318) and have been experiencing random openings/closings as well. I can confirm that selecting +1 is the only protocol option that works - neither +1 with smart panel or +2 work at all. I’ve ordered a 78LM and will confirm here if it solves the issue.
I don’t have the same model wall panel, but I do have an older (purple button) Security+1.0 garage door opener, as well as an old wall panel at one location.
Even before I installed the blaQ, I’d get some random weird experience with the motion sensor on the wall panel, where it wouldn’t trigger the garage light at all.
Anyway, I have alerts setup in HA to let me know if the garage door opens and no one is home, and it kept triggering, and I noticed this in the logs:
The garage door isn’t actually opening, so as a work around, I set a little delay on the alert I have setup. I suspect it’s either a failing wall control panel, and/or the wiring for it, rather than the blaQ itself.
If you’d like to have a look/investigate that particular blaQ, in case it’s some issues with the Security+1.0 protocol implementation, I’d be happy to help. Note that I also had to manually set Security+1.0 and not auto on this one, my other location with a much newer garage door opener supporting Security+2.0 works perfectly, with none of the same issues.
I can confirm that it was the wall controller (41A6318) that was causing the interference. I ended up replacing it with a basic momentary pushbutton instead of the 78LM and everything is working fine now.
Good to know. When I can get back to that location, I might switch out the wall panel, but to be honest, I’ve been thinking of upgrading the garage door opener entirely to a new one, preferably wall mount.
It seems that there may need to be a warning for the blaQ saying that any wall panel that’s anything more than just a button (i.e. ones with motion sensors, or the even smarter one you can get), might have issues.
@Benji These wall button issues and nuances are only an issue on the older Security+1.0 protocol (purple learn button) openers. The newer ones since ~2015 with a round yellow learn button (Security+2.0) are much more robust.
If you’re looking for a wall mount opener that works great with the blaQ, I’d suggest looking at the Chamberlain RJO101. I use this one for our demo garage and it’s awesome! Quiet and powerful and works perfectly with the blaQ (including the motion sensor).
Just for reference, I have another location with a Lift Master on Security 2.0+ and was considering replacing the wall control with this one:
There are other threads on here that seem to report similar weird issues.
It seems that adding the blaQ to the circuit just puts a little too extra load on the wires (even though it has its own power supply), that causes issues with that wall control panel (although in my research, it seems the capacitors inside it can fail as well).
Seems to affect the motion sensor ones as well, but to a much lesser extent.
Yes, we have heard a few isolated issues with the 880LMW panel, but it’s not widespread. I was unable to reproduce the problem in my own testing with the 880LMW, and many others have reported it working fine. So, I’m thinking its a capacitor issue with certain wall buttons, and not a protocol or GDO blaQ issue necessarily.
