Just set debug level to trace an post it here. Are you using the newest version?
Ok i had a openhab issue causing unresponsive items. Everything works except the colorpicker from sitemap. Seems it won’t send commands…
All my P100’s are offline in OH ( COMMUNICATION_ERROR
Invalid HTTP-Response). The P110 is ok. Yesterday everything was ok. Using the Tapo app all is ok.
Disabling/enabling the thing doesn’t help. Power recycle solved the problem. This also happened on Jan/17. What can be the cause ?
I’m still thinking that it’s caused by disabling internet connection to your devices. Got no problem withy devices.
I think so. Probably these devices “call home” periodically. I also have Kasa devices and they do not have this problem.
Maybe some keys changed in Tapo cloud and your binding is using the new keys instead of the old ones ?
@Bigdesaster question for you: have you tried to set tapo light on Apple HomeKit? i have some difficulties to set colors…can anyone point me in the right direction?
i have set as homekit item the color item from tapo binding, and with that i can control brightness and works perfectly on homekit, but when i set color of the light from iphone it does nothing on the light.
viceversa, if i set the color from openhab, the homekit device reflect the right color chosen.
my goal is to have the light controlled by my voice over siri commands…
I received a P110 today and am looking at getting it working on an isolated LAN. As you and @moody_blue found, it initially needs an internet connection to get metering data.
I put my packet capture trousers on and it appears the device does a DNS lookup to
pool.ntp.org when it starts, and tries to sync up with that. I implemented a NAT rule on Opnsense that redirected all NTP lookups destined for the internet to the router itself, and it now works without an internet connection - I am getting metering data while the packet capture shows the P110 sending a SYN packet every few seconds to
Thought I would post here so its clear that is what is happening - anyone who doesn’t have a router where you can do your own custom NAT rules could likely work around this issue by just allowing the device out to udp/123 so it can get its time data.
Great finding. I’m using OpenWrt with time service active so should not be a problem to parametrize it like you did.
If you intend to isolate your IoT lan from the internet pls note that some Tapo devices will be offline in OH approx 2 months after latest internet connection. In my case this happens with P100’s but so far didn’t happen with P110’s.
I think that probably this is a binding problem but so far @Bigdesaster did not address it, which is quite annoying because it force’s me to connect the IoT to the internet at least every 2 months
Just an FYI to anyone reading this thread and considering a Tapo P110 - the one I have has been running fine for the last few months. Its been restarted once as I needed to change the socket it was plugged into, and it came back to life within seconds.
It appears just letting it do its NTP lookup is enough for it to be happy. I bought several more recently as Amazon appear to regularly do them for £10 (which is brilliant value - they aren’t making much money on them at that price point), and all worked immediately. This could of course change in the future with a firmware update, but for now all appears well. The ones I have are destined to live a life of isolation without internet so should last me until they naturally go pop and stop working.
@Bigdesaster Maybe 3.3.0.M7 introduced some changes that can potencially affect this binding, see
Edit: The problem persists in 3.3.0
Any chance of getting Thing Type Tapo P115 integrated? I have one of those and they seem comparable to the P110 (energy monitoring on top of the switching). I can add a P115 using the P110 handler but they only come online randomly but usually return CONFIGURATION_ERROR “found type:‘P115’ with mac:‘xx-xx-xx-xx-xx-xx’. Check IP-Address”. Many thanks for considering my request.
sorry was not online here a while. Time is running…
Should not be a problem to add the P115. But i’ve got no device to test. Maybe i’ll order one.
But holidays are comming. Don’t know wheater i’ll can check this bevore them.
Sure i’ll check OH3.3 too
Sounds great, thank you. If there’s any way how I can help you testing it (so that you don’t have to order one) let me know. I’m not that expert about bindings but with some hints I can provide the infos you need. What I’ve already seen is that I’m able to turn it on and off occasionally when it’s online for some seconds, I giess right after that the binding again realizes it’s the wrong model and drops the error again.
The warning should be fixed too. Testet with snapshot 3.4.0. Seems that configuration file now returns a double instead an integer.
Great. What about my other problem “P100 goes to offline in OpenHab when unit not connected to internet during several weeks” ?
Thank you so much @Bigdesaster . It definitely works for me. It even was automatically discovered I can turn it on/off, and see the on-time, signal strength, and overheat information. What’s not working is the energy-related stuff sadly yet but that’s probably just fine-tuning now
ok i forgot to enable energy monitoring for the device. just try again.
i can’t track this problem cause i don’t have that. Did you try to let the NTP-traffic pass, like stuart suggests above? He added it to readme also. Sounds logical for me, cause in device requests there is always a timestamp sent. If there’s too much difference the device may ignore the request.
Fix confirmed and all working perfectly now @Bigdesaster
Thank you so much again for the rapid support
Yes, and that fixed the “P110 power cycle” problem. Would it help to enable debug logging ?
tank You for great work on the first place.
I have issues with connection of my P110, can You please help with that?
Binding is installed from store, version 3.3. Bridge is online. Auto-discovery worked and find the P110 correctly. IP address filled, but thing is offline with login error
2022-08-24 20:41:50.502 [DEBUG] [ntrol.internal. api.TapoDeviceHttpApi] - (tapocontrol: P110:50b368ddf3:54AF974A9228) login recieved errorCode -1501 - Login Error
Thank You very much,