Jimbo.Automates

Nice trick, didn't think of that.

Awesome! Yes, I'm converting many of mine and I'm amazed how many can be converted to share a few different Custom Contents! Also, for everyone's info, I added verbiage to the docs: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#service-nodes

Ya, that's not good, PM or email me the log package. That usually means there was an error prior to that. But, if that's the last warning then you are ok, it will continue to print those every second until it times out after 60 seconds. I probably should print a warning when it's ok, or just don't print warnings unless it times out. It's there because early on PG3 had issues with handlers but its pretty stable now.

Yes already provided that info to @Javi Sent from my Pixel 6 Pro using Tapatalk

That's something @bpwwer will have to answer. Sent from my Pixel 6 Pro using Tapatalk

I had the same error yesterday that I see in your log: 2022-04-03 20:22:46,838 MQTT udi_interface.interface ERROR interface:_connect: MQTT Failed to connect, invalid identifier Which I discussed with @bpwwer but he wasn't sure why that would have happened. Please restart PG3: sudo service pg3 restart

This is fixed in 3.2.2, but there is still an issue which I think will require an update to UD Mobile. I apologize to @Javi that I didn't give him access to this to test with the new editor that Chris added before this was released.

PG3 Notification node server 3.3.1 released See the Release Notes for more information. As mentioned in the release notes, this fixes the problem @brians found above, and sorry @brians you will have to edit your programs again and save them again, if you haven't already switched over to sys short messages.

Very sorry about this, it's not what I mentioned before, it's completely my fault. This changed from Send to Send Message so the programs do have to be edited. Now the question is, do I put it back so others don't break or leave it as is and just notify everyone... I would also suggest everyone move away from those messages and use the Sys Short Messages, and I'm about to release a new version that makes it easier to send them with one line in a program, but need to decide if put Send back to what it was or leave it...

Good catch @brians I didn't think about that possibility, this sounds like an ISY issue that happens when a device definition is modified, so PG updates the device on the ISY which invalidates programs that reference the device. I've talked to @Chris Jahn about this in the past but I'm not sure if we ever resolved it. Was the program yellow, or it would the program just not automatically run, or the program would run but the notification didn't happen? I currently am not using any old user defined short messages any more so I didn't notice this.

Does this happen on sync? Or when you open that node in UD Mobile? Sent from my Pixel 6 Pro using Tapatalk

Yes, probably in a complex cmdp structure I'll send you the nodedef when I get home. Sent from my Pixel 6 Pro using Tapatalk

The version info is stored in PG3 database so need help from @bpwwer Sent from my Pixel 6 Pro using Tapatalk

PG3 ELK node server 3.2.1 released: Release Notes

The $ and { do not count, what counts is what they resolve to. The 16 character limit is on the ELK, nothing I can do about it. For illegal characters like the degree, I though the API I was using already took care of that, but sounds like it's not. I'll put in a fix when I get time, but for now you can add .raw to not get the formatted value.

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.