Any chance you know how to run it so that it runs all windows minimized?
If you create the batch file from what I posted before then you wont see it at all.
-
create a new text file with the contents below.
::Run MyQBridge if not running
CD C:\SmartThings\MyQBridge
SET MYQ_SERVER_PORT=8125
tasklist /nh /fi âimagename eq myQBridgeServer-win-x64.exeâ | find /i âmyQBridgeServer-win-x64.exeâ > nul ||( start myQBridgeServer-win-x64.exe ) -
Rename the text file and change the extension from .txt to .bat . This will make it a Windows batch file. Make sure you change the CD command to the directory where you have myQBridgeServer-win-x64.exe. Also save the batch file in this directory.
-
Open Task scheduler in windows and create a new task that triggers on startup and every 6 hours and have it run the batch file.
-
make sure you put administrator in the tasks runs under spot and provide the password.
This will start the Qbridge server every time the server or PC starts and will also check every 6 hours and start it if itâs not running. It will run in the background and you will not see it.
If you cant figure this out then let me know and provide the path to your Qbridge exe and I will create the batch file and also a file that you can import into Task scheduler.
1 Like
I noticed a slight change in my door behavior when it comes to automation behavior. I have two manual run automations that includes closing the garage door. I was always confused by the options, that seem more like a switch than a door:
- Turn on or turn off
- Turn on (sub-menu: Door Closed, Door Open)
- Turn off
My rule used: Turn on, Door Closed command to close the door and that used to work. However, last night I put the house to sleep and the garage door was opening. This happened three times until I changed the automation rule to Turn off and the garage would stay closed or close the door if it was open.
Hereâs where it gets strange, my buttons used the Turn On, Closed and they close the door as intended. So why did my Manual Run Automations that utilized the Turn On, Closed command open the door? Iâm not sure if this is a change in the device driver or the ST automation.
Any thoughts?
Thanks for the upgrade. I just replaced my previous Windows executable with this one, rebooted my server to have it launch that one and all is working again. You are legend @brbeaird !
1 Like
I keep getting this error for some time now. I have this on an always on VM that I just boot and forget about. Figured Iâd look into it now. lol Anyone else encounter this / have a fix?
Morning @Chase84
What version of MyQ Edge are you running?
v1.04 fixed this issue for most of us (scroll back in this thread a bit for more context).
An alternative to a batch file that runs on startup is using NSSM to set up the bridge to run as a service. This is how my PC is configured. Search this thread for nssm and youâll find instructions someone posted on how to do this.
I use nssm to run the myQ bridge server and another Edge bridge server automatically on boot.
1 Like
Thanks @brbeaird ! I finally made use of my Pi 3A+ that I bought months ago and it was sitting in the closet! Everything was smooth with the installation. One item that I noticed, wasnât sure if it can be enhanced was that while the garage door is opening, hitting close does not stop the opening. Curious to know if it behave like the physical switch.
1 Like
That was it. Thanks. I havenât updated the bridge since its inception. Assumed it was just a middle man with the edge driver getting the updates. One more thig to keep an eye on. haha
1 Like
Was this fixed? I am running the docker version and itâs still not connecting? My controller keeps going through a repeated cycle approximately every 5 minutes:
Error: MyQ Bridget Offline
Connected: 1 device
Offline Error MyQ Bridge Offline
I have restarted my docker service a couple of time.
Are they any changes I need to make on my side ?
A new image for the MyQ server was released last week. If you have not already done so⌠you should pull the new image to your current docker container.
Executables were released days laterâŚ
1 Like
All issues seem to have settled down for me over the weekend. If you are still seeing problems, make sure you are running bridge server 1.0.4, either via updated Docker container or executable from the latest GitHub release.
I have plans for another update in the near-future to automatically handle MyQ region failover behind the scenes, which should silently take care of some of the problems we saw this weekend when just one of the regions went down.
5 Likes
I upgraded and rebooted both the bridge server and ST hub. Iâm getting a âMyQ Connector Refresh Failedâ in the CLI. Any next steps I should try?
more details please? what are you running the MyQ server on⌠pi, windows, NAS or Other?
Running on a Pi using docker (no portainer). I stopped docker, pulled the latest image, restarted docker. I also rebooted the Pi and then the ST hub. I confirmed username/password in the settings are also correct.
Check to make sure you do not have two containers for myq in docker
I ran âdocker statsâ and only see one container running.
Remove the container and create a fresh container
I see this error after removing and creating a new one.
ERROR MyQ Connector Non-200 response calling: http://192.168.86.xx:8090/devices - [string âsocketâ]:94: No route to host (os error 113) - body:
When I paste the url and run it: Cannot GET /devices
Use status instead of devices in the url
What command did you use to create the container