Release 3.3.6 (RC3) Is Now Available

[Michel Kohanim]

Hello all,

 

I am happy to announce the availability of our 3.3.6 (RC3) release! For a list of changes, please take a look at this post. This is a minor release and hopefully one which will become our official release.

 

Know Issues

- None

 

Things to test:

- SSL Communications with ELK which requires ISY994 PRO Series (Configuration instructions)

- File | Themes

- Accessibility using Alt key and keyboard accelerators

- Outdoor On/Off Module 2634_222

- SwitchLinc Dimmer 2478D

 

Important Information

1. Important Brultech module is no longer supported on ISY99 Series. Please contact sales@universal-devices.com for options

2. Important NetBios removed from ISY99 Series. You can no longer access ISY by going to http://isy on Windows

3. Important If you have a 994, you will need to re-install a certificate. Please review ISY994 Series Advanced Network Security Configuration for more information.

4. Important We have removed SSLv2 support (very insecure) from ISY99/ISY994. Unfortunately, the only protocol supported by MAC with Java 1.6 is SSLv2. As such, you MUST upgrade your MAC to Java 1.7 (Software Update)

 

4. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari.

 

5. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion

 

6. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly

 

7. For a discussion of variables, please look at our Program Variables forum.

 

 

Instructions:

1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK

 

2. Please download the firmware for your platform - please do not unzip

ISY 99i Series

ISY 994i Series

 

3. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system]

 

4. Choose the file saved in step 2

 

5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache

 

6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console:

a. http://your.isy.ip.address/admin - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d

b. http://your.isy.ip.address/admin.jnlp - Java application

c. http://www.universal-devices.com/99i/3.3.6 - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d

d. http://www.universal-devices.com/99i/3.3.6/admin.jnlp - Java application Best method to access Admin Console

 

Dashboard

- http://www.universal-devices.com/99i/3. ... board.jnlp

 

8. Please backup your system again

 

Thanks and with kind regards,

Michel

[jnaiser60]

And so why should we take this one? Looks to me as if its all about selling hardware to long time supporters.....

 

Merry Christmas to you as well.

[gatchel]

And so why should we take this one? Looks to me as if its all about selling hardware to long time supporters.....

 

Merry Christmas to you as well.

 

Are you using an ISY-26? That was "End Of Life" a while ago....

[TJF1960]

jnaiser60,

 

If you can't say anything nice.......

 

 

Michel, upgrade went perfectly. Thank You!

 

Tim

[db2ace2]

I just installed 3.3.6, Cleared JAVA Cache, and everything works except my EZFLORA. The EZFLORA is marked with the Red Exclamation Mark. I have tried unpluging and replugging the device, and Querying it with no success.

 

I will switch back to 3.3.5 and see if it works again. Please let me know if you have any ideas.

[LeeG]

db2ace2

 

Before going back to an earlier image check the EZFlora actually has power. I have two EZFlora devices , both pre and post I2CS which are fine on 3.3.6.

 

EDIT: depending on what the previous ISY firmware was, the later 3.3.x images fixed a bug where communications problems with the EZFlora did not result in the nodes being marked with a Red !. This meant that Program function Is Responding/Is Not Responding did not work for the EZFlora. This was corrected in the later 3.3.x images. Likely the EZFlora was having comm problems that went unnoticed because the nodes were not being marked with the Red ! as they are now.

[db2ace2]

I deeply apologize. This was a False Alarm, it just so happens that the problem with the EZFLORA happened at the exact same instant that I upgraded the new release. In this case, the EZFLORA had been running zones, and the sprinklers happened to get some outdoor Christmas Lights Wet which ultimately tripped the GFCI the EZFLORA is plugged in to. The EZFLORA is protected and indoors, but the outside lights tripped the circut. Sorry for the scare! The new version is working well!

 

Thanks

[Candide]

Upgraded from 3.3.5, so far no issues.

Like the themes.

Thanks...

[sbuckler]

Been using ISY for about a month now. Just love it. Quick question regarding 3.3.6. I just performed the upgrade and noticed the firmware and UI have different version nos. Is this correct?

 

Stan

[LeeG]

sbuckler

 

Thanks for checking that information and it is NOT correct. The UI and Firmware should both indicate 3.3.6. Either the Java cache was not cleared and/or the URL used to invoke the Admin Console (UI) has not been updated to pull the 3.3.6 Admin Console.

