Jump to content

Recommended Posts

Posted

Hello all,

 

I am happy to announce the availability of our 3.3.9 (RC6) release! For a list of changes, please take a look at this post. This is a minor release fixing minor bugs.

 

IMPORTANT If you have not already done so, please upgrade your Java to 1.7.11: viewtopic.php?f=44&t=10409 .

 

Know Issues

- None

 

Things to test:

- List in 3.3.7

- List in 3.3.8

- 2xx error code returns by a client to Network Resources should not cause an error

 

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

ISY 994i Z & ZS 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. Enable Java Plugin: http://www.java.com/en/download/help/di ... rowser.xml

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

c. http://isy.universal-devices.com/99i/3.3.9/admin.jnlp

d. Disable Java Plugin: http://www.java.com/en/download/help/di ... rowser.xml

 

Please note that both methods above should install an icon on our desktop which should be used instead of using a browser to access ISY.

 

Dashboard

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

 

8. Please backup your system again

 

Thanks and with kind regards,

Michel

Posted

Upgraded both Java 1.7.11 and 3.3.9 without issue.

 

-Xathros

Posted

I am having a rough day, and this is seeming to go on....I just read about the java problems and, sure enough, it was enabled in my browser. =(.

 

But, I wanted to upgrade my isy99i to the latest version. I followed the instructions and have upgraded the console, but, my firmware didn't upgrade.

 

What am I missing?

 

Thanks,

cats

Posted

Well, I installed the updated Java and 3.3.9 ISY program. Cleared cache. Rebooted PC.

 

I am able to run the Admin Console, but no matter what I do, there is no status shown for any device. Shut down and restarted console 5-6 times, rebooted 2 more times, but still no joy.

 

Any idea why I can no longer see any device status?

 

 

EDIT: OK, it appears to be related to the usage of Avast Anitvirus. When I disable Anitvirus, the device status seems to work fine. I will continue to test to make sure this is the problem.

 

EDIT 2: OK, I was able to resolve this. If you use Avast, do the following:

 

1. right click the icon in your tray and open user interface

2. select Real Time Shields

3. select Web Shield

4. select Expert Settings

5. put checkmark in "Scan traffic from well-known browser processes only"

6. Hit OK

 

I checked several times that this was the root cause by enabling and disabling this option in Avast. It correlated 100% with the ability to see device status in the ISY Admin Console.

 

All is now well in the world.

Posted

When I create a thermostat scene using a 2441TH thermostat with 3.3.9, the Fan State won't stick on Automatic. I set it to automatic, leave the scene, then return to find it set to On.

 

This appears to be a display issue only. The thermostat doesn't actually switch to fan always mode.

Posted

Perhaps a related issue: If I create a scene for multiple devices that include a thermostat in a Thermostat Mode other than Off, then go to one of the scene controllers and use the Copy scene attributes from... button, the controller's Thermostat Mode is changed to Off. It also appears to have swapped the heating and cooling setpoint.

Posted

Think I ran into a bug, just upgraded to 3.3.9 from 3.3.8 on my 99i. I have a program that runs every morning to ensure no lights get left on. Its:

 

If Time is Sunrise

or Time is Sunrise + 10 minutes

Then

Set Scene 'Main House Shutoff' off

 

It's 5:45pm (certainly not AM or sunrise) and when the ISY rebooted after the install the program both ran and evaluated true. It is *not* marked 'run at startup' so something about the evaluation fired. I now realize I've seen this before on other restarts but hadn't put it together so clearly until this one (so probably pre-exists 3.3.8).

 

I do have 'catch up' turned on but its set for 15 minutes so know where close to the times in question based on Sunrise.

 

Ideas?

Bill

Posted

Hi Bill,

 

There has been reports that the restore does not restore your time zone/location settings. The first thing I would do is to go to Configuration | Settings and make sure the time/timezone and location are all OK.

 

With kind regards,

Michel

Posted
Hi Bill,

 

There has been reports that the restore does not restore your time zone/location settings. The first thing I would do is to go to Configuration | Settings and make sure the time/timezone and location are all OK.

 

With kind regards,

Michel

 

Michael, this wasn't a restore, this was a simply upgrade from 3.3.8 to 3.3.9. In fact I can reproduce this 100% of the time now that I notice the issue by having the ISY reboot for any reason. Startup evaluation of something is broken, 'sunrise' should never eval to true (unless of course the unit was rebooted right around sunrise!).

Posted

I found another post talking about this, looks like this may be 'as designed' (but I'd suggest not 'as expected'). I thought that the catchup and the graceperiod worked together, but if catchup is truely from the previous midnight then the behavior makes sense. I think many folks believe that if catchup is checked then only schedules within 'missed schedule grace period' are executed. For my system it looks like I just one the missed scheduled grace period set but not set the catch up schedules at restart (going back 17 hours [in this case] after a restart seems way too long for whatever thats worth)

 

Catch up schedules at Restart - When this box is checked (default) the ISY will attempt to run all programs that are time dependent beginning at midnight until the present time.

 

Missed Schedule Grace Period - If Catch up schedules at restart is not checked or if a program is not run because the ISY is busy this will check for programs that were scheduled to run from the period specified until the present time. Default is 15 minutes.

 

Michel can you confirm the two options are independent and the second is not tied to the first?

 

Best,

Bill

Posted

Hi Bill,

 

Catch up schedules at Restart - When this box is checked (default) the ISY will attempt to run all programs that are time dependent beginning at midnight until the present time.

Correct!

 

Missed Schedule Grace Period - If Catch up schedules at restart is not checked or if a program is not run because the ISY is busy this will check for programs that were scheduled to run from the period specified until the present time. Default is 15 minutes.

Correct

 

Michel can you confirm the two options are independent and the second is not tied to the first?

I can confirm!

 

With kind regards,

Michel

Posted

bsobel-

 

Thank you for pointing this out. I was operating under the same assumption as you. Now, some occasional odd behaviors I had seen are starting to make sense.

 

-Xathros

Posted

Michel would you consider changing the ui text to something like 'catch up scheduled since midnight at restart?' I think that minor change would help clarify the intent.

 

Best

Bill

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.
  • Forum Statistics

    • Total Topics
      37.1k
    • Total Posts
      371.5k
×
×
  • Create New...