PG3 Notification Node Server 3.4.1 has been released to beta with support for ISY Portal -> UD Mobile notifications.

I would appreciate any existing users of the node server to give this a try, please install in a new slot and test it out. Do not replace your existing version in case there are issues, once it seems stable I will release to the production store.

 

See the README for more information, including information on moving from PG2.

See the Release Notes for more information.

Please reply on this thread you experiences or issues.  Thanks to @Javi and @bmercier for adding this support to UD Mobile and the Portal!

Edited May 21, 20232 yr by Jimbo.Automates
Change to 3.4.3

Never mind, there is an issue with running two copies at once since the REST server port is hardcoded.  I'll need to fix that.

 

PG3 Notification Node Server 3.4.1 released to Beta (non-production) store.

You can now change the REST Server Port in the configuration, and setting if set to nothing then the REST Server will not be started.

 

 

@JimboAutomates

The version in non-production store is asking for me to purchase it again. Please confirm if this will actually charge me again.

 

 

Yes, it will charge you again.  

The current PG3 release treats every node server as unique, with a unique id.  Thus even though it may be the same name in two different stores, they are treated as different node servers.

The next release of PG3 will change this and allow the same node server ID to be used in different stores so you can purchase a non-production version and then use the same license to install the production version.  But this change is still a ways off.

Ok, I will hold off testing until there is a resolution for the payment.

 

Brian

 

Ok, I was hoping they could install as trial in a new slot for now?

 

I believe all of the purchase options work for non-production. So installing a trial version in a new slot should work and be a separate license from anything previously installed (trial or other) from the production store.

You could even make the trial period longer or shorter and only have the trial option available. 

Thanks @bpwwer

I removed purchase option, and trial is 1 month so hopefully it should work for @brians now.

 

@JimboAutomates

Ok I will give it a try later this afternoon.

 

PG3 Notification Node Server 3.4.2 released to Beta (non-production) store.  See the Release Notes for more information.

On startup it will set the rest server port to 8199, but that will fail if you have the production version running, so change the port number on this one to something else like 8198, save it, and restart.

 

Edited June 29, 20223 yr by JimboAutomates

@JimboAutomates

I installed it and setup the api key, changed port.

However, in AC, the Service Node under Notification Controller does not refresh the right pane when clicking on it... and uses the information from last one clicked... here is an example... where I clicked on Ecobee and then the Service ISYPortal UD

 

 

I think this is also related that in programs I cannot see the service node like my pushover one.

I would expect it to be called Notification Controller / Service UD ISYPortal

 

 

@brians Did you restart the AC after the node server was installed and startup complete?

1 hour ago, JimboAutomates said:

@brians Did you restart the AC after the node server was installed and startup complete?

Yes I did. I even removed the node and added again. 

Ok, it must have an error, please downloas log package and PM that to me.

PG3 Notification Node Server 3.4.3 released to Beta (non-production) store.  See the Release Notes for more information.

On startup it will set the rest server port to 8199, but that will fail if you have the production version running, so change the port number on this one to something else like 8198, save it, add your ISY Portal node in the configuration and restart.  

Make sure to wait until it has completed startup to open the Admin Console.  @brians issue was resolved after waiting then reopening AC.

 

@JimboAutomates I've installed the beta version. I'm attempting to replicate the short custom content example you provide in on github. I'm running into errors both with Pushover and UD Mobile. Neither is getting over to my phone.

I'll send you the Node server log via PM.

17 minutes ago, DaveStLou said:

@JimboAutomates I've installed the beta version. I'm attempting to replicate the short custom content example you provide in on github. I'm running into errors both with Pushover and UD Mobile. Neither is getting over to my phone.

I'll send you the Node server log via PM.

That's odd... I can see the bug, but not sure why it's not happening to me.  I'll try and test and fix tonight.

Good news. I got it working for both Pushover and UD Mobile by using Send Sys Short with Parmas instead of the format used in your example. I'll do some more testing to see if I can figure out the difference.

14 minutes ago, DaveStLou said:

Good news. I got it working for both Pushover and UD Mobile by using Send Sys Short with Parmas instead of the format used in your example. I'll do some more testing to see if I can figure out the difference.

Yes, send sys short with params is the best way, and probably all I tested.

On 7/1/2022 at 11:15 AM, DaveStLou said:

Good news. I got it working for both Pushover and UD Mobile by using Send Sys Short with Parmas instead of the format used in your example. I'll do some more testing to see if I can figure out the difference.

This issue is fixed, and it is now released to production as 3.4.4.  Let me know if you have any further issues.

 

Edited July 4, 20223 yr by JimboAutomates