EP40 outdoor double plug stopped being recognized by Plug in

[dbwarner5]

It appears Kasa changed the structure for this outdoor Y plug. They used to have a name for the whole unit (parent) , with subnames  for the two plugs (children). These are my xmas light switches so havent been used since last year.

Testing them today, they only showed in ISY as the main unit with the two plugs greyed out. reflecting pgx.

I since deleted them in the KASA app, and re-added them to the KASA app. Now in the Kasa app, they only show as plugs one and two. There is no longer a name for the "parent".

In pgx, the old three names still showed: main unit, plug 1, plug 2. I was able to delete them by deleting the children first and then the parent node.

After several restarts of hte PI, nothing changes; no recognition of the new plug 1 and 2 nodes, nor the parent name.

I figure they changed the structure somehow  so that the PI no longer recognizes that the children are nodes. so needless to say, ISY will be wrong as long as the PI is wrong.

Any help? 

Thanks.

[Ross]

@dbwarner5 Doug, per @Jimbo.Automates, it appears the Kasa plug-in gets disrupted by the folks at Kasa as there is no official API.  I'm probably not saying that correctly, but that's what I gleaned (I don't speak API or Plug-in).

Do you think one can communicate with Kasa products via a Network Resource?  Or would that have the same issues?

I just bought 4 bulbs in the hopes that I could seamlessly integrate them into my setup; however, perhaps I need to turn to Hue?

Thanks, Ross

 

[Jimbo.Automates]

As stated in the README: This nodeserver relies on a mostly undocumented and unofficially supported local API which of course TP-Link could break at any time, and has in the past, but luckily others figure it out.  They have been changing a lot and others are figuring it out and trying to keep up with the changes, but due to my current work and personal schedule I have not had time to test those changes inside the plugin.  I have started looking into it but no promises on how long it will take to get it work, and I don't even have one of these devices that is breaking so it'll be difficult to work through the issues. I really should have made this plugin subscription based since they seem to be constantly changing the API and breaking everything.    

[Jimbo.Automates]

I had and HS107 and HS300 I wasn't using anymore, so plugged them in and they work as expected.

@dbwarner5 When you deleted them, did you delete them in the PG3 UI by selecting the X to the right of the device in the nodes page?  I did this with mine to confirm they add back and it also worked as expected, but after deleting them all you should restart the plugin.

 

[dbwarner5]

@Jimbo.Automates  Worked!!!  Shows and operates as expected again! Thanks!

[dbwarner5]

@Jimbo.Automates seems like the KASA plugin stopped recognizing the plugs under the parent.  (EP40)

The parent plug shows and I can turn it on and off, but it does nothing to the actual plugs. 

I first deleted the "children" and stopped / restarted the plugin.. It did not re-discover them as it did above. Tried several times.

I then deleted the parent (by hitting the x in the plug in on PGX) and restarted. Now it wont find the parent either. 

I increased the time out to 30 seconds, still no change. 

The last line in each restart under the INFO log is: 2024-12-28 11:48:45.829 Thread-10 (handler_start) udi_interface      ERROR    Controller:handler_start: discover failed

I then found the local IP address of the plug parent and added that manually in config. Restarted PI. It found the parent and the children and had the correct state for each. But I could not control the children. Then the plug in seemed to have gotten caught up in a loop and I had an error "high traffic" whenever I tried to do anything. Could not restart, quit or delete the PI. Had to reboot the EISY. 

Upon Eisy reboot, again it found one of the plug parents and children and reported the correct state, but no control and no reflection of changes that I make thru the kasa app etc. 

Restarted the plug in... it went back into a loop again. Was able to get it to stop so didnt need to reboot EISY this time. 

Deleted the manual IP. Restarted. Again it found one parent with correct states, but no control of parent or children. 

Deleted the PI. Reloaded it into the same slot. Now it isnt finding any of my KASA devices; only node is the controller. 

Any ideas? Thanks

[dbwarner5]

@Jimbo.Automates Here is the latest log after the latest restart. 

Kasa_12-28-2024_123554_PM.zip

it seems to be looking at the wrong network. My network is 192.168.68.xx

024-12-28 12:35:08.289 Thread-9 (handler_start) udi_interface INFO Controller:discover: enter: 172.26.18.255

2024-12-28 12:35:18.291 Thread-10 (run_forever) udi_interface INFO Controller:_discover: Discover.discover(172.26.18.255) done: checking for previously known devices

2024-12-28 12:35:18.291 Thread-9 (handler_start) udi_interface INFO Controller:discover: No manual networks configured

2024-12-28 12:35:18.291 Thread-9 (handler_start) udi_interface INFO Controller:discover: exit

2024-12-28 12:35:18.291 Thread-9 (handler_start) udi_interface INFO Controller:add_manual_devices: No manual devices configured

2024-12-28 12:35:18.292 Thread-9 (handler_start) udi_interface INFO Controller:handler_start: exit Kasa Controller

Edited December 28, 2024 by dbwarner5

[dbwarner5]

I seem to have just remembered that there may be an issue of the EISY being on wifi and this plugin.. I will hook the eisy back up to an ethernet later today and try it then. 

[Jimbo.Automates]

I seem to have just remembered that there may be an issue of the EISY being on wifi and this plugin.. I will hook the eisy back up to an ethernet later today and try it then. 

Oh yes, I forgot that as well! Thanks for the reminder.

Sent from my Pixel 8 Pro using Tapatalk

[Jimbo.Automates]

 

I'll order an eisy so I can test this myself in the future, but try entering your real network address in the config and see if that helps.  The configuration help explains it.

Extra Disovery Networks

By default the node server runs a discover on the default network of the machine running PG3. If the machine has multiple networks, or you have other networks on your LAN you can run discover on those networks e.g. 192.162.4.255.