Release 4.0.2 Beta Is Now Available

[Michel Kohanim]

Hello all,

 

I am happy to announce the availability of our 4.0.2 Beta release! For a list of changes, please take a look at this post.

 

IMPORTANT If you have not already done so, please upgrade your Java to 1.7.13+: Announcement .

IMPORTANT We will no longer have any firmware updates for ISY99i Series Announcement .

 

 

Know Issues

- None

 

Things to test:

[15]- RL2 Scenes do not show KPL sub buttons: origin

[39]- IOLinc Scene status still not working properly

[40]- Devices show 100% instead of On

[42]- Themes anomalies

[44]- Thermostat must be queried to report its status

[48]- Workaround for KPL v41 bug where NACKs do not appear for the correct message

[55]- Partial fix for ZBPCM not showing up in programs: origin

[61]- If you have a large number of programs, delete does not work (M. Armer)

[00]- Smoke Sensor issues: Have to remove from ISY and the link again

[New] Network Module - create/update/delete files and directories in the local ISY web directory (/user/web) using Custom Notifications in Programs

 

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

*For a discussion of variables, please look at our Program Variables Wiki.

 

 

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 994i Series including Z-Wave Support

ISY 994i Z & ZS Series (Zigbee)

 

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

 

4. Choose the file saved in step 2

 

5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache

 

6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console:

a. Enable Java Plugin: http://www.java.com/en/download/help/di ... rowser.xml

b. http://your.isy.ip.address/admin.jnlp - Java application

c. http://isy.universal-devices.com/99i/4.0.2/admin.jnlp

d. Disable Java Plugin: http://www.java.com/en/download/help/di ... rowser.xml

 

Please note that both methods above should install an icon on our desktop which should be used instead of using a browser to access ISY.

 

Dashboard

- http://isy.universal-devices.com/99i/4. ... board.jnlp

 

8. Please backup your system again

 

Thanks and with kind regards,

Michel

[andyf0]

Confirmed IO Linc now reporting last command sent correctly. Bug #39

[Brian H]

Installed fine for me.

Java did another update to 1.7.15 and it seems OK with 4.0.2.

The ISY Finder is also now working like it use to.

[scubaguyjohn]

Installed fine. Couple of notes:

 

1. when selecting Desert theme (likely applies to all themes as it did in 4.01), a blue bar from the default theme remains horizontally in the tabs area. Same default blue remains around the devices to be adjusted on the scene page.

 

2. I still need to click on the isy finder to launch the admin control panel

 

 

John.

[Candide]

Upgraded from 4.0.1 - no new issues.

Still need to click on the finder to launch, unless I use my IP address.

 

Update: I cleared the java cache again, on two machines, ran a java update on one (to make the same version) and now both are properly launching when using the UDI link.

[TJF1960]

Upgrade went without a hitch.

Finder launches right into admin console without prompting.

 

Thanks,

Tim

[scubaguyjohn]

My firmware is 4.02 but my UI is 4.01, should it also be 4.02? Clearing Java cache doesn't fix the console launch issues for me.

[LeeG]

scubaguyjohn

 

Yes, the UI should be the same as the ISY Firmware. Either the Java cache was not cleared including the Applications and Applets, something using Java was not closed such as a Browser or the Admin Console itself, or the URL used to invoke the Admin Console (UI) was not updated for 4.0.2

[G W]

My firmware is 4.02 but my UI is 4.01, should it also be 4.02? Clearing Java cache doesn't fix the console launch issues for me.

Go to the first message here and click on 6b. That will update the UI.

[scubaguyjohn]

thanks guys... happy to report that the console launches properly and the color bar issues in the UI are fixed.

 

I receive my zwave dongle tomorrow and will report back on functionality.

 

JOhn.

[barrygordon]

Upgraded to 4.02 and my iPad app stopped working properly. The following is a trace of what I see:

 

> startSubscribe: msg sent=

