Jump to content

Release 2.6.6 is now available


Michel Kohanim

Recommended Posts

Release 2.6.6 beta is now available and may be downloaded immediately.

 

WARNING: Release 2.6.6 contains a BUG, and therefore should only be used for WSDK support purposes!

 

This release includes the final version of WSDK 1.0 .

 

For fixes and enhancements, please peruse our beta forum at http://forum.universal-devices.com/viewtopic.php?t=930. You may also post your comments/questions and issues relating to 2.6.6 to the same forum.

 

IMPORTANT

1. For those upgrading from release 2.6, please note that releases 2.6.1 and above will use default HTTP/HTTPS ports of 80/443 respectively. As such, before upgrading Disable Internet Access

2. If you have used bookmarks, please update them accordingly. If you have problems finding ISY, try http://www.universal-devices.com/99i

3. If you are upgrading from 2.6.1, please make sure you export all your programs and store them in a safe place

4. As always, please take a backup of your ISY

 

Due to massive changes in this release, please do be kind enough to thoroughly test those functions most important to you specifically schedules, triggers, and Web Services.

 

INSTRUCTIONS

- Userid = isy

- Password = autoupdate

- For ISY-26, download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip

- For ISY-99i Series, download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip

- Login to Admin Console

- Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step

- Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step

- Important: After upgrading, please close Admin Console, close all web browser processes, clear your Java cache, and reopen Admin Console. If there are any web browser processes running, the Java cache will not be cleared.

 

LIMITATIONS

- IES Touchscreens will not work with this release. Update is forthcoming

- InterfaceGo will not work with this release. Update is forthcoming

- WSDK requires many modifications to work with this release

Link to comment
Share on other sites

Time looks OK here in EST.

I just did another sync with the ntp and it is okay now. I am on east coast DST time as well. I guess this was just related to the installation but not actual problem (just needed to run another time sync)!

Link to comment
Share on other sites

Thank you!

 

No problem with DST here in Central time. Stowaway, didn't you have that with 1.6.5?

 

Rand

Hi Rand.

Not sure what you are asking... I'm OK - just needed to do another time sync after I installed. No Issue.

Link to comment
Share on other sites

On my ISY26:

 

Something when wrong when I updated. I downloaded the zip file and manually updated. Now the box is dead (well not accessible via the ethernet port). I've tried power cycling it and it still doesn't come back.

 

When I say not accessible, I mean it's not sending the UPNP broadcasts and it's not responding on the IP address previously used.

 

I don't have physical access to the box right now so I can't see the lights. When I do get back home, is there anything I should check before trying to factory reset it?

Link to comment
Share on other sites

Hi bpwwer,

 

I am so very sorry to hear this. Please do not factory reset ... what we need to know is the status of the LEDs on top of ISY.

 

Again, I am so very sorry ...

 

With kind regards,

Michel

 

On my ISY26:

 

Something when wrong when I updated. I downloaded the zip file and manually updated. Now the box is dead (well not accessible via the ethernet port). I've tried power cycling it and it still doesn't come back.

 

When I say not accessible, I mean it's not sending the UPNP broadcasts and it's not responding on the IP address previously used.

 

I don't have physical access to the box right now so I can't see the lights. When I do get back home, is there anything I should check before trying to factory reset it?

Link to comment
Share on other sites

Hi bpwwer,

 

I am so very sorry to hear this. Please do not factory reset ... what we need to know is the status of the LEDs on top of ISY.

 

Both MEM and ERR are flashing on 2 seconds off 3 seconds. The link light on the ethernet port is lit.

 

After a power cycle, all the lights flash and it seems like it is communication with the PLM because it's light and other insteon devcices' lights are flashing too. This happens for about 1 minute and then it goes back to flashing the mem/err lights as above.

 

It doesn't appear to have requested an address from the DHCP server at any point.

 

Ahh, connection up the serial port provides a bit more info. it's displaying

"network cable disconnected or DHCP server error" over and over.

 

Resetting the router/dhcp server makes no difference

Manually configuring the network on the ISY makes no difference

