Jump to content

Recommended Posts

Posted

Hello all,

 

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

this post. This is a major specifically addressing two issues:

- MobiLinc and other clients take a long time to find ISY

- In extreme cases, database files may get corrupted

 

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 B) 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:

- MobiLinc connection issues

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

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

Posted

Nice! Been checking on this VERY frequently as I am looking forward to getting my Remotelinc2 into my ISY. My upgrade went fine as usually, and already have my Remotelinc2 linked in. So here is my question:

 

I have a 4 key remotelinc. When I linked into ISY it showed up as 6 seperate items (4 were for the keys). What do the remaining two represent? I am hoping that one is low battery. If so, which one? Can't find anything in forums/wiki (I am sure because this release is just a few minutes out).

 

Thanks in advance.

 

FYI, can't say enough how great I think your product is, and even better, the support and upgrades you continue have!!! Thanks again.

Posted

3.1.10 updated fine. Fixed the excessive communications from a Venstar T8000 Thermostat rf adapter Rev 2.2.

Thanks UDI! RL2 support is a nice addition.

Posted

Thanks. Upgraded and added one RemoteLinc 2. Works perfectly so far. Will add 3 others and keep testing. :lol:

 

I have now added all 4 RL2's, all without a hitch. All 4 of the Remotelinc-2's have worked flawlessly so far. I control only scenes so far (no programs) and response is immediate.

Posted

Upgrade of files went smooth. ISY took a long time with initial a status bar scroll after 1st reboot (3-5mins). All start up programs ran quickly in background during scroll and it completed fine.

 

******

Very nice addition on the Remote Linc2 support - thank you !

 

small stumbles I had adding Remote Linc2

1st time I tired to add (via add device, specified address and device) I forgot to put RL2 into linking mode. Did not receive warning message to place RL2 into linking mode but instead received error of "Failed writing the high water mark, Node not added - failed removing links". On my 2nd try I started with putting the RL2 into linking mode than did add device ... This time ISY placed new device names in My Lighting but they had i/o/i/o/i/o green mark. Clicked green button at top of screen to automatically write to devices, received nice pop up message informing me to battery powered devices into linking mode. 1 sec after clicking OK all green marks cleared (super quick).

 

Device added 8 entries in My Lighting; small note that devices are numbered slightly off to start instead of lettered. No big deal to rename but order stays slightly off in list.

 

remote linc = controlled by button B

remote linc - 2 = controlled by button A

remote linc - 3 = controlled by button D

remote linc - 4 = controlled by button C

remote linc - 5 = controlled by button F

remote linc - 6 = controlled by button E

remote linc - 7 = controlled by button H

remote linc - 8 = controlled by button G

 

******

Thermostats:

Confirmed the query V2 Thermostats for Fan Mode and Heat/Cool status is also working nicely with two Tstats on v.92. Thank you again.

 

Noticed set the "Set Options" button on the Tstat page which reveals option to report humidity. On the default setting here: One Tstat had the option checked by default (TstatUp) but the other Tstat has the option unchecked (Tstat Down).

 

Will we need to check that option now to have HUM updates to ISY ?

******

 

Agreed with prior posters here about how good this product is both from the continued updates and excellent support. Thank you and nice work UDI Team

Posted
I have a 4 key remotelinc. When I linked into ISY it showed up as 6 seperate items (4 were for the keys). What do the remaining two represent?

 

Hi tim2u,

 

I think you added it as a RemoteLinc, not a RemoteLinc2. Best thing to do would be to remove it, and add it back again using "New Insteon Device".

 

Looking at the dropdown menu, I can see how easily this mistake could be made. I'll have a look and see if we can make this a little nicer in the GUI.

Posted

Chris,

You were right. Sorry bout that. I think I was anxious to get my RL2 going and didn't look at all my options. In my opinion, your GUI is fine in regards to that. It was complete user error.

Posted

I've been running into IR issues over the last few builds, today IR wouldn't work at all.

I have a number of programs looking for IR presses, which then send network commands.

 

Over the last few builds I've seen a significant lag, where I'd press the remote button and a few minutes later the ISY would react. Today it stopped working all together. With an ISY reboot things go back to normal, but it gradually gets delayed again.

 

I check both the log and error log but see no IR details.

Sorry for the vague info, if there's anything else I can grab let me know.

Posted

io_guy...interesting observation with the IR...

 

I also have been having issues with IR functionality over the 3.x.x builds. It'll work for a while after reboot of the ISY, but becomes unresponsive after a very short while.

 

Are you using an IR-Link or is it the built -in IR module?

 

Either way, appears to be a similar problem.

Posted

Got another potential bug.

 

I have several networking resources that work fine when I hit the 'Test' button on the Networking Config page. However, when I try to call the networking resources from a program, they do not run at all. Am I missing something?

 

I saw that a previous beta release moved the resources into a separate 'thread' as to not hold up the programs. But mine are apparently not executing at all when called from a program

 

Any ideas?

 

BTW, just found this post also (same problem):

viewtopic.php?f=25&t=7112&p=54407#p54407

Posted

Hi all,

 

The address is for aws= Flex Your Power. If you have Flex Your Power enabled, that's what's causing ISY to go out to aws.

 

Networking resources is a bug which has already been fixed. I'll post a link for those who want this fixed shortly.

 

IR issues, we will have to investigate.

 

ELK ... the new module should be available shortly which will address all ELK issues.

 

With kind regards,

Michel

Posted

Hello Elvis,

 

I am so very sorry ... that IP is for WeatherBug (datafeed2.weatherbug.com).

 

io_guy,

 

We have been testing the reported IR issue and it's working flawlessly. Can you please look at your error log and see whether or not you see any type of errors such as Queue Full?

 

With kind regards,

Michel

Posted
I've been running into IR issues over the last few builds, today IR wouldn't work at all.
My IR scenes were not working at all with the last beta update either. But then I discovered my IR emitter had fallen off my ISY. I pasted it back on and the scenes are working again, sort of. I seem to have to repeat the remote button press to make a scene fire. Whereas before, there never seemed to be this stubbornness with my system as others are reporting.

My error log does repeat the "Queue Full' phrase during the time I tried using my remote.

Posted

Since I am not home I decided to try a remote update to 3.1.10. It sits at 1% for a while then I get "Upgrade failed: failed uploading file (reported written size is invalid).

Posted
Since I am not home I decided to try a remote update to 3.1.10. It sits at 1% for a while then I get "Upgrade failed: failed uploading file (reported written size is invalid).

 

Could there be a bad link to the download? When I downloaded, the file was 417k. Previous betas were 4.6M. I haven't tried to load the 417k version yet.

 

Kevin

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.


×
×
  • Create New...