bpwwer Posted April 28, 2022 Posted April 28, 2022 The Admin Console and the ISY independently read the profile file that maps the number to a string. From what @Javisays, it sounds like UD Mobile expects the ISY to send the formatted value. So if the admin console is correctly showing the string value, then it implies that the profile files are correct and it would be the ISY that's not reading and/or not mapping the values. There are times that the ISY needs a reboot to force it to re-read that file and get the contents into memory but it sounds like you already tried that. I think the next step may be to open a ticket to find out why that specific ISY either isn't reading the file or isn't performing the the mapping.
DennisC Posted April 28, 2022 Posted April 28, 2022 46 minutes ago, JimboAutomates said: If it's not showing in UD Mobile then hit the load profile button (or whatever it's called) in the PG3 UI for that Node server, then restart ISY again and re-sync UD Mobile to see if that fixes it. Although it's strange that it shows properly in AC... 36 minutes ago, Javi said: @DennisC, If that does not resolve the issue please send me an email. The app gets the formatted values from the ISY so this is very odd that it would show in the AC but not Mobile after reboot. 26 minutes ago, bpwwer said: The Admin Console and the ISY independently read the profile file that maps the number to a string. From what @Javisays, it sounds like UD Mobile expects the ISY to send the formatted value. So if the admin console is correctly showing the string value, then it implies that the profile files are correct and it would be the ISY that's not reading and/or not mapping the values. There are times that the ISY needs a reboot to force it to re-read that file and get the contents into memory but it sounds like you already tried that. I think the next step may be to open a ticket to find out why that specific ISY either isn't reading the file or isn't performing the the mapping. 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.
DennisC Posted April 28, 2022 Posted April 28, 2022 43 minutes ago, Javi said: Thanks @DennisC, Yes please open a ticket. Ticket submitted, thank you.
Recommended Posts