Release 4.0.3 Beta Is Now Available

[Michel Kohanim]

Hello all,

 

I am happy to announce the availability of our 4.0.3 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 the latest release (1.7.17)

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

 

 

Know Issues

- None

 

Things to test:

- All bug fixes especially I2CS group cleanup

- GreenEye Monitor support

 

*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. http://your.isy.ipaddress (or http://isy if you have Windows) - Java Applet

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

c. http://isy.universal-devices.com/99i/4.0.3 - Java Applet

d. http://isy.universal-devices.com/99i/4.0.3/admin.jnlp - Java application

 

Dashboard

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

 

8. Please backup your system again

 

Thanks and with kind regards,

Michel

[LeeG]

Installed no problem.

 

Deleted / readded KeypadLinc V41 I2CS and LeaK Sensor V3E I2CS. No Group Cleanup issued for either device. Not sure what the comment means in the 4.0.3 announcement regarding I2CS Group Cleanup.

 

Link records in both devices now have 00 for D2 (ramp rate). D1 (on level) continues to have FF which was suppressing Group Cleanup before.

 

Help | About shows 4.0.3 for Firmware and UI

[Michel Kohanim]

Hi LeeG,

 

Thanks so very much for the update.

 

You can now set the number of cleanup commands that should be sent from device to device as well as device to PLM/ISY.

 

The instructions were buried in "What's in 4.0.3" ... I do apologize:

http://wiki.universal-devices.com/index ... ed_Options

 

Thanks again and with kind regards,

Michel

[Brian H]

Mine updated with no problems.

[LeeG]

Thanks Michel - confirmed the Diagnostics | PLM Communication does force a Group Cleanup but the count does not affect the number of Group Cleanup messages. Set the count to 2 the Leak Sensor, 3 for the KeypadLinc, both devices send 1 Group Cleanup message.

 

EDIT: takes longer without the Developer doc. Retry could would produce a single Group Cleanup message.

[Xathros]

Hi Michel-

 

Moving back to the forum since 4.0.3 beta now released.

 

I downloaded and upgraded to 4.0.3 with no problems.

 

Per your last email, I checked and the java symlink in /usr/bin did in fact point to a 1.6 version. Even with that there, the Java preference panel only shows 1.7 installed and when running the console I would see the Java 7 splash screen about 5 seconds after I clicked the admin shortcut and a few seconds before the console main screen displayed. I renamed the symlink as requested. This eliminated the 5 second delay between clicking on the admin shortcut and the Java7 splash screen but otherwise has had no effect.

 

I am now testing on another MAC at the office and am running into the similar problems. Here are the details:

 

• Downloaded and installed the 4.0.3 beta.
  Cleared cache, renamed old java symlink.
  Went to

https:///admin/admin.jnlp and saved the resulting file.
Double clicked the above file - application downloaded to cache and launched. Somewhere in this process I was prompted to trust this developer which, of course, I did.
Logged in and verified 4.0.3 for both FW and UI.
Selected Tools / Error Log, File chooser opened (Defaulted to my home folder! ), clicked cancel.
Repeat the line above a few more times and on the third time, console hangs.

 

When the console locks, the clock stops, the java console is unresponsive and the only way out is force quit.

 

Both test systems are on MAC OS X 10.8.3

 

The hang appears to be directly related to the new file chooser - all other aspects of the console seem fine.

 

-Xathros

[Michel Kohanim]

Hi LeeG,

 

Thanks so very much for the update and confirmation. From our perspective, that's normal on some of the older devices.

 

Xathros,

 

Thanks so very much for detailed explanation. We are running 10.7.5 and perhaps we should upgrade to 10.8.3 to see if that makes a difference. The only difference between your installation and ours is MAC's firmware version on which we cannot reproduce this issue at all.

 

With kind regards,

Michel

[Xathros]

I have a 10.7.5 system at home. I'll see if the kids will let me use it for a bit this evening and I'll test there.

 

-Xathros

[andyf0]

