search

ratgdo / mqtt-ratgdo

ratgdo via mqtt
GNU General Public License v2.0
76 stars 16 forks source link

RATGDO not controlling opener #17

Open timwing opened 7 months ago

timwing commented 7 months ago

I have had RATGDO's installed, configured and working well for a couple weeks on two identical 2018 Chamberlain B970 MyQ openers. Just today one of them stopped controlling the opener. Both are configured with MQTT & HA. When I send a command to RATGDO from HA I see the RATGDO blue LED flash. I also see sent commands in MQTT. I checked the wire connections and they are sound. I have rebooted the RATGDO and removed power from the opener and it's backup battery.

If I watch the RATGDO door controls in HA and press the garage door opener button on the wall, I see the HA RATGDO status update so it is receiving state updates but the opener just wont respond to commands sent by RATGDO.

timwing commented 6 months ago

As of today it started working again all on it's own. What would cause this?

PaulWieland commented 6 months ago

Try upgrading to v2.53 (assuming you have a v2.5 board)

coreywilner commented 6 months ago

I found the BIN file for 2.55 and installed it with the OTA feature from the ratgdo main page. I too had the problem with the unit that status was showing up ok, but control was not happening. With 2.55, the unit is now working again for controlling the open/close of the ratgdo.

timwing commented 6 months ago

I tried the "ratgdo_esp8266_hV25_sV2.55.bin" but I get "Update error: ERROR[10]: Magic byte is wrong, not 0xE9" so I am now using 2.53.

michaelsleen commented 6 months ago

I have the same issue.

On 12/9, I installed Ratgdo v2.5 on a Chamberlain MyQ garage door opener (Model B4505) with a yellow learn button and Security+ 2.0 flashed with MQTT. Ratgdo was auto-discovered by MQTT in Home Assistant, and I could open and close the garage door and turn the built-in light on and off from Home Assistant. I could also open and close the garage door using the Chamberlain wall switch inside my garage, the wireless numeric keypad outside my garage, the garage remote, the MyQ iOS app, and the programmed button in my car – everything worked great.

However, sometime in the past couple days, I could no longer open and close the garage door or turn the built-in light on and off using Home Assistant or the wireless numeric keypad outside my garage. Everything else (wall switch inside my garage, garage remote, MyQ app, car button) can still open and close the garage door, and Home Assistant receives real-time status of the garage and obstruction sensor, and my automations notifying me when the garage door opened or closed still work.

To troubleshoot, I re-did the wiring same as before, but I still can’t regain the ability to open/close and toggle the light in Home Assistant (and I don’t know why my numeric keypad outside the garage stopped working as well).

Attached are photos of my setup. Any ideas on what to do to get this working so I can control via Home Assistant and MQTT?

Ratdgo_1

Ratdgo_2

Ratdgo_3

Ratdgo_4

Ratdgo_5

Ratdgo_6

PaulWieland commented 6 months ago

Make sure you are running firmware v2.55

michaelsleen commented 6 months ago

Where can I download the v2.55 .bin file for an OTA update? I don't see it here https://github.com/PaulWieland/ratgdo/releases or here https://github.com/ratgdo/mqtt-ratgdo.

michaelsleen commented 6 months ago

I was able to get v2.55 from someone in the HA community forum, but updating to v2.55 did not solve the issue. I still cannot open/close the garage door from HA, but HA does show real-time status and the physical wall mount garage button works.

timwing commented 6 months ago

@msl2424 Does operating the door a couple times with the remote help? I cant be sure but mine started working again without any firmware updating.

coreywilner commented 6 months ago

Even with 2.55, the ratgdo has reverted to simply reporting status and not responding to control actions. Do you have any new fixes for this defect?

michaelsleen commented 6 months ago

@msl2424 Does operating the door a couple times with the remote help? I cant be sure but mine started working again without any firmware updating.

I opened and closed it three times in a row with the remote. The remote worked but I still can't open and close using Home Assistant (but it reports the correct door status).

PaulWieland commented 6 months ago

Even with 2.55, the ratgdo has reverted to simply reporting status and not responding to control actions. Do you have any new fixes for this defect?

