Jimbo.Automates

Thanks Guys for the HS200 and KP125. The good news is that I have released 3.2.0 to Beta, but the bad news is that it requires an update to the python-kasa library I use. So once that library is released you can test. I'll be heading out of town this week but will keep an eye on it and let you know when you can give it a try. Please do not install this beta for production, there were a lot of changes and I've only done minimal testing.

Thanks, I added a black on to the list since it was cheaper. Personally I don't use many Kasa devices since they only update when polled, not push. Hopefully once matter is all working we can just use their matter supported devices. Sent from my Pixel 8 Pro using Tapatalk

Easiest way is with using a Simple shareable notifications where you use ${sys.node.#.name} ${sys.node.#.GV0} For Physical Status, or this for Logical Status ${sys.node.#.name} ${sys.node.#.ST}

When this happens please Download Log Package from the elk log page in the PG3 UI and PM it to me. Sent from my Pixel 8 Pro using Tapatalk

Because the Elk module is not supported on Polisy or Eisy, it's a PG3 Plugin now. Did you go to the PG3 -> Elk -> Nodes page as I suggested? No need to build a table, just find the one you want and hit the copy icon on the right. Yes, the module is no longer supported.

Yes, it's always best to post in the forum first so you get the help of the community and help others in the future. Those elk references are for the old elk module which isn't available in eisy. The elk plugin substitutions are shown on the PG3 UI under the elk nodes page. I can provide more details if necessary when at a computer. Some more in is in my document https://www.jimboautomates.com/pg3-node-servers If that doesn't provide the information you need then I'll try to add it. Sent from my Pixel 8 Pro using Tapatalk

I have confirmed all my current Kasa devices work as expected. Those of you that have Kasa devices which are not currently working, please checkout my Amazon Wish List and if you see your device then grant the wish if you want it supported. No guarantee on getting it right away, but I will try my best. If your device is not in the list, please post link in this thread and I will add it. This plugin is so inexpensive I can't justify purchasing all the different devices unless I decide to charge extra for the next upgrade, which is an option I will consider.

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.

When you say no errors or warnings in the log files, do you mean the plugin log as seen with the PG3 UI?

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.

Yes, that is a ELK limitation. I guess I could have the plugin do a Disarm if armed when you Arm... I created an issue https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/109

Sorry, no idea what the issue is. Please open Admin Console, select the "Elk Controller", click the "Update Profile". Then in the PG3 UI in the ELk -> Details -> Log -> Download Log Package and PM that file to me. Then in the Admin Console -> Configuration -> Restart IoX. Once it has restarted open Admin Console again and see if that fixed it.

Yes, it's an issue on their side https://groups.google.com/u/2/g/wireless-sensor-tags Sent from my Pixel 8 Pro using Tapatalk

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. And 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 node server. If you feel you wasted your money I'm sure you can ask for a refund and the license will be removed.

No that wouldn't be an issue. Sorry, I've not had a chance to dig in deeper. Sent from my Pixel 8 Pro using Tapatalk

Sorry, been traveling and busy. The Alarm-Elk is the folder I store all the elk nodes in. I'll try to take a look on my home computer when I have a chance. Submitting a support ticket likely won't help since they'll just ask me to take a look. Sent from my Pixel 8 Pro using Tapatalk

Did you install the PG3x ELK plugin and configure it? Sent from my Pixel 8 Pro using Tapatalk

Turn off smart home and away mode in the ecobee app under eco+ settings Sent from my Pixel 8 Pro using Tapatalk

Yes, works fine for me. 'Home' is my 'Area 1'.

It should be there, I'll look into it. Sent from my Pixel 8 Pro using Tapatalk

Awesome, glad it worked! Hope you are happy with the elk plugin, I know converting from the old method can be painful. Sent from my Pixel 8 Pro using Tapatalk

There have been issues with Python installs during the updates. Please submit a support ticket and they'll get you fixed. I've not seen anyone with this issue post the solution and previously @Michel Kohanim just mentioned it was a Python install issue. Sent from my Pixel 8 Pro using Tapatalk

The install.log is in your screenshot when you show the listing of the plugin directory. Sent from my Pixel 8 Pro using Tapatalk

Probably a system issue, can you cat the install.log? Are you on the latest versions? Try "Upgrade Packges" in Admin Console, and when complete reboot, then delete and install Elk plugin again. If you are on the latest, then probably have to submit a support ticket, we have seen this issue before.

I'm not sure it's possible, I'd have to look. As mentioned in the documentation, there is no official API for Kasa devices, a bunch of smart people have reverse engineered the communication and released a library that I reference. The communication can change at any time and break that library, and in fact new devices use different methods, so they have been releasing changes to their library to try and keep up. I plan to update the plugin to the new version of this library now that it seems to have stabilized. Sent from my Pixel 8 Pro using Tapatalk