Jimbo.Automates

In the AC you can test the node by turning it "On", same with a program. Just make sure you close and re-open the AC after the node was added. BTW, don't you ever one to turn the device off? If so, I would create a node called BRSensibo then define an On and Off Event.

There are 2 examples showing the usage, one is the "old" way setting them on the controller: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#send-sys-short and the other is the new way using one program line on the service node: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#send-sys-short-with-params You can put any ${sys.node.somenode.name} ${sys.node.somenode.driver} where the somenode is the node address and driver is the node driver that shoes the data you want as documented here https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables

I'm the PG3 UI under the node server log page set logging to debug and restart, and PM me the log package. It makes no sense that nodes page is empty, you should at least see a controller after installing. Sent from my Pixel 6 Pro using Tapatalk

Thanks all. @asbril I added a documentation example similar to what I described to you above https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#send-sys-short-with-params

I just made a minor change and released 3.3.3, I went to PG3 on my production machine, clicked restart and once it connected the version updated to 3.3.3 as expected. Bob also was unable to see the issue on his machine this morning. So anyone still having the issue with an update not showing properly, please describe in detail what you did and what you did not see and start a new thread so @bpwwer can help.

You have mixed together 2 different methods of sending a notification. The How it Works describes these as "messages" and "notify nodes", they are used individually, not together. The first line in your then sets the "message" to 'Bad Weather', then next three lines set params on a 'notify node' then the last line sends a message on the pushover service. The best way to do this now is to create a Custom Content in the Admin Console which can contain the drivers from the NOAA Weather node to tell you the Alert and Wind speed in the message. Then the program will just have one line in the 'Then' section.

Please stop saying the new version does not show in the PG3 UI after restarting. I've already said: The version info is stored in PG3 database so need help from @bpwwer so I'm sure he will look into when he has time. Sent from my Pixel 6 Pro using Tapatalk

Thanks for sending the log, pushed 3.3.2 to fix the issue which happens if you add a Telegram node, but don't give it a name. You should delete it in the config, but at least now the NS won't crash when it happens.

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)