Berry - Override web UI relay toggle

[valdus2]

Using Haspmota, I have the below function working for a relay:

tasmota.add_rule("hasp#p13b12#event=up",
def ()
var therm = tasmota.get_power(0)

   if therm == false
      tasmota.cmd('TimedPower1 3600000,on') 
      tasmota.cmd('Buzzer 3,3,1') 
      p13b12.bg_color = "#00FF00"
      p13b12.text = " ON "
   else
      tasmota.set_power(0, false)  
      tasmota.cmd('Buzzer 2,3,1') 
      p13b12.bg_color = "#FF0000"
      p13b12.text = " OFF "
   end

end
)

Now I have a second function when I toggle the relay from UI or http:

tasmota.add_rule('POWER1#State', 
  def (value,trigger,payload)
    var v = value 

   if v == 1
      tasmota.cmd('Buzzer 3,3,1') 
      p13b12.bg_color = "#00FF00"
      p13b12.text = " ON "
   else 
      tasmota.cmd('Buzzer 2,3,1') 
      p13b12.bg_color = "#FF0000"
      p13b12.text = " OFF "
   end

  end)

But this isn't a timedpower command....it just catches the on and off....

Can this be done only with berry so when I push the UI button do all that the first function does?

And if so how can it be done with http call too?

It must be something obvious, too obvious that It confuses me.

Thank you in advance.

[sfromis]

Not clear exactly how much you mean with "Can this be done only with berry", what function you wanted to happen, but doesn't, or if the main issue is to avoid repeating similar code.

In the latter case, you could have something like this, called from both places.

def setpower(onoff)
   if onoff == false
      tasmota.cmd('Buzzer 3,3,1') 
      p13b12.bg_color = "#00FF00"
      p13b12.text = " ON "
   else
      tasmota.cmd('Buzzer 2,3,1') 
      p13b12.bg_color = "#FF0000"
      p13b12.text = " OFF "
   end
end

Such a function could also be invoked via MQTT, http, command, or even the device groups feature. The last 3 (or 4) could be by executing a command. One way would be to define a command via tasmota.add_cmd, or simpler but less flexible by executing a command like Br setpower(true).

[valdus2]

Yes I know I'm not clear cause I'm confused....

So in simple words:

When I press the UI button does its default action(on/off) not a timedpower1 command which can be given in console or rule etc.

Now can this behavior change (thought through Berry...) so when I press it does a timedpower command or just runs my first function?

Could it be so simple just by catching POWER1#State translate it to a timedpower1 command?
So my second function becomes this

tasmota.add_rule('POWER1#State', 
  def (value,trigger,payload)
    var v = value 

   if v == 1
      tasmota.cmd('TimedPower1 3600000,on') 
      tasmota.cmd('Buzzer 3,3,1') 
      p13b12.bg_color = "#00FF00"
      p13b12.text = " ON "
   else 
      tasmota.cmd('Buzzer 2,3,1') 
      p13b12.bg_color = "#FF0000"
      p13b12.text = " OFF "
   end

  end)

Thank you.

[sfromis]

Without description of your use case, and the "why" about doing things, instead of unclear ideas about "solving" whatever you see as an issue, it gets hard to recommend anything.

There's nothing "wrong" about the last add_rule you posted, if it works as you want.

Seeing what you do - if what you want is that it gets powered off again one hour after being powered on, every time, you need no TimedPower command at all, you can instead use PulseTime to have this automation handled outside of Berry. This would cover other ways it might be turned on too. Of course, you can still have triggers on power status changes when you want to do additional stuff (like sounds and display updates).

And the first tasmota.add_rule("hasp#p13b12#event=up", could just turn on/off power, letting the tasmota.add_rule('POWER1#State', handle the sounds and display updates.

[valdus2]

Of course, you can still have triggers on power status changes

That's what I mean, If I can intercept the default on/off action from the UI button, so instead it effectively turns it in timedpower1.

ideas about "solving" whatever you see as an issue

Of course and I don't see any issues, I just want to know just the above, if I can intercept the default action through Berry...and how...and if it's right....

[sfromis]

Depends on what you mean by "intercept". What you get when triggering on power status changes is after the fact, not related to why the status changed. You cannot avoid the status already having changed, unless you instead do something to "take over" the "why". As power status may change for a number of reasons, you have no general way of avoiding the power status change. Closest is that the action could be on a virtual relay (not connected to anything physical), and then have triggers to get events about something happened there, and for you to decide what you want to do about that.

Still, if you use PulseTime, all that stuff about ensuring one hour of on-time can be handled by Tasmota itself, without using TimedPower. And then you can use triggers to get notifications about what happened and keep your display updated, along with producing sounds.

[valdus2]

Yes, both solutions seem right, either pulsetime or a virtual relay. Now I see it clearly.

For one more time, a big Thank You.