You need to post a serial log.

coreywilner commented 6 months ago

Even with 2.55, the ratgdo has reverted to simply reporting status and not responding to control actions. Do you have any new fixes for this defect?

You need to post a serial log.

Where are there instructions on how to grab a serial log? Can this be done remote or do I have to connect to the ratgdo directly?

coreywilner commented 6 months ago

Even with 2.55, the ratgdo has reverted to simply reporting status and not responding to control actions. Do you have any new fixes for this defect?

You need to post a serial log.

Where are there instructions on how to grab a serial log? Can this be done remote or do I have to connect to the ratgdo directly?

Interesting...a full reboot of Home Assistant and the ratgdo (2.55 MQTT version) is working again. Not sure the reason for this as all my other MQTT devices are not having issues with subscriptions. MQTT explorer shows that a command is published (for open or close) but ratgdo is not apparently acting on it. And it is publishing status which I can see changing in MQTT Explorer, and it does so with commands from MyQ app or keypad or HomeLink.

sejgit commented 6 months ago

coming and going as well. with a 3rd reboot & 5 min wait it came back. went along with the light status on mqtt showing unknown or [name of unit]/status/light when I turned it on or off manually.

jmedemar commented 6 months ago

Having the same issue here. Just got my revision 2.5 boards and loaded 2.56 firmware. Can see the status of the door, light, and obstruction sensors, but cannot send a command to the door. Are we supposed to be using a topic of "home/garage/ratgdo-65546/status/door" or "home/garage/ratgdo-65546/command/door" for sending the "open" or "close" commands via mqtt? The light responds using the topic of "status" but not "command". Cannot get the door to respond by using either topic.

michaelsleen commented 6 months ago

Is there a solution for this issue? I am on 2.56 firmware and still cannot reliably open and close the garage from HA, but HA continues to report the correct status and physical garage door controls work. I've tried updating the firmware, restarting HA, re-wiring the entire thing.

PaulWieland commented 6 months ago

Anyone having this issue needs to post a serial log so we can see what is going on.

treylok commented 5 months ago

Same problem here. Status reads correctly, but commands will not open or close the door or control the light. Attached is a log.

esp-web-tools-logs.txt

PaulWieland commented 5 months ago

Same problem here. Status reads correctly, but commands will not open or close the door or control the light. Attached is a log.

esp-web-tools-logs.txt

Did it work before and then stop working? Just to rule out a client ID issue, re-install with full erase so it generates a new client ID. You can also install the ESPHome version and test the controls or assign new client ID from the Web UI.

treylok commented 5 months ago

Did it work before and then stop working? Just to rule out a client ID issue, re-install with full erase so it generates a new client ID. You can also install the ESPHome version and test the controls or assign new client ID from the Web UI.

It did work before. It worked with original firmware shipped with unit, then stopped working. After flashing to 2.55 it was working again, then stopped. Flashing to 2.57 did not fix.

I will try a full erase, then ESPHome version.

Thanks.

PaulWieland commented 5 months ago

Just to be clear, no ratgdo hardware ships with firmware pre-installed.

treylok commented 5 months ago

Just to be clear, no ratgdo hardware ships with firmware pre-installed.

Sorry, yes, it was not pre-installed, just forgot initial procedure. I am not sure which version it was though.

I ended up just flashing to ESPHome and it seems to be working now.

brandonleon commented 5 months ago

I am experiencing a similar issue. It worked for the first few days, but now it is correctly reporting the status to MQTT, yet it ignores all commands. I can see the commands hitting MQTT and the state changes for the light in HA, but nothing actually happens.

PaulWieland commented 5 months ago

If you are using Home Assistant and you have a Security + 2.0 opener, you really should be using the ESP Home firmware... That being said, try re-installing with erase to see if a new client ID fixes the problem. Again, you need to post a serial log otherwise we're just guessing at what is going on.

brandonleon commented 5 months ago

If you are using Home Assistant and you have a Security + 2.0 opener, you really should be using the ESP Home firmware... That being said, try re-installing with erase to see if a new client ID fixes the problem.

Thanks, I already have MQTT devices in Home Assistant, which is why I went that route. I went ahead and installed the ESPHome firmware, and everything is working like new again. Thanks for an amazing little device.

