Release 3.1.6 (Beta) Is Now Available

[Michel Kohanim]

Hello all,

 

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

this post.

 

IMPORTANT

1. Since we added support for 2048 bit SSL, we had to change some of the networking libraries so as to make sure the overall system performance is not impacted. For instance, during key handshake, in previous releases, most other sub tasks would stop. In this release, those sub tasks continue to function although at a slower pace (the CPU is hard at work). As such, please do be kind enough to watch for any network anomalies.

 

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:

- New supported devices

- Network activity

- ELK causing system hang. Please DO NOT UPGRADE REMOTELY if you have this issue

 

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, 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)

 

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

ISY 99i Series

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

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

 

Dashboard - not fully supported

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

 

 

Thanks and with kind regards,

Michel

[sanders2222]

Michel, Thank you for this timely update. I'm happy to report my notifications are working again!

 

I'll re-check a couple of my programs where variables were not being evaluated correctly UNLESS all conditions were all enclosed in 'outside' parenthesis. I'll remove the outside parenthesis (if I can find them) and see if that issue has been resolved.

[elvisimprsntr]

Michel,

 

Thank you for addressing the Elk lockup issue! I confirmed the ISY does not lockup in all the scenerios i previously could induce the problem.

 

Elvis

[Brian H]

Updated with no major problems.

I am getting a failed to retrieve product update information warning when I start the Administration Console.

 

Actually that message started to show earlier today. Maybe while you where getting 3.1.6 ready to be downloaded.

[klundy]

I concur with Sanders. Update went fine and alerts using a TLS server appear to be working much better. 100% of a small sample set (10).

 

Kevin

 

 

Michel, Thank you for this timely update. I'm happy to report my notifications are working again!

 

I'll re-check a couple of my programs where variables were not being evaluated correctly UNLESS all conditions were all enclosed in 'outside' parenthesis. I'll remove the outside parenthesis (if I can find them) and see if that issue has been resolved.

[ryarber]

Install went well. How do I test for the ELK bug? I know I've had it, but I don't know how to reproduce it.

[elvisimprsntr]

Install went well. How do I test for the ELK bug? I know I've had it, but I don't know how to reproduce it.

 

Assuming your Elk is already running the latest firmware (most recent July 2011) and you have the Elk and ISY configured to communicate to one another, older ISY firmware (< 3.1.6) would lock up when you do one of the following:

1. Use the Elk RP software to change a XEP setting that requires a reboot or you can manually reboot the XEP

2. Reboot your router that is between your ISY and Elk.

 

While I am sure there may be other ways to have induced the problem, if your ISY does not lock up using the above methods, then I believe the problem is resolved.

 

Elvis

[Candide]

Upgraded from 3.1.5 - so far so good, notifications are working (no 'body' error), Wbug is getting data.

 

Will update about any issues.

 

 

Thanks....

-------------------------------------------------

Update @ 12:30 PM

 

So far only one wbug error:

Sat 2011/08/13 11:30:59 AM System -140005 CLI-WBug

 

Update @ 7:30 PM

 

Total of only three wbug errors so far:

Sat 2011/08/13 11:30:59 AM System -140005 CLI-WBug

Sat 2011/08/13 02:27:41 PM System -140005 CLI-WBug

Sat 2011/08/13 06:03:47 PM System -140005 CLI-WBug

 

Same station, same update interval.

Seems like a definite improvement!

[IndyMike]

Revision 3.1.6 downloaded and installed without issue.

 

Attempted a link table read from my 2876SB Icon V.39 using I2 protocol - no go. There is some upside. Previous revisions of the ISY firmware really wouldn't communicate much at all with this device in I2 mode. With rev 3.1.6 things are a bit more clear.

 

The ISY appears to be reading from start address 0FFF while the device is responding with start address 00FF. The ISY rejects the response and then "errors out" after 3 attempts (log below). The data reported by the Icon is correct for the first link record.

 

I believe this is due to the smaller link table in the more recent versions of the Icon switch (verified by LeeG some time ago). Not sure that I can call this a bug. Just another difference in the module configuration (exception) that needs to be accounted for in the ISY. Sorry guys, I've lost track of the number of "exceptions" and "workarounds" that you've already implemented. This may be another one for the list.

 