SUBSCRIBE(SP)/eventing(SP)HTTP/1.1(CR)(LF)HOST:(SP)192.168.1.229(CR)(LF)Authorization:(SP)Basic(SP)YWRtaW46YWRtaW4=(CR)(LF)Content-Length:129(CR)(LF)Content-Type:text/xml;(SP)charset="utf-8"(CR)(LF)CALLBACK:(CR)(LF)NT:upnp:event(CR)(LF)TIMEOUT:second-infinite(CR)(LF)SOAPACTION:"urn:udi-com:service:X_Insteon_Lighting_Service:1#Subscribe"(CR)(LF)(CR)(LF)(CR)(LF)

>

ISY.subscribeFeedback: FBstring=HTTP/1.1(SP)404(SP)OK(CR)(LF)Content-Length:(SP)0(CR)(LF)Connection:(SP)Keep-Alive(CR)(LF)WWW-Authenticate:(SP)Basic(SP)realm="/"(CR)(LF)Content-Type:(SP)text/html;(SP)charset=UTF-8(CR)(LF)Cache-Control:(SP)max-age=3600,(SP)must-revalidate(CR)(LF)EXT:(SP)UCoS,(SP)UPnP/1.0,(SP)UDI/1.0(CR)(LF)Last-Modified:(SP)Sun,(SP)3(SP)Mar(SP)2013(SP)18:11:13(SP)GMT(CR)(LF)(CR)(LF)

 

>

ISY.subscribeFeedback: ERROR:

Reply=

HTTP/1.1(SP)404(SP)OK(CR)(LF)Content-Length:(SP)0(CR)(LF)Connection:(SP)Keep-Alive(CR)(LF)WWW-Authenticate:(SP)Basic(SP)realm="/"(CR)(LF)Content-Type:(SP)text/html;(SP)charset=UTF-8(CR)(LF)Cache-Control:(SP)max-age=3600,(SP)must-revalidate(CR)(LF)EXT:(SP)UCoS,(SP)UPnP/1.0,(SP)UDI/1.0(CR)(LF)Last-Modified:(SP)Sun,(SP)3(SP)Mar(SP)2013(SP)18:11:13(SP)GMT(CR)(LF)(CR)(LF)

 

I know you no longer support uPnP, but I thought that was only for searches. The problem seems to be that it wants me to revalidate. I assume this means I need to send authorization again? The message I sent was to start subscription and what I got back was that I must revalidate. The message to start subscription did contain the proper authorization so I am quire confused.

 

Could you point me somewhere where this is clarified and/or tell me what I need to send?

[barrygordon]

I thought I would try and revert back to 3.3.10. When I try and do manual upgrade as I usually did it tells me:

 

Upgrade Failed: Invalid or incompatible upgrade file

 

I believe the last time I ran 3.3.10 was with my ISY99i. I thought 3.3.10 was for both the ISY99i and the ISY994i. Once again I am confused.

 

This has been a confusing day!!

 

Help greatly appreciated since nothing in my home is working properly now.

[LeeG]

barrygordon

 

Refer to the 3.3.10 announcement. There is a separate link for 99i versus 994i download

[barrygordon]

Yes I figured that out and did successfully revert back to 3.3.10 and all is once again working as it should.

 

I still have the issue with 4.0.2 and would like to keep current with the ISY firmware updates.

[Michel Kohanim]

Hi Barry,

 

The main difference is that we removed UPnP subscriptions from 4.0.x branch. And, that's where things are failing.

 

With kind regards,

Michel

[jjp076]

Upgraded to 4.0.2. The smoke detector and bridge are now working properly with the ISY. Thank you! After the upgrade I started seeing an occasional wet trigger from my leak sensor. I have a program that looks for the wet sensor to be on and sends me an email and several other tasks. It has triggered once a day since the upgrade. I am wondering if the leak sensor heart beat is somehow being interpreted as a wet condition by the program.

[johncrab]

