DennisC

I have previously rebooted Polisy several times and just tried again with no change. I then tried power cycling Polisy but that didn't work either.

Hi Jim, I run two Polisy's at two different locations, both are running the same versions of IoP (5.4.3.1), PG3 (3.0.59), Notification Node Server (3.3.4), and Weatherflow Node Server (3.0.19). I have 2 of the same Notifications set up with the Notification Node Server for Today's Weather Forecast and Tomorrow's Weather Forecast. However, I am getting two different format results for the same condition depending on the location the notification is coming from. The Notification NR sends: Forecast Conditions ${sys.node.n001_forecast_0.GV13} for today's forecast and Forecast Conditions ${sys.node.n001_forecast_1.GV13} for tomorrow's forecast. The formatted results are Clear, Rain Likely, Rain Possible, etc from one location and 0, 1, 2, etc from the second location. I have restarted Weatherflow and Notification Node Server, and I have restarted Polisy at the location sending numbers instead of the actual condition name with no change. I have also copy and pasted the Network Resources set up from one unit to the other in case there was a stray character in the one sending the numbers. Both locations are set up with no encoding and raw text. I also have included system date, system time, node name, high temperature, low temperature, and chance of precipitation in the same notification. I am not sure if the issue is with Polisy, Weatherflow or Notification Node Server. Can you offer any guidance on how to track down what is causing the one unit to send numbers?

I am also not experiencing any issues on the same versions you are running.

Thank you.

@bpwwer, I will be traveling to my other location that hasn't had an upgrade for several versions (isy, node server's, pg3), since I wasn't there and didn't want to upgrade remotely. Given the issue with pyisy module not working, does this mean I shouldn't perform an upgrade? While everything is not at the latest version on IoP, everything is currently working and since it is a remote site, I wouldn't want anything to break. Thanks for your opinion. dc

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