Jimbo.Automates

Those warnings are ok. The doc link I pointed to was showing the settings in an Area Node https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#area-node

I confirmed mine to look correct which I restarted last night. Notification(5) Current Status: Connected Current Version: 3.3.0 [Production] Time Started: Mar 31, 2022, 8:55:19 PM Uptime: 10 Hour(s) 30 Minute(s) 52 Second(s) ELK(4) Current Status: Connected Current Version: 3.2.0 [Production] Time Started: Mar 31, 2022, 8:30:50 PM Uptime: 10 Hour(s) 31 Minute(s) 54 Second(s)

That's odd, both looked correct for me. If you force refresh the browser does that fix it? Sent from my Pixel 6 Pro using Tapatalk

IMPORTANT: This release uses a new feature only available with ISY On Polisy 5.4.2. It should still function on older versions, but there may be issues loading the profile on older versions which may result in programs referencing the service nodes have issues. The Polyglot Version 3 Notification Node server 3.3.4 is released. See the README for more information, including information on moving from PG2. See the Release Notes for more information. Special thank you to @Chris Jahn for adding a needed feature and working out the best way to handle it.

IMPORTANT: This release uses a new feature only available with ISY On Polisy 5.4.2. It should still function on older versions, but there may be issues loading the profile on older versions which will make programs using at least the Area nodes have issues. The Polyglot Version 3 Node server for ELK Security Version 3.2.7 is released. Send messages to keypads! See https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#area-node -> Display Message Special thank you to @Chris Jahn for adding a needed feature and working out the best way to handle it. See the README for more information, including information on moving from PG2. The Release Notes are also available. If you have issues are requests please check PG3 ELK Github issues to see it has already been listed:

They can be yes, with ${sys.program.#.name} and ${sys.node.#.ST) https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Sent from my Pixel 6 Pro using Tapatalk

Should happen on a restart of the node server. Sent from my Pixel 6 Pro using Tapatalk

Yes, the custom content would contain the info about what it wants to post about the Ecobee node server. Sent from my Pixel 6 Pro using Tapatalk

You set the values for device, priorty, sound ... on the service node https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#service-nodes as shown the documentation I already referenced https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#short-custom-content which shows this picture https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/pics/Program_NotifyTestSysShort.png

@mbking I have it almost working for ELK, hopefully release soon @brians Thanks. Hopefully everyone who isn't responding feels the same Also, you can use Variables and any other system info in Custom Content, the only thing you loose is shorter length, and ability to set other params like device, priorty, sound... but that can always be done from the calling program. I was also thinking to add a single program command which could send all params in one call.

I will have a release of the ELK NS soon which will support sending text to keypads, but it will have the same issue as mentioned here: https://forum.universal-devices.com/topic/35543-pg3-notification-node-server-330-question/#comment-332635 Please let me know your thoughts on pushing out this update, I hate to break anyone that is currently relying on it.

That's odd, I know I have had ElkRP open when NS is also connected.

It's downloading the AC from the ISY in LAN mode, so why is it necessary to clear the java cache for LAN and not Cloud? Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 Notification Node server 3.3.0 is ready but not yet released. This version uses a feature that is only available with ISY On Polisy 5.4.2 which was just released today so I am going to hold off and ask if anyone has an issue if I release it. I'm not sure how it will act on older ISY versions. The problem is if I release it and PG3 restarts it will automatically upgrade. I will try to test on my production machine which is not yet upgraded, but in the meantime I want to ask if everyone using it was ok with forcing ISY 5.4.2? Please comment below. It has a really nice new feature: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#short-custom-content

Install on my dev Polisy, started ISY Launcher, select Admin Console -> LAN and it loads up 5.4.1 and I get error message that it's not compatible with 5.4.2? Edit: Works fine loading from Cloud.

Change log level, restart NS then it should work, then change log level back to your preference. Sent from my Pixel 6 Pro using Tapatalk

@Bumbershoot change the log level then restart and change it back to your preference. Sent from my Pixel 6 Pro using Tapatalk

Fixed. And Bob will add it to the NS page at some point.

I try to keep an issue for each thing that needs to be fixed because it's impossible to parse thru posts for all NS's to try and remember what needs to be done.

Yep, there's an issue already for that https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/4 Sent from my Pixel 6 Pro using Tapatalk

There should not be errors in NS logs... This error was the issue that 3.0.54 was supposed to fix. Try changing the log level to something different. like Debug, then restart and hopefully it works. Then change level back to warning or error.

It is working fine for me. Any errors in the log? Sent from my Pixel 6 Pro using Tapatalk

As I said, HarmonyHub does upgrade, it's just an issue that it doesn't actually see the new version and tries to upgrade on each restart, and UI shows old version. Sent from my Pixel 6 Pro using Tapatalk

Yes, it's one device.

It does not scan the network, it sends out discover packets which the devices respond to. I needed this NS because I really liked their power strips and the ability control each plug on them, and then added light strips and some color bulbs. But, I would not personally have my home relying on these everywhere due to the caveat mentioned in the README: This Node server 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.