Release 3.1.7 (Beta) Is Now Available

[Michel Kohanim]

Hello all,

 

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

this post.

 

IMPORTANT

1. This is a major release with very many changes to address performance and system stability especially in the case of adverse network conditions. Almost all parts of the framework have been touched in one way or another. The reason for the massive changes is related to Chrome's out of band HTTPS handling and support for 2048 bit SSL certificates. Although the whole firmware has been thoroughly tested, please do note that it is still beta and thus if you have mission critical applications, installation of this firmware is not recommended.

 

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

 

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

 

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

 

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

- System instability and network issues especially system hang (even though the programs continue to run)

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

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

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

[wrj0]

Thanks, Michel. Upgrade from 3.1.6 went smoothly and seems to be working OK so far, including Network Resource control of an ELK M1G and a Panasonic BB-HCM735 camera. Appreciate your getting the backup issue resolved - its good to once again have that capability!

[Morris Hansen]

Upgraded from 3.1.6 using a Mac. Seemed to work pretty easily.

 

Will test to see if I get Elk connectivity for more than a few hours.

 

thanks, Morris

[mathewbeall]

What am I doing wrong on the brultech side? I have the listener on my server on port 8084.

 

When I connect up to http://192.168.0.252:8084 I get an open session, and a posting of this every xx seconds:

 

CH1PAa=1015&CH2PAa=3&CH1PPa=0&CH2PPa=2&CH1Aa=8.4&CH2Aa=0.7&Paux1a=91&Paux2a=0&Paux3a=0&Paux4a=112&Paux5a=450&KWhCH1a=23080.199&KWhCH2a=16667.467&KWhAux1a=969.899&KWhAux2a=292.014&KWhAux3a=141.008&KWhAux4a=1585.818&KWhAux5a=1726.282&Timea=22:13:52&Volta=123.3&DevSNa=142267

 

But when the isy tries to check it -

 

MOD-EM-BRULTECH: Read Acknowledge Failed

 

Any ideas?

 

Thanks,

 

Matt

[j0dan]

Are the bugs with the ISY over writing internal link tables solved?

[Hurting2Ride]

Updated from 3.1.6. No issues in the update process. Have reviewed my devices, programs and variables and do not see any issues as of yet.

 

I think I might actually sleep easier tonight knowing that I have a working backup again...

[TJF1960]

Upgraded yesterday at 6pm, all seemed to go well and smooth. I just checked the error log. I have 1,106kb for a 10 hour period on 3.1.7, on 3.1.4 the average was 92kb. The errors are occuring about every 5 seconds and I don't know what they mean:

 

2011/09/13 05:55:11 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:55:13 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:55:15 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:55:18 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:55:31 PM	System	-170001	[uDSockets] HTTP:32 error:6	
Tue 2011/09/13 05:55:36 PM	System	-170001	[uDSockets] HTTP:31 error:6	
Tue 2011/09/13 05:55:36 PM	System	-170001	[uDSockets] HTTP:32 error:6	
Tue 2011/09/13 05:55:41 PM	System	-170001	[uDSockets] HTTP:31 error:6	
Tue 2011/09/13 05:55:41 PM	System	-170001	[uDSockets] HTTP:32 error:6	
Tue 2011/09/13 05:55:42 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:56:03 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:56:03 PM	System	-170001	[Auth] , Num=1
Tue 2011/09/13 05:56:03 PM	System	-170001	[Auth] , Num=1

 

On the up side Conductor for Android is working with this beta over wan way better than the last 3 beta's! And no issues that I have seen with DSCLink or WCLink.

 

Please advise on the error log.

 

Thank you for all of your hard work!!!

 

Thanks,

Tim

 

Edit: I shut down DSCLink and both WCLink programs for 3 minutes and the errors went away. I then restarted DSCLink and the errors returned. Then I shut down DSCLink and started one of the WCLink programs and the errors started again. I was trying to determine which program was causing the errors. The errors appear to be the same when running one or all three programs.

In past beta's I have seen System -170001 errors but the [Auth], Num=1 is new, and this error is what heavily populates the error log in this version.

 

Edit:Edit: Conductor did not seem to cause any errors for the ISY.

[Brian H]

Installed fine this morning.

[elvisimprsntr]

Upgraded this morning RDPed into my local W7 machine. Pleased to report the messaging issue UDI and Wes isolated fixed the keypadlinc status issue. Nice work!

 

Elvis

[C Martin]

My upgrade went flawlessly, so far.

 

Thanks for the hard work.

 

Clarence

[Candide]

Upgraded from 3.1.6 - so far so good.

