When it initially failed, the container console showed that the server found the door and the gateway. After I fixed the network connection, there was an additional line where the IP of the opener was recognized.
My NAS has it as an option in the Docker GUI. It may be as simple as adding --network bridge to the run command?
The idea to try that came from here; @jc214809 may be able to explain how to do it in a command line environment.
Yeah for any eagle eyes out there⌠yes I noticed I was using the wrong door sensor for the Charger Door close routine, and have fixed it. 
I am getting
Not sure why. Any Ideas?
Running on a Pi via Docker
Iâm in the middle of pushing some updates. Havenât had a chance to test on pi yet.
I had this and have been fighting it all day. I finally got the docker container to run. From my limited Docker knowledge and todays web education. I think it has something to do with the seccomp profile.
I was able to get past this error buy adding the following option to my run file.
âsecurity-opt seccomp=unconfined
Donât know why? and its probably not a smart thing to do? Iâm just hacking along trying to get things to work.
I got the docker container to work but still not seeing it find any devices in smartthings app. Sooooo still hacking along.
No luck for me. 
@brbeaird nice work on this new driver
I installed it on my Ubuntu server (under Proxmox), using docker and it is running fine, but Smartthings doesnât find anything and so driver is added.
Reading some of the comments, I think the problem is the port number. Does it need to be port 8125??
If so, then every time I restart the docker container, a new port is created for the HTTP listening (I can connect from a broswer to get details at the port published in the log files). Should I set the container to port 8125?
Sorry, in my experimenting throughout the day. This is the command that gets the container created and running for me.
docker run --security-opt seccomp=unconfined -d --name=âsmartthings-myq-edgeâ --net=âbridgeâ -e âMYQ_EMAILâ=âemail addressâ -e âMYQ_PASSWORDâ=âpasswordâ âbrbeaird/smartthings-myq-edgeâ
I have used this command twice now to get it running it reports in the logs it connects to MyQ and reports the devices. BUT still no luck in getting the devices discovered in smartthings. I am thinking its something to do with my network settings. I have tried pinging outside of the docker container and it seeâs the rest of the world.
Iâm now reinstalling again and gonna try to ping out to my garage door controller on my LAN and see what I learn.
Ok that fixed it I put the switch at the end, but when I moved it to the start of the command it worked. But like you I am not getting it to show in ST
So I went to ip:8125 on the raspberry Pi I am running the docker on and I get âCannot GET /â Not sure what the means
So we appear to be at the same place.
My latest command line change was to change the --network from bridge to host.
Hoping that would allow the container to have access to the hose network connections.
It did change my result when I went to the web address to the same you got.
Still hacking away at it!
I pushed a few updates today, mostly on the server side. You should see new docker images and executables.
I am still making a few tweaks to the driver to make sure it filters out unwanted ssdp traffic in periods other than discovery - not quite happy enough with it yet to fully push out.
I also have not yet made it to testing on the pi but hopefully should get time to focus on that soon. In theory, the Linux-arm64 executable should work for some, but I may need to generate a 32-bit one as well.
With the latest server code and images pushed, the port should be randomly generated each time.
I would suggest trying one of these:
I will look into that. Thank you for the reply.
Thank you for your help. I am 1 step closer.
I kept trying different run commands this is the one I used last
docker run --security-opt seccomp=unconfined -d --network host --name=âsmartthings-myq-edgeâ -e âMYQ_EMAILâ=âemailâ -e âMYQ_PASSWORDâ=âpasswordâ âbrbeaird/smartthings-myq-edgeâ.
This enabled me to finally get a reply in the web browser when I went to the
âPi IP addressâ:8125/details
It reports all the devices and the base IP address and port of the Pi.
unfortunately still no devices in smartthings.
Just to clarify I am supposed to select the MyQ Door driver not the MyQ DoorBeta?
I updated my docker container with the latest image and still Smartthings doesnât find it to create the devices. Read up on ssdp and wrote a small client script in nodejs to test the server and it finds it perfectly on my network. Iâm guessing something on the smartthings side is the issue at this point.
I updated to the latest stuff this morning. I also figured out how to setup and run CLI.
It appears from the logs it is all connecting and it looks like it thinks itâs creating the devices. They just donât show up in the app??
I kept a copy of the log data from the CLI if youâre interested.
Yes, if you can share those logs, that would be super helpful. Can you also just verify they havenât silently been created somewhere in the âNo room assignedâ group?
For @rtorch and anyone else able to get the server running but unable to get SmartThings to discover devices, could you try this?
smartthings edge:drivers:logcat --hub-address=0.0.0.0
If youâre running the latest server code, it starts up with a random port, not necessarily 8125. Youâll need to check the logs to see the port it started up with, then go to http://serverIp:serverPort/details
PM Sent
I have looked in every room, tried clearing app cach,
With this new version (non-Docker) the logs are confirming what I suspected:
10/4/2022, 12:33:25 PM | No environment variable found for MYQ_EMAIL
10/4/2022, 12:33:25 PM | No environment variable found for MYQ_PASSWORD
10/4/2022, 12:33:25 PM | Checking for config file ./config.json
10/4/2022, 12:33:25 PM | Error retrieving login information: ENOENT: no such file or directory, open './config.json'
The config.json file is in the same folder as the exec and permissions are good.
config.json myQBridgeServer-macos-x64
myQBridgeServer-macos
Yes, I know I have the prior exec still in the folder for now.