I locked up the console by doing File/Backup ISY. It just hung, only way out was to force quit. The file chooser box did not come up. I figured it was because I forgot to clear the cache. I cleared the cache and backup ISY worked fine, noticing the different file chooser window.

 

Oops, on an iMac running 10.8.3, Java 1.7 Update 17.

[Xathros]

Andy-

 

Try Tools / Error Log, Cancel. Repeat for two or three cycles and see if it locks. It looks like a glitch with the file chooser.

 

-Xathros

[jacobs-gc]

Michel

I cannot find any changes to the Electricity Module showing the GEM support. What changes should I be looking for?

Thanks

Gerry

[andyf0]

Andy-

 

Try Tools / Error Log, Cancel. Repeat for two or three cycles and see if it locks. It looks like a glitch with the file chooser.

 

-Xathros

 

Confirmed. Do Error Log first time, file chooser window comes up, hit cancel. Do Error Log again and nothing happens, do it again and get blue beach ball and locked up. Force quit to close.

 

Same results every time.

[andyf0]

Somethings still not quite right with the change to %. Consider the image below. The options for pull down in the GUI are Responding, ON or OFF. Also the code in the program is not checking for Responding but checking for 100%.

[LeeG]

andyf0

 

Have you checked Help | About for the level of the UI.

 

My Status FanLinc Motor options are Responding | Off | Low | Med | High

[andyf0]

andyf0

 

Have you checked Help | About for the level of the UI.

 

My Status FanLinc Motor options are Responding | Off | Low | Med | High

 

Yes, actually it's a SwitchLinc Relay not a Fanlinc. I'm at 4.0.3 both firmware and UI.

[Teken]

Michel

I cannot find any changes to the Electricity Module showing the GEM support. What changes should I be looking for?

Thanks

Gerry

 

Installed 4.0.3 with out issue. The GEM was showing some limited data on the ISY prior to the upgrade. Now, the ISY does not show anything in the first 7 channels. I have to gather I have to change the GEM back to simulate three or more ecm-1250's?

 

Please confirm if this is the case . . .

 

If there is a step by step guide as to what I should be doing in either controller(s) please do let me know. I will pose the same question to Ben at Brultech and hope they can provide some insight.

 

Since they do not have a ISY controller I am hoping this 4.03 firmware build was tested on UDI's GEM unit. If so, please do let me know what settings need to be configured to see all 32 channels etc.

 

Teken . . .

[Michel Kohanim]

MAC users,

 

Still cannot reproduce the FileChooser hang issue.

 

andyf0,

 

Will review and get back to you.

 

Teken,

 

First, you need to remove GEM from ISY:

1. Remove the nodes from the tree

2. Go to Configuration | Zigbee | Click on Diagnostics | Click on the record for GEM and then click on Remove

 

GEM will try and reconnect at which point you should get 32 nodes.

 

We are working with Brultech to see why values are so very much off.

 

With kind regards,

Michel

[Teken]

MAC users,

 

Still cannot reproduce the FileChooser hang issue.

 

andyf0,

 

Will review and get back to you.

 

Teken,

 

First, you need to remove GEM from ISY:

1. Remove the nodes from the tree

2. Go to Configuration | Zigbee | Click on Diagnostics | Click on the record for GEM and then click on Remove

 

GEM will try and reconnect at which point you should get 32 nodes.

 

We are working with Brultech to see why values are so very much off.

 

With kind regards,

Michel

 

Hello Mitchel,

 

The previous 7 nodes were removed. The GEM was also removed via the diagnostic menu. The ISY began to add in the 32 GEM channels. Sorry to report all 32 channels remain blank.

 

I have rebooted the ISY, the compatibility mode has been toggled to all with no positive change. I am thinking perhaps its because the GEM is set to emulate 1 ecm 1240?

 

Also, since this new firmware release, should the GEM not be programmed to start to use the ISY format packet?

 

Insight

 

Teken . . .

[Teken]

OK, after about one hour of trouble shooting the following are my observations. It appears that the latest 4.0.3 firmware is over writing the GEM's *Primary Packet Format* from my SEG Format, to the ISY Format.

 

