DennisC

Open a support ticket with UD. They will correct the issue.

To start with your program issue, right click on you program name and select copy to clip board and then paste the program here so we can offer assistance. For the rest of your issues, tell us about your setup: ISY or IoP, firmware and UI version, Insteon or zwave devices. Open the event viewer set to level 3 and try to operate your devices and see what messages are sent. If a physical switch isn't working are you sure you have it installed correctly? What device is it?

After entering the new IP address for your Elk and clicking on the save button in the admin console, what happens? Have you checked the error log? Also, make sure you are not connected to the Elk in another application, only one connection at a time is allowed. Are you using the correct port number?

Does your UI match your firmware version from the about page?

Can you provide more information about your setup? Are you using the Elk Node Server or the Elk Module, running N ISY 994 or Polisy and IoP? What is your firmware and UI version? Have you tried rebooting?

Have you cleared your java cache, downloaded a fresh copy of the ISY Launcher and tried running the Launcher?

How are you trying to add it? Have you tried manually typing in the Insteon ID? Are you sure you are correctly reading the ID? What error message are you receiving?

I would also add that if the ISY or IoP has trouble communicating with Insteon devices, your system probably has some interface or a device that is creating noise which in turn is causing the issue. The wiki has troubleshooting steps to help figure out where the noise is coming from.

In the screen shot a few post above: Remove a Z-Wave Device

I would try removing the conditions from the folder. I have found conditions on folder to be unreliable.

I agree with Elk being my source, but wouldn't be upset if you made it an option.

Ticket submitted, thank you.

I toggled load profile in PG3 for Weatherflow Node Server and rebooted IoP. After allowing sufficient time for start up, I re-synced UD Mobile. My results are the same, admin console shows the word description, but UD Mobile and a NR through the Notification Node Server shows the number valve for Forecast Conditions. I am not sure if this is related, but I did find the following error in Weatherflow Node Server log: 2022-04-28 13:08:39,137 Thread-5 udi_interface INFO derived:updateTrend: LAST entry = 1010.750000 2022-04-28 13:08:39,138 Thread-5 udi_interface INFO derived:updateTrend: TREND 1010.750000 to 1008.690000 2022-04-28 13:08:39,155 Thread-5 udi_interface ERROR weatherflow:udp_data: Failed to send data to ISY: '>' not supported between instances of 'NoneType' and 'int' I should mention that I am waiting for a replacement Tempest from Weatherflow as this one goes offline several times a day. Also, this has always been like this at the site for me. I never thought anything about it and shortly after setting this up I added tomorrow's forecast data to favorites in UD Mobile and mapped the numbers to the proper description. If I look at the Forecast data in Favorites, it reads correctly, but if I go under Devices & Scenes in UD Mobile and go to Weatherflow directly, I see the number for Forecast Conditions. It wasn't until I set up my second location last week and added sending forecast Data via the Notification Node Server and that system sent the words, that I realized there was a problem. @Javi, should I email you or directly or open a support ticket? Since this also happens when sending Forecast Data from the Notification Node Server, I don't think it is an issue only with UD Mobile. Thank you for all your comments and assistance, everyone.

They both show up correctly in the admin console. One site shows correctly in UD Mobile, the site that sends numbers in the Notification Node Server also shows numbers in UD Mobile. I tagged Bob to see if he has any suggestions. @bpwwer, could you look at the issue I describe starting with the post below and see if you have any thoughts on how to correct numbers instead of description showing up in Weatherflow's forecast conditions. Thank you both.

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.