I will not delete the old MyQDoor driver, so it should continue to work as long as you do not update the MyQ server-side, either.
I like Docker because it’s simpler to get apps like this to just auto-start and keep running. I find it also easier to update them when images get updated.
But the executable should work fine. From the command line, you should be able to run
./myQBridgeServer-linux-arm64
I hate to do this as I always try to figure these things out myself without badgering the community, but I have had a devil of a time setting this up…
I have the docker container running on my mac, but in bridge mode (not host mode as the other posts have described). I have been unable to run the container in host mode (I guess MacOS Docker Desktop does not allow running in host mode?).
I have moved on to trying to run the MacOS executable as my Mac is always on (I run Homebridge), but cannot figure out how to run the file - it opens as a .txt file.
Anyone out there have success running the MacOS executable and/or can point me in the right direction on how to execute that file and get this running would be extremely appreciated. Happy to take it to a private DM as well.
Thanks
The newest version should work fine in bridge mode as long as you have the ports mapped correctly. See the latest instructions on that.
Thanks for the response…
I have little experience running the container from terminal, but have been able to start the container from Docker Desktop - I dont see where to set the ports when starting the container - it randomly assigns a port…
Do i put that port into the settings of the hub device?
I’m not seeing any devices come though to smartthings - still says waiting on credentials
Interesting. I may need to include something slightly different to get the port settings to show up in docker desktop. I’ll look into that. If you run the command in the readme instructions, though, I think that still works?
So, i was able to run the executable for the docker in the directions and then the container shows the following in Docker Desktop…
Still getting the “awaiting credentials” in the app
Open the MyQ-Controller device in the SmartThings mobile app, tap settings, then put in your username/password. If you had something in there previously, change the interval or some other setting to trigger it to re-send.
I was also getting “awaiting credentials”. Changing polling did not work, had to add server ip and port to change status to “connected”, but did not add the 2 garage doors.
I am starting the container using docker start command specified in github. I do see in docker log that both the doors are discovered.
root@pi3:~# docker logs smartthings-myq-edge
11/2/2022, 3:56:34 PM | HTTP server listening on port 8090
11/2/2022, 3:56:35 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
11/2/2022, 4:31:09 PM | Got new username/password from hub. Initializing connection.
myQ API: Successfully connected to the myQ API.
myQ API: Discovered device family garagedoor: Garage Door Bay 1 (serial number: XXXXXXXX, gateway: XXXXXXXX).
myQ API: Discovered device family garagedoor: Garage Door Bay 2 (serial number: XXXXXXXX, gateway: XXXXXXXX).
myQ API: Discovered device family gateway: Hub [Chamberlain Smart Garage Hub] (serial number: XXXXXXXX).
CLI log below:
2022-11-02T16:31:04.506856654+00:00 INFO MyQ Connector Listening for a response at 192.168.1.240:54659:b6bc3f31-5ee2-4d80-bc99-4b09a1db5984
2022-11-02T16:31:06.527862279+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T16:31:07.761467738+00:00 TRACE MyQ Connector Received event with handler device_lifecycle
2022-11-02T16:31:07.766844113+00:00 INFO MyQ Connector <Device: b6bc3f31-5ee2-4d80-bc99-4b09a1db5984 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T16:31:07.806836613+00:00 TRACE MyQ Connector Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T16:31:07.809709863+00:00 DEBUG MyQ Connector Info changed handler invoked
2022-11-02T16:31:07.821999196+00:00 INFO MyQ Connector Send broadcast looking for bridge server
2022-11-02T16:31:07.835524113+00:00 INFO MyQ Connector Listening for a response at 192.168.1.240:54659:b6bc3f31-5ee2-4d80-bc99-4b09a1db5984
2022-11-02T16:31:09.223112613+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T16:31:09.226806738+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T16:31:09.229910196+00:00 TRACE MyQ Connector Received event with handler device_lifecycle
2022-11-02T16:31:09.234700030+00:00 INFO MyQ Connector <Device: b6bc3f31-5ee2-4d80-bc99-4b09a1db5984 (MyQ-Controller)> received lifecycle event: infoChanged
2022-11-02T16:31:09.309072446+00:00 TRACE MyQ Connector Found DeviceLifecycleDispatcher handler in myQConnectorDriver
2022-11-02T16:31:09.311878655+00:00 DEBUG MyQ Connector Info changed handler invoked
2022-11-02T16:31:12.050892572+00:00 INFO MyQ Connector <Device: b6bc3f31-5ee2-4d80-bc99-4b09a1db5984 (MyQ-Controller)> emitting event: {"attribute_id":"statusText","capability_id":"towertalent27877.myqstatus","component_id":"main","state":{"value":"Connected"}}
2022-11-02T16:31:12.069465280+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T16:31:12.084793863+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T16:31:14.756392239+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2022-11-02T16:31:19.872637989+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
@brbeaird Just a quick update. I power cycled the SmartThings hub and one of the garage doors showed up (the shared garage door). The reboot did not help with my garage door showing up.
Server log looks OK, I think.
11/2/2022, 7:57:42 AM | HTTP server listening on port 8090
11/2/2022, 7:57:43 AM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
11/2/2022, 7:57:44 AM | Got new username/password from hub. Initializing connection.
myQ API: Successfully connected to the myQ API.
myQ API: Discovered device family garagedoor: Garage Door (serial number: X, gateway: X).
myQ API: Discovered device family gateway: Garage Door [Chamberlain WiFi Hub] (serial number: X).
11/2/2022, 8:05:59 AM | Detected SSDP broadcast. Posting details back to server at http://192.168.4.239:39489/ping
Devices link is failing.
192.168.4.200:8090/devices
Cannot GET /devices
@j18hockey, maybe you’re seeing the same problem I am. If you hit the server URL/devices, do you get a response? I get a “Cannot GET /devices” response.
Appreciate the shout out! 
@brbeaird
Is the LAN LightBulb driver still necessary for controlling MyQ lights? …or does the MyQ Connector driver handle both doors and lights?
Next question. Since the new MyQ Connector driver has voice assistant functionality is it incorporated with the lock feature for security where you need to provide a PIN to the voice assistant? With the old driver I instaled a virtual lock that I then sync up with the door driver. Then the voice assistant would be able to use the PIN for unlocking (opening the door) and you can still just issue a regular close command to close it without PIN. I suppose I can continue to use a virtual lock but I’m not sure if I’m exposed with the new voice assistant switch functionality. If so I’ll have to see about how to remove Alexa visibility to the unsecure switch (open) function.
One thing I did notice – which may be more of an annoyance than a problem – is that if you put in an IP address and port and you then delete them to go back to broadcast discovery, you can’t. The driver seems to remember what you had entered.
I get that same response when trying to path to http://[IP]:[Port]/devices
I get the same response
Logs from the hub show this, and no devices in the ST app yet.
11/2/2022, 12:07:33 PM | HTTP server listening on port 8090
11/2/2022, 12:07:34 PM | SSDP server up and listening for broadcasts: urn:SmartThingsCommunity:device:MyQController
11/2/2022, 12:07:42 PM | Detected SSDP broadcast. Posting details back to server at http://192.168.62.14:50539/ping
11/2/2022, 12:07:43 PM | Got new username/password from hub. Initializing connection.
myQ API: Successfully connected to the myQ API.
myQ API: Discovered device family garagedoor: Garage Left (serial number: XXX, gateway: XXX).
myQ API: Discovered device family garagedoor: Garage Right (serial number: XXX, gateway: XXX).
myQ API: Discovered device family gateway: Grey Garage [Chamberlain Smart Garage Hub] (serial number: XXX).
When i executed the run container command as posted, my ST app edge driver kept saying awaiting credentials. Only when I nuked the container and ran again without the port bindings, it instantly changed to Connected. No device show up in the app though apart from the controller. I tried refreshing the interval to trigger a send as @brbeaird suggested as well.
Right - that is a POST endpoint now, not get. However, I just put in a status endpoint to help with troubleshooting. Can you update your server code, start it back up, and then hit this in your browser: http://serverip:port/status ?
No, that was early testing. I need to remove that from the channel.
I have not looked into how this might work with Edge. Might get to it eventually.
Interesting. It’s supposed to recognize if you completely clear them out. I’ll check on that.
I did some testing, and Docker Desktop on Windows just does not like the udp/ssdp discovery process. Kind of a bummer, but when I used the manual ip/port, it did work correctly.
Status URL doesn’t work either.
Did you pull the latest server image? The status endpoint was just added within the last 30 minutes or so.
yes, it shows the image was created 38 minutes ago when I pulled it.
Let me try another pull and see.
UPDATE: seems there was an updated image. with this one the status page shows correct info. no doors show up in the ST app though. I did a refresh of the interval to push it again.
How long does it usually take to create the devices?