3-way switch circuit stops working correctly

Configuration
1

I’ve been using this construct with TreatLife SS02 3-way switches flashed with Tasmota for a few years now but a recent update to HA broke it. Can someone spot what might be wrong in the config vis a vis current language specifications?

The correct behavior is observed when the circuit is operated from the physical switch in that the bulb goes on/off and the dashboard tracs along. Turning on from the dashboard, however, causes the icon to momentarily blip on and the connected bulb does not come on at all

mqtt:
  switch:
    - unique_id: study_lights
      name: "Study Lights"
      state_topic: "stat/TreatLife4/POWER1"
      command_topic: "cmnd/TreatLife4/EVENT"
      payload_on: "ON"
      payload_off: "OFF"
      availability_topic: "tele/TreatLife4/LWT"
      payload_available: "Online"
      payload_not_available: "Offline"
2

You have an event called, so without telling us what your rules are in
Tasmota on that device, it would only be a guess.

also you said 3 way, so that could change things as well.
How many switches? Do they all have the same Tasmota rules?
Is the load/bulb smart? If it is does it have Tasmota rules as well? Was the bulb replaced without programming it if it’s smart?

Before you get too deep into this, as you said this has worked for a while, why don’t you do a power restart on all the devices to make sure they are all doing what you think they are. like kill the breaker and let it sitt a minute, turn it back on and test it.

Is this Digiblur / Travis’s code? Know where you got it from?

3

Yes, it is Travis’s code. One smart and the remaining regular switches and with regular bulbs as loads :frowning:

The link to his Tasmota instructions isn’t working any more and I need to see if I have it in my notes somewhere.

Resetting the switch using its reset button did not help. Tomorrow, I will find the circuit breaker and power cycle the circuit.

In the meanwhile, here’s what the Tasmota console has to say (pardon the formatting):

22:00:38.828 CMD: rule
22:00:38.836 MQT: stat/TreatLife4/RESULT = {“Rule1”:{“State”:“OFF”,“Once”:“OFF”,“StopOnError”:“OFF”,“Length”:440,“Free”:71,“Rules”:“on power1#boot=0 do backlog nodelay ; var1 TOGGLE; var2 ""; ledpower1 0 ; ledpower2 0 endon on power1#boot=1 do backlog nodelay ; var2 TOGGLE; var1 ""; ledpower1 1 ; ledpower2 1 endon on power1#state=0 do backlog nodelay ; var1 TOGGLE; var2 ""; ledpower1 0 ; ledpower2 0 endon on power1#state=1 do backlog nodelay ; var2 TOGGLE; var1 ""; ledpower1 1 ; ledpower2 1 endon on event#ON do power2 %var1% endon on event#OFF do power2 %var2% endon”}}

4

I asked Gemini to parse the rule to make it more readable and it pointed out that the rule was off!

When I turned it on from the console, the correct operation was restored.