Jump to content

Relase 2.8.13 Is Now Available


Michel Kohanim

Recommended Posts

Hello all,

 

There was intermittent interoperability issue with UPnP routers and specifically Verizon and ActionTec in release 2.8.x . This release addresses this issue. For best operation, though, we strongly recommend creating manual port forwarding rules in the router ( http://www.universal-devices.com/mwiki/ ... o_Your_ISY ).

 

Things to test:

1. Load Controller operations

2. Motion Sensor operations

3. Trigger/Rest operations especially DSCLinc

 

 

For a list of changes, please take a look at this post:

http://forum.universal-devices.com/view ... =6475#6475

 

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

 

Instructions:

1. Please backup your ISY (File | Backup ISY)

 

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

ISY 99i Series: http://www.universal-devices.com/update ... 2.8.13.zip

OR 992i Series: http://www.universal-devices.com/update ... 2.8.13.zip

OR 994i Series: http://www.universal-devices.com/update ... 2.8.13.zip

 

3. Important

Due to invalid Java certificate chain in releases 2.8.5 and above, 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 ( http://www.universal-devices.com/mwiki/ ... Java_Cache

)

f. Go to http://www.universal-devices.com/99i/2.8.13/admin.jnlp

 

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:

http://www.universal-devices.com/mwiki/ ... 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. http://isy/admin - applet (Windows only)

b. 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/2.8.13 - applet

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

 

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

http://www.universal-devices.com/mwiki/ ... rtificates

 

Thanks and with kind regards,

Link to comment
Share on other sites

I had no trouble loading the new release and actually went from 2.7.15 to 2.8.12 then quickly on to 2.8.13. For the 2.8.13 update I had to follow your recommendation for MAC users and add the IP address.

EVERYTHING is working.... Motion, RemoteLinc, KeypadLinc, IOLinc, Ezrain/Ezflora, SwitchLinc Dimmers, LampLincs all functions and can be accessed via my programs or a RemoteLinc, Motion Sensor or KeyPadLinc. But not all of them are communicating their actions back to ISY 99pro.

Motion Sensors are working and actually seem more responsive than before. they turn on the light but within the ISY admin console the status of the light shows off nd there is absolutely no activity coming across the event viewer. If I walk over to the light switch, turn it off then on again the statius then shows ON in the console and all the associated activity is received by the ISY and displayed in the Event Viewer. This same thing happens with my RemoteLinc. All the linked lights respond as expected but nothing is transmitted back to the ISY. ISY thinks nothing has happened.

Suggestions????

I have tried two different AP's v2.1 and v2.0. I have removed my RemoteLinc, factory reset it and reloaded it back using the RemoteLinc method and using the "Start Linking" function. I have cleared java cache I have powered down my ISY Pro...... Im lost. I cant grasp how my finger on the on/off and ramping up a switch is any different than my finger on a remotelinc button which inturn ramps up a switch... <:) how does it know i didn't turn this on directly. it physically looks the same.

Link to comment
Share on other sites

smurt

 

For any Controller to cause a Responder to turn On or Off directly (not under ISY Program control), the Controller must have a Scene defined which contains the Controller device as a Controller of the Scene and the Responder device as a Responder of the Scene. For the Motion Sensor example it is a Controller of a Scene and Switch is a Responder of the Scene. The ISY is not aware of the Motion Sensor turning on the Switch unless the ISY PLM is also a Responder to the same Scene. The ISY automatically makes the ISY PLM a Responder for all the ISY Scenes that are created. Then the Motion Sensor not only turns on the Switch, it also notifies the ISY PLM (and therefore the ISY) that the Scene has been turned On and the ISY will reflect the necessary device status changes based on the Scene definition. Links that have been established by other than the ISY will not have this automatic notification of the ISY.

 

It sounds like the ISY PLM links may have been lost during the process of updating the various images.

 

Do a Tools | Diagnostics | Show PLM Links Table and then click on Compare when the Show is complete. This will compare the links that exist in the PLM against what the ISY thinks should be there. If there are missing or mismatches, do a File | Restore Modem (PLM). This operation could take some time to complete.

 

Lee

Link to comment
Share on other sites

I have 3 2420M's (V2) in my setup with two AP's. The only way I could get reliable operation is by leaving Jumper 5 off (none of the other jumpers are on either). If I press setup I am required to put the 2420M in linking mode where it appears to send the new settings to the device. If I leave Jumper 5 on then the 2420M will continue to show the sensor state as On - even after 5 minutes. Just for a lark I tried using the 2420M-SP device and it did not seem to make any difference in the operation. Could there be a difference between V1 and V2 devices when it comes to jumper settings?

This behaviour is exhibited in all three motions so either all my 2420m's are defective or they are operating according their intended design. I believe I am following the instructions to the letter. I would appreciate any input either via confirmation or potential miscues on my part. Thanks

Link to comment
Share on other sites

mjtyson

 

There are differences between V1 and V2 motion sensors. V1 MS do not have a functional Jumper 5.

 

The 2.8.13 image supports the V2 Motion Sensors. What are the exact options for each of the 6 motion sensor options. It sounds like they are in On Only mode when no Off commands are being issued. Or perhaps in Night Only mode so no new motion commands are sent until dusk setting is reached. With Jumper 5 in place press the MS Set button until the LED is flashing (linking mode) and then click Set Options. That will read the current options in the motion sensor.

 

Lee

Link to comment
Share on other sites

Lee, Thanks for the post. I followed your "Show Links" suggestions but did not find a compare function in any of the drops downs nor was there one in the SHOW LINK function itself. Given that I went ahead and performed a "Restore Modem PLM". No luck.

It surprises me that by deleting all the links from my RemoteLinc then went re-adding a device to a specific button on that Remotelink that the responder/controller relationship would not have been set up at that time. When I set this up llast year that is all I did and linking it this way automatically created the connection and the links. Anytime the motion sensor turn on a light or a button was pushed on the RemoteLinc signals were sent through the ISY and reflected in the logs and status shown on the admin. console itself. I never had to do any other work to create the Controller/Responder relationship.

Right now I am thinking that even if I took everything in my home out and re-added it I would not get see a difference.

Steve

Link to comment
Share on other sites

mjtyson

 

There are differences between V1 and V2 motion sensors. V1 MS do not have a functional Jumper 5.

 

The 2.8.13 image supports the V2 Motion Sensors. What are the exact options for each of the 6 motion sensor options. It sounds like they are in On Only mode when no Off commands are being issued. Or perhaps in Night Only mode so no new motion commands are sent until dusk setting is reached. With Jumper 5 in place press the MS Set button until the LED is flashing (linking mode) and then click Set Options. That will read the current options in the motion sensor.

 

Thanks for the response LeeG. The six set options are as follows: Timeout 1, Brightness 100, Sensitivity 128, Top Box is checked, Middle Box is unchecked, Bottom Box checked. With no jumpers bridged it works, with only pin 5 bridged sensor status remains on. I am perplexed

Link to comment
Share on other sites

mjtyson

 

Don’t know when it happened but at 2.8.13 the On only mode: is backward from the description in the popup. Put a check in the middle box to get On and Off commands. When unchecked the motion sensor is operating in On only mode. I confirmed this with both by checking the option bit that is being set in the motion sensor configuration and I get On and Off commands when the middle option is checked.

 

I'll pass this on to UDI support. Thanks for finding this change.

 

To enter linking mode, press and hold the motion sensor Set button for 5 seconds. Do not press the Set button again until the options have been read and written. You can let the motion sensor time out of linking mode or press the Set button twice.

 

EDIT: the wording regarding checked/unchecked for On Only mode on the popup was reversed at 2.8.13 (which actually makes more sense) but the code was not changed to match the wording change.

 

Lee

Link to comment
Share on other sites

Upgrading my ISY-99 from rev 2.8.7 to rev 2.8.13 seems to have completed successfully and without any error reports. After the upgrade the ISY appears to operate properly, and local access from my home network continues to work fine. Email reports from the ISY and NTP sync are still working fine, so outgoing access is functional, but I have lost remote access to the ISY, both on PCs from work and from MobiLinc on an iPhone. Other than updating to rev 2.8.13, no other system changes were made. Manual port forwarding in the router remains set just as it was prior to the ISY upgrade. ISY settings including CWP ports seem to be set properly, but remote access continues to fail. Upgrade instructions were followed including clearing cache.

 

Suggestions, please. Thanks.

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.


×
×
  • Create New...