Jimbo.Automates

Well, glad that resolved it. The only explanation I can think of is that the IP addresses of your Kasa devices changed so the attic light is using the IP address of the hallway lights at the time the Kasa nodeserver was started up. The NS tries to realize this happens and fixes its references but it's possible that logic is not correct. You could send me a log package, but if logging is not in debug mode then I can't see the issue. Ideally you should probably reserve IP addresses for all Kasa devices in your DHCP server. Sent from my Pixel 6 Pro using Tapatalk

Did you click refresh store? It only automatically updates occasionally. Sent from my Pixel 6 Pro using Tapatalk

I never said we shouldn't be able to restart a NS from the ISY. I leave that up to @bpwwer since he is the developer of that code, and I respect his thoughts. I merely pointed out the first thing to do is send a report to the author. Nothing we can do if the author is not responding, most of us have real jobs and do this on the side and occasionally go off line for extended periods as well.

Kasa PG3 NS 3.0.21 released with small bug fix https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md#release-notes Thanks to @TRION for sending the log package.

Ok, will take a look but nothing related to zones changed in this release. Sent from my Pixel 6 Pro using Tapatalk

As I mentioned Go to the node server page -> Log -> Download Log Package But, if you were not on 3.2.20 of the Kasa node server, then there was a know issue that was fixed last week.

Takes less time to download log package and send it then it did to create all these posts. Sent from my Pixel 6 Pro using Tapatalk

Yes, I've noticed that as well, might be a PG3 bug, I need to look into it further. Yes, I should change the Icons, but all tasks and counters defined in ElkRP are pulled across. I could add configuration options like I have for Area's and Outputs that allows you to define which tasks and counters were tracked in the NS.

As I said, there can be no confidence it will be the last if you don't send me a Log Package. I've only heard one issue for Kasa causing a crash in the last 5 months and it was fixed within a week because I was given a Log Package.

If a node server stops working you should 'Download Log Package' and send that in a PM to the developer to debug otherwise the issues will never get fixed. Version 3.2.20 of the Kasa nodeserver fixed a bug that was causing a crash: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md#release-notes For each nodeserver there is a sub-forum you should monitor and post there if you see issues: https://forum.universal-devices.com/forum/313-kasa-tp-link/

You'll probably get help here, but a good place is also here https://www.elkproducts.com/forums/forum/m1-support-forum/

Fixed

I don't see how ro create a program in UD Mobile that triggers from a variable change. For the "if" the only choices are schedule, control, status, parentheses and comment.

The Polyglot Version 3 Node server for ELK Security Version 3.6.5 is released. See the Release Notes This release added support for ELK Lights see Light Node. Since releasing and testing in my production environment I realize there is an issue since ElkRP has a 12 character limit for device names. If your device name is longer you are forced to use the node address which works perfectly but visually is not ideal in the ELk interface. Please provide feedback on this if you use this feature. This may necessitate adding the ability to export/import which is a fair amount of work. See the README for more information, including information on moving from PG2. If you have issues or requests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes.

Yes, the version issue is understood and no reason to keep restarting mode servers just for that issue. Bob and I had discussed that issue before you reported it, and as he mentioned in another post it is fixed in the new interface but will take a while to propagate to all installations. Sent from my Pixel 6 Pro using Tapatalk

This looks similar to an issue that @bpwwer is looking into. Sent from my Pixel 6 Pro using Tapatalk

It's really hard to read a log inserted directly in a post, please edit the post and inset the log as code using the "<>" icon in the forum, or just attach it. May need help from @bpwwer to debug this.

They would not. There is nothing the NS can do to control X10 devices, it can only happen thru the ISY.

It's been out. Refresh your store. Sent from my Pixel 6 Pro using Tapatalk

Should be fixed in 3.0.20, the error still shows until python-kasa is fixed, but it doesn't cause the NS to crash.

The Polyglot Version 3 Node Server for Kasa TP-Link 3.0.21 is released. See the README for more information, including information on moving from PG2. The Release Notes are also available.

Having Lights configured in ElkRP2 that do not exist in ISY will not cause an issue, so not sure why I need a toggle to enable this?

This looks like a bug in a library I reference, I've submitted a bug report to them. I can add a trap for if they don't fix it soon.

New discussion here:

New discussion here: