anne
January 26, 2019, 3:17pm
21
I have submitted an update of the app to the store which should take care of the issues.
If you are able to install via the ‘CLI method’ (refer to https://community.homey.app/t/how-to-cli-install-method/198 ), it can be downloaded from github (https://github.com/abaretta/nu.baretta.tplink .
Changes:
The ‘dynamic IP’ feature is now optional, and disabled by default
The discovery process would continue to run in case no new plugs were found. It will now run 3 times at 2,5 s. interval and stop after 9 seconds.
I added conditions on the driver type for the use of certain capabilities.
rafi
January 28, 2019, 11:12am
22
This is still not working after upgrading via cli. Getting loads of - Error sending value. And then the app crashes.
anne
January 28, 2019, 11:54am
23
Hi Rafi,
Can you send me the output from the cli?
rafi
January 28, 2019, 12:59pm
24
How do I do that in v2.0?
anne
January 28, 2019, 1:19pm
25
You started the app through the athom cli, right? If you start the app with
‘athom app run …’
You will get debugging output on your screen (if you use ‘athom app install’ it just installs the app and you do not get the output). Presumably that’s also where you saw errors?
Are you using hs100 or hs110 plugs?
rafi
January 28, 2019, 1:45pm
26
Below is the output from cli debugging. As soon as I tap on one of the TP-Link HS110 the app crashes.
C:\Users\rafal\Downloads\Homey\nu.baretta.tplink-master>athom app rundebugHomey (https://192-168-1-142.homey.homeylocal.com )…nu.baretta.tplink successfully installednu.baretta.tplink, press CTRL+C to quithttps://go.athom.com/app-profiling?homey=5881f9f0e9dd2f810d32d2de&app=nu.baretta.tplink
TypeError: this.LedOn is not a function
— INFO: nu.baretta.tplink has been killed —
anne
January 28, 2019, 2:40pm
27
Thanks, that helps in getting the cause of the problem.
The IP address appears to be incorrect for both devices. You can either enable the ‘dynamicIP’ option in the settings, or manually enter the correct IP address.
I’ll look into the ‘this.LedOn is not a function’ error… Yes, that’s a bug (typo). Fixed, no idea why that is a problem for some (on V2) but not everyone.
This is fixed in version 0.1.3, I have updated the github repository, so you can test it if you want.
Wow! Fastest approval from Athom ever, I have just publised v0.1.3 in the appstore
1 Like
rafi
January 29, 2019, 10:26pm
28
It’s not crashing now but you can’t turn on or off the plugs at all.
Pre-processing app…debugHomey (https://192-168-1-142.homey.homeylocal.com )…nu.baretta.tplink successfully installednu.baretta.tplink, press CTRL+C to quithttps://go.athom.com/app-profiling?homey=5881f9f0e9dd2f810d32d2de&app=nu.baretta.tplink
What do you mean by that:
The IP address appears to be incorrect for both devices. You can either enable the ‘dynamicIP’ option in the settings, or manually enter the correct IP address.
Those device can be managed by Kasa app with no issues.
Thanks
Thanks
anne
January 30, 2019, 5:51am
29
What I mean is that the Homey app is polling the devices at the wrong IP addresses! You have three options to address this and get it working:
Manually change the IP for each device in the Homey app to the IP currently used by the device.
Enable the ‘dynamicIp’ option in the Homey app for each device in the settings for the device. Or:
Remove the devices and add them again. The Homey app will discover them again at the correct IP’s.
Either way enable the dynamicIp option or the app will stop working when the devices get a different IP through dhcp.
rafi
January 30, 2019, 8:06am
30
Some progress here. I removed the devices from Homey and re-added them. Now I can turn on and off them. However the Switch LED ON/OFF doesn’t changed its status when it’s on and all meter readings don’t refresh automatically, you have to leave the window that shows them and re-open it to get the current readings. Thanks
bvdbos
January 30, 2019, 4:41pm
31
That’s something else I presume, that’s about screen-refresh. You can update the screen-value by clicking on it.
Created an issue for this at Athom already but would be good if you do that too:
anne
January 30, 2019, 4:56pm
32
About the LED, you can test the function with a flowcard, see if you can turn it back on manually.
And in your case you should enable the ‘dynamicIp’ option.
rafi
January 30, 2019, 11:48pm
33
Re the LED, it looks like the initial state is not reflected in the app. Once I turned it on and off, it started showing it correctly.
anne
February 11, 2019, 9:22pm
34
Hi all,
I have submitted an update of the TP-Link Smart Devices app to the app store, version 0.1.4.
The changes are minor, the most noticable change is that I have removed the ‘LED on/off’ functionality from the interface for the TP-Link smartplugs (hs100/hs110/hs200). The feature got in more or less ‘by accident’ with the Homey V2 upgrade, and I felt it was more of a nuisance (as you had to swipe it away to get to the on/off button) than adding any useful functionality.
Note that you can still toggle the LED with a flowcard, so if you really need a button for it this is still possible.
Unfortunately the now non-functional LED button will remain in the interface until you re-pair the plug, ie. remove the device and add it again. After adding it again you will need to repair all flows the device was used in. After adding the plug again you will only have an on/off button.
1 Like
I have some TP-Link light bulbs which appear to frequently pick up new IP addresses meaning I have to delete them in Homey and rediscover them. So I’m hoping that this post means that a solution is on the way. But I don’t know what the above SDK rewrite refers to. Will this be the Athom app I use on my WIndows laptop or something else?
anne
March 23, 2019, 7:33am
36
That rewrite was published months ago, the current version is v0.1.4. However, support for dynamic IPs is included as an option. All you need to do is go to the (advanced) settings and enable support for dynamic IP’s.
You mention a Windows app, are you still on Homey V1? It should work on V1 as well (albeit no longer supported by me as I can’t test it…).
Note that the appstore includes details such as this, click on the ‘show more’ link for the app to read it
Hi Anne,
Thanks for the quick response. I’m using the Windows desktop app and it’s version 1.0.4 I’ve checked for updates and it says it’s the most up to date version. I never found an option in there for dynamic IP addresses but the Homey hub is currently switched off at another address so I can’t get in to check any config at the moment.
What about firmware? Does that update automatically?
Cheers, David.
anne
March 23, 2019, 8:35am
38
Hi David,
In V1, if you go to the device view in the desktop app, there’s a little cog in the corner of each TP-Link device (bulbs in your case). Click it to enable the ‘dynamic IP’ option.
You may want to consider upgrading to Homey V2, V1 is not developed any further, and more and more apps are V2 only, as it is difficult to support apps for V1 once a developer has moved on to V2.
By default the firmware is updated automagically, except for the upgrade to V2. The reason is that you will lose the desktopapp (although for managing flows a new webinterface has been provided, it is very good). There are a zillion posts about this on the forum. You can upgrade by installing the new Homey app on your phone. You may want to check all your devices are supported, although by now that shouldn’t be an issue anymore I guess.
Hi Anne
Wondered if you could assist with a recent issue I am having with the app and TP-Link HS1000 switches. I am running v2 on my homey and latest v0.1.4 app. I had four HS100’s running fine with my Homey and for some reason, one dropped off and went “unreachable” and I am unable to get the app to pick it up again.
I have tried deleting the device and re adding it and manually adding the IP to the HS1000
I know it is not the HS1000 as I can control it with the TP-Link app.
Any assistance appreciated.
Regards
anne
April 3, 2019, 6:40pm
40
Any chance you can install the app via the CLI ? This may give some useful output.
When discovering plugs the app checks the ID of the discovered device against the ID’s of the devices that are already paired. It will only show devices that are not yet paired.
When you manually enter an IP it ‘should’ just work. In other words, no idea what the issue may be :-/
