Jimbo.Automates

A lot of people have converted to PG3x since it was released a long time ago, I did 3 systems with no problems. Submit a ticket and someone can take a look. Sent from my Pixel 8 Pro using Tapatalk

Looks like you are still on PG3 not PG3x. This is a know issue with PG3 on Polisy where files are not properly created during an install. The issue was never resolved since it no longer happens with PG3x. See "Upgrading to PG3x" at https://wiki.universal-devices.com/Polisy:User_Guide

I see. So you should never need to do anything in the plugins configuration menu for PG3 plugins, and editing and or saving changes can break the plugin. I wish that could be disabled for PG3 plugins... Sent from my Pixel 8 Pro using Tapatalk

That's odd that 1,3 doesn't work, that should mean 1 and 3, where 1-3 means 1 2 and 3. I can look into that. The library supports 208 zones, so it should work. A zone will be added if it is not disabled, and its area is included in the areas list. Set the Log Level to debug, restart the node server and after it completes the startup download log package and PM it to me with the number and name of a zone you expect to be added that isn't showing up. The node server configuration page help shows the format of the host as ipaddress:port where port is 2101. and you must specify a proper user_code which is only needed to arm/disarm the system.

Looks like I never upgraded telegram to use the new method, it still uses the old method where you set the custom message on the controller then send it from the service node. I'll try to add the new method soon.

Thanks Javi, didn't think about that. But the node server does support multiple portal accounts by adding separate "UD Portal" service nodes. The UD Mobile node doesn't support multiple portal accounts.

Sorry, I can't see how this could happen. I'll try to look into it and get back to you.

In UDM the only option is called group. This is a group I call JimsPhone which contains my current phone. Sent from my Pixel 8 Pro using Tapatalk

Actually, it is recommended to only use Groups, put the new phone in a group and send to the group. That way when you get a new phone you just have to edit the group.

Restart the Notification plugin, then after a couple minutes resync UDM. Sent from my Pixel 8 Pro using Tapatalk

Those errors are PG3 issues that @bmercier is aware of. Sent from my Pixel 8 Pro using Tapatalk

I wasn't saying the connect/disconnect was related to IoX being busy, only commenting on the error/warnings you posted, which I don't think are related to the same issue. You must be a light sleeper if the watch can wake you up [emoji16] mine is always on DND. Sent from my Pixel 8 Pro using Tapatalk

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