I would try removing and reinstalling the leak sensor and/or checking your program to make sure you are using "control" and not "status" to trigger the email. I am using a very similar setup here with fine results on the last official software release.

[LeeG]

Both the Leak Sensor and the Smoke Bridge should be deleted and readded under 4.0.2. 4.0.2 has a fix for the Smoke Bridge which requires the device to be deleted and added back. The Heartbeat support in 4.0.1 for the Leak Sensor adds an additional node which also requires a delete and readd. The Heartbeat message every 24 hours carries the current Leak Sensor Dry/Wet status which does seem to be affecting the Program.

[jjp076]

Deleted and re-added the leak sensor. All is well. Thanks!

[RLIKWARTZ]

I have noticed when the isy finder opens up the backround used to take on the theme so for instance it would be sand if the theme was sand. It now always comes up blue. Small thing.

[Xathros]

I have noticed when the isy finder opens up the backround used to take on the theme so for instance it would be sand if the theme was sand. It now always comes up blue. Small thing.

 

I think this was already reported over the weekend and UDI is aware.

 

-Xathros

[barrygordon]

Changed my iPad code to properly handle subscriptions using SOAP and all seems to be working well now.

 

My only question is:

 

If I want to stop subscriptions, what is the SOAP sequence I need to use. Not an issue right now since I never stop them but perhaps someday. I probably should stop them if the app is being terminated to make sure the ISY994i releases the Communications slot, although I assume it will do that if there is rejection of a message due to connection broken or it receives a session closed message

[grtaylor]

I'm seeing something I haven't seen before with 4.0.2 - After logging in to the admin console, the UI briefly appears, and then unexpectedly exits. If I re-launch the console it seems to work just fine.

[db2ace2]

Hello , The V4.0.2 Beta Installed and has been basically running successfully however I just noticed something that I did not notice happening on previous releases so without going back I cannot verify this. When I go to the Main Tab under the ADMIN Console, and select a Folder, I see all of the devices in the Folder, and Options for QUERY, ALL ON, ALL OFF, however when I select one of those options (Query) nothing happens. If I select a single Device in the Folder list and go to the device itself I can then right click it and query it but I cannot use the QUERY, ALLON ALLOFF options from the Folder Level. Basically I can query the Device OK from the Device level but it will not query from the Folder Level. Is this a known Bug or did this ever work?

 

Also I have a 2484SWH8 Keypadlinc Timer in my Pantry. I have a program to check Control and Status of the KPL so that even if you hit a 10 min or greater button, it will still turn off the lights after only 5 min effectively overiding the Hardware's timer. I noticed that the Pantry Light was staying on indefinately so I went to ADMIN to find out why. That's why I was trying to query the device at its folder level. Indeed the Folder Level reported all Buttons as being in an OFF state even though the KPL was definately in an On State since the light was still on in the Pantry. That's when I noticed the QUERY not working at the Folder level. Once I queried the Device then it detected as being ON and the Program works to turn it off after 5 min but It did not detect ON until I queried it. I have been running this program and device for quite some time now with no issues, so again I do not know if this is something related to the V4.0.2 release or if this is some other issue, but I though I would report it just in case.

 

I also have the same 2484SWH8 Keypadlinc Timer in my Master Bedroom Closet, and the exact same things is happening with it too. At the Folder Level, no QUERY, ALLON, ALLOFF commands work, and at both the Folder and Device levels all Buttons showed as OFF even though I pressed the 10 min button and the light was on. I had to go to the Device Level and run a QUery in order for the ISY to recognize that the button was indeed on.

 

 

Thanks

Charles Seiler

[Xathros]

I'm seeing something I haven't seen before with 4.0.2 - After logging in to the admin console, the UI briefly appears, and then unexpectedly exits. If I re-launch the console it seems to work just fine.

 

I saw this once right after the upgrade. First launch of the console did this. It's been fine ever since. Only on one Mac at home running OS X 10.7 / Java 1.7.15. 3 other Macs did not have this issue.

 

-Xathros