Hi all,

 

Thanks so very much for your patience.

 

If you would like to try 2.7.10 ALPHA, please do be kind enough to register at http://eepurl.com/ha4Z .

 

For a list of fixes in 2.7.10, please checkout this post:

http://forum.universal-devices.com/viewtopic.php?t=930

 

And, finally, general operations instructions:

Instructions for 2.7.8/9 can be found here: http://forum.universal-devices.com/view ... hp?p=27368

 

With kind regards,

Michel

Upgraded from 2.7.9 no problem and everything looks good. I had made only minimal changes in 2.7.9 (swapped 2 thermostats and modified a few programs so it appears everything carried over properly.

 

rob

Will we be required to sign up for a new list every time there's a new Alpha release? I thought I was already on the Alpha list...

 

If you would like to try 2.7.10 ALPHA, please do be kind enough to register at http://eepurl.com/ha4Z .

Hi Rob, yes.

 

With kind regards,

Michel

I have 2.7.9 running, and as you well know I've replaced my PLM while that version is installed. Thanks for your help with that.

 

So... my 2.7.6 backup obviously will be from the old PLM. Would the procedure be to restore that backup to the ISY, upgrade to 2.7.10, again re-do the restore PLM operation, and manually restore devices again if that seems to be necessary. Or do I do the restore PLM first with 2.7.6 and then upgrade? Or something else?

 

Especially with all the motion sensors and remotelincs around here, the PLM restore is a real job. And a little nerve-wracking. (Why SH couldn't just make the PLM ID soft-programmable is a bit of a mystery. It would make things soooooo much easier when they fail. Which they seem to like to do.)

 

I could just wait for another release. But reading between the lines I'm assuming 2.7.9 is using a dead format that won't be upgradeable with any future release? And if so do you think it likely that the 2.7.10 alpha format also will be deprecated before the final release?

 

Not complaining you understand -- I perfectly well saw the alpha notice on 2.7.9 and .10. Just asking the best way to go about this.

It looks like the drop down problem in a program where it wouldn't show the light levels is fixed. Thanks.

Hi ergodic,

 

First of all, you do have the right to complain ... this must have been quite an experience.

 

I think the best way to go about this is:

1. Upgrade to 2.7.10

2. Restore your backup from 2.7.6/7

3. Click on the Battery button (the last button on the Admin Console) so that it's grayed out (this makes the operations manual for battery operated devices)

4. Do File | Restore Devices (this will automatically do a Restore PLM for you)

5. When you are done, click on the Battery button again so that ISY starts restoring battery devices one at a time (you will see an indication of which one is being done)

 

With kind regards,

Michel

Thanks.

 

I just got the download and upgrade instructions for 2.7.10.

 

I haven't made any device KPL changes at all (too busy with the problems ) So is it possible to just update to 2.7.10 from 2.7.9 and leave it that way? Or not advised even those the upgrade notes suggest that's possible.

Hi ergodic,

 

Yes, you can but if you have not made major changes to your system, I advise against it.

 

With kind regards,

Michel

I don't have any KPL's so I upgraded from 2.7.9 to 2.7.10 Alpha and the only problem immediately visible was the thermostat set point value. It was set to 0 deg. I changed the mode from 'Program Heat' to 'Heat' and it changed to 16 deg and then I manually changed the value to 72 deg and everything seems to work. I'm not sure why it would start out at 0 deg and subsequently change to 16 because the actually thermostat is set to 72.

 

Is there any easy way to make sure the upgrade worked perfectly, like an upgrade log or something similar that enables us to view each step of the process.

 

thanks.

I just upgraded the firmware, it rebooted and everything works. Thermostat and everything. I don't have kpl switches.

Hi wwat,

 

Unfortunately there are no logs.

 

The setpoints must be reported by the thermostat or queried. I am suspecting that all these issues are related to Program Heat/Cool mode.

 

With kind regards,

Michel

I cannot get 2420 motion sensors added using "New Insteon Device" and selecting 2420m as device type. I've factory reset motion sensors but get same error with both:

 

[-200000] failed writing the hightwarer mark[n/a]

[-200000]Node not added - failed removing links[11 9A 95 10]

 

Same messsage for other with different address.

 

Motion sensors are 3 feet from access point which is plugged into PLM. Turned off all WIFI.

It appears it is only possible to add one device to a scene at a time. Selecting several devices and right clicking to pick add to scene "deselects" all but current device.

Can't seem to get my EZX10RF to add work with new X10 adreeses.

The ones I added previous to .10 still work.

TIA

I likewise replaced and restored a PLM during my 2.7.9 install. I also added a couple of v2 thermostats. Would it be possible to just ride this out for a while and see if everything is working okay before I make a decision to go back through that whole process again? I actually had everything working pretty well in 2.7.9.

I'd be interested in whether anyone else can duplicate this bug.

 

Description: Heat setpoint changes to 16 deg when the mode is changed from 'Program Heat' to 'Heat' mode.

 

Steps:

 

Open admin console and click on thermostat properties page.

Set mode to 'Heat' and heat set point to 72 deg

Change mode to 'Program Heat'

Change mode back to 'Heat'

 

At this point the setpoint will change to 16 deg if you experience the bug.

 

Thanks.

I tried the test mentioned previously and didn't see the 16 degree behavior.

I am having the exact same problem as hart2hart with 2.7.10, MS v1.1 and 2.0

 

I cannot get 2420 motion sensors added using "New Insteon Device" and selecting 2420m as device type. I've factory reset motion sensors but get same error with both:

 

[-200000] failed writing the hightwarer mark[n/a]

[-200000]Node not added - failed removing links[11 9A 95 10]

 

Same messsage for other with different address.

 

Motion sensors are 3 feet from access point.

Thanks,

Tim

 

Edit:

 

I did find that the MS could only be added by New Insteon Device and selecting Add devices found in links and keep existing links

 

Tim

I getting the same results adding a triggerlinc and remotelinc as adding Motion Sensor so appears to be rf device related. When you perform button press on triggerlinc the access point led flashes as expected

Hi all,

 

The issue with Motion Sensor (most i2 devices) have been verified and is now fixed in 2.7.11.

 

The issue with EZX10RF is still under investigation.

 

The issue with right mouse clicking a selection has been verified and shall be fixed.

 

With kind regards,

Michel

I've been a user for about 4 months, but never upgraded my firmware. I'd like to get current, but there seems to be so many changes, I can't find a version that will load without error. Please help.

I've been a user for about 4 months, but never upgraded my firmware. I'd like to get current, but there seems to be so many changes, I can't find a version that will load without error. Please help.

 

Hello donkur,

 

Any version should load without error. Be sure you have the correct file (99i/26) and use a PC that is wired to the same router/switch as the ISY. You may need to disable your firewall software.

 

Rand

Upgraded to 2.7.10.

 

Upgrade went well and funtionality is good.

 

I have noticed a strange format in my Event Viewer when doing a device restore:

 

Sat 01/30/2010 11:17:37 PM : [12 39 E5 1 ] Link 36 : 0ED8 [A2030E0A1FFF1F05] Writing [A2030E0A1FFF1F05]

 

Sat 01/30/2010 11:17:45 PM : [12 39 E5 1 ] Link 37 : 0ED0 [A2030DC82AFF1F05] Writing [A2030DC82AFF1F05]

 

Sat 01/30/2010 11:17:54 PM : [12 39 E5 1 ] Link 38 : 0EC8 [A2020E2BA6FF1F02] Writing [A2020E2BA6FF1F02]

 

Sat 01/30/2010 11:18:02 PM : [12 39 E5 1 ] Link 39 : 0EC0 [A2020E0A1FFF1F04] Writing [A2020E0A1FFF1F04]

 

Sat 01/30/2010 11:18:11 PM : [12 39 E5 1 ] Link 40 : 0EB8 [A2020DC82AFF1F04] Writing [A2020DC82AFF1F04]

 

Sat 01/30/2010 11:18:29 PM : [12 39 E5 1 ] Link 41 : 0EB0 [A20113387CFF1F07] Writing [A20113387CFF1F07]

 

Sat 01/30/2010 11:18:38 PM : [12 39 E5 1 ] Link 42 : 0EA8 [A201133761FF1F07] Writing [A201133761FF1F07]

 

 

The code in the [xxxxxx] is unusual. I have not seen this before. The device restore went very well and the links were proerly written to the device.

 

I am also getting a Cetrificate Mismatch when I log in through the web. I can still get into my console remotely, but have to try to create a new certificate through the ISY cert generator. This happened after upgrade.

 

Not big deal items as functionally, the upgrade seems to be stable so far.

 

Thanks for your hard work!

 

MORE...

 

Looks like local ramp rates are not being written to SOME devices (togglelinc dimmers). If they are part of a scene, there seems to be no problems.

Hi gfridland,

 

1. The certificate issue is normal and please do reinstall a new certificate

2. The event log now shows what we are writing to what memory location. This is used to write information to memory locations that are NOT link database related

3. Can you elaborate a bit on local on level/ramp rate not written to certain devices? Please note that unlike KPLs, most other devices have to be rebooted before local on level/ramp rate setting can take effect

 

With kind regards,

Michel