Jump to content

Release 3.1.13 (Beta) Is Now Available


Michel Kohanim

Recommended Posts

Hello all,

 

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

this post. This is a minor release with mostly ELK module bug fixes and enhancements:

1. Support for thermostats in ELK

2. Reliability enhancements

 

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

 

Important Information

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.

 

4. 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 B) if you are using DSCLinc and WebLinc, your programs may behave a little differently. Please do test your network resources thoroughly

 

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

 

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

 

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

 

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

 

Things to test:

- ELK Module (if you have ELK)

- Device Restore, Replace, and scene settings

- Adjusting scenes within programs continuously

 

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.13 - applet

f. http://www.universal-devices.com/99i/3.1.13/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

Link to comment
Share on other sites

Installed. A few things I noticed:

 

I have a M1KP2 and A P212S. To the elk system they are keypads but neither of them have temperature sensors. UNder the keypads tap they show -40 degrees.

 

Also on input 15 i have a M1ZTSR temp sensor. The temp is correct. On input 16 of the M1 I have a fire zone shows -60 degrees.

 

 

Under config-elk-config the refresh topology is greyed out. Is this only available after a change has been made to the M1 programming or should it be available all of the time. I haven't made any changes on the ELk programming since upgrading from 3.1.12 to 3.1.13.

 

Edit: I logged out and cleared java cache again and now the refresh topology is visible.

Link to comment
Share on other sites

Just tried upgrading and i am having a couple problems.

 

1) When trying to backup my ISY, I receive an error - "Could not create a zip file."

 

2)When I try the manual upgrade without backing up, I get an error "Socket Open Failed java.net.sockettimeoutexception"

 

Any suggestions. Also, even after Michel reactivated my Elk module because I installed it before upgrading, the ISY is very sluggish when I am in the Security section.

 

Is anyone having these issues. Is the ISY as responsive in the Security section as it is everywhere else?

 

Thanks

Link to comment
Share on other sites

Hi gatchel, we'll look into it.

 

Hi midrar, this is not normal at all. Please open the Event Viewer on Device Communications level. Make sure ISY can in fact make connections with your M1XEP. In 3.1.12, if ISY could not connect with M1XEP, it would get into a tight loop and thus would feel sluggish.

 

As far as not being able to backup, what's the error (i.e. could not backup /CONF/xxx.yyy)? You are welcome to send an email to me directly.

 

With kind regards,

Michel

Link to comment
Share on other sites

A problem with elk program.

 

I have a program to turn on my garage lights and the first part isn't working.

 

  • Elk Zone 'Den Garage Door' is Violated
    And Elk Zone 'Main Garage Door' 'Physical Status' is Short <-This line is the one not executing, but the physical status when I open the door is "Short"

 

If
       (
            Elk Zone 'Den Garage Door' is Violated
        And Elk Zone 'Main Garage Door' 'Physical Status' is Short
       )
    Or (
            From    Sunset 
            To      Sunrise (next day)
        And Elk Zone 'Main Garage Door' is Violated
        And (
                 Elk Zone 'Den Garage Door' is Violated
            )
       )

Then
       Set 'Equiptment / Garage / LightGarageWorkbench' Query
       Set 'Equiptment / Garage / LightGarageWorkbench' On
       Stop program 'GarageLightOff'
       Run Program 'GarageLightOff' (If)

Else
  - No Actions - (To add one, press 'Action')

 

This program now works, have to reboot the isy to get the programs with elk module inside of them.

Link to comment
Share on other sites

This time program is executing 8 seconds early. If I put it in a folder, and check if elk status is disarmed, it will never run.

 

If
       From    11:27:00PM
       To      11:27:25PM (same day)

Then
       Set 'Equiptment / LivingRoom / OutletTVWallLR' On

Else
       Set 'Equiptment / LivingRoom / OutletTVWallLR' Off

Link to comment
Share on other sites

After upgrading to .13 some things starting acting wonky. I could turn my lights on and off with the RemoteLinc but the ISY wouldn't report the correct on/off status. I then noticed that I was missing some devices from my scenes. Only in one room most of the scenes were missing devices.

 

I assumed that that the links in the devices were intact but were missing in the ISY since the controls actually worked, the status just wasn't being updated (which messed with some programs).

 

I tried my backup from .12 to restore the ISY but the scenes were still missing devices.

 

Not really knowing what I was doing:

 

