You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OK, this may indeed be related to this strip leading zeroes.
When parsing events, the first eventvalue must be a numerical and I think the stripping part may indeed mess things up here.
I was already a bit afraid this may become an issue and was tempted to add another checkbox to enable/disable this optimization.
Please don't add the checkbox, the optimization (or a value translation) works fine except this particular case, where the first zero looks to be eaten by wrong test condition. Hopefully this could be fixed without complicating the settings page.
I'm not sure it's because of #4146, but zero-valued eventvalues are not parsed anymore in the latest release.
Tested on ESP_Easy_mega_20220809_normal_ESP8266_4M1M build
The rule triggers log record upon arrival of setctl command
If I send to the command topic the following payload:
event,setctl=1,2,3
the log shows
If I change the payload to
event,setctl=0,2,3
logentry is not triggered:
This affects only %eventvalue1%, all subsequent zero values are processed as expected
The text was updated successfully, but these errors were encountered: