New plugin for TP-Link SmartPlugs HS100 and HS110

---

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

the day/month/year stats seem not to reset after removing the plug

Sounds great to me. Thanks for testing. I’ll create a PR.
EDIT: https://github.com/thexperiments/hs100-api/pull/1

We need support for something like this:

absolutely! expandable devices would be a great thing

I think there already is a way to remove the labels via config if you don’t want them.
Sure there might be the need of preventing switching the outlet but I’d rather add a config value which prevents switching it.

Maybe add a Config option to hide the switch.

I think I will have some time next week to properly add measurement.

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

< 00:19:18.375 [pimatic-tplink-smartplug, TPlinkHS100] Error getting attribute value TPlinkSmartplug-3.state: Maximum call stack size exceeded
< 00:20:29.693 [pimatic] A uncaught exception occured: RangeError: Maximum call stack size exceeded
< 00:20:29.693 [pimatic]>    at Function.isBuffer (buffer.js:163:23)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:28:68)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:20:29.693 [pimatic]>    at _hasBinary (/Users/thex/Dropbox/projects/pimatic/pimatic-beta/node_modules/pimatic/node_modules/socket.io/node_modules/has-binary/index.js:49:63)
< 00:2

Hi,
I replaced the two files from the PR of @sweebee butnothing changed in apperance.
Am I doing something wrong?
Best regards
Chris

thanks to a pull request from circuitdb and some little fixes from my side the hs110 now support measurement.

Hello,
My problem with the plugin is:

• system virtualbox ubuntu, 4cores, 4gb RAM same network like the nonvirtual hardware, google is pingable, plugin can be installed
• when I use discover devices, he offers me that he couldn’t find the tplink-api… the tplink-api is not defined

Mit freundlichen Grüßen
Chris

Edit:

• reinstalling via GUI and deleting the folder I have already tried…

Noticed this also yesterday. Seems to be a bug. Will check the next days.

puh nice… thought this was my systems-fail…

@chris should work again. I released the new version on Friday. Problem was a bit bigger as with the last version the API was changed but I now reimplemented the discovery and also made the default device naming a bit clearer.

@thex
hello yes it’s working again.

Thanks.

is it possible to implememt a config-option to set the intervall by a rule?

Because i have two HS110 plug wich a control a heater,
but when nobody is using the heater the plugs an turned of… by a normal switch.

so ever when this is happening i have every $intervall seconds an error message in the log.

so my rules would look like.

when tplink-smart-plug is present then set interval to 60
when tplink-smart-plug is absent set interval to 0

this would be nice feature…

Hm currently this is not planned. I think to make it accessible I would need to expose it as an attribute which by default would make it visible in the GUI.

I think this is a quite special usecase. Maybe you can find a workarround via updating the device config with an API call via CURL or something like this.

Oh I can configure a device via API.
Nice… didn’t know this…

Is there somewhere a overview for the API?!
For the curl commands especially…

Mit freundlichen Grüßen
Chris

Sure the web-frontend also “simply” uses the API so anything can be done via API

https://pimatic.org/api/actions/

I think what you would need is

updateDeviceByConfig

Ok how should a api call look like?

curl http//pimatic-ip/api/device-id/updatedevicebyconfig("parameter",60)

just as example?

Mit freundlichen Grüßen
Chris

No you need to create a patch statement with json data like here https://forum.pimatic.org/post/14996

Or like here… https://forum.pimatic.org/topic/1796/bash-script-to-write-into-an-pimatic-variable

curl and patch are the keywords

i have a strange problem. my HS110 get dscovered by pimatic and everything, i can also switch on/off but somehow i dont get any voltage/watts data
in error log i see

error [pimatic-tplink-smartplug]: Unable to get power state of device: Error: connect EHOSTUNREACH 192.168.2.150:9999

i dont get it, IP address is correct. i also made reset and reconnect to the network but still the same