Jimbo.Automates

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.

I've reported this to @bpwwer the UI shows 3.0.6 but looking at the install it's actually 3.0.7, but it's tickling another bug and fails to start. Did it actually run for you? Sent from my Pixel 6 Pro using Tapatalk

PG3 3.0.54 fixed that issue. Sent from my Pixel 6 Pro using Tapatalk

I did an install on my dev box and got the same error, so it's not just you @macjeff

Send log Package to @bpwwer Sent from my Pixel 6 Pro using Tapatalk

I upgraded to PG3 3.0.53 and all are working for me.

This is an error because PG3 is not sending the information needed by the NS. Need help from @bpwwer Sent from my Pixel 6 Pro using Tapatalk

Thanks, I've not had a chance to look into any issues, glad it's working. Sent from my Pixel 6 Pro using Tapatalk

3.0.52 is out and others are reporting that fixes these issues. Sent from my Pixel 6 Pro using Tapatalk

There are many posts about this already. We are aware and @bpwwer is looking into it. Sent from my Pixel 6 Pro using Tapatalk

This is a PG3 issue which seems to affect all NS's, will have to wait for more info from @bpwwer