New plugin for TP-Link SmartPlugs HS100 and HS110

---

@mwittig said in New plugin for TP-Link SmartPlugs HS100 and HS110:

@heiko1988 said in New plugin for TP-Link SmartPlugs HS100 and HS110:

ok, the valus i see direct in the shell console

Thanks for the update on log output. This was very helpful!

As one can see, hardware revision 2.0 plugs appear to provide the measurement data in a different format. I have updated my fork to handle both formats accordingly. The measurement data should now
be displayed properly in your setup (after having installed the latest changes).

Hardware Revision 2.0

14:21:47.915 [pimatic-tplink-smartplug] consumption data is { voltage_mv: 234260,
14:21:47.915 [pimatic-tplink-smartplug]>  current_ma: 1445,
14:21:47.915 [pimatic-tplink-smartplug]>  power_mw: 336228,
14:21:47.915 [pimatic-tplink-smartplug]>  total_wh: 2412,
14:21:47.915 [pimatic-tplink-smartplug]>  err_code: 0 }

Hardware Revision 1.0

15:05:14.574 [pimatic-tplink-smartplug] consumption data is { current: 0.136666,
15:05:14.574 [pimatic-tplink-smartplug]>  voltage: 229.637248,
15:05:14.574 [pimatic-tplink-smartplug]>  power: 16.457058,
15:05:14.574 [pimatic-tplink-smartplug]>  total: 0.009,
15:05:14.574 [pimatic-tplink-smartplug]>  err_code: 0 }

Thank you very much

work all fine toggle, smart meter.

you are the man of the day for me

Thank you!

All works fine now!

@thex said in New plugin for TP-Link SmartPlugs HS100 and HS110:

However I’m currently experiencing some endless loops somewhere deep in the socket.io and can’t figure out where the problem is…

I had the same. See my earlier post infinite loop/stack overflow. It is forked in my fork

Hi,

you can add the daily consumption and the running time to the tp link addon.
as it is in the kasa app?

maybe the variables are there, then it should not be too hard. I guess

that would be great.

Thank you

Hi,
today I got my 2nd HS110 with HW 2.0 -> switching yes, measurements not… same as you all.
With the fork of @mwittig it works well. But when will this find its way to the official plugin as an update?

@mwittig can you file a pullrequest? Hope I find the time to integrate it soon then. This thread somehow went under my radar.

I saw the update for the plugin and installed it. Unfortunately the HW ver.2.0 plug is still not working.

@thex said in New plugin for TP-Link SmartPlugs HS100 and HS110:

@mwittig can you file a pullrequest? Hope I find the time to integrate it soon then. This thread somehow went under my radar.

I already did back in July and you accepted the pull request
However, the is no package release yet

oops, will do it this weekend

published

Works for me!

One thing what would be nice to be solved. After startup there are many errors. Can this be handled?

22:43:08.903 [pimatic-tplink-smartplug] error: Unable to get consumption of device: Error: TCP Timeout
22:43:08.907 [pimatic-tplink-smartplug] error: Unable to get consumption of device: Error: TCP Timeout
22:43:08.909 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
22:43:08.912 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
22:43:08.914 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
22:43:08.916 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
22:43:08.932 [pimatic-tplink-smartplug, TPlinkHS110] error: Error getting attribute value tp-link-aquarium1.state: undefined
22:43:08.938 [pimatic-tplink-smartplug, TPlinkHS110] error: Error getting attribute value tp-link-aquarium2.state: undefined
22:43:09.228 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout
22:43:09.230 [pimatic-tplink-smartplug] error: Unable to get power state of device: Error: TCP Timeout

I also get those errors. Round about 80 per day. I don’t know why, but it seems, that some of my sockets aren’t reachable sometimes.

Nevertheless, I changed the loglevel for those messages to warn, because it isn’t a real “error” in my opinion.

@saxnpaule maybe file a PR and I can add it mor quickly

I only changed “env.logger.error” to “env.logger.warn” for the three cases that annoy me.

But I think it’s up to you to decide whether it should be an error or a warning.

I think that a timeout could really be a warning.

Hello,

Have asked for a couple of months before

You can add daily usage and runtime to the tp link addon.
how is it in the kasa app?

maybe the variables are there, then it should not be too heavy. I guess

That would be great.

Many Thanks

Is it possible to get the total consumption which is not reset to zero when the plug gets powerless? In the app the consumption continuous at the last value when the plug was unplugged for a while.