Replacing the network cable makes no difference.

Switching to a different port on the router makes no difference.

Link to comment
Share on other sites

Bob,

 

Unfortunately, it seems that ISY's network PHY is not working. Please verify your shipping address to support@universal-devices.com and another unit shall be sent to you immediately.

 

With sincere apologies for the inconvenience,

With kind regards,

Michel

 

Hi bpwwer,

 

I am so very sorry to hear this. Please do not factory reset ... what we need to know is the status of the LEDs on top of ISY.

 

Both MEM and ERR are flashing on 2 seconds off 3 seconds. The link light on the ethernet port is lit.

 

After a power cycle, all the lights flash and it seems like it is communication with the PLM because it's light and other insteon devcices' lights are flashing too. This happens for about 1 minute and then it goes back to flashing the mem/err lights as above.

 

It doesn't appear to have requested an address from the DHCP server at any point.

 

Ahh, connection up the serial port provides a bit more info. it's displaying

"network cable disconnected or DHCP server error" over and over.

 

Resetting the router/dhcp server makes no difference

Manually configuring the network on the ISY makes no difference

Replacing the network cable makes no difference.

Switching to a different port on the router makes no difference.

Link to comment
Share on other sites

Bob,

 

Unfortunately, it seems that ISY's network PHY is not working. Please verify your shipping address to support@universal-devices.com and another unit shall be sent to you immediately.

 

A quick update to note that it wasn't the upgrade itself that failed. It seems there may be a heat related issue with the network hardware itself. After sitting unplugged all night, I plugged it back in on a whim and it worked ... for a little while.

Link to comment
Share on other sites

Hi Bob,

 

Would you happen to have an extra PLM? What happens if you leave your PLM unplugged (you will get the RX light solid on but everything else non INSTEON related should work).

 

With kind regards,

Michel

 

Bob,

 

Unfortunately, it seems that ISY's network PHY is not working. Please verify your shipping address to support@universal-devices.com and another unit shall be sent to you immediately.

 

A quick update to note that it wasn't the upgrade itself that failed. It seems there may be a heat related issue with the network hardware itself. After sitting unplugged all night, I plugged it back in on a whim and it worked ... for a little while.

Link to comment
Share on other sites

I do have an extra PLM, but I won't be able to unplug the current one until tonight. However, it is still mostly working. I am able to control devices via the web interface and bring up the admin console, as long as I don't re-boot it. If I do, then I'll have to power it down for a couple of hours before I can use it again.

 

As soon as I do anything that requires a re-boot (switch back to using DHCP, firmware update, etc.) it thinks the cable is unplugged and I have to power it off for a while.

 

I think this is consistent with a problem I've had with this box for a while. For the past few firmware updates, I've had to power cycle it to get it working. It would do the firmware update, reboot, and then it would not be accessible until I power cycled it. It's just getting worse now.

 

 

Hi Bob,

 

Would you happen to have an extra PLM? What happens if you leave your PLM unplugged (you will get the RX light solid on but everything else non INSTEON related should work).

 

With kind regards,

Michel

 

Bob,

 

Unfortunately, it seems that ISY's network PHY is not working. Please verify your shipping address to support@universal-devices.com and another unit shall be sent to you immediately.

 

A quick update to note that it wasn't the upgrade itself that failed. It seems there may be a heat related issue with the network hardware itself. After sitting unplugged all night, I plugged it back in on a whim and it worked ... for a little while.

Link to comment
Share on other sites

bpwwer,

 

Ok. Thanks so very much for the update. It might be the case and hopefully the new one will solve all of these issues.

 

With kind regards,

Michel

 

I do have an extra PLM, but I won't be able to unplug the current one until tonight. However, it is still mostly working. I am able to control devices via the web interface and bring up the admin console, as long as I don't re-boot it. If I do, then I'll have to power it down for a couple of hours before I can use it again.

 

As soon as I do anything that requires a re-boot (switch back to using DHCP, firmware update, etc.) it thinks the cable is unplugged and I have to power it off for a while.

 

