Open jktikka opened 3 years ago
The switch history doesn't keep a record of when the broken custom command switch is turned on, but it does on a working one
Thanks for creating an issue! Interesting, I'll have a look this weekend.
Same for me. In addition, simple custom command "nircmd.exe monitor on" makes my workstation completely useless - it hangs in a loop of command execution. I had to force shut down loosing all opened/unsaved stuff. Best solution -> Uninstall.
New version was released today. This included some upgraded dependencies (including MQTT). Could you please try the new release to see if that fixes things?
Just like to add here. I am using several custom commands and even just regular commands such as mute and inc/dec volume. They become unresponsive after a couple days. The only way to bring them back is to edit the command and hit save again to reset it or restart the computer.
I love hass workstation and its update to the latest one. If there is anyway I can help let me know. Thanks again for hass workstation. I use it almost everyday to keep an eye on several computers.
I've been using a program called Auto Mouse Clicker (ExecuteAMC.exe) to run automations on my PC, triggered by hass-workstation-service custom commands.
The issue is that three times in a couple of weeks now, a custom command has become unresponsive in HA, only to be fixed by removing and adding the exact same command back with the same name. (The switch shows as off still, rather than unavailable like when my PC is powered off). Other sensors still work fine, this is specific to the custom command.
Here is my command if it would help:
C:\Remote\ExecuteAMC.exe "C:\Remote\Launch Flight Sim.mamc"