Jimbo.Automates

Google Home is showing my devices as offline for both homes. I can login to portal and send spokens which is successful, but the Home app still shows all offline.

The Polyglot Version 3 Node server for ELK Security Version 3.7.0 is released. See the Release Notes The 3.7.0 release added support for Export of ELK Lights see Light Node and Configuring the ELK Node Server. The 3.8.0 release added support for light_method=ELKALL to import all ELK Lights into the ISY as a light node. 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.

This error in the log can be ignored, I need to fix that. It's just printing the defaults: 2023-04-06 15:10:15,992 Thread-3 udi_interface ERROR CamectController:customNS_handler: Got key=nsdata which is not in data={ "user": "", "password": "" }, In that configuration page from your pic it should show these instructions: https://github.com/UniversalDevicesInc-PG3/udi-poly-Camect/blob/main/configdoc.md and I don't see in your pic where you have added a Camect Host? When adding new cameras, you should just be able to hit Discover in the PG3 UI or In the AC.

LOL, that video is awesome! Love it.

Can the notice show the System name (alias in Portal) along with the UUID? I just got a notice and had to go look which one it was associated with.

I would caution people on this recommendation. The Kasa API is not supported by TP-Link so it can break at any time, it has been reverse engineered and the developers keep up with changes as much as possible, but TP-Link could decide to lock it up at any point. That said, I do like my Kasa bulbs, LED strips, Outlets & Power Strips.

Glad you got it working, feel free to post your experience with it and let me know if you have suggestions are questions. There are very few using this NS.

Sorry, I should add this to the instructions: Please open https://local.home.camect.com/ in browser, sign in as admin and accept TOS before you proceed.

Thanks, yes I saw that error, it happens when you have no lights configured in the Elk. You can safely ignore until I can get a new rele out. Sent from my Pixel 6 Pro using Tapatalk

So is the current method for Elk<->ISY Lighting satisfactory our is there still a need to do export/import ? Please comment on the above post.

So is the current method satisfactory our is there still a need to do export/import ?

The Polyglot Version 3 Node server for ELK Security Version 3.6.5 is released. See the Release Notes If you are running 3.6.0 or greater then you need to update or may experience crashes.

Nevermind @garybixler I think I found the error, I'll have a new release soon.

There is an error, but it must have happened previous day because it's not in the log. I can tell because NS keeps printing this: 2023-04-01 08:03:46,526 Thread-232 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete So the initial sync didn't complete. This can also happen if ElkRP is connected. I need to look into a way to allow this to be detected on the ISY side... Please restart NS and when it completes PM me the log package.

Sorry, that's on my list for today. Had to fix a crash first and didn't have time to investigate that last night. Sent from my Pixel 6 Pro using Tapatalk

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/