macjeff

Kasa 6 port power Strip HS300 HW 1.0 FW 1.0.21 works with old KASA but not with beta version. All the other devices that were failing I am replacing with newer ones. I had 3 new ones and replaced 3 of the 6 already. So the only thing I am worried about is for now I have to run 2 versions of the plugin (old version just for power strip) and if you update KASA it will auto update the next time I reboot and I will lose that. UNLESS you name it as a Kasa V2 or something so its a different server. Here is amazon link- https://www.amazon.com/Kasa-Smart-Power-Strip-TP-Link/dp/B07G95FFN3/ref=sr_1_11?crid=2MWV325DVW41S&dib=eyJ2IjoiMSJ9.apRwjLLxaDW3zx_U0vHopt-ZBbqi3gNUh9IP8WOAa3OxJv6VmPFtGPTOKAV44awua7ksvyfHtjh_5ae32aC3CsUrTBJxKaUjDM2KQiJ7P7hHHAdgFojhp_nJB9cPSBJ1zcDo_omYiFF5g25AGjnKyyZ7-y6u152DU-Wuk96dPUQTMPM4GUcdh_q7P6UfYDtLX2nT0dZoor4VWpOnGnfbT2dnvShVnQvRMl8kXd4fzpQSOfopRnnR2xXpLjevwyO6Hqehyqi9jF-bRF57uXsjRS2eVtIZBa2-WaTn4-JPKh4._73lbizZ502-7s2r_UlrotW7Ru1s1u1CqxksaHlG6gQ&dib_tag=se&keywords=kasa%2Bplugs&qid=1778625888&sprefix=kasa%2Bplugs%2Caps%2C111&sr=8-11&th=1

also the surge strip only shows 1 node so I cant control the individual ports. Its an older one. Is there one you support now?

from logs and AI check- Working HS103 devices: 172.16.1.163 — HS103 hardware v3.0 172.16.1.164 — HS103 hardware v3.0 These use the older Kasa local protocol on port 9999, so the plugin can talk to them directly. Problem HS103 devices: 172.16.1.159 — HS103 hardware v5.0 172.16.1.189 — HS103 hardware v5.0 Skipped as unsupported: 172.16.1.189 HS103 v5.0 — KLAP 172.16.1.159 HS103 v5.0 — KLAP 172.16.1.180 EP10 — KLAP 172.16.1.188 EP10 — KLAP 172.16.1.187 EP10 — KLAP 172.16.1.186 EP10 — KLAP 172.16.1.228 EP25 — KLAP

the new beta fails after a while- see new log Kasa_5-12-2026_43439_PM.zip

actually only 6 missing devices in BOTH beta and production. Maybe this helps (See screenshot) These happen to be older devices. If I can get them to work with new version I dont need the old 3.1.4. Or worse case I buy new devices.

I have lots of issues. First I had both the beta and the production installed because some new device types were not supported. I accidentally deleted the production instead of the beta so I reinstall it. Now the production is seeing only 10 of my 17 devices. I attached that log. Then I updated to 3.3.4 The 3.3.4 is giving authentication errors but I know its correct. Its different IP's so its almost like it wont find those devices. So it to has only 10 devices now. Whats going on? (Beta log attached here...will have to do second post due to limits for Production log) Kasa_BETA-5-12-2026_34906_PM.zip production log Kasa-PRODUCTION_5-12-2026_34736_PM.zip

I know its off topic a little, but any ideas on a way to measure water in a pool. I used one called Pool Sentry but its not smart. I need a way to measure level thats smart!! (and waterproof battery)

I am getting YoLink for two reasons Outdoor motion sensor looks good The Water Level Filter with float First should I get the YoLink or the YoLink Local. Second, are those two devices supported (getting a speakerHub from them too) Goals---- Replace an oudoor (in waterproof case) Insteon Motion Sensor that is flaky. Right now I use another nodeserver called LinkTap (Jimbo I think did it) to control valves. I use a timer to add water a little each day and its been working for a couple years since it also monitors weather and rain amounts. But its not perfect with evaporation. The float would solve the issue by sending command to EISY that then will trigger program to turn the valve on or off. I can add a maximum daily so there is no chance of overfill. I hope you will (or can soon) support both devices. THANKS in advance

I posted back in 2023 that it would die. Surprized it lasted this long. I put a ticket in just in case. But the developer who did it is gone so someone would have to take it over, I am willing to pay again,.

Installed a new install yesterday- version 0.6.8 My sister setup the cameras and they are 1000 miles away and I am new to blink so maybe this is correct. She setup TWO networks. They both showup as ONLINE and I can arm and disarm so that seems correct. Under the network is the name of the camera in that network. I think she could have done it differently, but Blink worked with her and this is how they set it up. I would have made one network with two cameras under it but thats not the way it was done. The problem is the cameras (one under each of the two networks) show offline. But I can go in the blink app and watch them live. So they are NOT offline. I have rebooted and everything. I think this is a bug, possibly?

So my sister owns the camera and we take turns monitoring my elderly mother. She gets the codes. Everytime I have to reboot the EISY (or even the nodeserver) it needs a new code. There has to be an easier way? I can look into it, but maybe we can have multiple numbers to send the code. Jeff

Since the latest update it keeps failing. I need it for my latest devices. I have a couple logs of the failure Its only letting me attach one due to size. I can email you another if you need it. Kasa_10-30-2025_83403_AM.zip

Yes the new version seems to have fixed it.

it was checked on both EISY and not working. I did two things today. Upgraded to the latest pg3x .22 to .23 then I deleted the nodeserver, reinstalled (Same slot), and checked box. Now its working!!! So don't know if the .23 fixed it or the reinstall. But I had reinstalled before.

I will try tomorrow. Should they show up automatically as new nodes?