-
-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Execute commands" output doesn't turn off by itself #432
Comments
Thanks. I'll add this fix to the next release. It's good to see a bug report with an accompanying fix! |
Thanks for looking into this quickly Kyle, unfortunately I just noticed that the patch you submitted has the condition implemented backwards, so it doesn't work. The code is now:
But it should be:
|
Whoops! Thanks for catching that. I'll fix it for the next release. |
kizniche
added a commit
that referenced
this issue
Mar 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Mycodo Issue Report:
Mycodo Version: 5.6.6
Problem Description
When working with a "Execute commands" output, Mycodo turns this output on just fine but doesn't turn it off when appropriate.
Steps to reproduce the issue:
This is reproducible directly on the "Output" page:
Root cause and proposed fix:
Mycodo checks whether the output should be turned off with the following code snippet in controller_output.py:
The issue is that "Execute commands" outputs aren't associated to a pin. So the above condition never becomes true.
I get the expected behavior with the following fix:
The text was updated successfully, but these errors were encountered: