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.

Edited June 26, 20232 yr by Jimbo.Automates
Change to 3.3.4

I tried restarting the Node server several times and it does not update and is stuck on 3.2.4. Even restarted PG3.

 

 

 

Hi @JimboAutomates,  same here, stuck at 3.2.4

Sent logs to your email.

Thanks!

Tim

In my case, the node served updated but the version number never changed. You can check this by restarting and checking the log. The log in my case showed the updated version starting.

It's also happening with the Elk node server.

Good catch @DennisC, thank you.  @JimboAutomates, as Dennis pointed out, my log indicated 3.3.0 as well.

Thanks!

INFO Controller:handler_start: Started Notification Node server 3.3.0

The version info is stored in PG3 database so need help from @bpwwer

Sent from my Pixel 6 Pro using Tapatalk

I checked and confirm I do have the new version and is working good even though the reported version is incorrect  

 

Edited April 2, 20223 yr by brians

@JimboAutomatesI just noticed that the predefined short messages did not appear to be working after the update. I discovered that I had to go edit the programs that use those and just update the line that had Send. Seems that adding in the Send Sys Short option broke a reference in existing programs that were set to Send and showed nothing and did not send.

 

 

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.

 

52 minutes ago, JimboAutomates said:

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.

 

The program was not yellow, the program would run fine because in the same program it emails me besides sending me a pushover notification. I don't have an actual screenshot because I fixed the few that were an issue, but the line in the program where it has the Send Message didn't show anything.

Here is a current screenshot of one of the programs and where I have highlighted in yellow it was just blank until I selected the line and update, save program. The reason I discovered this is because I was getting emails but no phushover notifications. I am moving everything away from the old messages... for one it is a big process if need to change anything - restart Node server, restart IoP etc. Other methods are instant and support variables.

 

8 minutes ago, brians said:

The program was not yellow, the program would run fine because in the same program it emails me besides sending me a pushover notification. I don't have an actual screenshot because I fixed the few that were an issue, but the line in the program where it has the Send Message didn't show anything.

Here is a current screenshot of one of the programs and where I have highlighted in yellow it was just blank until I selected the line and update, save program. The reason I discovered this is because I was getting emails but no phushover notifications. I am moving everything away from the old messages... for one it is a big process if need to change anything - restart Node server, restart IoP etc. Other methods are instant and support variables.

 

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...

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.

 

not working for me. I deleted and reinstalled the Node server (in same slot) but it remains disconnected :

 

Notification_4-3-2022_82328_PM.zip

Edited April 4, 20223 yr by asbril

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

 

20 minutes ago, JimboAutomates said:

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

 

Thanks. That did the job !

1 hour ago, asbril said:

Thanks. That did the job !

Unfortunately, there still is an issue and tomorrow I will post the log, but this is where thens gets stuck :

2022-04-03 21:40:27,223 Thread-6 udi_interface WARNING Controller:handler_config_done: Waiting for all handlers to complete start=True params=True data=False typed_data=None cnt=2

I just tried... the send sys short with params seems to work good so far but have only tried one... 

Gonna start converting to that method now!

 

Edited April 4, 20223 yr by brians

24 minutes ago, asbril said:

Unfortunately, there still is an issue and tomorrow I will post the log, but this is where thens gets stuck :

2022-04-03 21:40:27,223 Thread-6 udi_interface WARNING Controller:handler_config_done: Waiting for all handlers to complete start=True params=True data=False typed_data=None cnt=2

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.

23 minutes ago, brians said:

I just tried... the send sys short with params seems to work good so far but have only tried one... 

Gonna start converting to that method now!

 

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

Yes and the customizations can be used for email also without making a new one... just make the subject suitable for pushover and it ignores the body which can be more detailed in the email. I only do this for real critical things like leaks and alarms.

11 minutes ago, brians said:

Yes and the customizations can be used for email also without making a new one... just make the subject suitable for pushover and it ignores the body which can be more detailed in the email. I only do this for real critical things like leaks and alarms.

Nice trick, didn't think of that.

1 hour ago, asbril said:

Unfortunately, there still is an issue and tomorrow I will post the log, but this is where thens gets stuck :

2022-04-03 21:40:27,223 Thread-6 udi_interface WARNING Controller:handler_config_done: Waiting for all handlers to complete start=True params=True data=False typed_data=None cnt=2

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.

8 hours ago, JimboAutomates said:

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.

Thanks so much.   I had not realized that I had added  a(n empty) space in Telegram and deleted it.

That resolved the issue. However I forgot how I previously used Pushover in my programs. What I did now does indeed push a message to Pushover App on my Iphone, but as "unknown"  and "Undefined message 0" :

Can you please remind me how to do it correctly ?

p.s. When restarting the ns in PG3, it remains on 3.3.1

 

1 minute ago, asbril said:

Thanks so much.   I had not realized that I had added  a(n empty) space in Telegram and deleted it.

That resolved the issue. However I forgot how I previously used Pushover in my programs. What I did now does indeed push a message to Pushover App on my Iphone, but as "unknown"  and "Undefined message 0" :

Can you please remind me how to do it correctly ?

p.s. When restarting the ns in PG3, it remains on 3.3.1

 

Same issue here.  Restarted and its on 3.3.1 not 3.3.2 but the UPDATE needed notice went away.

1 hour ago, macjeff said:

 

 

Same issue here.  Restarted and its on 3.3.1 not 3.3.2 but the UPDATE needed notice went away.

Same issue with me, 3.3.2 listed in store will not load.