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!