Release 3.1.12 (Beta) Is Now Available

[Michel Kohanim]

Hello all,

 

I am happy to announce the availability of our 3.1.12 release! For a list of changes, please take a look at

this post. This is a major release:

1. Support for ELK Integration Module ($99.00 ... 40% off during Beta using coupon code elk-module-beta). Please note upgrade to 3.1.12 must be performed before installing the ELK Module

2. Reliability enhancements

 

IMPORTANT

1. Please note that Network Resource modules are now running in their own task. This might have some ramifications as calling network resources from programs no longer waits for the resource to complete. As such, a) you will experience quicker handling of network resources/programs and if you are using DSCLinc and WebLinc, your programs may behave a little differently. Please do test your network resources thoroughly

 

2. 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.

 

3. 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

 

4. 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

 

 

Things to test:

- ELK Module (if you have ELK)

- Device Restore, Replace, and scene settings

- Adjusting scenes within programs continuously

- Network performance and status

- Network resources and programs

 

 

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

 

 

Notes:

1. ISY-26 is no longer included in the firmware builds

2. Due to the sensitive nature of supporting MorningLinc/ELK Security Systems, users now must agree to terms and conditions upon Admin Console start up otherwise the dialog keeps popping up every time the Admin Console is started

3. 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 before the upgrade.

 

 

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. Important (If upgrading from 2.8.5 through 2.8.14)

Due to invalid Java certificate chain, please make sure to remove all Universal Devices certificates from Java:

a. Close all browser sessions

b. Open Java Control Panel (Java Preferences on MAC)

c. Click on the Security tab. Remove all Universal Devices certificates (on MAC, click on the '-' button at the bottom)

e. Clear your Java Cache

 

 

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

 

5. Choose the file saved in step 2

 

MAC users: if upgrade fails, please add https://your.isy.ip.address to ISY Finder (see 3f above)

 

6. After the upgrade, ISY reboots. Please do ensure to clear your 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. 99/994i - http://isy/admin - applet (Windows only)

b. 99/994i - 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/3.1.12 - applet

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

 

Dashboard - not fully supported

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

 

8. Please backup your system again

 

Thanks and with kind regards,

Michel

[ryarber]

 

All smiles here. 3.1.12 downloaded and installed fine. Module purchased, installed, and ready to play with(ahem, sorry. I meant ready to work on).

 

Can't wait to get home from church tonight so that I can mess around with it.

[polexian]

Upgraded to 3.1.12 and installed the elk module, I am impressed. The security system now has it's own tabs and it is very detailed. They have truely outdone themselves on this one. I would suggest everyone purchase this elk module who has the elk system. I can't wait to play with it some more! Truely worth the wait!

[Moshe]

Installed 3.1.12. Everytime I start admin console I get error message: Request failed.

 

Any ideas.

[LeeG]

Installed 3.1.12 with no issues. Really appreciate the UI level in the Help | About. Thank you again.

[apostolakisl]

Installed 3.1.12. It needed a power cycle after the install as it locked up. After the power cycle all seems to be fine.

 

Installed Elk module. No problems there.

 

So far so good on playing with the Elk zones/outputs/status'/etc.

 

Just doing some stupid stuff right now. ISY makes the security system say "seven" when I open the back door. Good news is, that is what I programed it to do!

[apostolakisl]

So far this all seems very simple and self explanatory. You guys included a ton of stuff, even individual keystrokes on the keypads.

 

The main question I have at this point is what things will act as triggers. So far, everything I have tested behaves as a trigger.

[apostolakisl]

Is it possible that installing the Elk module has changed the indexing of lights on elk side? Since installing the module, Elk executed rules are now controlling the wrong lights.

[sanders2222]

For a little different approach, I upgraded to 3.1.12 and added the Elk Module. My ELK M1 is still in the shipping packaging and hasn't been hooked up.

 

All seems to to be working correctly so having the horses before the cart seems to have worked! Good work U-D as it appears you've thought of everything (again).

 

Now it's time for me to open my package and replace my 30 year old security system with the ELK.

[polexian]

Elk: Under configuration/security system/outputs, the status doesn't say on, it is blank.

 

Also, I only had 2 outputs turned on with show checked. So, in the isy I can only see outputs 3, 41 and 65-208. How do I get the others to show? I checked them in the elk to show, updated it to elk, then rebooted the isy. that didn't work.

 

Joe

[Sparks]

Looks like installing the firmware and ELK module does monkey around with the X10-esque addressing between ISY and ELK. All my lights are working incorrectly with ELK rules now.

I have had to "add" all devices in the "export" tab of the new Security system module to assign X10 addresses, then export to XML, import XML to ELK lighting module, and then edit all the ELK rules because most of the addressing changed. It's worth it to get the long-awaited ISY functionality, but seems like a bug as all previous firmware upgrades have always managed to preserve the ELK X10 addressing.

I'll be moving all my ELK rules to ISY now anyways.

Thank you Michel and the ISY team! It's been a most anticipated upgrade.

[polexian]

Elk: Under configuration/security system/outputs, the status doesn't say on, it is blank.

 

Also, I only had 2 outputs turned on with show checked. So, in the isy I can only see outputs 3, 41 and 65-208. How do I get the others to show? I checked them in the elk to show, updated it to elk, then rebooted the isy. that didn't work.

 

Joe

 

 

Cleared java cache and it fixed the status output indicator. still having trouble with the outputs.