IM

 

Sat 08/13/2011 12:29:33 PM : [14 78 3B 1 ] Querying engine version

Sat 08/13/2011 12:29:33 PM : [iNST-ACK ] 02 62 14.78.3B 0F 0D 00 06 (00)

Sat 08/13/2011 12:29:33 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 0D 01 (01)

Sat 08/13/2011 12:29:33 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 08/13/2011 12:29:33 PM : [14 78 3B 1 ] Retrieved engine version is i2

Sat 08/13/2011 12:29:34 PM : [14 78 3B 1 ] Using engine version i2 for 'BSMT Bed'

Sat 08/13/2011 12:29:34 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) {isy requesting data from address 0F FF}

Sat 08/13/2011 12:29:34 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00)

Sat 08/13/2011 12:29:34 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 08/13/2011 12:29:34 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00 {icon responding with data from address 00 FF}

Sat 08/13/2011 12:29:34 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Sat 08/13/2011 12:29:34 PM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored {response rejected due to invalid address range}

Sat 08/13/2011 12:29:43 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) {read attempt #2}

Sat 08/13/2011 12:29:44 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00)

Sat 08/13/2011 12:29:44 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 08/13/2011 12:29:44 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00

Sat 08/13/2011 12:29:44 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Sat 08/13/2011 12:29:44 PM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored

Sat 08/13/2011 12:29:53 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) {read attempt #3}

Sat 08/13/2011 12:29:54 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00)

Sat 08/13/2011 12:29:54 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 08/13/2011 12:29:54 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00

Sat 08/13/2011 12:29:54 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Sat 08/13/2011 12:29:54 PM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored

Sat 08/13/2011 12:29:58 PM : [All ] Writing 0 bytes to devices

[k7zpj]

Upgraded to 3.1.6 with no issues.

 

I am still getting the -14005 CLI-WBug errors.

 

In approximately 23 hours I had 40 of the -14005 errors.

 

Regards,

Bruce (K7ZPJ)

[Michel Kohanim]

Hello IM,

 

Ah ... this is not good and it seems that we have to add more exceptions! What happens when you use i1 (regular PEEK/POKE)?

 

Hello Bruce,

 

The error is related to how long ISY waits for a response from the server. Currently, it's set to 5 seconds which is already way too high. May I ask what's your polling interval?

 

With kind regards,

Michel

[wannab]

I upgraded to 3.1.6 (Beta) with no issues. I am still trying to add a new thermostat that doesn't seem to connect, high watermark error. The thermostat is the new Venstar (Item# 2491T7E) Thermostat - INSTEON Integrated Remote Controle Thermostat 7-Day Programmable. I was told this beta would include the needed support to add this new thermostat that has the embedded INSTEON adapter. Should the be connecting?

 

Regards,

 

Martin

[IndyMike]

Hello Michel,

 

I1 (peak/poke) operations work fine with the Icon. It's the I2 read/write operations that present a problem.

 

As expected, I2 restore operations fail for the same reason as the link read operation.

 

Honestly, not that big a deal with the Icon since it doesn't have that many links. Just need to make sure that "Automatic messaging" is checked in the ISY options to enable the I1 mode. If this were a KPL, I'd be whining a bit more.

 

Thanks for the prompt reply,

IM

[k7zpj]

Hello Bruce,

 

The error is related to how long ISY waits for a response from the server. Currently, it's set to 5 seconds which is already way too high. May I ask what's your polling interval?

 

I have the polling interval set to 600 seconds.

This was in response to my ISP complaining about frequent/repeated traffic to the Weather Bug site and me probably misunderstanding what the polling interval does.

 

What is a reasonable setting for the polling interval ?

 

 

Regards,

Bruce

[Michel Kohanim]

Hi Bruce,

 

Thank you. Polling interval means the duration in time between requests to WB. 60 seconds is default and I do not think your ISP would mind 60 seconds. But, anything below that will have two side effects:

1. WB service might consider you a hacker and then block traffic from your ISY

2. Your ISP might consider you a hacker and then block traffic from your ISY

 

With kind regards,

Michel

[Michel Kohanim]

Hello IM,

 

Can you do me a favor?

 

