Jimbo.Automates

That error is a known PG3 issue that hasn't been fixed yet. The 2 warnings are ok, typically happens when your IoX is to busy to respond.

The log shows a PG3x error, please submit a support ticket and include those log packages and information. 2024-01-06 19:34:06,657 Thread-34461 udi_interface.interface CRITICAL interface:send_thread: Message send thread aborting: Message publish failed: The client is not currently connected.

If you can grab a log package soon after it happens then please PM it to me. Sent from my Pixel 8 Pro using Tapatalk

I've pinged @bmercier and will let you know if anything comes of it or if he has a better solution. Sent from my Pixel 8 Pro using Tapatalk

Sorry, I did review the logs but nothing valuable. The problem is if it happens right before or at midnight, the logs are also rolled over at midnight so if there was an error it is missed. I'll talk to Benoit to see if we can do something about it.

As mentioned in the first paragraph of the README https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md 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 broken it with the newer devices... And more about TAPO here https://forum.universal-devices.com/topic/42251-tp-link-kasa-and-tapo-support/#comment-374057 There are people working to try and get this working and progress is being made. I'm not up-to-date on all the issues, but some of the newer devices support Matter, so hopefully ISY can eventually talk to them directly. Personally I would not use Kasa for many things, because of these issue, but also because they do not provide real time updates, the node server has to "poll" them for updates. I like their power strips, light strips, and bulbs, but do not have any switches.

/index.php?/topic/42729-Another-problem-with-no-devices-found#entry377345 Sent from my Pixel 8 Pro using Tapatalk

It is mentioned on the release page: IMPORTANT: You must have the latest updates released 12/03/2023 for this to install. If you are not sure, please 'Update Modules' and reboot when complete before installing.

Great, and thank you for the fix. Much appreciated.

For #2 add desired outputs in PG3 Elk Plugin configuration. I really wish I'd have fished wires to my garage door openers when we installed the elk and ran wires everywhere else... Sent from my Pixel 8 Pro using Tapatalk

It's in the PG3 UI, but it's updated in github as well now. Thanks.

Yes, this is the same issue reported and fixed in the other thread. Sorry I misspoke upgrade vs. update. But good you figured it out. ModuleNotFoundError: No module named 'kasa' Sent from my Pixel 8 Pro using Tapatalk

Yes, this issue was resolved. Make sure you have recently run an update packages so you have the latest release then reinstall the nodeserver. Sent from my Pixel 8 Pro using Tapatalk

The PG3 Node server for ELK Security Version 3.10.7 is released. See the Release Notes

It shouldn't matter, but you'll have to submit a bug report to UDI for @Chris Jahn and @Michel Kohanim to take a look Sent from my Pixel 8 Pro using Tapatalk

I have no control of this, it is handled by the Admin Console. Try restarting the AC. Sent from my Pixel 8 Pro using Tapatalk

Yes, I did, which is why I said it you still want/need Telegram then try to set it up again and we can see what the issue was.

I was able to fix this so 3.0.9 should now be available. Sorry for the confusion.

I figured out how to update it, so version is back to 3.0.6, please re-install in same slot to fix it. I'll enjoy Christmas better knowing that I didn't break everyone

So sorry, I just realized it was broken today. I accidentally released Harmony plugin code into Hueemulator release and I am traveling so can't fix it. I'll see if we can get it fixed. There's no rollback ability in PG3. Sent from my Pixel 8 Pro using Tapatalk

Sorry for the delay, I must have missed your post while I was traveling. Yes, the Telegram service is tricky to setup, I'd like to make it cleaner in the future when I have some time. If you really want/need Telegram then try to set it up again and PM me the file from 'Download Log Package' if you encounter issues.

Yes, "Send Sys Custom With Params" is the current recommended method to stick with, all others are legacy.

This is likely a configuration issue, but I created an issue to fix in the future: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/53

Issue created: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/52 Will look into it after the holidays.

Sorry for the delay, I am traveling for the holiday. I created an issue https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/21 But it is also have problems communicating with many of your devices: 2023-12-21 10:55:55,534 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.170 trying to connect to 10.100.100.170 2023-12-21 10:56:00,538 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.169 trying to connect to 10.100.100.169 2023-12-21 10:56:05,548 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.168 trying to connect to 10.100.100.168 2023-12-21 10:56:10,553 Thread-11 udi_interface ERROR Controller:_add_manual_devices: Timed out getting discovery response for 10.100.100.160 trying to connect to 10.100.100.160