[apostolakisl]

Looks like installing the firmware and ELK module does monkey around with the X10-esque addressing between ISY and ELK. All my lights are working incorrectly with ELK rules now.

I have had to "add" all devices in the "export" tab of the new Security system module to assign X10 addresses, then export to XML, import XML to ELK lighting module, and then edit all the ELK rules because most of the addressing changed. It's worth it to get the long-awaited ISY functionality, but seems like a bug as all previous firmware upgrades have always managed to preserve the ELK X10 addressing.

I'll be moving all my ELK rules to ISY now anyways.

Thank you Michel and the ISY team! It's been a most anticipated upgrade.

 

I think I am going to skip the export/import and just re-write the rules as programs in ISY and delte them from Elk.

 

 

It looks like the module does not include any provision for "tasks". I am trying to figure out how it would work to get ISY programs to respond to a task executed from an Elk keypad.

[automateme]

I was able to upgrade my ISY to 3.1.12, and install the ELK Module without any issues. When I go to the Security System tab, none of the information related to my Elk is populated - everything is empty and only the column labels are displayed. An additional issue is that the M1G integration module for Homeseer no longer works to control my lighting through the ISY. This was not an issue before 3.1.12 and the Elk module. I will continue to do some troubleshooting to see if I can determine where things broke.

 

EDIT: I see that I have to include my alarm code in the saved configuration. I now have all of the information related to my Elk populated, but still can't get Homeseer/Elk to control the lighting through the ISY.

[polexian]

When I reboot the isy from the system menu, my programs tab doesn't display anything until I clear my java cache.

[hagak]

Ok so I installed the update and the elk module but I do not see the security tab. What steps am I missing?

[apostolakisl]

Ok so I installed the update and the elk module but I do not see the security tab. What steps am I missing?

 

Did you clear your java cache?

[Michel Kohanim]

Hello all:

 

Moshe, that's not normal. Please do submit a ticket so that we can log into your computer and see what's going on.

 

idmills, we shall look into it.

 

hagak, two cases: either you installed the module before upgrading to 3.1.12 or you need to clear your Java cache.

 

polexian, can you verify that your UI version is 3.1.12 (Help | About). It's always best to use http://www.universal-devices.com/99i/3.1.12/admin.jnlp (after clearing your Java cache).

 

automateme, can you explain what you mean by HomeSeer not working? How did it work before? Please note that you will have to re-export your lighting after you configure it again (you can now choose devices that have to be exported to ELK).

 

With kind regards,

Michel

[automateme]

Michel,

 

That was it. I had to re-export my selected devices and configure them into the Elk. From there, I had to delete all of the lighting devices in HomeSeer2, reload the Elk data into UltraM1G and create new HomeSeer lighting devices. Lighting control is working fine now.

 

Thanks!

[polexian]

Michel,

I am on firmware and UI version 3.1.12 I followed the link to open the ISY and the outputs are still not visible.

 

I checked in ekeypad on my phone and the outputs do show on it, so I know I have the show button checked on the elk side and it took.

 

I tried upgrading from 3.1.12 to 3.1.12 again, that didn't fix the output problem i'm having.

 

Update:

 

If I login to elk through the http and turn on one of the outputs, it then shows up on the isy output listing immediatly. Only one problem, the name is "--"

 

 

 

Joe

[andyf0]

Installed 3.1.12. Everytime I start admin console I get error message: Request failed.

 

Any ideas.

 

Same here

 

I submitted a ticket with access details.

[apostolakisl]

Installed 3.1.12. Everytime I start admin console I get error message: Request failed.

 

Any ideas.

 

Same here

 

I submitted a ticket with access details.

 

Did you try power cycling the ISY?

[hagak]

Ok so I installed the update and the elk module but I do not see the security tab. What steps am I missing?

I was being stupid and not following directions. I was launching the applet using the old link and not the new one listed in the first post. All good now

[andyf0]

Installed 3.1.12. Everytime I start admin console I get error message: Request failed.

 

Any ideas.

 

Same here

 

I submitted a ticket with access details.

 

Did you try power cycling the ISY?

 

Hmm! No I didn't, haven't needed to before. I'll try it when I get home this afternoon. I'm actually getting a different error message each time I login in now. Sometimes it's the Request Failed, sometimes it's "Subscriber didn't reply to Event: 1" and other times I get an SSL error. It doesn't seem to affect how the ISY works. Once you click OK on the error everything seems fine, programs work, lights turn and off etc. The Admin Console seems functional. My Error Log is really large now with many

 

10108 Check Log

10011 n/a

170001 [Auth -10104 or -10011]

 

repeating over and over again. MobiLinc HD works fine.

[LeeG]

"Subscriber didn't replay to Event: 1"

 

I am seeing a similar popup when the Admin Console starts. Does not seem to cause an actual problem as far as I tell.

 

 

 

EDIT: I do not have the ELK Module if that makes a difference.

 

EDIT2: these are the only messages in the error log from today when I started the Admin Console

 

Thu 2011/11/17 08:53:05 AM System -170001 [uDSockets] RSub:29 error:6

Thu 2011/11/17 08:53:10 AM System -170001 [uDSockets] RSub:29 error:6

Thu 2011/11/17 08:53:14 AM System -170001 [uDSockets] RSub:29 error:6

Thu 2011/11/17 08:53:19 AM System -170001 [uDSockets] RSub:29 error:6