CoLong

I initiated the update from 5.4.4 to 5.8.3 and now my Polisy is no longer accessible via the IoX launcher and it's been knocked out, i.e. its not running any of its programs. I've cleared the Java cache, and reentered the URL into IoX in the correct format and no joy (the error message says "not found"). I know its on my network because I have a different locator app, which shows its correct name on the correct IP address, and it also shows up just fine my my router. I've also gone to my ISY portal, and it shows that my Polisy has been disconnected since I initiated the update. When I try to re-add it to the portal, it says its already there. I've also rebooted the Polisy several times with long waits, and still no joy. There are also no beebs when I do a cold boot - all three lights come on for a short time, and then the two on the right go off and the left-hand one stays on. There are also no beeps when I press the multi-function either, and no changes in the lights regardless of how many times I press the multi-function button. What am I doing wrong?

Neither issue is resolved at this point. I've put tickets in on both, but the response has been very slow - Michel says they are having an issue with their mail server, but he hasn't said when he will have it resolved. gmail is apparently not a solution either, and this thread shows several people also having ptoblems with gmail. My Polisy is supposed to be sending emails to my personal email domain. I'm especially concerned about havinig completely lost contact with my Polisy and knocked it out of service due to the firmware update attempt - I'm leaving town in a coupla of days, and my home automation has to be at 100% before then. Its very disconcerting to be having such slow responses from UD, and no announcement wither.

@Geddy: I've done several cold boots by pulling out the plug and waiting for several minutes before plugging back in. Checking the Wiki, there are no beeps when I press the multi-function either, and no changes in the lights regardless of how many times I press the multi-function button. When I do a cold boot, all three lights come on for a short time, and then the two on the right go off and the left-hand one stays on.

@Geddy: As I feared, I initiated the update to 5.8.3 and now my Polisy is no longer accessible via the IoX launcger. I've cleared the Java cache, and reentered the URL into IoX in the correct format and no joy (the message says not found). I know its on my network because I have a different locator app, which shits its correct name on the correct IP address. I've also gone to my ISY portal, and it shows that my Polisy has been disconnected since I initiated the update. When I try to re-add it, it says its already there. I've also rebooted the Polisy and still no joy.

