TP-Link Component scan_interval

[batgrr]

Since the migration to the new TP-Link Smart Home component, it seems we are missing some parameters that were available in the previous implementation. Specifically, the scan_interval and enable_leds variables are no longer configurable within the tplink component. Would this be added soon?

[aidbish (Adrian)]

@batgrr

enable_leds

for the scan interval

How to adjust scan interval with the new TPlink component

I had an automation that checked the power usage of a switch every 3 seconds, and did something when over a certain usage. With this new component, that automation reacts much more slowly. From @Bruce0’s testing it looks like this isn’t possible any more. Anyone else have any ideas? Does this need to be added as a feature request?

for the leds.

Disable TP-Link LEDs with the new configuration

This option was dropped to keep the code simpler, but you can configure them with the console tool pyhs100: pyhs100 led 0 to turn them off and pyhs100 led 1 to turn them on.

[SuctionSeat]

It may be worth asking for this in the ‘feature requests’ section.

It seems a shame when a component gets replaced by something with features missing from the old one, maybe someone with enough python skills would be able to add back in the scan interval feature

[amelchio]

You can use the service call homeassistant.update_entity to make it update more frequently though it will admittedly be a bit of work to make an automation that fires every 3 seconds.

[mrneilix]

I’ll say that before, I felt it was running fine, but after that update, my log got flooded with “went to unavailable” (I know it’s an issue with the switches though), so I had to remove it from the log

[batgrr]

Thanks for the references!

I was able to configure it for my automation with a few modifications for the scan interval part using this. Would be nice if it was added as a component feature itself

@SuctionSeat; I’ve moved this over to the feature request section, thanks.

[pimw (Pim)]

You have my vote! The default polling frequency is suboptimal: it is too low. A polling rate of 5 seconds works perfectly.

So, the wish would be:

• Either change the default polling rate from 30 seconds to 5 seconds
• Or introduce an option to let the user change it from the gui of the integration

I know this can also be done by setting up an automation (see an example below), but i feel this is the wrong direction. Home Assistant is focussing more and more on being user-friendly, so that more people will enjoy Home Assistant (not just tech-savvy people). Having to build your own automation for this is the opposite of being user-friendly.

alias: Update TP-Link HS110
description: ''
trigger:
  - platform: time_pattern
    seconds: /5
condition: []
action:
  - service: homeassistant.update_entity
    data:
      entity_id:
        - switch.energiemeter_pc
        - switch.energiemeter_tv
mode: single