Release 2.8.2 Beta is now available

[Michel Kohanim]

Hello all,

 

 

Release 2.8.2 Beta is now available. Although this firmware has been tested thoroughly, please note that this is still a beta firmware.

 

For a list of changes, please take a look at this post:

http://forum.universal-devices.com/view ... =6475#6475

 

Please note that ISY-26 is no longer included in the firmware builds.

 

Instructions

 

1. Please backup your ISY (File | Backup ISY)

 

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

ISY 99 Only - http://www.universal-devices.com/update ... nsteon.zip

 

3. It is very important that you use your current ISY's Admin Console to perform the upgrade by going to your http://your.isy.ip.address/admin. For MAC users, if upgrade fails, please try https://your.isy.ip.address/admin

 

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

 

5. Choose the file saved in step 2

 

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

http://www.universal-devices.com/mwiki/ ... Java_Cache

 

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

a. http://isy/admin - applet (Windows only)

b. http://isy/admin.jnlp - Java application (Windows only)

c. http://your.isy.ip.address/admin - applet

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

e. http://www.universal-devices.com/99i/2.8.2 - applet

f. http://www.universal-devices.com/99i/2.8.2/admin.jnlp - Java application

 

8. IMPORTANT If you have already installed a self signed certificate and your current firmware is 2.7.10 and below, you must reinstall a new one:

http://www.universal-devices.com/mwiki/ ... rtificates

 

IMPORTANT

Due to the sensitive nature of supporting MorningLinc, users now must agree to terms and conditions upon Admin Console start up otherwise the console closes.

 

Thanks and with kind regards,

Michel

[k7zpj]

Hi Michel,

I had a minor issue when upgrading the firmware in my isy-99 from 2.8.1 Beta to 2.8.2 Beta.

 

The small window with the message "Please Reopen your Browser" didn't close at the end of the upgrade. After waiting a few minutes I tried to close it but was unable to get focus on the window to close it.

 

I ended up going into task manager/applciations tab and ending the task for the admin Window.

 

I then cleared the Java cache and reopened the browser and the isy-99 seemed to be functioning normally.

 

My system configuration:

Win 7 X64

IE8 32 bit

Java build 1.6.0_21-b06

 

Regards

Bruce Powell

[/img]

[lawr1000]

I am still having problems with the 2477SA2 v.3A Load controller. I only see one node for the Load Controller and as I understand there should be more. One is the basic switch controller. Another is Scene 1 which is activated when the load turns on and finally Scene 2 which is activated when the load turns off.

 

I did clear the Java cache after upgrading the firmware. I did see the new Term and Conditions and Accept dialog. I did try removing/adding the Load Controller with both Automatic and Manual selections.

 

So here are my questions:

 

What should I see in the ISY for the Normally Open (see edit below) load controller?

Is there are way to tell that the Java Applet version matches the Firmware version?

 

I am running Windows 7 64-bit

Internet Explorer 8

 

EDIT: This is actually the Normally Closed controller.

[brad77]

The small window with the message "Please Reopen your Browser" didn't close at the end of the upgrade. After waiting a few minutes I tried to close it but was unable to get focus on the window to close it.

 

I ended up going into task manager/applciations tab and ending the task for the admin Window.

I experienced the same, but with Firefox. Killing Firefox allowed me to continue and all seems A-OK.

[LeeG]

I have the same browser problem with IE8 on XP. I've seen it on 2.7.15 and all images since then. Happens about 1 in 8-10 times doing an image update. I cancel the IE session with the task manager with no adverse effects.

 

Regarding the Load Controller, the post refers to it as a "Normally open" load controller, the type number is for the "Normally closed" load controller. Which type is it?

[Michel Kohanim]

Hello all,

 

Thanks so very much for the feedback. That was indeed a bug with 2.8.1 and should be fixed in 2.8.2.

 

With kind regards,

Michel

[lawr1000]

Regarding the Load Controller, the post refers to it as a "Normally open" load controller, the type number is for the "Normally closed" load controller. Which type is it?

 

Sorry about the confusion, the model number is correct. It is the Normally Closed version.

[gfridland]

Upgrade went well...all work fine so far.

 

Only issue encountered was with IE browser freezing after download of firmware...had to force it closed and after reopening, all worked fine.

 

Thanks for the work!

[lawr1000]

What nodes should I see under the 2477SA2 Load Controller?

 

I still only see one on 2.8.2.

[Michel Kohanim]

Hello lawr1000,

 

You should only see one. A load controller is no different than a SwitchLinc Relay ...

 

With kind regards,

Michel

[ceaves]

In 2.8.2, my Current State Field just goes blank. If I reboot the ISY, it comes back. Even querying the device does not populate the field.

 

I don't know, but I think this worked fine in 2.7.*

[Michel Kohanim]

Hello ceaves,

 

There are two explanations for this:

1. Java cache was not cleared properly

2. Firewall issues ... please do ensure that ISY's IP address is in the Trusted/White list on your firewall

 

With kind regards,

Michel

[dougos2]

I upgraded to 2.8.2 and my programs stopped working. Any program that checks the status of any switch will not function. Direct control in programs does function however. The admin console shows the correct status and it changes correctly. the event viewer also indicated correctly that the changes are being received. However no "if status" or "if control" program functions are working at all. I tried to downgrade back to 2.8.1 but no luck. Any ideas???? Thanks

[Michel Kohanim]

Hello dougos2,

 

This is quite strange: if the event viewer shows that ISY actually receives device statuses, then the program MUST be evaluated as soon as the events are received.

 

Two questions:

1. In Program Summary tab, can you please ensure that all your programs are enabled?

2. For those programs that you are having issues, please

a. Check the last run time, last finish time columns

b. Turn on/off a device to cause a program to run and then check the last run/finish times

 

With kind regards,

Michel

[dougos2]

To answer your questions.

 

All programs are enabled and I even sightly modified one and resaved it.

 

The last run time and finish times are blank and never change despite activating the devices. The devices do change their status in the command console correctly but do not initiate the programs.

 

I fixed it by doing a factory reset and reloading the backup configuration. I did save the corrupted configuration and tried reloading it and it caused the same error. Clearly my configuration became corrupted during the upgrade and maybe this will help others.

 

Backup is very important before all firmware updates!

[Michel Kohanim]

Hello dougos2,

 

Thanks so very much for the update!

 

With kind regards,

Michel

[rlrjupiter]

I so wished I had written down the sequence that caused this issue because I can't reproduce it now.

 

Essentially I followed the upgrade instructions to 2.8.2. When ISY99 restarted it did indeed ask me to agree to some new terms and opened a html page in IE9 beta. I agreed, but when I went back and focused the ISY admin window, there was a small pop-up that said something to the effect that agreement not authorized and is closing.

From that point on all current devices worked normally, but when I tired to add the Morninglinc, I got a "no network available" (once) and the add of the device failed (wish I had writen down the error). When I tried again to add the morninglinc device, I get no errors, just a short delay and the add device window goes away. If I try to add any other insteon device, it would work with no issues.

I tried reverting back to 2.7.15 firmware then going forward again to 2.8.2, but have not been able to get back to a point of seeing the "agreement" window request in the ISY99 admin window or IE that I saw when I first started 2.8.2. I thought maybe if I could get back to that agreement window I could resolve the problem. Essentially get past the ISY99 error on not agreeing to the new terms.

I did follow the instructions for an updated certificate, but that had no effect on the problem. I cleared Java cache on each change of the firmware.

So I finally just backed back out to firmware 2.7.15.

 

Any ideas on how I can get 2.8.2 firmware install to act like a fresh install, so it will ask me the "agreeement" question and possibly enable the "network connection" needed to attach the Morninglinc device?

 

Also I have another question concerning 2.8.2. Is it compatable with Mobilinc Iphone app 2.17.00? Because I could not get it to load correctly after the 2.8.2 update, but could possibly be associated with the above issue where it did not seem to complete installation.

 

Really sorry for the lack of detail on my problem, but just can't seem to get 2.8.2 to act like a fresh install again. If I had a repeatable problem on the Morninglinc add error or the get the "agreement" pop-up again, I could provide more detail, so please understand.

[Michel Kohanim]

Hello rlrjupiter,

 

I am so very sorry for the inconvenience. First of all, once you agree to the terms and conditions, your agreement is stored in ISY and no longer would the Admin Console pop up the dialog.

 

Now, No Network means that during the process, ISY was trying to renew the lease on your router and it failed. Sometimes this happens but it should not impact anything else.

 

As far as adding MorningLinc, please do be kind enough to use the third option (import existing links). In all likelihood, your morninglinc has already been added to ISY. If you wish, you can remove it, make sure it's linked to the door lock and then redo the process making sure you choose the third option.

 

As far as MobiLinc, that's a question for MobiLinc forum and unfortunately I do not know the answer.

 

With kind regards,

Michel

[Candide]

I upgraded to 2.8.2, from 2.7.15 and all appeared to be fine.

Programs ran and all devices functioned - except a Motion Detector (2420M).

 