[IndyMike]

Upgrade went smoothly (V3.1.6 to V3.1.7).

 

Some good results, some not so good -

 

1) Verified that the irrigation calculation persists through ISY resets - thank you.

2) Verified that Generic X10 Devices (non-queryable) are not interrogated during "my lighting" query - thank you again.

3) Lost the "batch write control" capability that was a feature of the PRO version. The control buttons are missing in the GUI and I do not see a method of activating things through the menu system. I really hope this feature hasn't been eliminated - I used it constantly.

 

IM

[LeeG]

Michel

 

Ditto on the two Pro write options (batch and RF) being missing. Did not notice until IM noted the problem.

 

Lee

[polexian]

There is a problem with ir. It will accept the first command then it will not accept anymore or commands until a power cycle.

 

 

Sent from my iPhone using Tapatalk

[Michel Kohanim]

Hi all,

 

Thanks so very much for the feedback.

 

Matt, you have to make sure EP1 is in server mode ... in most cases, the port is 5000.

 

j0dan, we hope so.

 

Tim, those are initial requests from DSC/WebLinc which come without userid/password. The code is already updated to log attempts of more than one.

 

IM, that's a bug and it's already fixed.

 

polexian, it might be a bug; it shall be verified and fixed immediately.

 

I am hoping to have a minor release shortly to address these issues.

 

With kind regards,

Michel

[mathewbeall]

Hi Mike,

 

My ECM1240 is sending data via serial to the ECM1240 software running on a PC. On that PC I have it set to "forward data" via the "Custom" tab, and then "Forward Data Via TCP/IP (Server)"

 

As I said I can see the ISY connecting, but get the read acknowledge error.

 

Help!

 

Thanks,

 

Matt

[io_guy]

Tim, those are initial requests from DSC/WebLinc which come without userid/password. The code is already updated to log attempts of more than one.

Michel,

Can you provide a little more detail on what you mean? I have the same "-170001 [Auth] , Num=1" on my 3.1.7 logs but was not aware I was sending unauthorized REST commands. If it's something wrong on my side (Link code), I'd like to try to get rid of it.

Digging a little deeper, it appears these are happening every time I set a variable, however the response back from each ISY REST request is a 200 (success).

[sanders2222]

Upgrade was smooth, I deleted a pair of new 2476D v.00 switches and re-linked them. This time the ISY was able to discover them, v.40 now appears on the device description.

[Michel Kohanim]

Hello Matt,

 

We have never tested this configuration. As I mentioned, EP1 must be in server mode (i.e. it will respond to requests and NOT push data) for this to work.

 

io_guy, this is not anything you or your application doing that's wrong. It's our logging that has a bug: in http basic authentication, the client sends a request without userid/pwd and the server sends back the www-authenticate header. So, obviously, there will be at least one request without userid/pwd to ISY. We should log attempts of more than one and we are not doing that. This shall be fixed.

 

With kind regards,

Michel

[mathewbeall]

Ok - I see what you are saying. Can you add it to the list of enhancements... it seems like a pretty simple thing to connect to the port and wait for it to send the ASCII data over (in my earlier email) as opposed to writing a command string and retrieving the data. I am using the supported ECM Engine by Brultech.

 

I can't use the EP1 due to the fact that I don't have network connectivity by my monitor. I use a RS232 connection over bluetooth to get the data to my server.

 

Thanks,

 

Matt

[Michel Kohanim]

Matt,

 

I think you may want to use our 994 with integrated Zigbee. This way, ECM will publish its events to ISY.

 

polexian,

 

I cannot reproduce the IR issue. Can you please give me more details as to the use case?

 

With kind regards,

Michel

[mathewbeall]

I might be not quite understanding this, but my ECM doesn't have the zigbee module... its just serial... so it sounds like I would need to ugprade that also...

 

Matt

[polexian]

Michael,

I will work on the IR problem for you to be able to reproduce.

 

On another note, when you change in configuration from admin to advanced, save and reboot the authenticate box opens and can't be closed in mozilla firefox 6.0.1

 

Joe

[j0dan]

Are the bugs with the ISY over writing internal link tables solved?

 

I'm still having my link tables for some devices wiped out. I have a KeypadLinc with only 1 link in the ISY table.

 

I've added Wait commands almost everywhere I adjust devices & scenes. Help! There also needs to be a way to repair it without deleting the device and repairing every single scene and program that has a button connected to this keypad.

[LeeG]

If the problem is limited to the physical device losing link records a Restore Device will resolve. If it is the ISY losing track of links that is a different matter.