Regressions with the 1.1.1183 beta just posted

[pncortes]

I´ve just updated to 1183 from 1047 and my IR devices on GC-100 stopped working. Also, I have a motion sensor that triggers a scene´s event to turn on a light and it is taking a little longer to turn it on (was about 1s, now about 5-10s).

Just an update: The ethernet light on GC-100 blinks, but the message is not sent to the IR port.

[N5NHL]

Rocky start but eventual success:

I checked for new firmware and it said I had the current version (1047).  I used strangely's link and updated.  The message I got upon completion was 'update failed' with a choice to reboot or reload.  When Vera came back up it had a blank configuration (I made sure I selected to keep my configuration) and was 'finding devices'.  As soon as Vera got to where I could click on the 'Advanced' button again I restored my settings (than goodness I did that step) and after another requested reboot I was back in business.  I checked the firmware tab and it actually did update (1183).  I checked a few scenes and devices.  Everything seems to be running smoothly now and maybe even a little quicker.

I need to assist 2 others with their updates (I offered my tech support to them).  I will report back if I run into this scenario again.

Update:  the other 2 updates went much better.  No issues other than having to paste the link to start the update.

[strangely]

I am having the same problem with the ? over the battery indicator on the Schlage lock. If I drill into the device however, it shows 67% battery life remaining. I am also able to control the door lock from the console, so it is in communication. I've tried the Ctrl+F5 refresh without success.

I had this with one of my Kwikset locks, it'll probably clear the next time the lock sends the information.
The value thats there (BatteryDate) is the last one it received, or the field may not be populated, and I suspect the question mark is because the last battery update date is prior to 7 days for some reason.

[terencec]

MIOS says it has found more than 1 Vera on my network and asks which one I want to upgrade.

It then lists my one and only Vera.

[micasaverde]

I'm glad that most users upgraded without incident.  I see a couple users have reported serious with the upgrade process itself.  And I see what might be a regression with an Insteon device and the gc100.  We'll look into those too.

[yovinman]

I'm glad that most users upgraded without incident.  I see a couple users have reported serious with the upgrade process itself.  And I see what might be a regression with an Insteon device and the gc100.  We'll look into those too.

What is the recommended upgrade process for users on Vera 1/UI2 (.996)? Is it simply going to the link you posted on the Official Announcements? Will we have to add all our devices/scenes again after the upgrade or can we restore from a UI2 back-up? Thanks in advance for the insight.

[kirbyb]

Installed new firmware without problem, thanks!