I think this is consistent with a problem I've had with this box for a while. For the past few firmware updates, I've had to power cycle it to get it working. It would do the firmware update, reboot, and then it would not be accessible until I power cycled it. It's just getting worse now.

 

 

Hi Bob,

 

Would you happen to have an extra PLM? What happens if you leave your PLM unplugged (you will get the RX light solid on but everything else non INSTEON related should work).

 

With kind regards,

Michel

 

Bob,

 

Unfortunately, it seems that ISY's network PHY is not working. Please verify your shipping address to support@universal-devices.com and another unit shall be sent to you immediately.

 

A quick update to note that it wasn't the upgrade itself that failed. It seems there may be a heat related issue with the network hardware itself. After sitting unplugged all night, I plugged it back in on a whim and it worked ... for a little while.

Link to comment
Share on other sites

I am unable to upgrade to 2.6.6 (from 2.6.4).

 

I get the "upgrade failed" message about incompatible file type.

 

This also happens when I open admin console with the suggested link:

http://www.universal-devices.com/27

 

I cleared my Java cache and unloaded my AV program - just to be sure.

 

Any suggestions or other actions I can try?

Link to comment
Share on other sites

I had downloaded the file with a different name - Insteon.2.6.5.Zip.

 

The upgrade worked after I renamed it back to just Insteon.zip.

 

Maybe the extra dots have something to do with that. I use Insteon_x_x_x.zip with no problem.

 

Rand

Link to comment
Share on other sites

  • 4 weeks later...

2.6.6 doesn't seem to allow for more than 4 mutually exclusive buttons on a KeypadLinc 8-button dimmer. The GUI lets me add all 8, but there's strange behavior:

 

* Pressing any of the first 4 turns off all other 7 buttons, so these 4 seem to work correctly

* But, pressing any of the last 4 just act as normal toggle buttons and don't turn off any other buttons

 

Looks like it's not sending all of the commands correctly. I've done this over 20 times with the exact same behavior, so it's not a connection issue. I've tried deleteing all programs in the GUI, resetting the keypad to it's factory defaults, forcing a device reset from the GUI, but nothing did the trick.

 

Any ideas? Is this a known bug with this version?

Link to comment
Share on other sites

Hi franky,

 

ISY allows for 4 mutually exclusive groups simply because when you have 8 buttons, there are at the most 4 ways that you can group them together. In short, buttons in the same group are mutually exclusive from one another: if you turn one on, the others will turn off and vice versa.

 

I think you've put all your buttons in the same group and thus what you are witnessing.

 

With kind regards,

Michel

 

2.6.6 doesn't seem to allow for more than 4 mutually exclusive buttons on a KeypadLinc 8-button dimmer. The GUI lets me add all 8, but there's strange behavior:

 

* Pressing any of the first 4 turns off all other 7 buttons, so these 4 seem to work correctly

* But, pressing any of the last 4 just act as normal toggle buttons and don't turn off any other buttons

 

Looks like it's not sending all of the commands correctly. I've done this over 20 times with the exact same behavior, so it's not a connection issue. I've tried deleteing all programs in the GUI, resetting the keypad to it's factory defaults, forcing a device reset from the GUI, but nothing did the trick.

 

Any ideas? Is this a known bug with this version?

Link to comment
Share on other sites

Actually, you can cross link the 8-key KeypadLinc buttons manually so that all 8 buttons are mutually exclusive from eachother (although it will take you an hour of pushing and holding the buttons for 10 seconds each)...meaning that at any given point, only one button can be lit up. The ISY software has the limitation of only allowing 4 buttons to be mutually exclusive to each other at a time. This is what I was asking. Is there a way to make the ISY setup the KeypadLinc to make all 8 buttons mutually exclusive to each other so that pushing any of the 8 buttons turns off the other 7?

 

ISY allows for 4 mutually exclusive groups simply because when you have 8 buttons, there are at the most 4 ways that you can group them together. In short, buttons in the same group are mutually exclusive from one another: if you turn one on, the others will turn off and vice versa.

 

I think you've put all your buttons in the same group and thus what you are witnessing.

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...