I guess this post will end up burried since TP-Link don't care about this. It's too bad cause in the money for quality range, it used to be the defacto buy. Nice looking device, working properly most of the time and doesn't cost a lot. But the cloud requirement that remove local control is a very bad thing. I can't believe my on/off call need to go over the internet to turn on/off my light when it could be done directly between my home automation and the switch directly.

  @Wayne-TP There is some mistake in your answer.

 

Once I cut internet to my switch, neither Kasa app or Tapo app work with it. The switch blink red saying no internet and it stop responding on lan only network. Funny thing, I currently have some device that are showed offline in both kasa and tapo, meaning I cannot control them by those apps, but no problem with my openhab server that control them locally (which is like home assistant, a product that is mentionned under tapo labs => third party compatibility). Except for that online only switch that can only be talk through the cloud.

 

Risks and vulnerabilities to use an official API is really not a good argument. If your own apps is using the same api, the only vulnerabilities are the one exposed on the device. Now if you are talking about vulnerability in my openhab installation vs kasa/tapo apps themself, that's another story that you shouldn't be concern. Main reason is those people using either HA or OH for local control are normally way more tech savy then your average user. Discussion abour risks and vulnerabilities at that stage are something that shouldn't concern you since it's not your own software. But making the API available on local control without cloud authentication is something Kasa was praised for.

 

Honestly, you guys should open the API instead of closing it. The more open an API is, the best support you get from the community altogether. Even you're firmware could benefit from an open platform.

  @Wayne-TP If you think that enhancing security means removing all controls from the end user and placing it solely into the API of ANY company, you are incorrect. Especially when that API is located on a separate continent from the one the device being controlled originated from. I wish companies would stop with the "in the name of security" camouflaged motive statements.

 

The problem with your statement is that your sentence has the exact opposite meaning of security and everyone is taking notice.

 

Google "tp-link-china-routers-congress-commerce-ban-letter"

 

But whats most aggravating when someone spouts this line. Is that the open source community (WHERE YOU STILL USE LINES OF CODE FROM TO THIS DAY) becomes the punching bag of concealment within your sentence.

  @Wayne-TP The kasa app used to be able to control without internet all switchs and plug. Why it cannot anymore? All new switch using the new TP Authentication require internet access. Which mean no more iot lan without internet access for added security (way higher security then any firmware you could push). Why?

 

Also by the way, in the Tapo Apps, you have a switch "Enable Third Party Management" where you explicitly state Home Assistant as an exemple. So why you don't support it, you still have feature so it can connect to it. Although I didn't see any difference with the feature enable or disable.

 

Honestly, I'm looking right now to replace over 20 more switch and outlets, and adding many security camera. I'm rethinking my brand loyalty to TP-Link with that switch to online only that doesn't benefit the user

I guess we will never get an answer to that. Switch to online only and that's it.