Would you please use the Tools | Diagnostics menu item to retry and then choose your begin/end address (check the box next to the address). I tried this with one of our I2 devices and it seems to work fine. This said, unfortunately I do not have any Icons to test with.

 

With kind regards,

Michel

[IndyMike]

Hi Michel,

 

Great idea - I had forgotten about the manual scan. The manual scan works like a charm using a start address of 0x00F8.

 

Sun 08/14/2011 08:43:02 PM : [14 78 3B 1 ] Using engine version i2 for 'BSMT Bed'

Sun 08/14/2011 08:43:02 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 00 FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Sun 08/14/2011 08:43:02 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00)

Sun 08/14/2011 08:43:02 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sun 08/14/2011 08:43:02 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 FF 01 A2 00 13 22 F9 FF 1F 00 00

Sun 08/14/2011 08:43:02 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Sun 08/14/2011 08:43:03 PM : [iNST-ACK ] 02 62 14.78.3B 1F 2F 00 00 00 00 F7 01 00 00 00 00 00 00 00 00 00 06 (00)

Sun 08/14/2011 08:43:03 PM : [iNST-SRX ] 02 50 14.78.3B 13.22.F9 2B 2F 00 (00)

Sun 08/14/2011 08:43:03 PM : [standard-Direct Ack][14.78.3B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sun 08/14/2011 08:43:04 PM : [iNST-ERX ] 02 51 14 78 3B 13 22 F9 11 2F 00 01 01 00 F7 01 A2 10 13 22 F9 FF 1F 00 00

Sun 08/14/2011 08:43:04 PM : [Extended-Direct][14.78.3B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Sun 08/14/2011 08:43:04 PM : [All ] Writing 0 bytes to devices

[Michel Kohanim]

Hi IM,

 

Thanks so very much. I totally understand that the Admin Console must figure out the database size automatically but, if you don't mind, I would like to leave this as a very low priority since there's a workaround.

 

Please advise.

 

With kind regards,

Michel

[Candide]

Hello Bruce,

 

The error is related to how long ISY waits for a response from the server. Currently, it's set to 5 seconds which is already way too high. May I ask what's your polling interval?

 

I have the polling interval set to 600 seconds.

This was in response to my ISP complaining about frequent/repeated traffic to the Weather Bug site and me probably misunderstanding what the polling interval does.

 

What is a reasonable setting for the polling interval ?

 

 

Regards,

Bruce

 

I set my polling interval to 240 seconds (4 minutes).

[IndyMike]

Hello Michel,

 

The Icon is fully functional when used in the "Automatic" messaging mode which the ISY defaults to. Issues only arise when the user manually switches to the "Device reported mode".

 

I completely agree with your assessment of the priority. I noted the addition of I2 support for the Icon in the release notes and wanted to give feedback.

 

Sincerely,

IM

[Michel Kohanim]

Thanks so very much IM.

 

The i2 support for ICON was a different issue:

1. i2 as data transfer mode ... for this ISY fails since ICON returns an address which ISY does not expect

2. i2 as command mode ... we could not support this since during initialization, #1 failed

 

So, in essence, we have now added an exception for ICON dimmers such that regardless of 1, ISY will always try i2 commands for backlight and other features.

 

With kind regards,

Michel

[Morris Hansen]

I upgraded a couple days ago without any issues.

 

Tonight I got home and noticed my Elk was not triggering the ISY. It worked earlier today but seemed to stop. I had to reboot ISY to recover. I did not access ElkRP at all since the update.

 

Any ideas?

[Michel Kohanim]

Hello mohansen,

 

Sincere apologies for tardy reply ... was trying to reproduce alas failed.

 

Can you please let me know whether or not other ISY programs were running? I assume you didn't have regular browser access to ISY either, is that correct?

 

Would you be kind enough to send me your error log to support@universal-devices.com?

 

With kind regards,

Michel

[Morris Hansen]

In the past when this happens, I was never able to access the ISY via the browser. I didn't try it this time.

 

The only programs I have are for Fast On / Fast Off to control some scenes. 90% of my logic is in the Elk.

 

I have emailed my error log.

 

If you need access, I can provide that as well.

[polexian]

Is there anyway to do an automatic requery of a device when it's link is broken and then if not reset the isy?

 

 

---

- Sent from my iPhone using Tapatalk