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
statetext invert - 6.20 not working #3656
Comments
Hi, Confirmed. Console Output:
|
... i chanched my switchmode - thats ok for me... |
Ah nice one... To get status 0 output you need to execute command status 1 To get status 1 output you need to execute command status 0 Considering this workaround it will be fixed in next release. |
Fix possible ambiguity on command parameters if StateText contains numbers only (#3656)
The issue as noted has been solved by removing the possibility of allowing StateText as input to a command parameter.
If a user configures StateText1 as "1" and StateText2 as "0" be prepared to see messages like
for the simple reason that the command |
Version 6.2.1 20180905 * Fix possible ambiguity on command parameters if StateText contains numbers only (#3656) * Fix Wemo emulation to select the first relay when more than one relay is present (#3657) * Fix possible exception due to buffer overflow (#3659) * Fix lost energy today and total energy value after power cycle (#3689)
Version 6.2.1 20180905 * Fix possible ambiguity on command parameters if StateText contains numbers only (arendst#3656) * Fix Wemo emulation to select the first relay when more than one relay is present (arendst#3657) * Fix possible exception due to buffer overflow (arendst#3659) * Fix lost energy today and total energy value after power cycle (arendst#3689)
i use my switchbutton inverse - now it work with 6.2.0, but status 0 dosnt work...
MQT: /ESP_02/stat/RESULT = {"StateText1":"1"}
MQT: /ESP_02/stat/RESULT = {"StateText2":"0"}
CMD: status 0
MQT: /ESP_02/stat/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoff4096","OtaUrl":"http://10.1.1.......
only status1
The text was updated successfully, but these errors were encountered: