Release 2.8.3 Beta is Now Available

[Michel Kohanim]

Hello all,

 

 

Release 2.8.3 Beta is now available. Although this firmware has been tested thoroughly, please note that this is still a beta firmware. Please do be kind enough to :

1. Test Linking/Adding Devices/Creating and/or Modifying Scenes and Adjusting Scenes within programs

2. Observe any type of network anomaly

 

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

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

 

Please note that ISY-26 is no longer included in the firmware builds.

 

Instructions

 

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

 

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

ISY 99 Only - http://www.universal-devices.com/update ... _2.8.3.zip

 

3. It is very important that you use your current ISY's Admin Console to perform the upgrade by going to your http://your.isy.ip.address/admin. For MAC users, if upgrade fails, please try https://your.isy.ip.address/admin

 

4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system]

 

5. Choose the file saved in step 2

 

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

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

 

IMPORTANT

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.

 

 

Thanks and with kind regards,

Michel

[rlav]

Hello,

 

I try to upgrade this morning from 2.8.2 to 2.8.3 and had some issues.

 

The first try I got an error message toward the end "Upgrade Failed :Failed uploading file (reported written size is invalid).

 

I then reboot the ISY and try again. This time the upgrade is complete. I did not run the backup this time, if this could have an impact.

 

Usually, after the ISY restart, the "Query at restart" is visible. This time nothing was visible but the interface was very slow. I assume the Query was running in the background. Stange also that 2 of my KeypadLinc (2486D) status are not reported.

 

I then reboot again. This time the query is visible at restart. I got the disclaimer message and all my KP are reported properly.

 

Look like everything is back to normal. I will let you know if this change.

 

 

RLav

[Michel Kohanim]

Hello rLav,

 

Thanks so very much for the update. Did you clear you Java cache?

 

With kind regards,

Michel

[Candide]

Upgraded to 2.8.3 from 2.7.15 - so far so good.

I'll let you know how the Motion Detector actions are after a couple days/nights.

 

Thanks...

[Brignolo]

Hello,

 

I try to upgrade this morning from 2.8.2 to 2.8.3 and had some issues.

 

The first try I got an error message toward the end "Upgrade Failed :Failed uploading file (reported written size is invalid).

 

I then reboot the ISY and try again. This time the upgrade is complete. I did not run the backup this time, if this could have an impact.

 

Usually, after the ISY restart, the "Query at restart" is visible. This time nothing was visible but the interface was very slow. I assume the Query was running in the background. Stange also that 2 of my KeypadLinc (2486D) status are not reported.

 

I then reboot again. This time the query is visible at restart. I got the disclaimer message and all my KP are reported properly.

 

Look like everything is back to normal. I will let you know if this change.

 

 

RLav

 

Not so much for me. None of my devices report and I can't even revert back to 2.8.2.

 

Tried rebooting several times; tried reloading the 2.8.3 I get the "Upgrade Failed :Failed uploading file (reported written size is invalid) message every time; yes I cleard the Java cache several times.

 

No luck; stuck.

 

Joe

[rlav]

Michel,

 

Yes I cleared the Java Cache.

 

I just try to use the console mode again. All the Current State are now empty again. Got out and come back, same results. I then try Mobilinc on iPad without luck. No more access from console. I had to unplug the ISY to reboot. Back to console mode, samething. I try to downgrade, I got the error message.

 

I reboot from the console, clear the Java Cache, try to downgrade to 2.8.2 and 2.8.1, error message.

 

A few time after entering the username/password from the console, a few second later I get an Authenticate screen again while there are ! beside all devices list.

 

I try to play with a simple scene with 2 devices, just On and Off. The lights react about 10 sec later. No Current State.

 

Then I waited for 15 min with the console open, and try to downgrade again. I got it and I am back to 2.8.2 and working.

 

 

 

Robin

[TJF1960]

I had the exact same problem as rlav this morning. In fact I spend the better part of this morning messing with it. I finally had to do a factory reset on the ISY because even when I reverted back to 2.8.2 I was having the same problems!

 

After factory resetting and reverting back to 2.8.2 and reinstalling the last good backup all was normal again.

 

Before the upgrade I rebooted the ISY and plm, after the upgrade went thru I cleared java just like I always have in the past.

 

Very strange..

 

Thanks,

Tim

 

Edit: One more thing I noticed, may or may not be important. The first time the console comes up and the devices appear there is a delay and then the batch mode buttons appear at the same time as the status updates do. The second time and after of opening the console the batch mode buttons don't appear nor do the status indicators, just the devices show up.

 

Running ISY99Pro/ir with network and WB modules.

Thanks

Tim

[Brignolo]

Finally was able to reinstall 2.8.2. Took quite a few tries, with a reinstallation of the security cert as well.

 

One other thing I noticed in the config panel was that in 2.8.3 there was not the standard climate displays: temp, rainfall, etc. There was just a WeatherBug link which was useless.

 

Joe

[thruster999]

Hi guys

 

Can you please explain the new motion sensor setting in 2.8.3?

 

Also, does this mean the only jumper setting required is jumper 5?

 

Thanks

[LeeG]

When Jumper 5 is in place all the options and settings are done through programmatic settings. I don’t think the other jumpers matter once Jumper 5 is in place. Be sure to follow the Quick Start guide instructions for the Set button or motion detection sequence for the MS to be aware of Jumper 5.

 

(Occupancy) Sensing Mode: when checked an On command is sent for every motion detected. When unchecked an On command is sent only after the Timeout value has expired.

 

On Only Mode: On commands only are sent when checked. When unchecked an Off command is sent when the Timeout value has expired.

 

Night Mode: signals motion all the time when checked. When unchecked sends motion commands only when Dark.

 

Darkness Sensitivity controls how dark is Dark. The lower the number the darker it has to get to be in Night Mode.

 

LED Brightness controls the brightness of the LED that indicates motion. I don’t think this setting affects the LED brightness when put into linking mode.

 

Timeout (minutes) specifies the Timeout time between the last motion sensed and the Off command.

 

Note that Jumper 5 is only available on V2 Motion Sensors.

[Michel Kohanim]

Hello all with 2.8.3 issues. I do apologize for the inconvenience.

 

Would you be kind enough to let me know whether or not you are using static IP address for your ISY?

 

With kind regards,

Michel

[thruster999]

Thanks LeeG

 

If you don't mind could you give me an example where you'd think setting the Occupancy to checked (IOW when checked an On command is sent for every motion detected) is useful?

 

 

When Jumper 5 is in place all the options and settings are done through programmatic settings. I don’t think the other jumpers matter once Jumper 5 is in place. Be sure to follow the Quick Start guide instructions for the Set button or motion detection sequence for the MS to be aware of Jumper 5.

 

(Occupancy) Sensing Mode: when checked an On command is sent for every motion detected. When unchecked an On command is sent only after the Timeout value has expired.

 

On Only Mode: On commands only are sent when checked. When unchecked an Off command is sent when the Timeout value has expired.

 

Night Mode: signals motion all the time when checked. When unchecked sends motion commands only when Dark.

 

Darkness Sensitivity controls how dark is Dark. The lower the number the darker it has to get to be in Night Mode.

 

LED Brightness controls the brightness of the LED that indicates motion. I don’t think this setting affects the LED brightness when put into linking mode.

 

Timeout (minutes) specifies the Timeout time between the last motion sensed and the Off command.

 

Note that Jumper 5 is only available on V2 Motion Sensors.

[thruster999]

Thanks LeeG

 

If you don't mind could you give me an example where you'd think setting the Occupancy to checked (IOW when checked an On command is sent for every motion detected) is useful?

 

 

When Jumper 5 is in place all the options and settings are done through programmatic settings. I don’t think the other jumpers matter once Jumper 5 is in place. Be sure to follow the Quick Start guide instructions for the Set button or motion detection sequence for the MS to be aware of Jumper 5.

 

(Occupancy) Sensing Mode: when checked an On command is sent for every motion detected. When unchecked an On command is sent only after the Timeout value has expired.

 

On Only Mode: On commands only are sent when checked. When unchecked an Off command is sent when the Timeout value has expired.

 

Night Mode: signals motion all the time when checked. When unchecked sends motion commands only when Dark.

 

Darkness Sensitivity controls how dark is Dark. The lower the number the darker it has to get to be in Night Mode.

 

LED Brightness controls the brightness of the LED that indicates motion. I don’t think this setting affects the LED brightness when put into linking mode.

 

Timeout (minutes) specifies the Timeout time between the last motion sensed and the Off command.

 

Note that Jumper 5 is only available on V2 Motion Sensors.

[rlav]

Michel.

 

Yes, I am using a static IP address.

 

 

Thank You for your support.

 

 

 

Robin

[LeeG]

If Occupancy Sense is not checked the Motion Sensor is strictly for detecting motion. The first motion detected sends an ON command and when the Timeout has expired, say 5 minutes later, an OFF command is sent. One ON command and one OFF command. The Timeout value is reset to the full Timeout value for any additional motion detected but no additional ON commands are sent.

 

When Occupancy Sense is checked it is functioning as an Occupancy Sensor and sends ON commands for every motion that is detected regardless of whether the Timeout value has expired. In this mode one is able to identify that someone is still moving in the detection area during the Timeout interval.

 

I have seen complaints on the Smarthome forum that this capability could not be set with jumpers but do not remember the scenario that could not be achieved without this feature.

[silverton38]

I just upgraded from 2.7.15 to 2.8.3. I cleared the java cache and then attempted to log in using safari on my Mac. I go the error "XML Parse Error http://10.0.1.2/desc". I will attempt to exit and log back in now.

[silverton38]

Now I can access the ISY but is does not have any status of my lighting. It does not know if a light is on or off. It also takes a minute to send a command.

 

I decided to restore the ISY with my saved configuration. It does not seem to help.

 

Any ideas?

[Michel Kohanim]

Hello silverton38,

 

Apologies for the inconvenience.

 

Can you try and turn something on and off and let me know whether or not it works?

 

Please note that we had to renew our Java certificate and it might have something to do with that.

 

It would be great if you could try http://www.universal-devices.com/99i/2.8.3 ... this will put a Java icon in your system tray which will enable you to double click on it to see whether or not there are any errors.

 

With kind regards,

Michel

[Michel Kohanim]

Hello Robin,

 

Are you still on 2.8.3 or back to 2.8.2?

 

Would you be kind enough to try:

http://www.universal-devices.com/99i/2.8.3/admin.jnlp

 

If it lets you login, then would you please try turning something on/off and let me know if it works?

 

With kind regards,

Michel

[thruster999]

So, if Occupancy is checked and the Motion Sensor is the Controller part of a scene, it will send an ON command to all the Responders every time it senses motion - even if the Responder is already on?

 

 

 

If Occupancy Sense is not checked the Motion Sensor is strictly for detecting motion. The first motion detected sends an ON command and when the Timeout has expired, say 5 minutes later, an OFF command is sent. One ON command and one OFF command. The Timeout value is reset to the full Timeout value for any additional motion detected but no additional ON commands are sent.

 

When Occupancy Sense is checked it is functioning as an Occupancy Sensor and sends ON commands for every motion that is detected regardless of whether the Timeout value has expired. In this mode one is able to identify that someone is still moving in the detection area during the Timeout interval.

 

I have seen complaints on the Smarthome forum that this capability could not be set with jumpers but do not remember the scenario that could not be achieved without this feature.

[LeeG]

That is correct. An ON command will be sent regardless of the status of each responder.

[Candide]

Upgraded to 2.8.3 from 2.7.15 - so far so good.

I'll let you know how the Motion Detector actions are after a couple days/nights.

 

Thanks...

 

 

It's not working right with the 2420M Motion detector.

 

Dusk-Dawn is being set multiple times and motion-off does not seem to be processed.

 

I'll try reverting to 2.7.15 for now.

 

Thanks...

[TJF1960]

Hi Michel,

 

I am using static ip with a specified port other than default.

 

And I tried http://your.isy.ip.address/admin and http://www.universal-devices.com/99i/2.8.3/admin.jnlp both of which produced the same results after the first log in.

 

Thanks,

Tim

 

Hello all with 2.8.3 issues. I do apologize for the inconvenience.

 

Would you be kind enough to let me know whether or not you are using static IP address for your ISY?

 

With kind regards,

Michel

[silverton38]

When I try to switch a light on and off there seems to be about a 30 second delay. It still does not report the status. I ran the last version that you gave me; no changes.

 

If i was a betting man I believe there is some issue communicating with the PLM. Maybe a serial communications issue?

[silverton38]

I know that I can always revert back to the older version but i do not mind assisting the development.