Tapo p110 Switched on and off every 5 Minutes?

JohnSwift10

GDB2222 said:

You could just try out ChatGPT's  code and see whether it works. No guarantees, of course, but it's unlikely to cause a major calamity.

 There is no attribute for getState().

  current_state = p110.getState()  # Check if the plug is on or off

AttributeError: 'P110' object has no attribute 'getState'

bob_a_builder

Since your main issue was to prevent the multiple repetitions of an On command when it was already ON  ( or visa versa) 

You can set up a variable in your code to record the 'state' of the plug as you see it, 
where the state reflects what you last set it to and use that the prevent issuing further On commands if already On

Something like this, pseudo code

Int state = false
const  OFF = 1
const  ON = 2

Loop
If temp < 20 and state  != ON then
     turn on heater
     state = ON

if temp > 20 and state != OFF then
    turn off heater
    state = OFF

bob2302

bob_a_builder said:

Since your main issue was to prevent the multiple repetitions of an On command when it was already ON  ( or visa versa) 

You can set up a variable in your code to record the 'state' of the plug as you see it, 
where the state reflects what you last set it to and use that the prevent issuing further On commands if already On

Something like this, pseudo code

Int state = false
const  OFF = 1
const  ON = 2

Loop
If temp < 20 and state  != ON then
     turn on heater
     state = ON

if temp > 20 and state != OFF then
    turn off heater
    state = OFF

As I already pointed out this has no benefit and makes the control slightly less reliable. If, for whatever reason, the code loses track of the remote state, it will lock-up indefinitely. Sending the command unconditionally avoids this possibility without any penalty, since it doesn't affect the number of relay switches.