How to check a actual Switch state in rule

[Aint-Nobody]

Hello everyone,

I'm once again struggling to solve a rule problem.
I want to use a rule to query the current status of a switch at any given time.
Not the message when it's turned on or off.

As a trigger event, I use the command Status 10, which returns the JSON string StatusSNS.
I've tried evaluating this in different ways, but nothing has worked.
I tried the following:

On StatusSNS#Switch1 do If %value%=="ON" tmsend blabla Endif endon

On StatusSNS#Switch1 do If %value%==ON tmsend blabla Endif endon

On StatusSNS#Switch1="ON" tmsend blabla Endif endon

On StatusSNS#Switch1=ON tmsend blabla Endif endon

The first two examples are always true, even when OFF.
The other two don't even work.

I don't work with MQTT; everything should work via rules.

Where am I making a mistake?
Or is there perhaps a completely different approach to solving the problem?

[sfromis]

The general way is doing it without needing a Status 10 command and StatusSNS payloads, like:
on Switch1#state==1 do .... endon
Acts when something happens to change state.

In a rule, you can also use %Switch1% as a rule variable without needing triggers.

When it comes to your first two rules, the correct format (if you want to use Status 10 etc) would be:
on StatusSNS#Switch1 do if (%value%=ON) .... endif endon
Use = for string compare (== is for numeric), no string delimiter and () around condition.

The last two rules lack the do keyword, and endif is bad when there is no if. Otherwise the last one is "closest" to right.

Beware that if you issue the Status 10 command from a rule, it must be Backlog Status 10 for triggers to work.

As you did not explain your "problem", hard to say if there would be other ways.

[Aint-Nobody]

Your answer helped.
The most important information was the difference between = and == .
Thanks.
The rule syntax can be quite tricky sometimes.

But another problem is that Tasmota doesn't properly initialize the GPIO pin states after a deep sleep wakeup.
After a power-on reset, the state is displayed correctly, but not after a wakeup on the reset pin. Then the input is always initially displayed as on even though it is off.
Only after a switching cycle does the state become correct again.

Is there a plausible reason why this is done this way?
Where can I change the source code so that the GPIO pins are properly initialized during a deep sleep wakeup?

[sfromis]

You also have triggers like Switch1#boot, did you try that?