I definitely need to improve the documentation to make this more clear. If you’re going the executable route, you need to also download this file: https://github.com/brbeaird/SmartThings-MyQ-Edge/blob/main/src/server/config.json
Put it in the same directory as the executable you’re running.
Open it and set your email and password, then save it.
Run the executable again.
I think I may also modify the executable version so it pauses before just closing so you can at least see any error messages.
Can you verify that you are calling the executable from the directory it’s actually in? Like if you open a terminal, cd into the directory, then call the executable - is that the same result where it can’t pick up the config file? It’s gotta be either some weird directory context issue or else a file permission issue.
Thanks for the pointers. I tried your command but turned out I had to remove the single quotes. Caused an error on the Mac. Worked fine without. Also, I didn’t need the ‘-e’ options since I defined the environment variables in my .bashrc file. So this is what worked for me:
docker run --security-opt seccomp=unconfined -d --network host --name=smartthings-myq-edge brbeaird/smartthings-myq-edge
Now my problem seems to be that it immediately exits. The ‘ls -a’ helped also so now I can see all the containers. Using the information from the ‘docker container ls -a’, I can start a container using
I don’t think it will actually access what’s in .bashrc at that level. That’s part of what makes containers so isolated by design. You’ll still need to pass in username and password in the docker command itself.
OK, finally up and running. Once I got the syntax right and removed the existing container, worked ok. The run command creates a container each time so I guess if I have to restart I need to remove the old one first? Anyway running now. Next I need to try to hook it up with ST.
I haven’t done it yet either , but you can make the container restart on its own. I didn’t do it when I created it in case I needed to stop it and remove it.
That is also discussed a ways further up the thread.
I believe there is a way to do it by adding it to the system startup too. But I think it’s more complicated.
@brbeaird, let me start with a big thanks. I’ve been using the old DTH and App you created for this for a while now and still works.
While trying to get this to work, I’m trying on a Windows 11 machine, that I have usually running 24/7. I would later want to migrate this to a Pi or similar.
For now, I cannot get the ST to detect the devices and logs show this. When i hit the details page, I do see the both Garage doors are being discovered correctly.
one thing I noticed in the logs, that the IP of the server is showing up different than the rest (192.168.62.xxx) of my network and this IP is only accessible on the browser on the system running the server. If I try to access it on any other systems/phones on the same network, the URL/IP doesn’t resolve.
I believe that could be the issue here, but, cannot figure out what since ST is able to discover the server.
PS: thanks to @ThomasTrain on the tip for nssm. working like a charm.
you can copy and paste it in notepad and then save it as config.json.
when entering the filename, please ensure to use “” in the front and end of the file name to avoid fron notepad to convert and save it as a config.json.txt file.
I’m running it on Windows as well and can help if you have any questions.
ok it looks like it found my door. it says found 1 compatible device waiting for discovery. not sure what im supposed to do next? i installed the MyQ door under channels and drivers but i dont see anything in my smartthings yet
That’s great. You just need to go to your ST app, select add a device and scan for devices nearby. That should fetch the device and add it to your app. and you’re all set.