[sbuckler]

LeeG,

Thanks. All fixed. I had not updated the url of the admin console.

Stan

[foxcob]

I'm still seeing issues with this release. I tried running a program that gave me problems with 3.3.4 and 3.3.5 (but not 3.2.6) which sets a keypadlinc led brightness at a certain time of the day. The result was that the keypadlinc started fading very slowly to a 6% on level. I tried to restore the device and after the system busy dialog went away, I attempted to do it again. Still nothing. I then tried to query the keypad and the system busy dialog popped up and has been sitting for about 5 minutes at 33%. Not sure what is going on here. I'm going to close the console, restore the device, and try again. Can anyone else confirm an issue setting led brightness on a 2486D keypad? Mine is V.36.

 

Jacob

[LeeG]

foxcob

 

I am able to set my v.36 KeypadLinc LED Brightness level on 3.3.6.

 

i don't remember if an event trace was run on the previous ISY levels.

 

These are trace entries from 3.3.6, setting to 0/15, 4/15, 7/15.

 

Sat 12/15/2012 07:55:49 PM : [iNST-TX-I2 ] 02 62 15 9A F9 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB

Sat 12/15/2012 07:55:49 PM : [iNST-ACK ] 02 62 15.9A.F9 1F 2E 00 01 07 0F 00 00 00 00 00 00 00 00 00 00 BB 06 (00)

Sat 12/15/2012 07:55:50 PM : [iNST-SRX ] 02 50 15.9A.F9 19.70.06 2B 2E 00 (00)

Sat 12/15/2012 07:55:50 PM : [std-Direct Ack] 15.9A.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 12/15/2012 07:56:04 PM : [iNST-TX-I2 ] 02 62 15 9A F9 1F 2E 00 01 07 4F 00 00 00 00 00 00 00 00 00 00 7B

Sat 12/15/2012 07:56:04 PM : [iNST-ACK ] 02 62 15.9A.F9 1F 2E 00 01 07 4F 00 00 00 00 00 00 00 00 00 00 7B 06 (00)

Sat 12/15/2012 07:56:04 PM : [iNST-SRX ] 02 50 15.9A.F9 19.70.06 2B 2E 00 (00)

Sat 12/15/2012 07:56:04 PM : [std-Direct Ack] 15.9A.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Sat 12/15/2012 07:56:24 PM : [iNST-TX-I2 ] 02 62 15 9A F9 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B

Sat 12/15/2012 07:56:24 PM : [iNST-ACK ] 02 62 15.9A.F9 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B 06 (00)

Sat 12/15/2012 07:56:25 PM : [iNST-SRX ] 02 50 15.9A.F9 19.70.06 2B 2E 00 (00)

Sat 12/15/2012 07:56:25 PM : [std-Direct Ack] 15.9A.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

[junkycosmos]

Hi All !

 

Quick report that I just upgraded from 3.1.17. Hey no laughing, its been a while I know. Anyways upgrade went smooth as usual. Thanks again Team for another great update.

 

Junkycosmos

(99ir pro)

[TheWizard]

I'm still seeing issues with this release. I tried running a program that gave me problems with 3.3.4 and 3.3.5 (but not 3.2.6) which sets a keypadlinc led brightness at a certain time of the day. The result was that the keypadlinc started fading very slowly to a 6% on level. I tried to restore the device and after the system busy dialog went away, I attempted to do it again. Still nothing. I then tried to query the keypad and the system busy dialog popped up and has been sitting for about 5 minutes at 33%. Not sure what is going on here. I'm going to close the console, restore the device, and try again. Can anyone else confirm an issue setting led brightness on a 2486D keypad? Mine is V.36.

 

Jacob

 

I had the same problem. If I remember correctly I think the following worked. Not sure why, but it did. I had the problem while running v3.3.3.

 

Right click on the main KPL button (the one controlling the load, not A, B, C or D) and select Diagnostics | Query Insteon Engine.

 

The Wizard

[foxcob]

