Kasa smart plug goes to "unavailable" state

I have an automation that is triggered by Kasa smart plug’s current consumption - basically when it goes below certain value.

The behavior I see is that sometime this automation is wrongly triggered. I looked in the trace logs and I see this:

trigger:
  id: '0'
  idx: '0'
  platform: device
  entity_id: sensor.washer_plug_current_consumption
  below: 2
  above: null
  from_state:
    entity_id: sensor.washer_plug_current_consumption
    state: unavailable
    attributes:
      state_class: measurement
      unit_of_measurement: W
      friendly_name: Washer plug Current Consumption
      device_class: power
    last_changed: '2022-01-16T04:35:48.388935+00:00'
    last_updated: '2022-01-16T04:35:48.388935+00:00'
    context:
      id: 99aa4d6cb49984eec14ce4e5424def29
      parent_id: null
      user_id: null
  to_state:
    entity_id: sensor.washer_plug_current_consumption
    state: '0.3'
    attributes:
      state_class: measurement
      unit_of_measurement: W
      friendly_name: Washer plug Current Consumption
      device_class: power
    last_changed: '2022-01-16T04:36:08.376758+00:00'
    last_updated: '2022-01-16T04:36:08.376758+00:00'
    context:
      id: 1462744b1b3bb8830e1999cdb3b547da
      parent_id: null
      user_id: null

So basically sometimes the smart plug is unavailable, what causes the automation to be triggered.

How can I configure the trigger so that it will basically ignore when the plug goes temporarily into unavailable state?

Thanks!

1 post - 1 participant

Read full topic