So I want to give a big kudos for this driver and the ability for it to have the devices survive connectivity breaks, but also to survive a wholesale deletion of the garage door openers from the MyQ App.
So a few days ago one of my openers dropped offline… took me a few days to finally get the time to work on it.
Needless to say, it was a bear to get back up and running as I believe the WiFi card on the logic board is starting to die. Anyway, as part of the troubleshooting, I had to completely delete both openers from the myq app, then effectively re-register them as if they were new.
So I added them back in and imagine my amazement the Edge MyQ driver not only didn’t delete any of the old devices, but it picked right back up and started using them. I fully expected to have to recreate the devices and recreate some automations.
Hi all, recently it keeps saying missing username or password, but this used to work. Running it in docker and no issues finding the doors, but then it says can’t open or close due to missing username or password inputted in the app. It would have had to recognize them with working username and password though as removed/readded and it finds the doors/hubs in the account fine but just cant open or close once recognized? Thanks for all the hard work on this product! It’s been very useful. Thanks as well in advance for any support, greatly appreciated!
4/30/2023, 10:20:58 PM | HTTP server listening on port 8090
2
4/30/2023, 10:20:58 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
3
4/30/2023, 10:21:04 PM | Got new username/password from hub. Initializing connection.
4
myQ API: Successfully connected to the myQ API.
5
myQ API: Discovered device family garagedoor: Heitmeyer 1
6
myQ API: Discovered device family garagedoor: Heitmeyer 2
7
myQ API: Discovered device family gateway: Hub [Liftmaster WiFi GDO AC 3/4 HP]
8
myQ API: Discovered device family gateway: Hub2 [Liftmaster WiFi GDO AC 3/4 HP]
9
4/30/2023, 10:22:20 PM | Setting Heitmeyer 1 to open
10
4/30/2023, 10:22:20 PM | Missing username or password.
logs from CLI
2023-05-01T13:17:35.570901068+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:17:35.572662401+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:17:45.584718382+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:17:45.586647+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:17:55.593000656+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:17:55.594791968+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:04.838241017+00:00 WARN MyQ Connector Attempted to generate event for 80dbba16-7add-4872-a370-b54a3ea46d9e.main but it does not support capability myqserveraddress
2023-05-01T13:18:05.186892142+00:00 WARN MyQ Connector Attempted to generate event for 6d7da0a1-d4fc-405c-ad30-08dad8ef6915.main but it does not support capability health
2023-05-01T13:18:05.192339476+00:00 WARN MyQ Connector Attempted to generate event for 6d7da0a1-d4fc-405c-ad30-08dad8ef6915.main but it does not support capability myqserveraddress
2023-05-01T13:18:05.206494976+00:00 WARN MyQ Connector Attempted to generate event for 912f6bd2-3c7c-40f8-880e-4c112f1f053b.main but it does not support capability health
2023-05-01T13:18:05.212496767+00:00 WARN MyQ Connector Attempted to generate event for 912f6bd2-3c7c-40f8-880e-4c112f1f053b.main but it does not support capability myqserveraddress
2023-05-01T13:18:05.213239184+00:00 INFO MyQ Connector Refresh successful via http://192.168.1.15:8090. MyQ devices: 2, ST-installed devices: 2
2023-05-01T13:18:05.213922392+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:05.623215267+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:18:05.623935892+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:15.602655685+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:18:15.604454227+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:25.680766103+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:18:25.692812770+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:34.852223188+00:00 WARN MyQ Connector Attempted to generate event for 80dbba16-7add-4872-a370-b54a3ea46d9e.main but it does not support capability myqserveraddress
2023-05-01T13:18:35.084715896+00:00 WARN MyQ Connector Attempted to generate event for 6d7da0a1-d4fc-405c-ad30-08dad8ef6915.main but it does not support capability health
2023-05-01T13:18:35.088632938+00:00 WARN MyQ Connector Attempted to generate event for 6d7da0a1-d4fc-405c-ad30-08dad8ef6915.main but it does not support capability myqserveraddress
2023-05-01T13:18:35.101703604+00:00 WARN MyQ Connector Attempted to generate event for 912f6bd2-3c7c-40f8-880e-4c112f1f053b.main but it does not support capability health
2023-05-01T13:18:35.102707229+00:00 WARN MyQ Connector Attempted to generate event for 912f6bd2-3c7c-40f8-880e-4c112f1f053b.main but it does not support capability myqserveraddress
2023-05-01T13:18:35.103681146+00:00 INFO MyQ Connector Refresh successful via http://192.168.1.15:8090. MyQ devices: 2, ST-installed devices: 2
2023-05-01T13:18:35.114885063+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:35.622044521+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:18:35.623808896+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:45.633544647+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:18:45.634217855+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:18:55.632675857+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:18:55.634558732+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:19:04.888089899+00:00 WARN MyQ Connector Attempted to generate event for 80dbba16-7add-4872-a370-b54a3ea46d9e.main but it does not support capability myqserveraddress
2023-05-01T13:19:05.132505233+00:00 WARN MyQ Connector Attempted to generate event for 6d7da0a1-d4fc-405c-ad30-08dad8ef6915.main but it does not support capability health
2023-05-01T13:19:05.134568524+00:00 WARN MyQ Connector Attempted to generate event for 6d7da0a1-d4fc-405c-ad30-08dad8ef6915.main but it does not support capability myqserveraddress
2023-05-01T13:19:05.142561816+00:00 WARN MyQ Connector Attempted to generate event for 912f6bd2-3c7c-40f8-880e-4c112f1f053b.main but it does not support capability health
2023-05-01T13:19:05.143574483+00:00 WARN MyQ Connector Attempted to generate event for 912f6bd2-3c7c-40f8-880e-4c112f1f053b.main but it does not support capability myqserveraddress
2023-05-01T13:19:05.144545983+00:00 INFO MyQ Connector Refresh successful via http://192.168.1.15:8090. MyQ devices: 2, ST-installed devices: 2
2023-05-01T13:19:05.148344858+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:19:05.634159316+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:19:05.635937650+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:19:15.647822859+00:00 INFO MyQ Connector No credentials yet. Waiting.
2023-05-01T13:19:15.648496151+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-01T13:19:25.651683569+00:00 INFO MyQ Connector No credentials yet. Waiting.
So I love Brian and all he has done for us over the years and will it be ever grateful for his work. I opted to go with the Zooz relay and remote and love the solution so far. I to have 2 garage doors and set up automations for left, right, and both. While you can control the relay directly, I set up a series of virtual switches that I call, and those virtual switches are in the logic to compare for door position. The automations confirm the position of the tilt sensors, so I’m not randomly opening and closing the door just because a virtual “button was pushed.” These virtual switches (buttons) are what I use with the Alexa.
Here is a helpful article
And if your not into soldering or just to lazy like me. Here is a link to purchase modified remotes. I received mine in just a few days.
Daily for the last week or so, I have been getting an invalid credentials error. I have had to go into the Controller settings, change a character of my password, save, re-enter the correct password, save and viola…working again…until the next day or so. Any reason I might be experiencing this? Changes on the MyQ side perhaps?
So i’m kind of dumb and not sure what i did wrong. Like an idiot (possibly) i installed all the drivers which i probably don’t need. I was able to get just about everything else up and running but the MyQ-Controller (i have 2 and i think that’s the driver problem) the one i was able to log into and it shows “myQStatus: Connected: 1 Devices” and the shows my bridge IP. However no garage door ever appeared under my unassigned devices and nothing comes up when i do a scan. The controller portion doesn’t seem to do anything as far as opening or closing the door. Is there something i’m missing or have just done something super wrong? Any help or insight would be appreciated. Oh i can say i’m currently running HomeBridge on my RPi4 and it is also using the same port 8090 not sure if that could also be the problem.
So after much confusion on my part. Reading comprehension isn’t always my strong suite. These are the logs. I did edit the IP there, better safe than sorry. I was able to remove all the other drivers and now only have the MyQ Connection installed. However the in trying to uninstall everything i removed each device and now when i scan it’s not finding the MyQ Connector anymore. Sorry i’ve made a mess of this and do really appreciate the help and insight.
2023-05-21T06:21:25.093586270+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-21T06:21:35.050636942+00:00 INFO MyQ Connector Ready to create Garage Door (CG0860A56982) MyQLock.v1
2023-05-21T06:21:35.093738608+00:00 INFO MyQ Connector Refresh successful via (new user was yelled at about links):8090. MyQ devices: 1, ST-installed devices: 1
2023-05-21T06:21:35.100269275+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-21T06:21:45.098047280+00:00 INFO MyQ Connector Ready to create Garage Door (CG0860A56982) MyQLock.v1
2023-05-21T06:21:45.100204613+00:00 INFO MyQ Connector Refresh successful via (new user was yelled at about links):8090. MyQ devices: 1, ST-installed devices: 1
2023-05-21T06:26:25.307878957+00:00 INFO MyQ Connector Incoming ping from 192.168.0.0:8090 4b0c60ad-45c3-4b8b-ac62-e78d9e7a4b63
2023-05-21T06:26:33.233456909+00:00 TRACE MyQ Connector Received event with handler discovery
2023-05-21T06:26:33.235062909+00:00 DEBUG MyQ Connector Device discovery invoked
2023-05-21T06:26:33.701131576+00:00 DEBUG MyQ Connector Exiting discovery
2023-05-21T06:26:33.702093576+00:00 DEBUG MyQ Connector discovery device thread event handled
2023-05-21T06:26:35.367678910+00:00 ERROR MyQ Connector Non-200 response calling: http://192.168.0.0:8090/devices - 401 - body: Unauthorized
2023-05-21T06:26:35.374920910+00:00 ERROR MyQ Connector Refresh Failed.
2023-05-21T06:26:35.376279910+00:00 INFO MyQ Connector Send broadcast looking for bridge server
2023-05-21T06:26:35.479411577+00:00 INFO MyQ Connector Listening for a response at 192.168.0.1:54075:4b0c60ad-45c3-4b8b-ac62-e78d9e7a4b63
2023-05-21T06:26:35.552462910+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-05-21T06:26:35.592023910+00:00 TRACE MyQ Connector Server:tick
2023-05-21T06:26:35.644402577+00:00 TRACE MyQ Connector Server:_tick
2023-05-21T06:26:35.730358577+00:00 TRACE MyQ Connector Server:route
2023-05-21T06:26:35.734938910+00:00 INFO MyQ Connector Host: 192.168.0.1:54075
Accept: application/json, text/plain, /
Connection: close
Content-Length: 72
User-Agent: axios/0.27.2
Content-Type: application/json
Just modified my Z-wave control setup for the Chamberlain garage door opener so that the remote control now has an AC power supply instead of a battery. I ordered an AC power supply that puts out 12v DC. I also ordered a resistor that steps down voltage from 12v to 3v DC. I soldered the output wires from the resistor to the battery terminals in the remote. As with the relay wires, I melted the plastic on the remote cover with the soldering gun to form holes so I could pass the power wires through the cover.
The Zooz Zen16 Multirelay can be powered by the USB 1 amp power supply or by the 12v DC power supply. Zooz told me not to use the 12v power supply simultaneously for the Zen16 and the Chamberlain remote, but, as you can barely see in the photo, I did it anyway, and it worked. So, now I just have one AC plug-in for the whole shabang. As with my previous work, it ain’t purty, but it works. It’s parked in the garage so, hopefully, we will hardly ever have to mess with it and it is out of sight.
Someone told me that I could use the USB power supply to power the multirelay, then tap power from the 12v terminals to power the remote. I put a multitester on those terminals while using USB power and found no power at all coming from those terminals. So, that idea doesn’t work.
I got the AC power supply from The Smartest House. I couldn’t find one I liked at Amazon. I got the 12v-3v stepdown at Amazon. There are a variety available there.
Update: while investigating this issue, I found I had 2 instances of the bridge exe running on my PC, so I closed and removed one from my windows startup folder and has not been an issue since. Fingers crossed!
I am done with trying to get MyQ to work with SmartThings. It is just not worth it anymore. I went with the new Konnected Smart Garage Door Opener. I love it! It works with SmartThings out of the box. The only bad thing is the open/close senor does not show up in STHM, so if you want to monitor the garage door you have use a different sensor.
Any old garage door smart controller will work if you solder the trigger wires to an old garage door car remote. Then it bypasses all the MyQ security and just opens the door like you pushed the remote button. The controllers come with a tilt switch and everything works like before this edge driver world.
I am trying to get this up and running and also stuck on “Searching for bridge server.” I did initially install the beta and garage door drivers as well, but after reading this thread I realized that was a mistake and uninstalled them, so now I only have the MyQ Connector driver installed. I’m running the bridge server on an x64 (not arm) Mac mini. My hub is connected to my xFi router via Ethernet and the Mac mini running the server is on a Wifi network from that same router. All seemed to go fine until this last step where my hub and the Docker server seem to not be able to find each other.
Here is all my server log says:
2023-05-30 17:03:47 5/30/2023, 10:03:47 PM | HTTP server listening on port 8090
2023-05-30 17:03:47 5/30/2023, 10:03:47 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
I also tried going into my router settings and adding a port forward for the Mac mini for port 8090, and that made no difference. Is there anything else I can try? Thanks so much in advance!
Can you expand on that Terminal command? I am also trying to run the executable on a Mac and it’s reading as a text file. I don’t have much experience with Terminal commands - can you write out the full line you used?
I’m running the LAN bridge server in a docker container on a Firewalla Gold router (running Ubuntu 22.04.1 LTS) with a Chamberlain myQ Smart Garage Control and everything worked smoothly out of the box!
Same, this worked great out of the box. Detected both of my garage door openers automatically and quickly. Now what do I do with those extra SmartThings tilt sensors I had attached to the doors? What will I do with all those extra batteries?!
While on the topic, is there any chance of getting garage door opener light controls thru the new edge driver?
MyQ does not expose remote door light control unfortunately. Missed opportunity in my opinion. If that ever changes, I can certainly update the driver to work with it.
