DennisC

Before buying, I would suggest trying UD Mobile.

Try checking the router for the new IP address and make sure the sub-domain hasn't changed. If all else fails, have you tried the instructions from the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY A word of caution, this method requires a good back up.

Hi @Javi, Just checking, if the expectations was that the recent releases were to fix the UOM error, it hasn't. I am still getting that error.

I think it has been stated that PG2 development is over. I don't think you will see any additional activity for. I would guess that when all node servers are available on PG3, PG2 will be phased out and shutdown.

I experienced the same thing. I restarted the Node Server and the message went away. My install was already at v3.3.3, so there was no change.

The upgrade went fine for me also. I also restarted Elk node server and that now shows the installed version number to match the store. Thanks for the update.

According to the log, after restarting the Notification node server, the version starting is 3.3.1 not v3.3.2 listed in the store.

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

@JimboAutomates, @bpwwer Has the issue causing the correct updated version from showing been identified? Is there anything needed to help identify the issue?

After running the update and syncing UD Mobile, the error changed to: java.lang.Error:UOM Suffix is null. 500

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.

Thanks to @glarsen, using the raw value has it working. There is no issue with it the way it is, as long as we know the situation. Maybe updating the documentation would help?

Thanks for that, adding raw to the end worked.

I have been playing around with sending text to Elk keypad. Previously, using the Elk Module, I was sending the OA temp to my keypads and I wanted to reinstate this. As a test, I have been successful placing the following in the body: ${sys.date} ${sys.time} I have even placed ${sys.date} ${sys.time} in the subject and it has worked (does $ & {} count has a character?), even thought I am not sure if it exceeds 16 characters. However, I can not get the Tempest temperature or humidity value to appear on the keypad using either one in the subject or both on two lines in the body. Is this a limitation of the 16 characters and if so, can that be upped so we can pass node server values to the Elk Keypad?

Ok, looking again I can see that. It's a long list and reading through it, I lost sight of it being in Area Node. My bad, sorry.

I restarted the Elk Node Server again with log set to debug. I checked in the log file and I see the following: UDI Python Interface for Polyglot version 3 3.0.38 Starting... I do not see any error messages. There are a couple of warnings as follows: 2022-04-01 13:08:17,674 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2022-04-01 13:08:17,675 MainThread udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-04-01 13:08:17,675 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'set': [{'key': 'notices', 'value': {}}]} It took me awhile to see where the message keys listed in help appear. I finally found them under the "Area 1" node. As a suggestion, maybe you want to list the location in the instructions?

I just rebooted Polisy with no change. Notification(6) Current Status: Connected Current Version: 3.2.4 [Production] Time Started: Apr 1, 2022, 10:37:45 AM Uptime: 2 Minute(s) 41 Second(s) ELK(2) Current Status: Connected Current Version: 3.1.4 [Production] Time Started: Apr 1, 2022, 10:10:23 AM Uptime: 1 Minute(s) 49 Second(s)

No it does not, neither does logging out and back in, or restarting Polyglot.

@JimboAutomates, @bpwwer I can confirm the same thing happening when upgrading both Elk & Notification Node Servers. Neither updated the version number. Tried the restart option more than once and ssh in to IoP to insure there were no missed updates.

If all else fails and you feel you have a good backup from before the change, you can do a factory reset as a last option. https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY

Also for clarity, are you talking about 1 switch or multiple switches and are these switches that have never been included in your ISY?

I have made the change to Polisy at two locations for both Insteon and Zwave. The Insteon backup and restore works well, although manual intervention is required. Zwave backup and restore is not yet available. If you are going to make the switch I suggest you copy to clip board all programs and paste in text document for reference. Also take screenshots of all Network Resources. There is nothing I was doing on ISY that I can't do on Polisy. I believe there is currently a discount on Polisy because of PGC being off line. Check the PGC thread.

I have a disabled program in my favorites in UD Mobile. While mine has no if statement, I run it manually, I thought I remembered the icon changing to indicate running. I just ran the if statement manually and it did display a filled in dot in the corner to indicate running. Not sure if the comparison is the same.

I use to use native ISY text messages to send notifications and alerts. For years this worked fine. After recent changes by my cell provider, there were long delays in receiving messages and long messages were cut off. I recently switched to this Node Server and found it to be beneficial with lots of advantages. Besides being very quick, from within a program you can configure different notification "services", by which I mean creating alert names for specific events. Also within a program you can select different notification sounds, priorities (have an alarm - check emergency alert which need to be acknowledged to stop sending), and the ability to send to different devices. When combined with Network Resources, the same message can be used for different occurrences by implementing substitutions within the notification. One suggestion I can make is to be sure to follow the configuration instructions carefully. If you have difficulty with a specific step, post a question here and someone will assist.

I should of asked this question in my prior post. Wile updated version require the step value to be re-added or is it set once and forget? Will backup and restore set this value?