Jimbo.Automates

The ST doesn't come fr the API, it is handled my PG3. With the previous logs I posted the excerpts of node server and PG3 sending the 1 to the ISY. I'll review these new logs.

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

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.

In PG3 UI select non production store and install it. If you have issues ask on the Notification node server forum post about it.

Yes, that's why it confused me that they are unique based on sound because customizing sounds is one of the options. @DaveStLou are you using the notification Node server? Would like a couple more testers to confirm beta is good before I release.

If users want to enable/disable showing date/time, but seems important enough to always show it. Also, when I mark one as read in the app, would be nice to close the notification if possible. Also, would be nice to have a mark-all-as-read button.

I see you edit a device and add it to the group, could you also make it so I can open the group and see all devices and turn them on or off there? Sent from my Pixel 6 Pro using Tapatalk

Javi, When you pull down and select the group of notifications from the shade it just takes you to the default page because the notifications are grouped together with the ISY service. Message. Can those be grouped separately? And make it so the group can all be swiped away at once? Can you show the date/time the message was sent in the UD Mobile Notifications list? Maybe with an option for users to disable it? The notification configuration in Android lists them all separately by sound, is that intentional? Sent from my Pixel 6 Pro using Tapatalk

Probably fixed by the daily query-all? Sent from my Pixel 6 Pro using Tapatalk

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.

Great. I did test sounds ony Android phone and they all worked.

Yes, I started working in it, but UD Mobile Push Notifications support in Notification node server took priority. Hope get back to it this weekend.

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

Odd, that ST driver is managed by PG3 and is mentioned in the node server log: 2022-06-27 20:55:00,893 MainThread udi_interface.interface INFO interface:setController: Using node "wtcontroller", driver "ST" for connection status. and in the PG3 log it shows the value is 1: {"address":"wtcontroller","driver":"ST","value":"1","uom":25} Go to the Nodes page and see what the value is for ST on wtcontroller node.

Installing the node server on PG2 or PG3 will not interfere with existing programs on ISY994i. Moving from ISY994i to ISY on Polisy will mess up all your existing programs since the ELK module doesn't exist on Polisy. But, I honestly can't remember the state of ELK PG2 node server. I'm pretty sure it was all working, just doesn't have all the latest updates made in the PG3 version.

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

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.

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

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

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.

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.

It is released to beta @brians

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!

I also use a simple dog bark to know when the doggy door opens/closes, like this, but just one bark https://www.shutterstock.com/sound-effects/sound-11179-big-dog-bark-multiple-2 other than that I use a few of the ones included in Pushover.

Yes of course, I've been speaking with @Javi for a while about this and it's in development now. Hopefully have something releasable for alpha testing soon.