1. I restored all the devices that participated in the bad scenes hoping to get the devices and the ISY in sync (didn't do anything noticeable)

2. Added the missing devices back into the scenes. It seems the ISY doesn't add links to a device if they already exist because the write was really fast.

 

Everything seems to be working now. I hope I haven't created extra unused links in my devices.

Link to comment
Share on other sites

Hello andyf0,

 

I do apologize for the inconvenience. The fact that scene were missing is quite troubling ... is it possible fo you to restore a 3.1.9 backup and see if your scenes show up?

 

polexian,

 

Unfortunately I will have to leave the answer to your questions for our guru who's taking a well deserved breather for a couple of days.

 

With kind regards,

Link to comment
Share on other sites

Hi Michel,

 

Unfortunately I don't have a backup from 3.1.9 and even if I did the scenes were not the same back then. I've been doing some extensive work in the last couple weeks with KPL buttons indicating whether I left anything on when I leave the house.

 

I do seem to be up and running now and I've saved a backup which I will keep.

Link to comment
Share on other sites

.13 installed fine. I like how the tabs with the Elk information were rearranged. Looks great! And now thermostats! I will be busy this weekend moving over thermostat rules. So far ALL my Elk rules are just so much more comfortable living in the ISY!

 

Sent from my SCH-I510 using Tapatalk

Link to comment
Share on other sites

I am trying to use 3.1.13 with the Elk module.

I am using the admin Console App on a Mac.

After connecting to my ISY-99i/IR Pro, I can click between the Main and Config tabs just fine.

If I click on the Programs Tab or Elk tab, the admin console becomes unresponsive and eventually shows an empty alert window with a title of "Security Warning"

 

After a very long wait (several minutes) I got a an Error alert "Socket Open Failed java.net.SocketTimeoutException"

 

And after that, the Security Warning alert finally filled out with text and buttons saying "ISY is currently configured with the default SSL certificate..."

 

I've tried several times to generate and install a new self-signed certificate without luck.

 

I have cleared the Java cache and restarted the machine.

 

Any suggestions?

Link to comment
Share on other sites

I need to know that ISY is connected and communicating to ELK at all times. I tried writing a test program to check the connection state "IF Elk System is Connected" or "IF Elk System is Enabled" and they are always false. I do have an active connection because I can change a output and also see a zone status change in real time in the ISY admin app.

 

Seems that System is Connected or Enabled are not functional. What am I missing?

Also what the difference between Connected & Enabled?

 

If ELK-RP steals the connection, will ISY reconnect automatically when ELK-RP releases the connection?

 

Thanks

Frank

(3.1.13 Installed)

 

 

Here's the simple program I used to test the functionality:

If

Elk System is Connected

Then

Set '2nd Floor / Master BedRm_Floor Lamp Lt' On

Else

Set '2nd Floor / Master BedRm_Floor Lamp Lt' Off

Link to comment
Share on other sites

andf0,

 

Unfortunately the problem was the migration from 3.1.9 to later releases as noted by IM and LeeG. If you do not have 3.1.8/9 backup, then the best thing to do would be to add those devices/scenes back.

 

ooker,

 

Please do make sure:

1. You have cleared your Java cache

2. You are using http://www.universal-devices.com/99i/3.1.13/admin.jnlp

 

If you are still having problems, please contact our tech support so that we can login and do root cause analysis.

 

FRR,

 

You do not want to use Enabled because as long as you have ELK enabled in the configuration panel, then the condition is always true. Or, perhaps, you would want to use AND instead of Or.

 

With kind regards,

Michel

Link to comment
Share on other sites

If I try to connect to my ELK M1 Gold (using the network) with the ELK RP software when my ISY-99i is powered up, I get a lot of errors, and it is very slow. If I unplug the ISY-99i, I can communicate with the ELK M1 from the ELK RP software just fine.

 

Is this expected behavior with v3.1.13? I only just added the ELK and the ELK module, so I can't compare with previous releases of software for the ISY-99i

 

I have the latest firmware on the ELK and on the ELK ethernet module.

 

Also, regarding my previous post the issue is not specific to the mac for me. I've tried accessing the admin console via the standalone app and via the link from the web interface. I can typically click quickly between the Main tab and the Configuration tabs, but if I click on the Programs tab it can take minutes to come up or will get a socket error.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

    • There are no registered users currently online
  • Forum Statistics

    • Total Topics
      36.9k
    • Total Posts
      370.6k
×
×
  • Create New...