Minor issue:  I have the Aeon Labs power meter.  I pressed 'Configure Node' on the primary (i.e. the one not labeled Power Clip #) and its working away, and ends with "Failed at Setting user configuration"  It also doesn't seem to be updating the power numbers all that frequently.  Is there something else I need to do?

Thanks,

Kirby

[strangely]

Installed new firmware without problem, thanks!

Minor issue:  I have the Aeon Labs power meter.  I pressed 'Configure Node' on the primary (i.e. the one not labeled Power Clip #) and its working away, and ends with "Failed at Setting user configuration"  It also doesn't seem to be updating the power numbers all that frequently.  Is there something else I need to do?

Thanks,

Kirby

Everyone else's Aeon HEM are operating the same and there needs to be a firmware update (of the HEM) to fix that.

Despite the failed to configure, I get updates about every 5 seconds; however this maybe because I'm powering mine from USB and not battery perhaps!

Out of interest, how are you powering yours?

[Don Diego]

Hi -

  First let me thank everyone for making a great leap forward. This really is a great improvement.  

  I attempted to upgrade from UI4 (1.1.1047 to 1.1.1183). However, it wasn't as smooth a process as I had hoped. Comments are as follows:

     1. As others have commented, the upgrading process has several bugs.
            a. Going to the Advanced/firmware tab. Pressing "save backup" produced a binary flow of characters in that window. I experienced this both a a Windows 7/x64 workstation and a XP/x32 workstation. I tried this both with IE8 and Firefox 3.6.13. I don't know if I was ever able to save a backup or not..
            b. The upgrade continued forever... after 30 minutes on the upgrade window (I know it says it should be done in 15 minutes) it had not completed. I used iVera to determine that the upgrade had run successfully (and closed the window).
            c. Despite the heart stopping moments (my vera is 200 miles away). The upgrade was complete.

     2. Some brief impressions.
            a. 1.1.1183 is a much better version of UI4. It seems to fix many of the previous features that were less than perfect.
            b. I was particularly interested in setting schedules for the Schlage door locks. The functionality is now there is set a schedule (which wasn't there in 1.1.1047) BUT after setting the schedule the UI briefly incorrectly showed the WRONG schedule (It looked like this: 1. (daily) 4-JUN-2011 15:0 - 31-DEC-1969 19:0). Upon saving the changes the UI appeared to save correctly (but I have not tested it). It still truncated the last digit of time -instead of 1500 it showed 15:0. Better, with not perfect.

UPDATE:

   Second attempt to set a schedule (for the second pin) for the Schlage locks produced no UI response. It did not display anything to the screen. However, after clicking the red "save" button it finally appeared. Suspect this is just a display issue.

FURTHER UPDATE:

   I had set two schedules using the daily option. I set them for two different weeks in June. Both schedules and PIN code expired overnight on February 4th. I verified that the correct date time is set in Vera.

2/6/11 UPDATE:

   I believe that the Schlage door lock schedule loss is related somehow to the heal/repair network process. When I do not run repair network the schedule is retained. When I run repair network the pin code is deleted (along with the schedule). It retains the pins that do not have daily schedules associated with them. I have been able to replicate this error consistently.


    More feedback to follow.


    Again, many thanks for the fine work.. Not perfect but definitely much better!!!!!

[pgrover516]

I have 3 HM-TS001's, I am finding on 1183 I have 2 problems, 1) I can not change the wakeup interval from when they were originally configured even if I wake the node and do a "configure now" it says it configures but continues to use the old wakeup interval,
Edit: scratch prblem 2 my error, just the first problem is valid

[kirbyb]

I'm powering mine with batteries.  I originally had it via usb, then tried batteries just to cover my bases...  I'll try USB and report back.

[/quote]
Everyone else's Aeon HEM are operating the same and I there needs to be a firmware update (of the HEM) to fix that.

Despite the failed to configure, I get updates about every 5 seconds; however this maybe because I'm powering mine from USB and not battery perhaps!

Out of interest, how are you powering yours?


[/quote]

[achalhoub]

I have a scene where 2 lights gets turned on ( 2x Aeon Labs Microswitches) when the door gets opened ( Aeon Labs Door/Window Sensor) and go back to their previous state after 30 seconds.

The issue is the following. if I turn off the lights manually, then I open the door , the lights go on and stay on. I guess it has something to do with the polling of those devices, i.e vera does not know that the last light state was OFF. I tried changing the polling of these specific devices to 2 seconds but to no avail. Is there any way to deal with this in the new framework? (some kind of priority polling for example?)

[Don Diego]

1.1.1183 looks pretty stable. One minor issue is the repair report. The report is no longer formatted as it was in 1.1.1047. It looks like:

11-02-04 8:55:05 report for HealNetwork. Successful: Y Updated net: N Job ID: job#2 :heal network resume (0x0x810e80) P:50 S:5 =======NEIGHBOR NODE UPDATES======= Node 1 Device 2 Vera #1 neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES Node 2 Device 3 Thermostat neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES Node 3 Device 4 Kitchen Sliding Door Light neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES Node 4 Device 5 Front Door Light neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES Node 5 Device 6 Garage Door Light neighbor nodes updated 2 times (incomplete 0 in a row 2), woke up 0 times configured: YES Node 6 Device 7 Front Door Lock neighbor nodes updated 2 times (incomplete 1 in a row 2), woke up 0 times configured: YES Node 7 Device 8 Kitchen Lamp neighbor nodes updated 2 times (incomplete 0 in a row 2),

 A few carriage returns would go a long way of formatting the report and making it more readable. Also not sure what (incomplete 0 in a row 2) means?

Thanks again for your efforts.

[santakrooz]

Upgraded to 1183 yesterday, all seems to work ok so far except for iVera - which is no longer working remotely. cp.mios.com seems to be working ok remotely, but appears to have broken iVera unless on the local lan with iVera.

-sk

[santakrooz]

Upgraded to 1183 yesterday, all seems to work ok so far except for iVera - which is no longer working remotely. cp.mios.com seems to be working ok remotely, but appears to have broken iVera unless on the local lan with iVera.

Ok, killing the account info and resetting it up in iVera seemed to do the trick. Is now working fine remotely.

-m