26 minutes ago, jec6613 said:

I had the same issue - see my post earlier about DHCP changes with the OS update.

So did the unit change its MAC address?  I don't know how else it would not follow the DHCP reservation.

20 minutes ago, wmcneil said:

Thanks. I had to increase the timeout to 20,000 (I tried a curl at Michael's suggestion, and that was taking 12 seconds, so I increased to 20 to be on the safe side.). 

That's a crazy long time for a server response 12 or 20 seconds.

Weird that we're both using the same server and mine is less than 2 sec.

What's your ping response time?

23 minutes ago, apostolakisl said:

So did the unit change its MAC address?  I don't know how else it would not follow the DHCP reservation.

It's sending a unique ID, not its MAC address, to supported servers.  This has been the new standard for a few years now to support IPv6 - that unique ID is not dependent on the NIC but is for the entire system, so a well designed system can multi-path over multiple NICs with multiple IPv6 addresses.

38 minutes ago, mmb said:

That's a crazy long time for a server response 12 or 20 seconds.

Weird that we're both using the same server and mine is less than 2 sec.

What's your ping response time?

I'm getting about 10 msec ping response. So there must some other overhead in the SMTP interaction that is taking significantly longer.

53 minutes ago, wmcneil said:

I'm getting about 10 msec ping response. So there must some other overhead in the SMTP interaction that is taking significantly longer.

You're obviously special, my gmail smtp is sub 2 sec. on a Polisy.

I did have to increase the timeout from 1 sec because I was getting the error.

1 hour ago, jec6613 said:

It's sending a unique ID, not its MAC address, to supported servers.  This has been the new standard for a few years now to support IPv6 - that unique ID is not dependent on the NIC but is for the entire system, so a well designed system can multi-path over multiple NICs with multiple IPv6 addresses.

I know the OS can probably deal with IP6 but this is the first I've heard of it. 

Does that extend to Portal UUID?

@jec6613 can you confirm you have an IP4 ip address?

Edited February 14, 20251 yr by mmb

21 minutes ago, mmb said:

I know the OS can probably deal with IP6 but this is the first I've heard of it. 

I think maybe IPv6 support is a requirement for supporting Matter.  Anyway, the eisy does support it.

Thank you much!

Timer - [ID 003E][Parent 0030]

If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        Repeat Every  1 hour 
           Run Program 'Airthings AQ Normal' (If)
 
Else
   - No Actions - (To add one, press 'Action')
 

Airthings AQ Normal - [ID 006D][Parent 0030]

If
        'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM
    And 'Airthings Controller / Main Level' VOC <= 225.0
 
Then
        Set 'ERV' On
        Wait  15 minutes 
        Set 'ERV' Off
 
Else
        Set 'ERV' On

 

Edited February 14, 20251 yr by pjjameso

1 minute ago, pjjameso said:

Thanks you much! Dumb followup, how do you tell a program to run at startup?

Program Summary tab, right click the program and select Enable Run at Startup

3 hours ago, apostolakisl said:

And you will need to manually run the second program "run then" to get it started.  Unless you reboot ISY, then it will run automatically.  A "run at startup" program with a blank "if" will execute "then" at startup.

 

5 hours ago, pjjameso said:

So migrated to Eisy after bricking my Polisy with the upgrade.  All seems to be working except for one program which I cant figure out why.  The program shows green which means the If statement is true but the ERV doesnt turn off after the 15 min wait period.  Any thoughts?

Airthings AQ Normal - [ID 006D][Parent 0001]

If
        'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM
    And 'Airthings Controller / Main Level' VOC <= 225.0
 
Then
        Repeat Every  1 hour 
           Set 'ERV' On
           Wait  15 minutes 
           Set 'ERV' Off
 
Else
        Set 'ERV' On
 

 

Okay, no idea why it worked on Polisy perfectly as one program, but to get it working on Eisy had to break into 3 programs. Issue solved so far...

Airthings Timer - [ID 003E][Parent 0030][Run At Startup]

If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        Repeat Every  1 hour 
           Run Program 'Airthings AQ Test' (If)
 
Else
   - No Actions - (To add one, press 'Action')

Airthings AQ Test - [ID 003F][Parent 0030]

If
        'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM
    And 'Airthings Controller / Main Level' VOC <= 225.0
 
Then
        $sAirThings  = 1
 
Else
        $sAirThings  = 0

Airthings AQ Normal - [ID 006D][Parent 0030]

If
        $sAirThings is 1
 
Then
        Set 'ERV' On
        Wait  15 minutes 
        Set 'ERV' Off
 
Else
        Set 'ERV' On
 

43 minutes ago, pjjameso said:

Okay, no idea why it worked on Polisy perfectly as one program, but to get it working on Eisy had to break into 3 programs. Issue solved so far...

        'Airthings Controller / Main Level' CO₂ Level <= 775.0 PPM
    And 'Airthings Controller / Main Level' VOC <= 225.0
 

I generally write device info to variables so you can pop into the AC and validate the program is working properly.

Question why wouldn't you use an OR Then On Else Off?

Any suggestions on how to improve process would be appreciated. Not an expert at programing by any means, more like try, fail, try again, rinse and repeat!

1 hour ago, pjjameso said:

Any suggestions

I would start a new thread as a starter.

There's lots of talent on this forum.

Updated my Polisy tonight. Started around 4:30 p... didn't seem to reboot or anything but the AC went offline, I then saw UID of 00:00:00:00:00:01 and I could connect but not control any Insteon. Still showed 5.8.4.

I decided to ssh and rebooted after over an hour waiting.

Then after UID was correct and still on 5.8.4, I did another update packages in AC and this time it had a more detailed dialog that was updating to version 14.xxx whatever it said can't remember. Then it updated correctly maybe 20 min.

But had me very concerned for hour there.

 

 

 

 

Edited February 15, 20251 yr by brians

We left town on vacation on last Monday when this was announced. Did it this morning. I was on 13.2 of OS and 5.8.4 of iox and they both upgraded as expected.

It did not take long, like 10 - 15 minutes. I'm wired, insteon for powerline. My plugins are Ecobee, Notification, Yolink, Ring and Timedata. All came up as expected. My "audit' of programs and manual device settings show that things are working.

21 hours ago, mmb said:

@jec6613 can you confirm you have an IP4 ip address?

I haven't checked the portal UUID or looked at what the UID coming to my DHCP server is since I changed the reservation, but yes I can confirm that I have an IPv4 address.

Add another bricked polisy.  Very annoyed.  Backup up everything.  Ran update from the admin console.  Waited over an hour.  Solid green left-most LED on the Polisy.  Does not show up on my unifi router as a device, so no IP address to ping or ssh to.

The polisy was hardwired ethernet.  I had a reserved IP address, so followed the prior threads and unreserved it on the router before updating.

Tried power cycling.  Same single LED is on.

What do I do now?

Im on a mac mini, ran the update now I get this:

 

any helpful tips how to proceed?

Sure: 

7 minutes ago, oamber said:

any helpful tips how to proceed?

Open System Settings, then Java, then Settings… then Delete Files.  Select all 3 options under Delete the following files? then click OK.  Then, run IoX Finder, and please report the results here.

Edited February 15, 20251 yr by GHenry
report

Upgrade went fine including pg3

My ip address did change though.

44 minutes ago, bob123 said:

Add another bricked polisy.  Very annoyed.  Backup up everything.  Ran update from the admin console.  Waited over an hour.  Solid green left-most LED on the Polisy.  Does not show up on my unifi router as a device, so no IP address to ping or ssh to.

The polisy was hardwired ethernet.  I had a reserved IP address, so followed the prior threads and unreserved it on the router before updating.

Tried power cycling.  Same single LED is on.

What do I do now?

Ticket time.

cleared Java etc then got this:

3 minutes ago, oamber said:

cleared Java etc then got this:

Download and run a fresh copy of Start.jnlp 

1 hour ago, bob123 said:

Add another bricked polisy.  Very annoyed.  Backup up everything.  Ran update from the admin console.  Waited over an hour.  Solid green left-most LED on the Polisy.  Does not show up on my unifi router as a device, so no IP address to ping or ssh to.

The polisy was hardwired ethernet.  I had a reserved IP address, so followed the prior threads and unreserved it on the router before updating.

Tried power cycling.  Same single LED is on.

What do I do now?

You should open a support ticket with UD.

I also ran in to a problem on my test Polisy, waited over 3 hours with nothing happening & Polisy unresponsive. Finally tried a reboot and my router shows Polisy is on line, but that is it. Can not get in with start.jnlp or ssh & portal shows it off line. The Polisy is dead.

Started a support ticket with UD and there is a method to recover, but you will need to get instructions from them. It requires an inexpensive hardware adapter, but since this is my test unit, I am not sure if I will proceed.