See: [Ticket #24315] Default email service on my Polisy suddenly stopped working

I also got a bunch of delayed notifications last night, but this morning my expected notifications have not come in. I will start a support ticket.

Thanks Geddy: I'm on 5.4.4. Its been a too frequent occurance that when I've done firmware updates in the past, something gets changed in my Polisy that I don't know about, and I have to struggle through all my programs fo find out what went wrong and fix it. As a result, I'm reluctant to implement updates unless there's some speciflc benefit to me, that's worth the risk. In this case, an email was received successfully from one of my programs at 01:02 MDT today, but several that I should have received since then have not arrived. Including several tests. Here's what shows up in the error log when I send using the "Test" button in the Emails/Notifications Settings/Groups tab: Wed 2024/05/01 12:02:35 0 -170001 <s:Envelope><s:Body><u:SendTestEmail xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><id>1</id></u:SendTestEmail></s:Body></s:Envelope> I've made no changes since 01:02 MDT, so I reason that something has changed external to my Polisy, to cause this problem. I've used a gmail account in the past instead of the default in Polisy, and I've found that its unreliable, often due to gmail's policy constraints. That's why I switched to the Polisy default, and its been relizble for years since then.

Email messages stopped beinbg sent out shortly after midnight MDT when requested by programs. I have rebooted, and syill no joy. Any ideas?

I would like to program an event to occur on the same day and month every year. How do I do that without having to go into the calendar and reset the year each time a new year rolls around?

Thanks for the alternate URL format. It worked, but only after a rebot The URL fromn the ISY Portal was correct, but it still doesn't woprk. I've deleted it, as the alternate URL is working fine.

My Polisy has been accessible from my Admin Consule for the past 10 months with no problems. All of a sudden it went missing from the IoX finder. I added back its URL that I copied from my ISY portal, but now I get "Invalid URL" when I try to launch the Admin Console from that URL in IoX finder. I know my Polisy is working because the programs are running correctly, and I can also operate it just fine from UD Mobile on my iPhone. I can see it sitting at the correct IP address on my network using other locator apps.

That's exactly what I was looking for. Many thanks.

The top of the display frame of the IoP admin console on Polisy shows the date. Does anyone know how to get access to the date (i.e. the calendar) in IoP, so that actions can be triggered by date and time, and not just by time?

My programs that checked the ETO value from the AERISWeather node server were not working correctly after migration to IoP. Chris J. and I ran various checks and the event viewer showed all checks to be working correctly. Then I noticed that copied versions of ETO-checking programs set themselves automatically to the correct True/False state based on the ETO set point after they were copied, even though their originals remained in the incorrect True/False state as though they are not reading the actual ETO. Just the copies seemed be to reading the ETO correctly. So, replaced each of the ETO-checking programs with new copies. Based on that observation, I checked all my programs to see if they were working correctly – some of them don’t get used very often, so they’ve had no opportunity to malfunction in the last several weeks. I found that many of them had to be replaced with new copies which then showed corrupted/altered lines of code that I had to correct manually. All my IoP programs came from a backup of my ISY 944i that I migrated over to IoP when I got my Polisy several weeks ago. I think this means that many lines of code got corrupted in the migration process, even though they displayed correctly in IoP on my monitor. Now, everything seems to be working correctly after spending several hours checking all my programs for errors, by comparing new copies to the originals, manually correcting the lines of code in the new copies that had errors, deleting the originals and removing the “copy” suffix from the new programs.

Issue resolution summary: ISY to IoP migration process corrupted many lines of code. Regarding the ETO issues, Chris and I ran various checks and the event viewer showed them to be working correctly. Then I noticed that copied versions of ETO-checking programs set themselves automatically to the correct True/False state based on the ETO set point after they were copied, even though their originals remained in the incorrect True/False state as though they are not reading the actual ETO. Just the copies seemed be to reading the ETO correctly. So, replaced each of the ETO-checking programs with new copies. Based on that observation, I checked all my programs to see if they were working correctly – some of them don’t get used very often, so they’ve had no opportunity to malfunction in the last several weeks. I found that many of them had to be replaced with new copies which then showed corrupted/altered lines of code that I had to correct manually. All my programs come from a backup of my ISY 944i that I migrated over to IoP when I got my Polisy several weeks ago. I think this means that many lines of code got corrupted in the migration process, even though they displayed correctly on my monitor in IoP. Now, everything seems to be working correctly after spending several hours checking all my programs for errors, by comparing new copies to the originals, manually correcting the lines of code in the new copies that had errors, and replacing the originals with new copies. The issue with IoP correctly detecting Precip changes, and taking correct actions based on IF AND statements, resolved itself over the course of the last 5 weeks. I speculate that there must have been an unannounced change made at the AERISWeather end which caused that correction, since no other changes were made to IoP or my programs in that time fram

@bpwwer I thought you might like to know this additional information . I've added it to the support ticket, which is currently unresolved: "I've repeated the precip test a couple of times now, and I see a pattern in the error that you might find diagnostic. With the precip manually set at 0.003 at mid-afternoon, IF precip >0.001 succeeds. But IF precip <= 0.010 initially fails, and then later succeeds, but only when precip is reset back to 0.000 automatically at midnight." @Chris Jahn

I've opened a UDI ticket for the above ETo-related problem, and I've included a link to this thread to show all the background information. IN addition, we had rainfall this evening and I'm seeing a situation with the PRECIP variable similar to the above problem with ETo. The AERISWeather table in IoP shown 0.27" of precip (see attached), but two different programs that should have been triggered by any level of precip over 0.100" have failed to run (see attached). In both cases, the program icon shows green, which (I think) means that the IF condition has been met, but in both cases, the THEN portion of the program fails to run, unless I manually click on "RUN THEN."

Many thanks @bpwwer. I will open a UDI ticket.

This is what the log shows at the time I took the Forecast 0 screenshot above: 2022-08-07 08:35:04,562 Thread-8252 udi_interface INFO aeris_daily:set_ETo: Conversion of temperature/wind speed required 2022-08-07 08:35:04,563 Thread-8252 udi_interface.node DEBUG node:setDriver: forecast_0:Forecast 0 No change in ETO's value 2022-08-07 08:35:04,564 Thread-8252 udi_interface INFO aeris_daily:set_ETo: ETo = 0.2 2022-08-07 08:35:04,564 Thread-8252 udi_interface DEBUG query:query_forecasts: >>>> period

Thanks @bpwwer. How do I see/find what the node server is actually sending to IoP, or is that something i need to ask UDI to do?

I'm not sure that truncation explains this, because e.g. Forecast 2 is currently displaying ETo as 0.24 not 0.2.

IoP is not responding correctly to EoT values from the AERISWeather Node Server. Today, the here EoT is 0.2 as shown in the Forecast 0 table in IoP (see attached), yet the first IF statement (see attached) fails, and the second one (see attached) succeeds. @bpwwer

Your latest version of the AERISWeather Node Server (2.0.9) has fixed the missing PRECIP values in IoP problem. Many thanks for you help.

@bpwwerDoes the parsing improvement apply to all AERIS Weather parameters not just PRECIP - just in case there are errors in those too (e.g. pressure), that we haven't been able to spot yet.

The error log shows syntax errors. I've sent it to you separately.