This explains why my SEG has been down for almost two hours. I believe the solution is to code the next ISY firmware to send ISY Format packets using the *Secondary Packet Format* channel, as the Primary Packet Format channel is reserved for the SEG.

 

It also appears that the other packet formats are grayed out in the secondary channel, there for the secondary channel must be used to send ISY data packets.

 

I was able to obtain all 32 channels at one point. Later I was also able to see the huge power readings Michel had observed. All other box's were indeed blank. In the interim I have disabled the Zigbee on the ISY, as it continuously took control of the GEM, and rewrote the primary packet format channel as ISY.

 

So, I hope this proves helpful.

 

Teken . . .

[Michel Kohanim]

Hi Teken,

 

Thanks so very much. You do need to get GEM's latest firmware update. We did that because of two reasons:

1. Ben told us that the primary packet format should be ISY (11) and secondary should be none

2. That's the only way we can identify a GEM device is really a GEM device and not ECM. We expect a PKT response which is what we get

3. I do not think it would be a good idea to change that

 

andyf0, sorry to report that we cannot reproduce your on level issues. I suspect that for some reason MAC has decided not to clear Java cache properly. The only thing I can recommend is to reboot your MAC.

 

With kind regards,

Michel

[Teken]

Hi Teken,

 

Thanks so very much. You do need to get GEM's latest firmware update. We did that because of two reasons:

1. Ben told us that the primary packet format should be ISY (11) and secondary should be none

2. That's the only way we can identify a GEM device is really a GEM device and not ECM. We expect a PKT response which is what we get

3. I do not think it would be a good idea to change that

 

andyf0, sorry to report that we cannot reproduce your on level issues. I suspect that for some reason MAC has decided not to clear Java cache properly. The only thing I can recommend is to reboot your MAC.

 

With kind regards,

Michel

 

Hello Michel,

 

I have left my replies also in the Brultech forum and will await Ben's reply as to next steps. Please confirm the firmware you are using for the GEM for me in case I am not at the latest release.

 

I am currently on COM 1.96, Engine 1.41 as this resolved a few com issues along with the inclusion of the secondary packet format type option. I believe once I receive my Dash Box and the firmware for both the GEM / Dash Box has been some what finalized. That the primary channel will indeed use the ISY packet format. The secondary channel will be set to what ever format (Binary) Brultech deems necessary to communicate to the Dash Box. The Dash Box will in turn take the accumulated data and push it to the SEG site.

 

The ultimate goal is to have local / remote data capturing. While having the ISY see the power, current, volts, KWH used and thus control the Insteon network. I know this is the first go round for the GEM via the ISY-994iZ IR Pro.

 

So, progress is being made!

 

Once again, thank you for your continued support and development of the GEM to interface to the ISY.

 

Teken . . .

[andyf0]

Hi Teken,

 

Thanks so very much. You do need to get GEM's latest firmware update. We did that because of two reasons:

1. Ben told us that the primary packet format should be ISY (11) and secondary should be none

2. That's the only way we can identify a GEM device is really a GEM device and not ECM. We expect a PKT response which is what we get

3. I do not think it would be a good idea to change that

 

andyf0, sorry to report that we cannot reproduce your on level issues. I suspect that for some reason MAC has decided not to clear Java cache properly. The only thing I can recommend is to reboot your MAC.

 

With kind regards,

Michel

 

I deleted the program and re-created it and it behaves the same each time Admin Console is closed and re-opened. However, even though the UI looks wrong it behaves the way I expect it to.

[LeeG]

What is the firmware of the SwitchLinc. I added a SwitchLinc Relay with firmware V.3A. Both the Conditon and Action statements have the correct (no %) nonmencalture on 4.0.3 on a PC.

[Xathros]

andyf0-

 

I also am unable to reproduce your issue. What does the ISY show for details on your Swicthlinc Relay?

 

-Xathros

[Michel Kohanim]

Hi Teken,

 

My firmware version:

Com firmware ver: 1.99

Engine1 firmware ver: 1.41

 

Please note that I was told that GEM does not send "Current" ... you might want to verify that with Brultech.

 

With kind regards,

Michel