Dusk was not reported properly, read 'off' when dark.

Dusk was also triggered simultaneously with any detected motion, when dark.

 

I have reverted to 2.7.15 and, so far, it is functioning as it should.

I will let it go for a couple days and see how it goes, but 2.7.15 was functioning properly for a long time.

[rlrjupiter]

Hello rlrjupiter,

 

As far as adding MorningLinc, please do be kind enough to use the third option (import existing links). In all likelihood, your morninglinc has already been added to ISY. If you wish, you can remove it, make sure it's linked to the door lock and then redo the process making sure you choose the third option.

 

With kind regards,

Michel

W7 64bit isy99 2.8.2 - Java 1.6.0-17

 

Can't find the Morninglinc 2458a1 address in any of the link tables. But I was able to reproduce the error when adding the device under firmware 2.8.2. Could I have a bad device, which is strange because I was able to program device to activate locks and able to link device manually to a desktop controlLinc "button" controller.

 

If I do a link query on the Controlinc it shows the Morninglinc device on button 5 as

0FC8: E2 05 15.14.D9 05 00 02

But if I do a query at the Admin Console on the controlinc (button 5 - manages) it refuses to show the link I made between the two devices.

 

Error when adding and defining device as MorningLinc and using last option "keep existing links" as you asked above. Pop-up window on add.

[-2000000]"Node not added - failed restoring device [15 14 d9 1]

 

Error in event log.

Mon 09/27/2010 11:07:34 AM : [15 14 D9 0 ] MorningLinc not manually linked, cannot read device database.

 

Mon 09/27/2010 11:07:34 AM : [ 15 14 D9 1] Cannot validate device, ignoring node

 

Mon 09/27/2010 11:07:34 AM : ---- All Remaining Device Added

 

----------------problem resolved------------------------------------

 

I had been trying to add the device via the "add device" icon where you select the device "morninglinc" or let it query the device. Never worked and the errors are above.

 

But then tried the "start linking" way of adding devices and it found the device right away and found the link to the controllinc with no issues.

So fair warning, don't bother to add the device manually, use the "Start Linking" option and option three to keep existing links.

 

I've always added my device manually one at a time, but your note started me thinking that if I could add a manual link outside ISY, then I ought to be able to read those links somehow.

 

Working and happy, thanks so much for your time.

[Michel Kohanim]

Hello rlrjupiter,

 

Thanks so very much for the update: my bad since I had not read the instructions correctly myself.

 

Candide, I am not sure why you would have those conditions. INSTEON code has not been changed since 2.7.15. Please do be kind enough to try 2.8.2 again later and report back. Also, it's working fine here.

 

With kind regards,

Michel

[Candide]

I just tried it again - upgrading from 2.7.15 to 2.8.2 - and the same thing happens. The ISY logs show that thge desk/dawn setting is being triggered at the same time as motion.

 

When I drop back to 2.7.15 everything is normal.

Are there any steps I can take to troubleshoot this?

 

Thanks...

[Michel Kohanim]

Hi Candide,

 

Thanks so very much for retrying. I think the problem is in 2.7.15 and not 2.8.2. Please wait for 2.8.3 wherein you can actually set all these modes and, at the least, we will know what the settings are before arriving at any conclusions.

 

With kind regards,

Michel

[bmarsh]

I updated to 2.8.2 from 2.7.14 I am running linux and using Java 1.6.0_21 and also the java app to run an 99I without a browser. Has been working fine through 2.7.10 - 11 - 12 - 13.

 

But with 2.8.2, it would not show unit status (blank) as other people have reported. If I used a browser, than it would work ok. So it is a java issue but I cleared all cache but no help. Did several boots of the 99I. And also, under the Java app, it would not let me downgrade to 2.7.14 but gave an error.

 

I had decided that I would have to go the browser route but then decided to try the downgrade under the browser, and it worked.

 

So now I am back to 2.7.14 and using the Java app and everything is working find again.

 

There must be a problem with 2.8.2 somewhere. Will try again when 2.8.3 becomes available.

[Candide]

Hi Candide,

 

Thanks so very much for retrying. I think the problem is in 2.7.15 and not 2.8.2. Please wait for 2.8.3 wherein you can actually set all these modes and, at the least, we will know what the settings are before arriving at any conclusions.

 

With kind regards,

Michel

 

Sure, that's no problem, thanks for the reply.

It seems to work correctly on 2.7.15

 

Also, the 2420 is set to only trigger motion when dark and is running on a 9v transformer (no battery) and the jumper "to allow it to be managed" (jumper 5) is not set.

 

Thanks...