john-kapp commented 5 months ago

@PaulWieland I believe I have this same problem. My Security+ 2.0 opener worked well for about a week after the initial installation of v2.57, but then I stopped being able to control the door via HA although HA still reported status changes (door open/close, motion, etc.). Simply restarting RatGDO had no effect on the issue. Per your message above, I reinstalled v2.57 with an erase and HA was then able to control the GDO once again. I have attached four log files. The first two are before the erase and the second two are after the erase. One using HA to try to control the opener and one using the wall button. I hope this are helpful in debugging. Thanks for all your work on this.

file1-ha-open-command-nowork.txt file2-wallbutton-open-works.txt file3-post-erase-wallbutton-open-works.txt file4-post-erase-ha-open-command-works.txt

michaelsleen commented 5 months ago

Moving from MQTT to ESP Home firmware appears to have resolved this for me, but it's unclear why it would not reliably work with MQTT. I have a Security + 2.0 opener with a yellow learn button.

mabordas commented 4 months ago

I'm also definitely having the same problem. After the initial install everything worked perfectly, but then after a few weeks I noticed it wasn't able to open/close the garage door, but it was still getting status updates if I opened the door with the physical button. Two weeks ago I erased and reinstalled and it worked again. Now it's having the same issue. Here are some logs after I tried to open the garage. I still haven't erased it yet, so I can do more debugging if it's useful. esp-web-tools-logs.txt

hart-2-hart commented 3 months ago

I'm an eISY user with the ratgdo node server/plugin that utilizes MQTT on a Security + 2.0 gdo. I installed fine several weeks ago and it worked great and then it just sopped controlling both doors. Did the normal restart and reinstall on the eISY side to no avail. Flashed the 2.57 software back to it as OTA and still not responding.

I reflashed with erase each of them one at a time and they immediately resumed working. There is at least one other use of the eISY that has had the exact same experience. @PaulWieland , ratgdo is an incredible product -- what do you need from us to assist determining where the issue is occurring?

sejgit commented 3 months ago

Same issue. We are all using the MQTT version. Works for a bit then stops controlling. Works again with a refresh but not just a power cycle. Up to date with 2.57

Goose66 commented 3 months ago

If you are using Home Assistant and you have a Security + 2.0 opener, you really should be using the ESP Home firmware...

Does that suggest that this problem (one of requiring a new client ID to be generated?) is fixed in the ESPHome firmware? Any chance of this same fix being applied to the MQTT firmware?

geozahar commented 3 months ago

Same issue. Using Security + 2.0 opener with MQTT firmware. Have to erase/flash (using latest) periodically to regain control. If you still need more logs. Let us know.

graydavidw commented 3 months ago

I now think that I’ve had this issue as well- originally I thought it was part of a crash I had with my system (Homeseer plugin for MQTT) but then had it again this week.

Ishfal commented 3 months ago

+1 to this issue

hart-2-hart commented 3 months ago

I read where others are conjecturing that power issues like failure or brown-outs may affect the electronics and result in this issue. Both of my ratgdo had this issue at the same time several weeks after install. My electric service is underground and to fix a sinking conduit that was pulling free from meter, the utility company cut power for a repair. Not saying it is connected but just that both doors had issue at same time, and I'd had a full outage and restore of power.

If this issue is not found, I may locate access to the UPS battery in one of the openers and draw power from it instead of AC wall wort. I can then test if both get issue or only the one on AC.

graydavidw commented 3 months ago

I’ve had this issue again and I don’t believe it was after a power outage nor brown out. I’m tempted however to connect to the door battery backup via a 12v to 3.3v converter and see if the ratgdo commands continue to work after a re-flash gets it working again.

mlamoure commented 2 months ago

Piling on with my experience:

If there's anything I can do to help diagnose, please let me know.

hart-2-hart commented 2 months ago

@PaulWieland

Second time with issue. I have log for one of two ratgdo where it stopped responding but continued to update status. First time it happened both had the issue but unsure exactly when it occurred. Not comfortable just posting log here. Please confirm nothing sensitive is included in log.