I did a restore this morning of the device after doing a query of the device. One thing I noticed is that when doing a restore, it says that i2 may not be fully supported and uses i1. But then when I tried to set the keypad brightness, it looks like it used an i2 message. I attached a screenshot of what happened after the device restore when I tried to set the keypad brightness. The busy dialog has been stuck at 94% for about 5 minutes at the time of this writing. What's strange is that currently only one of my keypads is exhibiting the issue. The other two are working fine. But all three exhibited the problem with 3.3.5. Somehow I got them all to work with 3.3.5 by downgrading to 3.2.6, restoring the devices and doing the upgrade again. Everything was working fine until I upgraded from 3.3.5 -> 3.3.6 where the problem showed up again with one keypad. For everyones info, I have a program that sets the keypad brightness levels to 1/6 at night and then sets it back to 0/5 during the day. This has always worked great until my use of any of the 3.3.x series releases. Any ideas?

 

Jacob

[LeeG]

foxcob

 

Using I1 for link management and I2 for device configuration is normal. ISY uses I2 (or I2CS) for link management only for those devices that cannot support I1 (motion sensor, triggerlinc, and others).

 

The values posted for the different LED Brightness values are not valid for the KPL but I don't think that is the issue. The KPL hardware/firmware requires a minimum separation of the low/high numbers by 8. For example 7/15 or 1/9. The device enforces this to maintain a consistent visual difference in LED level between Off and On even though the KPL accepts other combinations of numbers.

 

I do not see the command to change LED Brightness level but it could be under the progress popup or off the screen altogether. There are also several other commands being issued. Was this LED Brightness test/change done with the Admin Console LED Brightness button?

[foxcob]

Yes, this particular test was done with the LED brightness button. The events under the dialog were the messages from a restore to the device I did previously. I was not aware of the minimum brightness distance between on/off, but like I said, it at least programs correctly on the other keypadlincs. I keep running into strange problems with this new admin console where it appears to freeze up with a busy dialog. Closing and reopening the console seems to restore operation. Just in case anyone is wondering, I did clear my java cache and browser cache immediately after the upgrade before loading the new console and the about dialog shows a version of 3.3.6 for both UI and firmware.

 

I haven't studied the actual Insteon protocol in order to decode the messages myself, but I could do that if I have to to get to the bottom of this.

 

As to your comment about not seeing the command to set the keypad brightness, that was what the event table showed when I issued the command to set it. Thanks for everyones' help!

 

Jacob

[LeeG]

Run the Event Viewer at LEVEL 3. Click the Clear button on the event viewer and then change the KPL LED Brightness with the Admin Console. Post the event trace and I will analyze.

[foxcob]

LeeG,

 

I opened the admin console and did exactly what you said, here's the result. The busy dialog is still stuck open as well...

I was attempting to set a keypad brightness of 1/9. The keypad currently has the off state at 0 (no light) with the on level at about 5. I didn't see any change when trying to issue this command from the console.

 

Jacob

[LeeG]

The ISY is updating something, not the LED Brightness, with the command traced. With the popup still displayed the ISY has not completed whatever updates it thinks it needs with that KPL. I am concerned the movement back and forth between 3.2.6 and 3.3.x may have done something to that KPL definition. The 3.3.x images made changes to the ISY configuration that were not backward compatible with 3.2.6.

 

It may be necessary to Delete that KPL device and add it back from scratch.

[foxcob]

LeeG,

 

I think you're probably on to something. Just to note though, that I originally went back to 3.2.6 because this problem showed up when I went from 3.2.6 to 3.3.4. When I did go back to 3.2.6, I also restored the ISY from the 3.2.6 backup, so I shouldn't have had 3.3.4 config with 3.2.6. I think something is wrong with the upgrade process converting the configuration from a prior version. This time it messed up the config of the one KPL, but not the others. Like I said, everything was working with 3.3.5, then I upgraded to 3.3.6 and it failed again. I'm going back to 3.2.6 and restoring from my 3.2.6 backup to see if everything goes back to normal. At that point I'll try a direct upgrade from 3.2.6 to 3.3.6.

 

Jacob

[foxcob]

Just downgraded and restored from backup 3.2.6 and everything works normally again. I'm going to attempt to go directly to 3.3.6 now. Hopefully everything goes correctly this time.

 

Jacob

[foxcob]

Alright, I'm back to 3.2.6 for now. Every time I upgrade to 3.3.6, I run into this problem. Unfortunately, this means that twice a day I end up with a KPL that is corrupted and misbehaves. I'm totally willing to try something if anyone has a specific procedure they want me to try. I haven't tried going to 3.3.6 and recreating the KPL from scratch. Maybe I can do that later, but I'm out of time for now. Thanks again to those who have helped!

 

Jacob

[LeeG]

Stay on 3.3.6. Delete the KPL and add it back under 3.3.6