m0unt41nm4n Posted September 8 Share Posted September 8 Howdy, I have been running the Chowmain TP-Link drivers for a while and have been running quite well. We got a new set of EP25 Kasa TP-Link plugs and installed them. They are unrecognized. Chow's drivers show them as unknown and are unable to control them (Yes I know very well how to use them, set them up, provision them, etc). These new EP25s are a different hardware version (v2.6/Firmware 1.0.3) than my other EP25s (1.0.10/Firmware 1.0). I did a wireshark sniff on them and these are giving security errors. Looking at the python-kasa software, sure enough, the newer EP25s require authentication. The user/password happens to be your Kasa or TP-Link creds. In adding my creds, python-kasa was able to gather info for them the same as my older ones. The bottom line is Chow's driver is incompatible with newer EP25. Being a Control4 driver developer, it would not take much time for Chow to integrate Kasa creds in his driver to make this work. He just needs to add user/password and have a checkbox to state whether creds are required or not. I haven't seen much discussion on this issue, but I think its going to become more prevalent as TP-Link begins to add authentication to its plugs/switches. I just wanted to see if others have experienced a similar issue with the newer EP25s as there is currently no solution for this? Quote Link to comment Share on other sites More sharing options...
neil12011 Posted September 8 Share Posted September 8 You could just reach out to Alan and his team on this, or post in the 3rd party drivers section, instead of posting it in the General section of a Control4 forum...But hey, what do I know? Quote Link to comment Share on other sites More sharing options...
m0unt41nm4n Posted September 8 Author Share Posted September 8 yeah sorry, I searched TP-Link and it brought me to general. Mods, please move this to the proper forum, my apologies. Quote Link to comment Share on other sites More sharing options...
zaphod Posted September 9 Share Posted September 9 @Andrew luecke or @alanchow - any idea on this question. Quote Link to comment Share on other sites More sharing options...
m0unt41nm4n Posted September 9 Author Share Posted September 9 Some more info for @alanchow... The New Kasas use the KLAP transport and add in 2 new types of handshakes. Looks like it's just a simple MD5/SHA256 mixture hash for the creds. More info on it is here: https://github.com/python-kasa/python-kasa/blob/master/kasa/klaptransport.py Quote Link to comment Share on other sites More sharing options...
msgreenf Posted September 9 Share Posted September 9 30 minutes ago, zaphod said: @Andrew luecke or @alanchow - any idea on this question. these are not supported today - correct Quote Link to comment Share on other sites More sharing options...
m0unt41nm4n Posted September 9 Author Share Posted September 9 So that is kind of the question... Kasa has made clear they are moving towards secure comm on their devices. Firmware in the near future will likely move many of their devices in that direction. From the Amazon comments, it even looks like the newer EP10 (That Chow supports) v4 has enabled encryption. So that one may be the first one to go that was listed as one of Chow's supported devices. Hence the question is, will Alan be supporting the new encryption standards moving forward? Because if TP-Link keep son this KLAP secure comm initiative, the driver may not be working in the future. I don't even want to upgrade my firmware on some of my other Kasa devices in fear that this will push them off my Control4. I posted the source code link above in hopes that Alan and crew can take a look at it and consider converting that to Lua and using it in his driver. Any input would be gladly appreciated. Quote Link to comment Share on other sites More sharing options...
zaphod Posted September 9 Share Posted September 9 What's the need for encryption? Because they are cloud devices? I am starting to like my Sonoff devices flashed with Tasmota firmware more and more. Quote Link to comment Share on other sites More sharing options...
cjh Posted September 10 Share Posted September 10 I’ll add my two cents. We have a home full of Kasa switches and use the Chowmain driver. Right now none of the Kasa devices we own require encryption - but to future proof this, yes, please update the driver! It seems an inevitable necessity. Quote Link to comment Share on other sites More sharing options...
cshepard Posted Saturday at 11:09 PM Share Posted Saturday at 11:09 PM On 9/9/2024 at 2:58 PM, zaphod said: @Andrew luecke or @alanchow - any idea on this question. I’m sure these guys are pretty busy with signing up new dealers since removing their drivers from DriverCentral this week. I’m hoping they approve us & get our new account set up soon. Quote Link to comment Share on other sites More sharing options...
Andrew luecke Posted Sunday at 09:41 AM Share Posted Sunday at 09:41 AM G'day, Any chance you can file a ticket using: https://chowmain.software/for-integrators/technical-support to allow better tracking of this issue Thanks, Andy Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.