Vera - Smarter Home Control Forum

Beta and Pre-Release (Public) => Beta Testing (Public) => Topic started by: micasaverde on February 02, 2011, 05:46:37 pm

Title: Regressions with the 1.1.1183 beta just posted
Post by: micasaverde on February 02, 2011, 05:46:37 pm
We just made an official announcement about the availability of our next release, 1.1.1183.  If you have comments, please start a new thread.  But if you find problems with this version that you didn't have previously, namely regressions, please post them to this thread.  Developers will be monitoring this thread to see if there are any serious issues introduced with this version, and if not, it will become an automatic upgrade for all Vera users next week.  The announcement, release notes, and link are here: http://forum.micasaverde.com/index.php?topic=5560.0  Thank you!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mvakoc on February 02, 2011, 06:26:59 pm
Forward servers no longer work.  Updated to 1.1.1183.  

http://sta1.mios.com/locator_json.php reported the vera2 (though it still listed the previous firmware version)

http://fwd1.mios.com/username/password/serial/data_request?id=lu_alive or any other data request doesn't return anything, same when using fwd2.mios.com

rebooted vera, then

locator_json.php returned the new firmware, but

fwd servers still don't return anything

fwd servers return HTTP 200 with zero content (content-length: 0 )

UPDATE:  Seems to be a transient issue... coming and going
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Mac on February 02, 2011, 06:49:50 pm
I had this with 1.1.1047. I put a ticket on it and they replied that they have identified this and fixed it in the new release. I upgraded to 1183 and the problem still exists. It's likely not the firmware. I hope they look someplace else now.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ncherry on February 02, 2011, 08:00:48 pm
So is has anyone upgraded? My Vera 1 can't I keep getting:

Quote
ERROR

Cannot communicate with your Vera.
This is after it identifies the IP and some number.

I was able to upload via tftp.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Chimpware on February 02, 2011, 08:38:34 pm
Upgraded my Vera 1 earlier today with no issues.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: saf101 on February 02, 2011, 08:44:31 pm
Update Vera 2 with no issues so far everything is good
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: maks327 on February 02, 2011, 08:44:55 pm
I upgraded my Vera2 from 1047, no problems so far.

Also, it's been mentioned in the remotes thread already, but the TrickTV iphone app (FREE) now works with Vera.  Totally free, works on home wifi or cell data.  That alone is pretty exciting!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: crpeck on February 02, 2011, 09:34:53 pm
Just upgraded my vera1 - no problems so far, I have the iPhone app iVera - which still works great with it.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MNB on February 02, 2011, 09:37:11 pm
Just updated my Vera2 from 1047 to 1183, seemed to update without a problem, however, I now have two boxes with red X where my Hour digit should be... The Hour digit is veiwable while during the inital Load Data. I've already did a Power On reset with no availa.. Help. Mike
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 02, 2011, 10:08:42 pm
I upgraded my Vera2 from 1047, no problems so far.

Also, it's been mentioned in the remotes thread already, but the TrickTV iphone app (FREE) now works with Vera.  Totally free, works on home wifi or cell data.  That alone is pretty exciting!
TrickTV not working for me after update. Made sure I had an account on the website but still nothing. Vera 2
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 02, 2011, 10:11:01 pm
@Michael_N_Blackwell,

Clear your browser cache. Ctrl + F5

JOD.
 
 
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MNB on February 02, 2011, 10:18:03 pm
JOD,

Many thanxs fixed the box problem, question I noticed that the seconds are no longer displaying only the hours and minutes. Personally not a problem for me I never cared for the seconds clocking away.. Mike
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: GT! on February 02, 2011, 10:20:14 pm
Upgraded my Vera 1 earlier today with no issues.

Same here.  Upgrade was smooth, so far everything seems to be working.  I'm hoping the reboot problem is solved.

-GT
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: halfpress on February 02, 2011, 10:27:23 pm
 Eager to test the new beta since my Vera2 - which does very little and has seen no configuration changes in weeks - wigs itself out sometimes multiple times per day, then runs for a few days just fine. No rhyme or reason to it that I've seen. I'm hoping maybe the USB storage expansion and other fixes might resolve this. We'll see.

 Anyway - is there a direct way to download the firmware and apply it? That infuriating website that is supposed to find a vera on my network has never worked for me - even when it was fresh out of the box. My vera has a static IP address that I configured after I worked my way past the failed find/startup process on the first day, so I wasn't expecting the beta update process to reopen that issue for me.

Thanks!
 - Aaron

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 02, 2011, 11:33:41 pm

 Anyway - is there a direct way to download the firmware and apply it? That

If you have a V2 the link is:

[Link to Beta Firmware redacted]

Copy and past it in the custom MiOS firmware field in advanced / firmware
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ctbaker on February 02, 2011, 11:51:10 pm
If you get a "?" in your battery icon instead of the correct battery level for your lock. Do a Control+F5 as JOD mentioned in a previous post to fix the problem.

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mda on February 03, 2011, 12:19:26 am
in 1183 on Vera2 i can no longer delete insteon devices and the insteon keypadlinc dimmer switch (the switch with the load) that worked somewhat in 1062 (even though it would not stay in sync it was controllable) is no longer controllable. the IOLinc relay still works well though. (using a 2413U PLM).

otherwise seems to be working well and upgrade was hassle free
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: hankai on February 03, 2011, 07:03:59 am
My Vera2 did not like to loose it's old firmware(1147). When upgradning my V2 would not take 1183, but instead telling me on the firmware tab that the "platform" was wrong. After a new try after reboot my V2 infact auto downgraded to an old firmware before the 1047?? then telling me to upgrade to 1147 again because my firmware was outdated, right ??? Not a word about the 1183. I then copied the link from strangely into the URL for MiOS custom firmware in the firmware tab. When taking backup it went wrong again, no backup, so had to go to the backup tab to make one from there, and that worked. Started firmware backup from firmware tab direct now without backup first and this time it worked, but my wifi setup was gone, ssid diplaying openwrt in the wifi tab. Not able to set up my old wifi again with my home lan network. Had to hook up directly into Vera to change anything in the wifi tab. Everything working now, but i wasted 4 hrs on this. :o
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: hankai on February 03, 2011, 07:10:26 am
No 24hrs option in time display, only PM/AM?? Is it my Vera2, or.....

Thank's
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 03, 2011, 07:12:38 am
A couple of my scenes have really slowed down. I have a scene that runs when I activate my stair lights that turns on the middle floor hall light. This scene always finished running by the time I made it down the stairs but this morning I made it down the stairs, down the hall and to the coffee maker before it ran. I also have a "Downstairs Off" scene that I counted to 87 before it ran.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MNB on February 03, 2011, 08:23:53 am
After upgrading last night, everything worked great was able to access controller locally and via MyMIOS without issue. Tried this morninig and got message was unable to start MySQL server, tried for the second time and and my MyMIOS logon screen wouldn't continue. I am still able to access locally. If I were a betting person, looks like Vera Servers are either frozen or down. Anyone else have same issues. Mike
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MNB on February 03, 2011, 08:30:13 am
Belay my last comment, seems to be up and running again... :-* P.S MCV and beta tester, I ditto the majority of comments, so far, I seem to be access quicker and without issues, my device seem to work correctly and I for one am happy once again. Many thanxs.

MCV now that you've got this release out, please start working on your communications skills to keep us in light as to what your up to and what future release/fixes we can expect, also how does TrickTv and Vera work and what is the future according to MCV would be welcomed in the company Blog once in a while (maybe monthly?). Mike
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 03, 2011, 08:56:26 am
@mbairhead,

Do you have any devices out of config (red halo's) ?
If so, Vera could have been trying to configure those devices at the time the scene executed, timed event or device trippped, you will see blue halo's around delayed devices.
Just a thought.

JOD.

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 03, 2011, 09:03:12 am
JOD - I just ran it again and it was all green halos (downstairs off), the one that turns the hall on is just one device and it's green as well.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: bennynations on February 03, 2011, 09:09:18 am
Everything was smooth for my local Vera1 and the Vera2 400 miles away.  Seem to be running smoothly.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 03, 2011, 09:41:07 am
The upgrade was smooth but I noticed one minor issue.  The temperature reading for the Fortrezz WMA-01 still does not show up on the GUI.  You need to view it still from the Control tab.

Edit:  One more problem, any value entered in "Fire warning event when battery is below:" for a Schlage door latch is lost and not saved.
Edit2: 3 in 1 sensor; Device Options, current parameter values (1-6) are showing up in the heading "Desired Value" and not under "Current Value"
Edit3: All optional parameters in the 3in1 are lost after the firmware upgrade.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: richard_canada on February 03, 2011, 10:00:28 am
Has anyone upgraded from V1 996 to 1183 ?
Can it be done remotely (400 miles away)...
Do I have to upgrade to 1047 first ?

Tks

PS: Only reason to upgrade now is to get panasonic camera PTZ & archiving back
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: TheGadgetGuy on February 03, 2011, 10:26:17 am
If you get a "?" in your battery icon instead of the correct battery level for your lock. Do a Control+F5 as JOD mentioned in a previous post to fix the problem.



Hello.  The "?" replacing the battery icon is NOT a bug.  It is a new feature.

The question mark is intended to indicate that the battery powered device hasn't communicated with Vera in about 7 days.  The purpose is to tell you that the device might have a dead battery, because Vera can't talk to it.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mikemsd on February 03, 2011, 11:29:50 am
Hello.  The "?" replacing the battery icon is NOT a bug.  It is a new feature.

The question mark is intended to indicate that the battery powered device hasn't communicated with Vera in about 7 days.  The purpose is to tell you that the device might have a dead battery, because Vera can't talk to it.

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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: TimAlls on February 03, 2011, 11:30:43 am
Upgraded with no problem. New version allows communication with Leviton controller.....still unable to use Vera as a master due to the inability to properly program Leviton Zone Controllers. It is working fine as a secondary.....
Tim Alls
AllSeas Yachts
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pncortes on February 03, 2011, 11:48:00 am
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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: N5NHL on February 03, 2011, 12:01:59 pm
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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 03, 2011, 12:07:29 pm

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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: terencec on February 03, 2011, 12:19:17 pm
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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: micasaverde on February 03, 2011, 01:08:21 pm
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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: yovinman on February 03, 2011, 01:23:42 pm
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.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: kirbyb on February 03, 2011, 03:21:35 pm
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
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 03, 2011, 03:26:38 pm
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?

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on February 03, 2011, 05:39:29 pm
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!!!!!

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pgrover516 on February 03, 2011, 05:45:22 pm
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
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: kirbyb on February 03, 2011, 05:57:01 pm
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]
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: achalhoub on February 04, 2011, 04:01:23 am
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?)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on February 04, 2011, 11:25:10 am

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.
Title: iVera no longer works remotely with 1183
Post by: santakrooz on February 04, 2011, 05:26:56 pm
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
Title: Re: iVera no longer works remotely with 1183 - UPDATE got working
Post by: santakrooz on February 04, 2011, 05:31:01 pm
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
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sjolshagen on February 04, 2011, 08:33:17 pm
I'm using a USB stick on my Vera2 which was upgraded to v1.1.1183 as soon as it posted. For about 48(or so) hours, the Lua engine only restarted once every 8(ish) hours. As of 2:30pm ET today, I'm seeing roughly hourly restarts which (again) affect the reliability of luup.call_delay() functions (they get "lost"). I was pleasantly surprised by the initially much longer restart times (went from about 4-6 hours/restart to 8-12 hours/restart with 1.1.1183), but the acceleration I'm seeing now is a bit troubling.

I have _not_ rebooted my Vera2 to see if this is an anomaly as it may be of interest to Micasaverde to troubleshoot it (let me know and I'll open the system for tech support again)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: saf101 on February 04, 2011, 09:14:15 pm
The upgrade went very smooth all seems working but was poking around with Scene and it seems like the tab remote is showing Received invalid response when this had a list of remote in 1.1.1047. Have the remotes move and also for IR in the third icon from the wizard has a drop down box but nothing in it.

Scott
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 04, 2011, 11:43:42 pm
I found another problem.  I have two Leviton RZCS4 4 scene controllers.  I decided to assign scenes to each button using the "Scenes" tab.  After assigning a scene for both on and off I did a "Save"  The scenes in the controller didn't work so I went back into each scene and looked at the auto_Generated scene and noticed that the "Enabled" box was not checked.  I checked it for all the scenes and did a "Save" again.  Looked at the scene again and once more the auto_Generated scene was not checked.  The off scenes do not work at all.  I programmed the scenes manually and removed all settings from the "Scenes" tab and everything except the off scenes worked again.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ridgecat on February 04, 2011, 11:56:20 pm
Forward servers no longer work.  Updated to 1.1.1183. 

http://sta1.mios.com/locator_json.php reported the vera2 (though it still listed the previous firmware version)

http://fwd1.mios.com/username/password/serial/data_request?id=lu_alive or any other data request doesn't return anything, same when using fwd2.mios.com

I am forwarding over the Internet from my cell phone with no problems. Try fwd2.mios.com instead of fwd1.mios.com. [sorry about the fwd2 suggestion; I didn't see your comment about fwd2 in your original post. It's just late here.

Vera-2 running 1183.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ridgecat on February 05, 2011, 12:19:21 am
I found another problem.  I have two Leviton RZCS4 4 scene controllers.  I decided to assign scenes to each button using the "Scenes" tab.  After assigning each scene for both on and off I did a "Save"   <snip >  The off scenes do not work at all.  I programmed the scenes manually and removed all settings from the "Scenes" tab and everything except the off scenes worked again.

I have the same problem. When you activate a scene, does the green LED come on for about 5 seconds and then go out as does mine? If so, you can probably get the off scenes to run if you hit the button, wait about a second or so, then hit it again while the LED is still green. Let me know your experience.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mda on February 05, 2011, 01:46:22 am
With 1183 on ver2:

1. I am sometimes getting 2 or 3 notifications when i enter a pin on my kwikset lock. Other times I just get one.

2. Awhen i enter pin #1, the vera notification says I entered pin #2. All other pin notifications reference the correct pin.

I have reset the lock and added all pins again through Vera. That did not resolve either problem.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sjolshagen on February 05, 2011, 08:24:41 am
My LuaEngine restart frequency has remained consistent all through the night with a restart every 60 minutes. This is a problem for me since I've got luup/lua code that uses the call_delay function with a value of greater than 60 minutes and thus the action does not get triggered as the LUA engine got restarted.

I recognize that a Lua engine restart beats a full on Vera reboot, but frankly, the improvement is only marginal IMHO.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sjolshagen on February 05, 2011, 08:40:26 am
Just downloaded the LuaUPnP.log file to review from the last restart and it almost seems as if the LUA engine restarts because the energy reporting fails to connect with evt2.mios.com (get several "Operation timed out after 10000 milliseconds" messaged leading up to the following:

02      02/05/11 8:30:49.290    FileUtils::ReadURL pos: -1 ret 0 foo empty output:
error: curl: (28) Operation timed out after 10000 milliseconds with 0 bytes received <0x402>
2011-02-05 08:30:49 - LuaUPnP Terminated with Exit Code: 245

I'll be monitoring this going forward.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sjolshagen on February 05, 2011, 10:43:33 am
Quote
I'll be monitoring this going forward.

It's consistent. Every restart, on the hour, comes after curl timeouts and the File:ReadURL error listed above. I'm putting together a support incident report.

Additionally, it seems I can't send in a problem report from "Advanced"->"Tech Support". It fails with "Incorrect Response".
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pkitch on February 05, 2011, 11:07:50 am
Scene notifications from Events are lost/deleted when saved.

Add a new scene notification, save it, come back and it has disappeared.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: RobertN on February 05, 2011, 11:39:07 am
Anyone getting any notifications? My Door opened with PIN code notification has not being received yet...
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 05, 2011, 01:36:03 pm
ridgecat

When I press a scene button on my RZCS4 4 scene controller the green LED flashes for a split second only.  I have not found a way to activate the "Off" scenes.  I have tried to quickly press the button then press it again, no results.  I can see the scenes listed in the Control tab, they look fine, I'm stumped.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: terencec on February 05, 2011, 01:47:21 pm
UI has frozen but the Vera engine seems to be running normally judging by luup.log entries in PuTTY. This is the second instance since I upgraded.

Action messages under the device boxes no longer appearing.

3-in-1 temp sensor showing 18C when log shows 21C.

Continuous "Sever Busy" message on UI

Restart button not responding. Can get the "Edit Startup Lua" to show from MIOS Developers but clicking Go and Save clears the Save flag but otherwise appears to have no effect.

Closing the UI and opening a new instance solves the problem.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ctbaker on February 05, 2011, 01:51:43 pm
Anyone getting any notifications? My Door opened with PIN code notification has not being received yet...

My kid tried to open a kwikset lock about 30 mins ago and started jacking with the handle as soon as the code was entered causing the door to fail to operate and a text message went to my phone immediately.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: RobertN on February 05, 2011, 02:21:11 pm
Thanks - but I am still not getting any notifications. I see the logs as follows:

05-02-2011 01:04:58    Garage door opened UserID=\"3\" UserName=\"xxxx\"
Device Description    GarageEntr
Room    
Text    User: xxxx
11
Notifications to users
#    Username    Destination    Notification Type    Notification Result
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on February 07, 2011, 07:47:26 am
MCV or Beta Testers --

  OK we have made significant progress with 1.1.1183. That's great!! Thanks

  There still remains several bug fixes that need to be resolved.  When can we expect for the next release of new firmware?

  
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 07, 2011, 11:53:06 am


  There still remains several bug fixes that need to be resolved.  When can we expect for the next release of new firmware?

  

I suggest detailing your bugs here and also cross checking with bugs.mios.com to see if your issues have been raised already. If you don't see them, then you should create one.

There was hint of a February release also, but given this release was held up, my guess would be that the date would be pushed back a month or so.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on February 07, 2011, 11:59:24 am
Hi Strangely --

  Good idea! But a quick review of bugs.mios.com suggests that not many of our recent bug reports have made it into Mantis.

  How can we get the 1.1.1183 bugs entered into the system? I have a mantis account but it does not give me access to all of the required fields so I can submit problems.

  Any thoughts?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: smarttechnology on February 07, 2011, 04:47:24 pm
I have just upgraded to this beta and have now lost total control of my iTach (gc100) device. This worked perfectly with the old firmware but I suffered Un related crashes etc. I have put a ticket in but have had no response from mcv. Has anyone got a gc100 working with this firmware?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: guessed on February 07, 2011, 04:55:19 pm
I have just upgraded to this beta and have now lost total control of my iTach (gc100) device. This worked perfectly with the old firmware but I suffered Un related crashes etc. I have put a ticket in but have had no response from mcv. Has anyone got a gc100 working with this firmware?

See Bug# 1393, as it's likely related:
     http://bugs.micasaverde.com/view.php?id=1393

The only way to know for sure would be to enable Verbose logging, login (SSH) and look at the logs during an IR Operation, but it's likely a generic "IR-Device" problem, given what I've seen so far (it also impacts the MiOS Plugin for SQBlaster)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: saf101 on February 07, 2011, 06:28:34 pm
Schlage Lock use to have a event valid pin any user would be nice to have back. not I have to setup for a exact pin so for each person have to ad a event to the event.I would log this but not sure how can see the bug log but will not allow me to add

Scott
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: scotthay on February 07, 2011, 08:27:36 pm
I would like to see that added back in also.

Schlage Lock use to have a event valid pin any user would be nice to have back. not I have to setup for a exact pin so for each person have to ad a event to the event.I would log this but not sure how can see the bug log but will not allow me to add

Scott
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: saf101 on February 07, 2011, 08:44:56 pm
Schlage Lock issues II have a scene created Valid Pin entered XXXX then turn on two lights and leave on for 5 min then turn off. is not working on 1.1.1183. It was working in previous build,

Thank you Scott
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: smarttechnology on February 08, 2011, 03:16:58 am
I have just upgraded to this beta and have now lost total control of my iTach (gc100) device. This worked perfectly with the old firmware but I suffered Un related crashes etc. I have put a ticket in but have had no response from mcv. Has anyone got a gc100 working with this firmware?

See Bug# 1393, as it's likely related:
     http://bugs.micasaverde.com/view.php?id=1393

The only way to know for sure would be to enable Verbose logging, login (SSH) and look at the logs during an IR Operation, but it's likely a generic "IR-Device" problem, given what I've seen so far (it alsoimpacts the MiOS Plugin for SQBlaster)




Thank you Guessed very helpful as always. I will have a look at the logs just to make sure.

Damn annoying as my whole sq remote setup is currently rendered useless!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 08, 2011, 07:01:16 am
Ok, I decided to stay off the forum for a few days after upgrading to let the new OS speak for itself. Here's my experience so far...it's basically the same. I lost a fan switch when installing and my scenes are running slower but beyond that, I don't see much difference.

Here's what I was hoping for, and maybe it's there and I just don't see it.
1. Clear, easy to read documentation that is easy to find. (the search function on the wiki SUCKS!)
2. Support for the Puck (without having to write a bunch of code)
3. and/if control of scenes
4. The ability to run a "Heal" without spending 2 days trying to get my locks to work again

Did any of these come to be?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Vali on February 08, 2011, 07:20:48 am
           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.

a. Looks like backup headers were sent incorrectly when you uncheck "Backup my configuration at MiOS.com" via remote access server, so the backup was sent as text/html instead of being sent to download. I fixed the problem, it should work right now.
b-c. We're currently trying to reproduce the issue, I'll keep you posted about cause and fix.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Ap15e on February 08, 2011, 07:44:57 am
Quote
a. Looks like backup headers were sent incorrectly when you uncheck "Backup my configuration at MiOS.com" via remote access server, so the backup was sent as text/html instead of being sent to download. I fixed the problem, it should work right now.

Same problem with (remote connection via cp.mios.com):
'MiOS developers' -> 'Luup files' -> 'Download'

Still not fixed (remote connection via cp.mios.com):
'MiOS Marketplace' -> check 'Show unreleased beta plugins' -> go to page 2

Code: [Select]
Not Found

The requested URL /sid-... was not found on this server
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 08, 2011, 09:36:34 am
4. The ability to run a "Heal" without spending 2 days trying to get my locks to work again
Did any of these come to be?
This was a known issue of this release. Due to the stability issue complaints and the pressure from users to hurry, MCV decided to let 1.1.1183 out with the heal network issue.

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 08, 2011, 10:15:01 am
This was a known issue of this release. Due to the stability issue complaints and the pressure from users to hurry, MCV decided to let 1.1.1183 out with the heal network issue.

JOD.

That's actually pretty low on my list, I don't actually know what benefit their is to running a "Heal" since the first/last time I ran it I lost so much time trying to fix the heal.

I really don't expect these guys to walk on water and they really do have a nice product but it would be SUPER cool if they'd let people know how to actually use it. Mine has been pretty stable lately and it does most things I want it to do but it sure would be nice to know what it's capable of and how to achieve it.

I guess I feel pretty let down by this "upgrade". We were told "it's coming, it's coming, be patient, it's going to be great" by the beta testers for a long time but here it is and I don't see any advantages.

Again, I don't want MCV or the beta tester to take this as a slam on the product or their work, I would just like something that explains it to me. I would like to see the things promised, such as The Puck support that we've been hearing so much about, the "and/if" control everyone is asking for.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 08, 2011, 10:44:01 am
This was a known issue of this release. Due to the stability issue complaints and the pressure from users to hurry, MCV decided to let 1.1.1183 out with the heal network issue.

JOD.

That's actually pretty low on my list, I don't actually know what benefit their is to running a "Heal" since the first/last time I ran it I lost so much time trying to fix the heal.

I really don't expect these guys to walk on water and they really do have a nice product but it would be SUPER cool if they'd let people know how to actually use it. Mine has been pretty stable lately and it does most things I want it to do but it sure would be nice to know what it's capable of and how to achieve it.

I guess I feel pretty let down by this "upgrade". We were told "it's coming, it's coming, be patient, it's going to be great" by the beta testers for a long time but here it is and I don't see any advantages.

Again, I don't want MCV or the beta tester to take this as a slam on the product or their work, I would just like something that explains it to me. I would like to see the things promised, such as The Puck support that we've been hearing so much about, the "and/if" control everyone is asking for.
You likely feel this way because you weren't blighted by many of the serious issues some users had! I was also lucky in that mine has been pretty stable and therefore wouldn't have seen a major difference unless I know what went into getting it working for some folks.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: TheGadgetGuy on February 08, 2011, 11:06:33 am
Ok, I decided to stay off the forum for a few days after upgrading to let the new OS speak for itself. Here's my experience so far...it's basically the same. I lost a fan switch when installing and my scenes are running slower but beyond that, I don't see much difference.

Here's what I was hoping for, and maybe it's there and I just don't see it.
1. Clear, easy to read documentation that is easy to find. (the search function on the wiki SUCKS!)
2. Support for the Puck (without having to write a bunch of code)
3. and/if control of scenes
4. The ability to run a "Heal" without spending 2 days trying to get my locks to work again

Did any of these come to be?



The main focus of this latest firmware was bug fixes.  There were a lot of seemingly minor issues within Vera that had caused the user experience to be very poor for some people.  Lots of system restarts, reliability issues, etc.  The focus of the firmware was not to add new functionality.

Follow this link for release notes on the firmware.  Then, maybe you will see the extent of the efforts.  There are a LOT of fixes included in this release...

http://wiki.micasaverde.com/index.php/Release_Notes
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pgrover516 on February 08, 2011, 11:28:58 am
I hold my breath (dont jinx me!) while saying this but my system had been much more reliable since upgrade, I had scenes that would run in 3-10 seconds sometimes, and 1-3 minutes (or not at all) other times, since upgrade they have run every time in less than 5 seconds (knocking on wood!), as others have mentioned the focus of this release was on stability not features and my experience has been a substantial improvement, rest assured the drumbeat for contined improvements is already sounding behing the scenes, overall though the end user experience is going to be shaped by each persons particular setup on whether they will notice improvements or lack thereof
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 08, 2011, 11:53:52 am

I feel your frustration and if it gives you any peace of mind, there are a bunch of great guys working every day here both in front and behind the scenes pushing for everything you can imagine to better the product.

Hang in there...

JOD.

Uh....no there's not.
 
As I’ve said before, the beta testers are end users, we suffer the same problems that everyone else suffers from. My comment above was letting you all know that the beta testers are working behind the scenes to make Vera a better product and they push MCV every day to try to achieve that. That’s probably why MCV has no time to make announcements, they are tied to their desks working hard on the next release....
Seriously though, 1.1.1183 contained more fixes than I’ve seen in one release and yes, there are still issues that need to be resolved. One way to help get issues resolved is to post them. If possible, record them on Mantis too..

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: fall-line on February 08, 2011, 12:32:12 pm
I just read through the mantis bug, but just wanted to be certain. It is expected that the SQ blaster plugin is totally broken with the new firmware? So far this is the only functionality that I have lost with the 1183 upgrade. I have IR commands built into several key scenes, so I'm finding I miss it more than I expected.

Thanks



See Bug# 1393, as it's likely related:
     http://bugs.micasaverde.com/view.php?id=1393

The only way to know for sure would be to enable Verbose logging, login (SSH) and look at the logs during an IR Operation, but it's likely a generic "IR-Device" problem, given what I've seen so far (it also impacts the MiOS Plugin for SQBlaster)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: TheGadgetGuy on February 08, 2011, 12:44:29 pm
No, SQ Remote should work just as before.  There are no reported issues on that as of now.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: fall-line on February 08, 2011, 12:56:03 pm
SQ Remote iOS app is working fine for both Vera and SQ Blaster control for me. The problem I'm having is controlling the SQ Blaster from Vera scenes via @guessed's SQ_Blaster plugin (http://code.mios.com/trac/mios_sqblaster (http://code.mios.com/trac/mios_sqblaster)).

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mhn on February 08, 2011, 12:56:26 pm
http://forum.micasaverde.com/index.php?topic=4987.0

"I have been told by MCV that this has now been fixed, and the next official release of Vera firmware will no longer have this problem. So something WAS broken... thanks to everyone (especially krfar) for bringing this to our attention.

John "
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: TheGadgetGuy on February 08, 2011, 01:50:22 pm
@fall-line:  Sorry, misread your original post.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: bdevaux on February 08, 2011, 02:36:07 pm
my 2 cents as a new user with few items, less reboots and all works as is
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: micasaverde on February 08, 2011, 03:50:47 pm
We went through the items users have reported so far:

Confirmed regressions that we fixed today:

r1 - mda - can no longer delete Insteon devices

r2 - mda - Keypadlinc dimmer not working

r3 - JimMac - 3-in-1 parameters lost and in wrong column

r4 - pncortes - i/r with gc100 broken

r5 - sjolshagen - restarts every hour (this was a bug in our Energy reporting)

r6 - saf101 - tab remote shows 'received invalid response'

The following issues we do not feel are related to the firmware:

x1 - mvakoc - fwd servers down, several users not getting notification, MySql Error on server: This isn't firmware related.  One of the event servers was getting flooded yesterday.  Our IT guy is working on another update to prevent these problems, but the release of a new firmware isn't effected

x2 - hankai - Wrong platform error: This is something with the configuration of your Vera, and is not firmware related.  Our IT guy is working to figure out why.

x3 - n5nhl - 'update failed': Same as x2

x4 - mbairhead - scenes slowed down: This isn't really firmware related.  The scenes will take longer to run if devices are being configured or the network is busy.

x5 - DonDiego - formatting of repair report missing cr/lf.  They're still there.  Nothing changed.  I think it's a browser issue

x6.  DonDiego - save backup not working.  This seems to be related to some headers getting stripped when using this remotely.  The firmware isn't effected.

x7.  terencec - more than 1 vera on the update page: not firmware related.  Do you have a screen shot?

x8.  terencec: 3-in-1 temp sensor showing 18C when log shows 21C, Continuous "Sever Busy" message on UI.  I found your Vera's logs on our server, and strangely, everything seems to be running fine.  No crashes, no reboots, nothing.  I think it must be a networking problem.

The following issues are not new, so we don't want to hold up this release:

i1.  scotthay: Schlage lock pin event for 'any user'

i2.  ap15e: 'MiOS Marketplace' -> check 'Show unreleased beta plugins' -> go to page 2  (we're in the middle of redoing this whole thing anyway)

To resolve the following issues we would need you to turn on verbose logging (advanced, logs), and after the problem happens again, submit a trouble ticket

d1.  JimMac - Schlage battery low not working

d2.  DonDiego - Schlage schedule doesn't update properly

d3.  pgrover516 - can't change wakeup value

d4.  JimMac - Off Scenes didn't work on the Leviton controllers

d5.  mda: 2 or 3 notifications when i enter a pin on my kwikset lock

d6.  mda: Wwhen i enter pin #1, the vera notification says I entered pin #2

d7.  pkitch: Scene notifications from Events are lost/deleted

d8.  saf101: scene created Valid Pin entered XXXX  not working

Next steps:

We're going to build a new firmware that addresses r1-r6, and release it as a 'beta 2', and then release it publicly if no further regressions are found.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sjolshagen on February 08, 2011, 03:56:23 pm
Credit where credit is due, so I wanted to acknowledge the impressive improvement in communications.

Thanks for the detailed list & update!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 08, 2011, 04:10:39 pm
Credit where credit is due, so I wanted to acknowledge the impressive improvement in communications.

Thanks for the detailed list & update!

Agreed. If MCV just lets us know what's going on then we won't have the feeling we're off on our own. Oh and acknowledge help requests (before just today) would be nice.

So the next several updates are going to be fixes, no new features if I read above right. While I know I would be cursing blue blazes if I was one of the ones without a working Vera and not getting any help, I'm not, so I'm slightly disappointed. Is there any chance of getting better documentation in the mean time?


x4 - mbairhead - scenes slowed down: This isn't really firmware related.  The scenes will take longer to run if devices are being configured or the network is busy.


Can someone explain this to me? These scenes run slow all the time so it can't always be when devices are being configured or the network is busy. And even if it was, why did they slow down with this latest update? (btw, thanks for adding it, I really thought I was shouting down a hole).
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: anthonyris on February 08, 2011, 04:15:25 pm
.1183
- Ditto on not being able to save any values in the "Fire warning event when battery is below" setting. Mine happen to be two ZIR000 sensors. Both have same behavior.

- Battery level not being reported correctly (all show 100%, and batteries are at least 6 mos old...).

Chatty Logs sent with Support ticket.
.//A.

Edit:  One more problem, any value entered in "Fire warning event when battery is below:" for a Schlage door latch is lost and not saved.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pgrover516 on February 08, 2011, 06:32:00 pm
MCV: scratch d3, after giving it some time they seem to be correctly configured. In the past when I changed wakeup interval on these sensors I used to get a status message saying "waiting for wakeup to configure" then upon wakeup/configuration this message would go away. Now when I change the interval I get no message but given enough time they seem to be correctly configured. My bad   :P
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: jsed on February 08, 2011, 07:09:09 pm
Error when changing Vera2 connection to a bridge. Scan for networks will not work- so cannot convert Vera to bridge. 2nd time out of 2 installations of 1.1.1183 beta that this has happened. Reboot does not fix.
Title: ERROR: Invalid Platform
Post by: FrankHill73 on February 08, 2011, 09:11:44 pm
I'm getting the following error message when I launch into the interface.

How do I know what version I'm running?  :-\
Title: Re: ERROR: Invalid Platform
Post by: scotthay on February 08, 2011, 09:52:51 pm
I'm getting the following error message when I launch into the interface.

How do I know what version I'm running?  :-\

I had that happen to a couple units I was updating.   Something went wrong with the firmware update.  In that box on the screen you posted, enter this and update manually again;

[Link to Beta Firmware redacted]


BTW, I had to do it a couple of times for it to take on those units I was having an issue with.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MNB on February 08, 2011, 09:58:42 pm
sjolshagen ditto your comments. MCV again, I would like to thank-you for the recent communications as to whats going on and what your forward plans are. I for one like to be well inform so that know issues are documented and are accordantly dispositioned and worked into the next release. Mike
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MNB on February 08, 2011, 10:05:09 pm
MCV in your recent note i2. ap15e: 'MiOS Marketplace' -> check 'Show unreleased beta plugins' -> go to page 2 (we're in the middle of redoing this whole thing anyway). Can you shed some light as to what redoing means and is there anyway to add the weather plugin as part of a new option? I assume that this is not part of the firmware but rather a web page/server function? Mike

Title: Re: ERROR: Invalid Platform
Post by: FrankHill73 on February 08, 2011, 10:16:54 pm
I'm getting the following error message when I launch into the interface.

How do I know what version I'm running?  :-\

I had that happen to a couple units I was updating.   Something went wrong with the firmware update.  In that box on the screen you posted, enter this and update manually again;

[Link to Beta Firmware redacted]


BTW, I had to do it a couple of times for it to take on those units I was having an issue with.

I did try the manual update as well, didn't seem to help. I'll give it a shot a few more times. Thanks!
Title: Re: ERROR: Invalid Platform
Post by: scotthay on February 08, 2011, 10:51:43 pm
I'm getting the following error message when I launch into the interface.

How do I know what version I'm running?  :-\

I had that happen to a couple units I was updating.   Something went wrong with the firmware update.  In that box on the screen you posted, enter this and update manually again;

[Link to Beta Firmware redacted]


BTW, I had to do it a couple of times for it to take on those units I was having an issue with.

I did try the manual update as well, didn't seem to help. I'll give it a shot a few more times. Thanks!


One of the units I had this problem with (I was upgrading remotely) I couldn't get back into from cp.mios.com, the url didn't work because it was changed to a different firmware version in the url, I manually changed it to the old firmware (or new, I can't remember now) and was able to get into it ok to get the update completed and then reboot the unit and all was well at that point.

Good luck.

Title: Re: ERROR: Invalid Platform
Post by: FrankHill73 on February 08, 2011, 11:03:33 pm
I'm getting the following error message when I launch into the interface.

How do I know what version I'm running?  :-\

I had that happen to a couple units I was updating.   Something went wrong with the firmware update.  In that box on the screen you posted, enter this and update manually again;

[Link to Beta Firmware redacted]


BTW, I had to do it a couple of times for it to take on those units I was having an issue with.

I did try the manual update as well, didn't seem to help. I'll give it a shot a few more times. Thanks!

Still no go after several manual installations. Hope MCV gets it resolved.
Title: Re: ERROR: Invalid Platform
Post by: scotthay on February 08, 2011, 11:08:03 pm
I'm getting the following error message when I launch into the interface.

How do I know what version I'm running?  :-\

I had that happen to a couple units I was updating.   Something went wrong with the firmware update.  In that box on the screen you posted, enter this and update manually again;

[Link to Beta Firmware redacted]


BTW, I had to do it a couple of times for it to take on those units I was having an issue with.

I did try the manual update as well, didn't seem to help. I'll give it a shot a few more times. Thanks!

Still no go after several manual installations. Hope MCV gets it resolved.

I assume you have rebooted a couple times?

You might try another firmware and then try to upgrade.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: micasaverde on February 08, 2011, 11:50:19 pm
I just emailed Frank.  If the upgrade doesn't work, rather than trying to force it, it would be nice if we could get in using the log-me-in support remote desktop system so we can see why it's not working and fix it.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: scotthay on February 09, 2011, 01:08:05 am
I just emailed Frank.  If the upgrade doesn't work, rather than trying to force it, it would be nice if we could get in using the log-me-in support remote desktop system so we can see why it's not working and fix it.

FYI, On the units I had problems with, in the past I have had internet issues at those particular installations.  I assumed that was the issue with the updates.  If you figure out something else, I would appreciate knowing what the issue was. 
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on February 09, 2011, 07:39:56 am
MCV-

  As users I know we have been impatient for bug fixes and for a clear plan for the future.

  Been impressed with the latest release and your plan to fix the few remaining issues. Thank you.

 :)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: FrankHill73 on February 09, 2011, 10:10:01 am
I just emailed Frank.  If the upgrade doesn't work, rather than trying to force it, it would be nice if we could get in using the log-me-in support remote desktop system so we can see why it's not working and fix it.

I just replied with an e-mail and the connection parameters.

Thanks
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mtncomm1 on February 09, 2011, 10:36:54 am
My Vera1 is not seen on MiOS, and therefore I have been unable to migrate from UI2 to UI4. Is there a direct link to download (Vera1 compatible) firmware so I can update my Vera1 locally, from UI2 to UI4 (1.1.1183)? I've seen other posts from users requesting info on updating their Vera1's, but nothing in the way of comprehensible answers.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 09, 2011, 11:30:03 am
My Vera1 is not seen on MiOS, and therefore I have been unable to migrate from UI2 to UI4. Is there a direct link to download (Vera1 compatible) firmware so I can update my Vera1 locally, from UI2 to UI4 (1.1.1183)? I've seen other posts from users requesting info on updating their Vera1's, but nothing in the way of comprehensible answers.
Try this:

http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1183-1.trx
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mtncomm1 on February 09, 2011, 12:01:03 pm
My Vera1 is not seen on MiOS, and therefore I have been unable to migrate from UI2 to UI4. Is there a direct link to download (Vera1 compatible) firmware so I can update my Vera1 locally, from UI2 to UI4 (1.1.1183)? I've seen other posts from users requesting info on updating their Vera1's, but nothing in the way of comprehensible answers.
Try this:

http://download.mios.com/betafirmware/wl500gP_Luup_ui4-1.1.1183-1.trx

Thanks! Unlike my prior attempt to upgrade to 1047, this one worked fine. However, MiOS is not allowing me to activate my Vera1. Vera asks for my MiOS username and password, and when I hit the "activate" button it does nothing. I have tried to activate from the MiOS site, but the activation code sent in a past activation email does not work. So how do I know what the activation code is, OR how to obtain one???
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: fall-line on February 09, 2011, 03:21:16 pm
@MCV, just a quick note to corroborate the experience that mbairhead has reported with scene execution slowness. It's a difficult thing to measure exactly (performance pre & post upgrade) since the scene execution time fluctuates due to network activity, etc as you mentioned, but I definitely do feel as though my scenes have slowed down on the new 1.1.1183 firmware.

Larger scenes (those involving more than 5 devies) are taking upwards of 15 seconds to execute now, which is making for a less than ideal user experience. I've attempted to run a repair (heal) operation (though I unchecked the reconfigure all devices when done option) which had no impact.  Any suggestions?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: terencec on February 09, 2011, 03:47:37 pm
UI has frozen but the Vera engine seems to be running normally judging by luup.log entries in PuTTY. This is the second instance since I upgraded.

Action messages under the device boxes no longer appearing.

3-in-1 temp sensor showing 18C when log shows 21C.

Continuous "Sever Busy" message on UI

Restart button not responding. Can get the "Edit Startup Lua" to show from MIOS Developers but clicking Go and Save clears the Save flag but otherwise appears to have no effect.

Closing the UI and opening a new instance solves the problem.

Another instance of the UI freezing. Scenes trigger OK and clock advances but UI otherwise not updated. No "Server Busy" this time
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pgrover516 on February 09, 2011, 04:42:32 pm
re: whatever scene slowdowns users are seeing, there is more to it than number of devices as I have scenes with 15 devices which are faster and far more reliable since upgrade, I am not doubting your problem, just that there is something beside number of devices, I would still submit a ticket, even if it is not a firmware "failure" per se, tech support ought to be able to read your logs and give a breakdown of where the time is going
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: buerger on February 09, 2011, 04:45:44 pm
I can't get the energy usage to work at all?   Is there a bunch of setup required?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: krfar on February 09, 2011, 05:52:36 pm
I tried upgrading from .1093 to .1183 and I kept getting "Communication Error" message so I downloaded the firmware file.  My two problems still persists, timer reverts back to central time and I cannot get GC100 to work with Sq Connect.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Les F on February 09, 2011, 07:12:09 pm

Network config changed on me...

Just upgraded from 1047 to 1183 and have seen same problem that has bit me before.  My vera is set with a static ip using "Through another gateway on my network. MiOS is a switch". After the upgrade it switched itself to "automatically configure" and would not talk on the network.  I hooked up eth2, changed configuration back to the original network config, selected static and is started working again.  If in fact it really was in a DHCP mode it was not getting an address.   When in this state the eth1 light flashed what I would call a  blink, blink, rest pattern.  Other than that it looks great.  Firmware seems to be working fine.

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: micasaverde on February 10, 2011, 06:05:12 pm
Here is an additional list of items that have been reported with 1183.  It includes technical details for those who may be inclined...  Post 1 of 2 (too big for 1 post).  The bottom line is that we've fixed the regressions in 1183 which we could confirm as fixable, so we're going to do a new beta/release candidate and try to get it live as soon as possible.

1.  JOD: reports device #54 is showing unlocked, but it really is locked, and that the notifications are missing.

result: Don't see a problem.

I see in our database notification id 83384 at 00:07:16 door locked, then id 83394 at 07:35:58 door unlocked, then id 83404 door locked, then id 83454 at 12:06:33 door unlocked, then id 83484 at

13:59:54 door locked.  JOD reported at 13:12 that it was out of sync and the door was locked, but reported as unlocked.  I've combed through all the logs, and Vera seems to be working fine.  The

door lock simply never reported that it was locked, so Vera thought it was unlocked.

2.  JOD: The door lock didn't trigger a scene

result: Don't see a problem

It did trigger the event.  Here's the log:
02/10/11 12:06:33.373   Event::Evaluate 1 Front Door Unlocked scene Front Door Opened or Unlocked is true
that caused it to run the scene:
02/10/11 12:06:33.515   Scene::RunScene running 1 Front Door Opened or Unlocked <0x803>

That scene has luup code that it aborts if it's not night.  Since it's not night, the scene aborted.  So as far as I can tell everything worked just like it should have.  Vera correctly stopped

running the scene because it's day time.

3.  guessed: can't pick a new IR device.

result: Not sure.  I've asked our web guy to look into it.  I don't remember where the IR device picker was and didn't know there ever was one.  I've asked him to put it back.

4.  jod: 12709 2/10/11 @ 07:00am "John Wakes" scene did not turn On Node 18, device #19 "Master Bed Lamp John". A timed event as part of the same scene for 15 minutes later did not turn Off Node

19, device #20 "Master bed Fan"

result: Generic Z-Wave radio problem

It ran the scene here:
08      02/10/11 7:00:00.011    Scene::RunScene running 15 John Wakes  <0x803>

it turned on the light here:
08      02/10/11 7:00:00.013    JobHandler_LuaUPnP::HandleActionRequest device: 19 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x803>
08      02/10/11 7:00:00.014    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x803>

this was the job #1153:
10      02/10/11 7:00:00.027    JobHandler::AddJob job#1153 :ON node 18

It ran within 3 seconds, and here's the low-level log of all activity on the Z-Wave chip:
41      02/10/11 7:00:03.702    0x1 0xa 0x0 0x13 0x12 0x3 0x20 0x1 0xff 0x4 0xe8 0xc5 (#\n#### #####) <0xc04>
42      02/10/11 7:00:03.951    0x6 0x1 0x4 0x1 0x13 0x0 0xe9 (#######) <0x1406>
42      02/10/11 7:00:03.951    got expected ACK <0x1406>
41      02/10/11 7:00:03.953    ACK: 0x6 (#) <0x1406>
41      02/10/11 7:00:15.041    0x1 0x3 0x0 0x16 0xea (#####) <0xc04>
42      02/10/11 7:00:15.160    0x6 (#) <0x1406>


Note that Vera waited 12 seconds for the Z-Wave chip to send a reply to the command.  It never did.  At 7:00:15 Vera had to abort the job because the Z-Wave chip never reported being able to talk

to the light.  Vera will keep trying to run the job over and over and over until it eventually gets through (hence the blue halo's).  However 15 minutes later, at 7:15:00 there was another command

to that same light, so Vera aborted job #1153.

5.  jod:  2/09/11 @ 15:31:00 my wife emailed me to say the "Arrive Home" scene did not fire when she entered her code (#2) into Node 49

result: Z-Wave issue #9 on our list of 17 Z-Wave issues that plague customers.  I've reported this to Sigma for over a year.  I'm flying to Denmark this weekend to work with Sigma's engineers to

find a resolution to these issues.

There was nothing from the lock at 15:31:00.  There was, however, at 15:37:38 a nonce get from the lock.  Nonce means a use-one-time security code, meaning it wants to send us a message:

Vera is trying to control a different, totally unrelated device
(thermostat) here:

Vera sends:
41      02/09/11 15:37:37.122   0x1 0xc 0x0 0x13 0x3 0x5 0x43 0x1 0x2
0x9 0x52 0x4 0x14 0xed (######C###R###) <0xc04>
Vera receives:
42      02/09/11 15:37:37.391   0x6 0x1 0x4 0x1 0x13 0x0 0xe9 (#######) <0x1406>
Vera sends:
41      02/09/11 15:37:37.412   ACK: 0x6 (#) <0x1406>

Now Vera is waiting for the final REQ on the SendData to the
thermostat, but before it comes in, here's the nonce request from his
lock:
42      02/09/11 15:37:38.801   0x1 0x8 0x0 0x4 0x0 0x31 0x2 0x98 0x40
0x18 (#####1##@#) <0x1406>
41      02/09/11 15:37:38.803   ACK: 0x6 (#) <0x1406>

So, Vera aborts the thermostat command:
41      02/09/11 15:37:38.962   0x1 0x3 0x0 0x16 0xea (#####) <0x803>
42      02/09/11 15:37:39.060   0x6 (#) <0x1406>

And Vera sends the nonce:
41      02/09/11 15:37:39.132   0x1 0x11 0x0 0x13 0x31 0xa 0x98 0x80
0x34 0x67 0x36 0xb3 0x70 0xe7 0x5e 0xb 0x5 0x15 0xda
(####1\n##4g6#p#^####) <0x803>
42      02/09/11 15:37:39.511   0x6 0x1 0x4 0x1 0x13 0x0 0xe9 (#######) <0x1406>
41      02/09/11 15:37:39.522   ACK: 0x6 (#) <0x1406>

But you'll see Vera never gets back the REQ frame indicating the nonce
was successfully transmitted.  Instead, while the above SendData is
still pending, we get several more nonce requests.

42      02/09/11 15:37:41.631   0x1 0x8 0x0 0x4 0x0 0x31 0x2 0x98 0x40
0x18 (#####1##@#) <0x1406>
41      02/09/11 15:37:41.633   ACK: 0x6 (#) <0x1406>
42      02/09/11 15:37:44.631   0x1 0x8 0x0 0x4 0x0 0x31 0x2 0x98 0x40
0x18 (#####1##@#) <0x1406>
41      02/09/11 15:37:44.633   ACK: 0x6 (#) <0x1406>
42      02/09/11 15:37:44.851   0x1 0x8 0x0 0x4 0x0 0x31 0x2 0x98 0x40
0x18 (#####1##@#) <0x1406>
41      02/09/11 15:37:44.853   ACK: 0x6 (#) <0x1406>
42      02/09/11 15:37:47.651   0x1 0x8 0x0 0x4 0x0 0x31 0x2 0x98 0x40
0x18 (#####1##@#) <0x1406>
41      02/09/11 15:37:47.769   ACK: 0x6 (#) <0x1406>

Per an email exchange with Sigma FAE's back when we were working
on the Black & Decker lock and I first reported this problem with
multiple nonce gets and no REQ frame, they said not to send multiple
nonce reports because then when we get the encrypted message we won't
know which nonce it was encrypted with.  So rather than sending
another ZW_SendAbort and a new nonce, we continue to wait for the
final REQ from the SendData.  But you can see the final REQ never
comes in.  This violates the rules of the Z-Wave serial API protocol.  Vera resets the Z-Wave module, and things go back to normal, but whatever message the lock was trying to send was lost.

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: micasaverde on February 10, 2011, 06:06:17 pm
post 2 of 2:

6.  JOD: Blue halo's and delayed scene execution (up to 30 minutes) "waiting for node to reply after 0" #12709 2/6/11 @ 00:29:33

result: Z-Wave issue #9

There was only 1 scene ran between 0:00 and 1:00, here:

0:22:52.209    Scene::RunScene running 29 LV. TV Viewing with Lights

It resulted in about 33 devices being turned on or off.  Here are all the jobs:

10      02/06/11 0:22:52.296    JobHandler::AddJob job#22 :OFF node 32 (0x0xc3db30) N:32 P:25 S:0 <0xc3db30> OFF node 32 type ZWJob_SendData first 0 size 5 <0x4412>
10      02/06/11 0:22:52.310    JobHandler::AddJob job#23 :OFF node 43 (0x0xca2ea0) N:43 P:25 S:0 <0xca2ea0> OFF node 43 type ZWJob_SendData first 0 size 6 <0x4412>
10      02/06/11 0:22:52.323    JobHandler::AddJob job#24 :OFF node 44 (0x0xaa2770) N:44 P:25 S:0 <0xaa2770> OFF node 44 type ZWJob_SendData first 0 size 7 <0x4412>
10      02/06/11 0:22:52.337    JobHandler::AddJob job#25 :OFF node 45 (0x0xcb07a0) N:45 P:25 S:0 <0xcb07a0> OFF node 45 type ZWJob_SendData first 0 size 8 <0x4412>
10      02/06/11 0:22:52.350    JobHandler::AddJob job#26 :OFF node 46 (0x0xab8f40) N:46 P:25 S:0 <0xab8f40> OFF node 46 type ZWJob_SendData first 0 size 9 <0x4412>
10      02/06/11 0:22:52.364    JobHandler::AddJob job#27 :OFF node 29 (0x0xa83d60) N:29 P:25 S:0 <0xa83d60> OFF node 29 type ZWJob_SendData first 0 size 10 <0x4412>
10      02/06/11 0:22:52.381    JobHandler::AddJob job#28 :OFF node 31 (0x0xad1158) N:31 P:25 S:0 <0xad1158> OFF node 31 type ZWJob_SendData first 0 size 11 <0x4412>
10      02/06/11 0:22:52.394    JobHandler::AddJob job#29 :OFF node 37 (0x0xae4dd8) N:37 P:25 S:0 <0xae4dd8> OFF node 37 type ZWJob_SendData first 0 size 12 <0x4412>
10      02/06/11 0:22:52.408    JobHandler::AddJob job#30 :OFF node 39 (0x0xacfbc8) N:39 P:25 S:0 <0xacfbc8> OFF node 39 type ZWJob_SendData first 0 size 13 <0x4412>
10      02/06/11 0:22:52.422    JobHandler::AddJob job#31 :Level 0 node 40 (0x0xab9190) N:40 P:25 S:0 <0xab9190> Level 0 node 40 type ZWJob_SendData first 0 size 14 <0x4412>
10      02/06/11 0:22:52.435    JobHandler::AddJob job#32 :OFF node 30 (0x0xab7a00) N:30 P:25 S:0 <0xab7a00> OFF node 30 type ZWJob_SendData first 0 size 15 <0x4412>
10      02/06/11 0:22:52.451    JobHandler::AddJob job#33 :OFF node 28 (0x0xaad378) N:28 P:25 S:0 <0xaad378> OFF node 28 type ZWJob_SendData first 0 size 16 <0x4412>
10      02/06/11 0:22:52.557    JobHandler::AddJob job#34 :OFF node 21 (0x0xaf9a50) N:21 P:25 S:0 <0xaf9a50> OFF node 21 type ZWJob_SendData first 0 size 17 <0x4412>
10      02/06/11 0:22:52.571    JobHandler::AddJob job#35 :AutoChangeOver node 3 (0x0xaf3b10) N:3 P:25 S:0 <0xaf3b10> AutoChangeOver node 3 type ZWJob_SendData first 0 size 18 <0x4412>
10      02/06/11 0:22:52.781    JobHandler::AddJob job#36 :Cool SP 82 node 3 (0x0xa6cf90) N:3 P:25 S:0 <0xa6cf90> Cool SP 82 node 3 type ZWJob_SendData first 0 size 19 <0x4412>
10      02/06/11 0:22:52.794    JobHandler::AddJob job#37 :Auto node 3 (0x0xa8aa70) N:3 P:25 S:0 <0xa8aa70> Auto node 3 type ZWJob_SendData first 0 size 20 <0x4412>
10      02/06/11 0:22:52.808    JobHandler::AddJob job#38 :ON node 3 (0x0xaf9430) N:3 P:25 S:0 <0xaf9430> ON node 3 type ZWJob_SendData first 0 size 21 <0x4412>
10      02/06/11 0:22:52.820    JobHandler::AddJob job#39 :Heat SP 75 node 3 (0x0xab7c60) N:3 P:25 S:0 <0xab7c60> Heat SP 75 node 3 type ZWJob_SendData first 0 size 22 <0x4412>
10      02/06/11 0:22:52.837    JobHandler::AddJob job#40 :OFF node 12 (0x0xa8f100) N:12 P:25 S:0 <0xa8f100> OFF node 12 type ZWJob_SendData first 0 size 23 <0x4412>
10      02/06/11 0:22:52.851    JobHandler::AddJob job#41 :ON node 17 (0x0xb0b5c8) N:17 P:25 S:0 <0xb0b5c8> ON node 17 type ZWJob_SendData first 0 size 24 <0x4412>
10      02/06/11 0:22:52.867    JobHandler::AddJob job#42 :Level 99 node 20 (0x0xa792f8) N:20 P:25 S:0 <0xa792f8> Level 99 node 20 type ZWJob_SendData first 0 size 25 <0x4412>
10      02/06/11 0:22:52.885    JobHandler::AddJob job#43 :OFF node 18 (0x0xb28fa0) N:18 P:25 S:0 <0xb28fa0> OFF node 18 type ZWJob_SendData first 0 size 26 <0x4412>
10      02/06/11 0:22:52.902    JobHandler::AddJob job#44 :Level 0 node 19 (0x0xb29aa0) N:19 P:25 S:0 <0xb29aa0> Level 0 node 19 type ZWJob_SendData first 0 size 27 <0x4412>
10      02/06/11 0:22:52.916    JobHandler::AddJob job#45 :OFF node 33 (0x0xaa3290) N:33 P:25 S:0 <0xaa3290> OFF node 33 type ZWJob_SendData first 0 size 28 <0x4412>
10      02/06/11 0:22:52.930    JobHandler::AddJob job#46 :Level 0 node 41 (0x0xb13838) N:41 P:25 S:0 <0xb13838> Level 0 node 41 type ZWJob_SendData first 0 size 29 <0x4412>
10      02/06/11 0:22:52.943    JobHandler::AddJob job#47 :OFF node 14 (0x0xa96d98) N:14 P:25 S:0 <0xa96d98> OFF node 14 type ZWJob_SendData first 0 size 30 <0x4412>
10      02/06/11 0:22:52.957    JobHandler::AddJob job#48 :OFF node 13 (0x0xa7dad8) N:13 P:25 S:0 <0xa7dad8> OFF node 13 type ZWJob_SendData first 0 size 31 <0x4412>
10      02/06/11 0:22:52.971    JobHandler::AddJob job#49 :OFF node 15 (0x0xaae390) N:15 P:25 S:0 <0xaae390> OFF node 15 type ZWJob_SendData first 0 size 32 <0x4412>
10      02/06/11 0:22:52.985    JobHandler::AddJob job#50 :OFF node 16 (0x0xab8c38) N:16 P:25 S:0 <0xab8c38> OFF node 16 type ZWJob_SendData first 0 size 33 <0x4412>
10      02/06/11 0:22:52.998    JobHandler::AddJob job#51 :Level 0 node 38 (0x0xaed270) N:38 P:25 S:0 <0xaed270> Level 0 node 38 type ZWJob_SendData first 0 size 34 <0x4412>
10      02/06/11 0:22:53.033    JobHandler::AddJob job#52 :OFF node 36 (0x0xa90c58) N:36 P:25 S:0 <0xa90c58> OFF node 36 type ZWJob_SendData first 0 size 35 <0x4412>
10      02/06/11 0:22:53.051    JobHandler::AddJob job#53 :ON node 74 (0x0xa98fc8) N:74 P:25 S:0 <0xa98fc8> ON node 74 type ZWJob_SendData first 0 size 36 <0x4412>

So far, it seems that in every case the problem was caused by the Z-Wave module in Vera manifesting that same 'issue #9' where it doesn't send back a REQ frame:
10      02/06/11 0:23:15.351    JobHandler::Run ready to run job#22 :OFF node 32 (0x0xc3db30) N:32 P:25 S:0 OFF node 32 status 0 <0xc3db30> priority 25 tNextRunAttempt 0 <0xc04>
41      02/06/11 0:23:15.412    0x1 0xa 0x0 0x13 0x20 0x3 0x20 0x1 0x0 0x4 0x2b 0xcb (#\n## # ###+#) <0xc04>
42      02/06/11 0:23:15.641    0x6 0x1 0x4 0x1 0x13 0x0 0xe9 (#######) <0x1406>
42      02/06/11 0:23:15.660    got expected ACK <0x1406>
41      02/06/11 0:23:15.662    ACK: 0x6 (#) <0x1406>

The Z-Wave chip should have replied with a REQ frame.  It didn't, so Vera has to abort the job:
10      02/06/11 0:23:26.704    JobHandler::Run ready to run job#22 :OFF node 32 (0x0xc3db30) N:32 P:25 S:5 OFF node 32 status 5 <0xc3db30> priority 25 tNextRunAttempt 1296969806 <0xc04>
41      02/06/11 0:23:26.752    0x1 0x3 0x0 0x16 0xea (#####) <0xc04>
42      02/06/11 0:23:26.870    0x6 (#) <0x1406>

This repeats for every job.  I know customers, like John, naturally blame us for this.  And, we are the seller of the system, so we are responsible for working with Sigma to get these Z-Wave

problems resolved.  Unfortunately, though, at this point the only solution we've found that works is to use multiple Veras.  You have to break a complex Z-Wave network into smaller networks, each

is a separate Z-WAve network with it's own Vera.  Each Z-Wave network has little or no routing involved because each Vera is within direct range of the nodes it's paired with.  All the Veras can

then be 'virtually' bridged if they're on the same network.  It's a function of our software -- not Z-Wave -- to combine all the devices into one so they appear as one home.  As far as Z-WAve is

concerned, they're all small networks, though.  I'm going to Denmark over the next week for Sigma meetings and will report what I can about these issues.

7.  JOD: Heal network not working

result: Something odd happened.  Fortunately it appears to be a bug in our code, so it's fixable.  There wasn't enough logging in a certain function to know the cause though.  I've added an extra

log entry for this code, and will start a new heal so when it happens again the log will let me pinpoint the cause of the issue.

8.  JOD: Failed to go into learn mode

result: Z-Wave bug

We see this problem a lot.  Here's the log of the Serial communication with the Z-Wave chip.

41      02/03/11 13:52:41.442   0x1 0x5 0x0 0x4a 0x82 0x1 0x33 (###J##3) <0xc04>
42      02/03/11 13:52:41.582   0x6 0x1 0x7 0x0 0x4a 0x1 0x7 0x0 0x0 0xb4 (####J#####) <0x1406>


In the first line, Vera is sending the 0x4a command (ZW_AddNodeToNetwork command).  The 0x82 is the mode, which is:
#define ADD_NODE_CONTROLLER   2
#define ADD_NODE_OPTION_HIGH_POWER           0x80

The second line has the response.  0x4a is the command, 0x1 is the id, and 0x7 is the status.  This is defined as "ADD_NODE_STOP_FAILED".  These are all defined by Sigma.  Vera has no control over

the details of the add/remove process, and gets no error message or status code other than the 0x7, which means 'general/unspecified failed'.  So there's nothing that you can except try to add the

node again.  This is actually quite common.

9.  JOD: GC-100 child devices (relays) do not work.

result: not reproducable

I tried this on my gc100 and it worked fine.  There's no specific date/time mentioned, so I can't check JOD's logs to know why it didn't work.  I searched JOD's logs for commands to the gc100 over

the past 7 days and I do see responses which indicate it's working:

50      02/02/11 22:27:02.188   luup_log:111: SetTarget send: setstate,3:3,1 <0x700b>
51      02/02/11 22:27:02.194   0x73 0x65 0x74 0x73 0x74 0x61 0x74 0x65 0x2c 0x33 0x3a 0x33 0x2c 0x31 0xd 0xa (setstate,3:3,1\r\n) <0x700b>
52      02/02/11 22:27:02.205   intercept 0x7e5f9918: 0x73 0x74 0x61 0x74 0x65 0x2c 0x33 0x3a 0x33 0x2c 0x31 (state,3:3,1) <0x4412>
50      02/02/11 22:27:02.208   luup_log:111: good response: state,3:3,1 <0x700b>

that 52 line is the response from the gc100 confirming it switched the relay.

10.  JOD: Comma delimited watt values do not work for the Trane T-stat

result: Don't see a problem.

You don't mention which thermostat.  You have 5 (devices 3, 4, 9, 10, 11, 12).

        02/10/11 12:42:47.349    device: 3  UserSuppliedWattage startup: 12,Cooling,48 v:0xb77b60/NONE
        02/10/11 12:42:47.396    device: 4  UserSuppliedWattage startup: 5000,11000,485 v:0xb77b60/NONE
        02/10/11 12:42:47.567    device: 9  UserSuppliedWattage startup: 12,24,48 v:0xb77b60/NONE
        02/10/11 12:42:47.643    device: 11  UserSuppliedWattage startup: 12,24,48 v:0xb77b60/NONE
        02/10/11 12:42:47.686    device: 12  UserSuppliedWattage startup: 100,200,300 v:0xb77b60/NONE

All of them, seem to have accepted commas fine.  device #3 won't work because "Cooling" is supposed to be a value in watts.

11. JOD: Scenes do not work when moved & using the standard smartphone interface., also 404 not found:

result: I will forward this to the web developer.  I don't think this is a regression, though, since afaik nobody's touched this plugin, and even so, plugins can be updated at any time and aren't part of a firmware build, so there's no reason to block the firmware release.

12.  JOD: Server busy. Engine restarts. #12709 2/7/11 @ 21:42:00

result: fixed

This was the 'restart' bug which was mentioned by another user in 1183.  It was fixed and won't happen with 1186.  As far as I can tell, though, the server busy was only 30 seconds from 21:39:31 to

21:40:06.  It was basically a reload.

13.  shady: No ZWave dongle

result: not enough info

Please provide the serial number and date/time.  Be sure verbose logging is enabled, or else the logs won't have enough detail in them.

14.  CMRAncho: V2 on 1183 froze up twice 36 hours apart

result: not enough info

Please mention the serial number, and leave verbose logging on (be sure you use USB logging), and then I can see what happens

15.  FrankHill: Platform error

result: appears to be user error

It looks like the customer at some point inadvertently in the past manually pasted a .trx image for a Vera 1 into the advanced URL for a Vera 2, so it doesn't know which version it is and failed to

do an automatic update.  This shouldn't happen under normal use.

16.  mtncomm1: Vera1 not seen on MIOS

result: not enough info

If you enable the tech support back door (advanced, tech support, enable it) and email support with the code, we can see why your Vera isn't reporting to our server.

17.  lesf: Network config changed on me

result: Trying to reproduce it.

18.  zmistro: wi-fi client mode not working

result: most likely fixed

We made some changes to the network initializing script so it will re-attempt a wi-fi client mode connection if the initial handshaking fails.

19.  jimmac: lost 3-in-1 varaibles

result: fixed

20.  jimmac: the enabled button won't stay checked on auto generated scenes

result: not an issue

The enabled button isn't used for auto generated scenes.  It has no effect, and you cannot enable or disable them.

21.  jimmac: Leviton scene controllers aren't firing the scenes

result: don't see a problem

I checked the logs and see you pressing buttons on the scene controller and it is firing scenes.  Without a specific date/time of an incident I can't say what the issue is.

22.  jimmac:  Fortrezz WMA-01 not displaying the temp in the GUI

result: not a regression

This doesn't appear to be a new issue, and we can't hold the release for non-regressions.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: FIST on February 10, 2011, 06:22:17 pm
MCV, Thank you do much for the details of the new release! Good to see so much time is put on keeping us up to date on it.

Thanks for your hard work!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: saf101 on February 10, 2011, 06:34:19 pm
I have tried to submit three support tickets and get the following;
Reporting issue from ap: 12235
Collecting logs...
. Network...
Done.
. System...
Done.
. Kernel...
Done.
. Zwave Status...
Done.
Compressing logs...
Compressed /etc/config /etc/firewall.user /etc/lighttpd /etc/lighttpd.conf /etc/lighttpd.users /etc/cmh /etc/cmh-ra /etc/cmh-lu /tmp/log /tmp/log.LuaUPnP /tmp/log.NetworkTroubleshoot /tmp/log.Provision /tmp/log.RA-handler /tmp/log.Report_AP /tmp/log.Rotate_Logs /tmp/log.SetupRemoteAccess /tmp/log.StartNetworkMonitor /tmp/log.branding /tmp/log.check_internet /tmp/log.cmh-ra-daemon /tmp/log.cmh-ra-keepalive /tmp/log.cmh-ra-keepalive.gz /tmp/log.cmh_pnp.err /tmp/log.dmesg /tmp/log.freshinstall /tmp/log.lighttpd_error /tmp/log.logread /tmp/log.logread.gz /tmp/log.mios_firmware /tmp/log.mios_services /tmp/log.no_internet /tmp/log.platform_init /tmp/log.proxy.sh /tmp/log.restart_zwave /tmp/log.sh /tmp/log.trouble_report /tmp/log.trouble_report_response /tmp/log.upgrade /tmp/logrotate_timestamp /tmp/log/cmh in /tmp/12235_troublereport.tar.gz
Submitting trouble report...
ERROR:Wrong response from server:
Done.

the issue I'm having is the I have a scene setup to turn lights on when a v pin is entered to unlock door the light stays on 5 mins then returns to prior state. I just can not get it to work. Matter of fact I can not get a lot of the events to to work Door Open/Door Close, A Pin is entered, Bad pin entered.

Thank you Scott
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: marcoose on February 10, 2011, 08:46:25 pm
MCV, Thank you do much for the details of the new release! Good to see so much time is put on keeping us up to date on it.

Thanks for your hard work!

I definitely agree!  I appreciate how much effort goes into gathering and reporting back on all these issues, and it goes a very long way to making customers happy.

Now we can send the angry mob to Sigma instead for what seem like several underlying Z-wave issues.  :-\
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: anthonyris on February 11, 2011, 04:42:41 pm
.1183
- Ditto on not being able to save any values in the "Fire warning event when battery is below" setting. Mine happen to be two ZIR000 sensors. Both have same behavior.

- Battery level not being reported correctly (all show 100%, and batteries are at least 6 mos old...).

Chatty Logs sent with Support ticket.
.//A.

Quote from: JimMac on February 03, 2011, 06:41:07 am
Edit:  One more problem, any value entered in "Fire warning event when battery is below:" for a Schlage door latch is lost and not saved.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mda on February 12, 2011, 03:27:30 am
@micasaverde

re: on page 6 of this thread:

 d5.  mda: 2 or 3 notifications when i enter a pin on my kwikset lock

 d6.  mda: Wwhen i enter pin #1, the vera notification says I entered pin #2

i have been trying to submit tickets with logs for these but each time i try i get:

  Submitting trouble report...
  ERROR:Wrong response from server:
  Done.

i am using USB logging

is there some other way i can get you what you need? thanks.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: stampe on February 12, 2011, 02:48:33 pm
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?



I get the same "Failed at Setting user configuration", and only the primary node shows the energy, not the (three) legs, however it seems to report a more correct usage now than before, so we are moving forward.

I hear about this "new" firmware for the AEON HEM's, can anyone please point me to where to find it, does not get any response from AEON themselfs, they only point to bugs with the Vera...

Another (minor) bug is that the kwh and w display in Chrome browser is messed up. See attached
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: myhomeserver on February 12, 2011, 03:46:23 pm
Quote

22.  jimmac:  Fortrezz WMA-01 not displaying the temp in the GUI

result: not a regression

This doesn't appear to be a new issue, and we can't hold the release for non-regressions.


This has been an issue for well over 1.5 years and I've asked them to fix this over and over and over.  General rule of thumb, if a device can display temp, humidity, or some data, SHOW IT ON THE GUI!  Temperature is one of the main reasons I run Vera and it's such a pain to have to click on the device each time to see the temp. Aaron, please fix this, many of us use the fortrezz sensors to get temps.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: FIST on February 13, 2011, 05:02:17 pm
I just installed the beta today (and searched this thread for the same problem)-

I saw that folks can't delete Insteon devices, but has anybody had any issues deleting Z-wave devices?

The "Delete Device" button no longer exists at the bottom of "Advanced" and when I select the Trash icon in the upper right, the response is "Received Empty Response"

Any other way to delete a device from the network?

Thanks
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: stampe on February 13, 2011, 07:12:47 pm
I just installed the beta today (and searched this thread for the same problem)-

I saw that folks can't delete Insteon devices, but has anybody had any issues deleting Z-wave devices?

The "Delete Device" button no longer exists at the bottom of "Advanced" and when I select the Trash icon in the upper right, the response is "Received Empty Response"

Any other way to delete a device from the network?

Thanks

Yep, I am having the same issues, trying to delete (and re-add) an Aeon Labs HEM Z-wave device.
I get the "Received Empty Response". The device disappears for a short wile (visually at least) , but then reappears, and then it fails configure the device (posted in previous message)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pgrover516 on February 14, 2011, 12:08:54 am
It appears that some are having problems pairing schlage locks after upgrade to 1083
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: shady on February 14, 2011, 07:38:31 pm
13.  shady: No ZWave dongle

result: not enough info

Please provide the serial number and date/time.  Be sure verbose logging is enabled, or else the logs won't have enough detail in them.

I am trying my best to catch this condition with Verbose logging turned on.  As soon as I do you'll be the first to know.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: FIST on February 14, 2011, 08:00:01 pm
I just installed the beta today (and searched this thread for the same problem)-

I saw that folks can't delete Insteon devices, but has anybody had any issues deleting Z-wave devices?

The "Delete Device" button no longer exists at the bottom of "Advanced" and when I select the Trash icon in the upper right, the response is "Received Empty Response"

Any other way to delete a device from the network?

Thanks

Yep, I am having the same issues, trying to delete (and re-add) an Aeon Labs HEM Z-wave device.
I get the "Received Empty Response". The device disappears for a short wile (visually at least) , but then reappears, and then it fails configure the device (posted in previous message)

..Update.. I was able to delete a Generic IP Camera with no problems..
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: stampe on February 15, 2011, 03:46:39 am
I just installed the beta today (and searched this thread for the same problem)-

I saw that folks can't delete Insteon devices, but has anybody had any issues deleting Z-wave devices?

The "Delete Device" button no longer exists at the bottom of "Advanced" and when I select the Trash icon in the upper right, the response is "Received Empty Response"

Any other way to delete a device from the network?

Thanks

Yep, I am having the same issues, trying to delete (and re-add) an Aeon Labs HEM Z-wave device.
I get the "Received Empty Response". The device disappears for a short wile (visually at least) , but then reappears, and then it fails configure the device (posted in previous message)

Replying to myself here...

I got an update (3.60) from AEON for the HEM, and now they are working a notch better, however I get way off scaling (factor x100).
Is there a way to set the scaling in the GUI? Or is it poosible to (hack) the xml (D_PowerMeter1.xml) file directly. I found it, but it's compressed in lzo, so I'll need find a way to change it...
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Ap15e on February 15, 2011, 05:28:34 am
Download, modify and re-upload it via GUI or use pluto-lzo from the command line to decompress and recompress it.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mtncomm1 on February 15, 2011, 04:46:23 pm
It appears that some are having problems pairing schlage locks after upgrade to 1183

I had zero luck pairing 2 Schlage lever locks on a Vera2 that was recently updated from 1047 to 1183. I attempted multiple times over 2 days to unpair/reset lock/pair with no success. Tried both hi power and low power, with various time outs and various distances between locks and Vera. I ended up reverting back to 1047 firmware, and got green lights on both locks at 15-20 feet from Vera on the first try. Locks were recognized as new nodes AND as door locks with 1183, but would not exchange name, secure classes, associations, etc.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 16, 2011, 08:03:24 am
x4 - mbairhead - scenes slowed down: This isn't really firmware related.  The scenes will take longer to run if devices are being configured or the network is busy.

Ok, seriously guys, if this is actually the problem, what's the fix. This is getting worse and worse. Now my iVera and SQ remotes are timing out waiting on Vera and I don't even bother trying to run scenes anymore. I have one that runs correctly with input from me and the rest are time based so I wouldn't notice if it took an extra 3 or 4 minutes.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 16, 2011, 10:23:15 am
mbairhead,
If you dont have any devices with red halo's in your system then your question may be answered by the following quote.
"Z-Wave issue #9"

Personally I dont believe this is the cause. It makes no sense to me that Vera waits for 30 mins (Sigma issue) to execute a scene when my secondary controller (non Vera) can execute the same scene in seconds, both controllers use the same Zensys / Sigma chipset and the same build. For me there is still a bug in the FW but without the data to prove it, I have to wait to see what comes out of MCV's Sigma trip.


JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mversluis on February 16, 2011, 10:27:08 am
We faced the same problem after upgrading to the new ( beta ) firmware.

Every motion sensor in / and arround the house has a delay of 20-30 seconds till 3-10 minutes. This is not working any more like this.

Open the garage door and most wait for the light will go on ( the switch is located at the back of a other "locked" door )
Yesterday evening it took about 3 min.

Walk to the hallway , motion sensor is tripped , just wait for a couple of minutes and then the lights will go on.

Open the front door , the door sensor is tripped, just walk to the hallway near the kitchen and after some minutes the lights go on.

Same on the first floor.

I really have a issue´s with this F##### delay and its not working any more for me.

Is there any possible way to go back to the older ( more stable ) version ..?


Many thanks in advance
Best regards,
marco
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 16, 2011, 01:23:08 pm
Well last weekend my Vera2 decided to die a slow ugly death. I am not sure what series of events triggered the problem(s) but here is what happened:

First I upgraded to 1183 then 1186 and all seemed well (except the known 3in1 problem) until I turned on Verbose logging without the USB option.  After a day I lost contact with my Vera so I reset it.  On start up after the Server Busy window I found that ALL of my devices were doubled.  The second set of devices were placed in the Devices tab but each and every one had the same name as the original.  I tried to delete them but received a "Received Empty Response" or no error at all but the device won't delete.
After some playing around with a factory reset and dongle erase, every backup restored had the same problem.  I tried to pair my schlage door locks and received a security code error.  Some more playing around landed me the "No Zwave Dongle" error.  After a series of dongle firmware flashes I just could not get rid of that error.  I have no idea what I did but the next day something fixed the no zwave dongle error.  I took the opertunity to rebuild from scratch.   Once again the Schlage locks have security code problems and the 3in1 with the same data but all lights switches worked.  I got half way entering my devices and adding a few scenes when I decided to enable the remote USB logging.  Guess what!  All my devices doubled again.... back to square one.

Has anyone had this doubling issue?  I can load any old backup and all devices will be doubled on restart.

 
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mbairhead on February 16, 2011, 01:49:27 pm
mbairhead,
If you dont have any devices with red halo's in your system then your question may be answered by the following quote.
"Z-Wave issue #9"
No red halo's but my issue has started before I even run my scenes now. My Vera2 seems to be busy all the time, it's causing my remotes to either lose connection or not connect for an extended period....rendering them basically useless. I've made no changes since the new firmware, no new switches, scenes, literally nothing is new.

Quote
Personally I dont believe this is the cause. It makes no sense to me that Vera waits for 30 mins (Sigma issue) to execute a scene when my secondary controller (non Vera) can execute the same scene in seconds, both controllers use the same Zensys / Sigma chipset and the same build. For me there is still a bug in the FW but without the data to prove it, I have to wait to see what comes out of MCV's Sigma trip.


JOD.
I understand that MCV is working on patching things up with the new firmware but I'm worried that they are blowing this issue off altogether, given their statement in my complaint.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 16, 2011, 01:52:56 pm
@JimMac,

There is a warning message next to Verbose logging that reads.....
Verbose logging (May cause system instability if you're not using USB logging)

Did you have a USB drive plugged in?

If you only have a few devices or your backup file is less than say 250kb there is no real need for the USB logging to be enabled.


JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 16, 2011, 02:04:01 pm
JOD

I read the warning thinking that a lockup may occur but not this.  I have 38 devices and my Vera is located in my summer house 60 miles away.  When MCV asked me to tun on Verbose logging I took the chance as I could not plug in a memory stick without a long drive.  

Edit:  The second time I activated USB logging I had a memory stick in Vera's USB port.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 16, 2011, 02:28:31 pm
It sounds like there was more going on than just enabling verbose logging..
I know it's a moot point now but...
Did you try clearing your browsers cache before doing the dongle erase and factory resets?

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 16, 2011, 02:42:51 pm
JOD

I always use Ctrl-F5 when ever I make a change.  I'm going to try to revert back to 1074 and see if the problem persists but I think I need to be on-site to test it fully.  Looks like a weekend job.

Edit:  I just noticed something interesting.  I loaded a backup image using 1074 and duplicate devices showed up.  I selected to reset the zwave chip and when Vera restarted (and after I cleared the browser cache) all the devices showed up again.  I thought this button deleted all devices?  Maybe I have a bad zwave chip?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 16, 2011, 03:44:36 pm
Resetting the zwave chip just reboots it.

JOD

Edit:  I just noticed something interesting.  I loaded a backup image using 1074 and duplicate devices showed up.  I selected to reset the zwave chip and when Vera restarted (and after I cleared the browser cache) all the devices showed up again.  I thought this button deleted all devices?  Maybe I have a bad zwave chip?
To remove all your devices, reset the house ID and start from scratch you need to click Reset Z-Wave network.

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JimMac on February 16, 2011, 06:56:34 pm
I reset the zwave network but I'm not familiar with how to change the Home ID.  I found the number but what is the process of changing it?

Edit: I took the drive to my summer home and did a hard reset.  Added all my devices back in and half of the scenes before I had to leave.  24 hours later all my devices were doubled again but I was using 1.1.1047.  I don't think this problem has anything to do with the new release, there must be something else wrong.  I'll wait to see what MCV can find.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 16, 2011, 07:21:40 pm
Its automatic, the ID changes with the reset.

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: krisid on February 18, 2011, 12:33:06 am
I can't control IR devices via USB-UIRT.
Was working fine before the firmware upgrade.

Otherwise the build appears stable and faster overall.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on February 18, 2011, 09:43:02 am
I can't control IR devices via USB-UIRT.
Was working fine before the firmware upgrade.

The IR issue is reported as fixed for the next release.

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: krisid on February 18, 2011, 07:07:53 pm
I can't control IR devices via USB-UIRT.
Was working fine before the firmware upgrade.

The IR issue is reported as fixed for the next release.

JOD.
Can I go back to the previous version of the firmware?
What is the url for the current stable version?

Thanks
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ctbaker on February 18, 2011, 11:38:18 pm
The power went out last night a few times and power cycled the vera2 box and now the Vera2 is showing "Slave SIS:NO PRI:NO"

Seems like after you power cycle the Vera2 about 5 times, it will lose its Primary controller status. This also appeared to be the problem in the previous firmware.

Also, the kwikset lock will not report the correct lock/unlock status from time to time. Usually updating the neighbor nodes will solve the problem, or power cycling the vera2.

Thanks
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on February 20, 2011, 08:14:56 am
Hi-

  I had paired several Schalage locks under 1.1.1047.  Under 1.1.1183 one of the locks no lobger accepts programming from Vera2. Excluded the lock several times and reset it accoring to Schlage instructions. Tried re-pairing. No luck after repeating this process several times over a 24 hour period.

 Reset Vera to factory defaults and reloaded oldest backup to get to 1.1.1047. Work contnues on day 2 of this process. No luck so far in getting back to 1.1.1047 or pairing the locks.

UPDATE: Have now worked on this for the past 2 days. Still doesn not work. I have tried unsuccessfully to go back to 1.1.1047. Have run the Schlage reset every 5 minutes for the past 8 hours and have tried unsuccessfully to exclude the lock. I'm out of ideas and patence.. Help!!! The frustrating thing is that I have paired these locks before without a problem on 1.1.1047.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: krisid on February 20, 2011, 01:45:57 pm
Looks like version 1.1.1186 available.
Just upgraded, fixed the IR issue.

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: blacey on February 20, 2011, 02:19:42 pm

Hi-

  I had paired several Schalage locks under 1.1.1047.  Under 1.1.1183 one of the locks no lobger accepts programming from Vera2. Excluded the lock several times and reset it accoring to Schlage instructions. Tried re-pairing. No luck after repeating this process several times over a 24 hour period.

 Reset Vera to factory defaults and reloaded oldest backup to get to 1.1.1047. Work contnues on day 2 of this process. No luck so far in getting back to 1.1.1047 or pairing the locks.

Hi Don,

I managed to pair my Schlage lock using the z-wave button.  Checkout http://forum.micasaverde.com/index.php?topic=5661.msg33463#msg33463 and the messages prior for others' experiences/successes.

Regards,
Bruce
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: DA INFERNO on February 20, 2011, 03:11:11 pm
Does any one have the direct link for the 186?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 21, 2011, 02:48:21 am
Does any one have the direct link for the 186?
V1 or V2?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: ggraja on February 25, 2011, 01:36:43 am
I have V1 any direct link? When I try updating using the link provided, It recognizes Vera on 192.168.1.120 though my Vera is on 192.168.1.101.

Do I need to remove the Aeon Labs Z-Stick during the upgrade?

Do I need to remove the connection between the main router and Vera? Currently Vera is being used as an access point.

I had earlier written about my inability to choose an Indian Time Zone, I have no problems choosing an Indian location though which would help my scenes for using the Google weather server. The email has not been responded to at all.

I purchased this Vera1 sometime during the last quarter of 2010, since I was unaware of Vera2. I also went ahead and followed procedures to upgrade my Aeon labs EU dongle.

Not able to find any Z-Wave locks for the EU frequency, any links folks?

Govind

Update : Although during my first attempt the upgrade said it failed. The firmware actually shows 1.1.1186.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on February 25, 2011, 10:42:38 am
@ggraja,

Quote
Do I need to remove the Aeon Labs Z-Stick during the upgrade?
Nope

Quote
Do I need to remove the connection between the main router and Vera? Currently Vera is being used as an access point.
Nope

Quote
I had earlier written about my inability to choose an Indian Time Zone, I have no problems choosing an Indian location though which would help my scenes for using the Google weather server. The email has not been responded to at all.
If you are using the weather plugin written by @guessed, then you can override Vera's location setting within the plugin itself in the location override box. This wont help you with your main location problem, but at least it should  allow the plug-in to give you the correct weather.

Quote
Not able to find any Z-Wave locks for the EU frequency, any links folks?
I don't think any exist!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Ap15e on February 25, 2011, 01:23:42 pm
You could try changing the timezone manually:

http://forum.micasaverde.com/index.php?topic=4653.0
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: mjbarlia on March 02, 2011, 03:20:23 pm
Is there any word when the updated Firmware announced on Feb 21st with the major fixes will be released in either beta or official form?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on March 02, 2011, 03:53:59 pm
No word yet.
Title: Major Firmware Update Problem
Post by: aecchalet on March 04, 2011, 10:14:34 pm
I was desperate for the fix to schedule pins so I tried to do a firmware update to 1183 from 1047, remotely via cp.mios.com.  I copied the URL provided by MCV support into the custom line and got the backup performed and then the message saying that it may take up to 15 min to do upgrade.  I waited about 25 min and no change in the screen occurred so I tried reconnecting via cp.mios.com. At first I seemed to be able to reach the dashboard but only my 2 scenes were present.  My 2 Schlage locks, 6 door sensors and 2 motion detectors and 2 trane thermostats were missing.  I retried several times that night but still no success seeing anything on my dashboard.  Next I had my property manager power cycle my Zwave.  Then I couldn't load my dashboard. I kept getting a message "data not loading". I tried resetting my cable modem, my router and then vera2 in that order but still I get "data not loading" message when I try to reach dashboard.  I tried that twice to no avail.  Any suggestions!! Help!
Thanks
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: aecchalet on March 04, 2011, 10:49:42 pm
My guest at my home discovered that my property manager had plugged my ethernet cable into wrong wall port when I asked her to unplug the power supply for 20 seconds then plug it back in!!
However, I am now back to a dashboard with just my 2 scenes an no components.  It says that I am now running firmware version 1179.  That was the version that I last tried to update. Should I try to updatee my firmware to 1183 or reload my backup now?
Since it is Friday night and I didn't get any response to my first post tonight, I have decided to paste "<Link removed by an administrator. Posting links to unofficial firmware versions is not allowed.>" into the mois custom firmware space and give it a try!
Thanks
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on March 05, 2011, 12:39:39 am
If you have a backup, then it doesn't really make a difference whether you load this or the firmware first, as the backup is independent.
Title: Dashboard still empty after backup
Post by: aecchalet on March 05, 2011, 03:58:43 am
I did have the automatic backup button checked and have tried restoring several different backups dated before I tried to update firmware.  My dashboard is still empty with no components displayed (after cntrl-F5).  Any ideas?
This hasn't happened to anyone else?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: jsed on March 05, 2011, 11:16:15 pm
Yes, had that happen.

Solution was to physically reset the Vera to factory defaults (how helpful is your tenant?? :) b/c the wizard for resetting Vera didn't work/factory defaults did not take. Then install new firmware and reload latest backup.

My Vera simply would not install the new firmware properly w/o that step and therefore nothing really worked including restoring the backups.

Good luck!
Title: Reseting Vera2
Post by: aecchalet on March 07, 2011, 12:52:47 pm
At MCV suggestion, this morning I went to the Advance/Backup page and clicked on "Restore to factory defaults".  It did seem to successfully do that remotely.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on March 07, 2011, 04:07:55 pm
After I do a reset to" factory defaults (while completing a firmware upgrade) after about 30 minutes I have a "room" full of configured and partially configured devices. This was not what I expected. I had hoped I would have to start over again to re-include each device. Now I have to exclude each device before re-including them? Any thoughts? What am I doing wrong?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: oTi@ on March 07, 2011, 04:12:23 pm
Zwave device -> Advanced -> Reset Z-Wave network  wipes out the Z-Wave related information and lets you start with a clean slate.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on March 07, 2011, 04:13:38 pm
Thanks
Title: Problems restoring backup after firmware upgrade
Post by: aecchalet on March 07, 2011, 05:31:28 pm
I am currently still running 1183 after doing the "reset to factory default settings."  However, I am having problems with the restore from backup.  When I restore, it seems to go well and be restoring all of my components up to when it says "Restoring 1500 of 16383".  However, when it stops the restore process, all of my components are gone again!  I tried it with a backup file that was saved automatically before I began the attempt to upgrade my firmware. Any way to stop at 15000 of 16383 in the restore?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: MikeQ on March 09, 2011, 04:19:27 am
Hi people!
What about smoke detector support? I mean Everspring SF812...

Can new firmware trigger scene with alarm from smoke detector?

I test this smoke detector in LinuxMCE it works fine...
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: saf101 on March 09, 2011, 01:23:57 pm
would love support for Everspring SF812...
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sschick77 on March 16, 2011, 08:56:07 pm
I upgraded to 1.1.1224 this morning, and since then my Kwikset lever lock has stopped logging.  Tried excluding and readding, but still no events logged
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: CMRancho on March 16, 2011, 09:29:52 pm
1224 was a limited beta which we tested yesterday. It had some regressions that are being fixed today. I really don't recommend installing beta versions until we've done some testing on them. But if you must, well, there you go.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: garrettwp on March 17, 2011, 12:27:08 am
I have reported issues with my kwikset locks using 1.1.1224. They are not getting the correct status after issuing a lock or unlock command. As CMRancho has stated please do not load a beta firmware that has not been publicly announced and report issues. If you feel that you want to help out with beta testing, contact MCV support via email and let them know you are interested in beta testing.

- Garrett
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: oTi@ on March 17, 2011, 01:02:27 am
If you feel that you want to help out with beta testing, contact MCV support via email and let them know you are interested in beta testing.
Any particular qualification requirements?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: guessed on March 17, 2011, 01:15:01 am
Yes, a few.   They typically involve long-time usage of Vera, strong demonstrated Technical background, active (and useful) posts in the Forum, with strong/clear communication skills and a general sense of pragmatism.

Of course, these are just my observations of the characteristics of the Beta team members that frequently contribute.

Not all are SW folks, but most have a proven technical background in their respective field, and a general ability to calmly use things that will often require you to feel comfortable breaking and rebuilding your Vera on a regular basis.... up to and including running with a Broken Vera for days on end as issues get resolved...

I like to use the term "crash test dummy", as it's often appropriate.   8)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sschick77 on March 17, 2011, 09:21:42 am
I really don't recommend installing beta versions until we've done some testing on them. But if you must, well, there you go.

Sorry I know it was my first post, but I have a strange compulsion to install software updates to satisfy my curiosity that I might be missing a new cool feature (streaming video!).  And since it was an open link I went for it.  I didn't see anything regarding the door lock log, so I thought I'd post for awareness.  If there's a more official route, I'll use that next time, or if not, I'll just keep quiet until the true RTM releases.  As for beta software, I'm a senior developer for a Fortune 50 company, so have a high tolerance for breaking/fixing things.

But anyway, I've been lurking on the forum for a while.  Had my Vera for a couple months now.  Adding more components as I go.  Currently have 3 cameras, a Kwikset lock, 4 water leak sensors, thermostat, and a water shutoff valve.  Have a bunch of light switches ordered and another Kwikset deadbolt. Having fun so far, and my wife's even starting to get into the fun. 
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: CMRancho on March 17, 2011, 10:01:01 am
@sshick77: We're glad to have you join in the fun! It sounds like you will bring a lot to the party.

And your wife must be a very special person. Treasure her.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Don Diego on March 21, 2011, 09:58:48 am
SSCHICK77--

  Can you describe specifically what zwave water sensors and water cutoff valves you're using. Thanks for your help in advance.

       Don



I really don't recommend installing beta versions until we've done some testing on them. But if you must, well, there you go.

Sorry I know it was my first post, but I have a strange compulsion to install software updates to satisfy my curiosity that I might be missing a new cool feature (streaming video!).  And since it was an open link I went for it.  I didn't see anything regarding the door lock log, so I thought I'd post for awareness.  If there's a more official route, I'll use that next time, or if not, I'll just keep quiet until the true RTM releases.  As for beta software, I'm a senior developer for a Fortune 50 company, so have a high tolerance for breaking/fixing things.




But anyway, I've been lurking on the forum for a while.  Had my Vera for a couple months now.  Adding more components as I go.  Currently have 3 cameras, a Kwikset lock, 4 water leak sensors, thermostat, and a water shutoff valve.  Have a bunch of light switches ordered and another Kwikset deadbolt. Having fun so far, and my wife's even starting to get into the fun. 
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: myhomeserver on March 21, 2011, 01:18:08 pm
Most likely he's using the FortrezZ WWA water and freeze alarms and the FortrezZ water main valve. I also have been using these and they work well, although I've had some reliability issues with the older FortrezZ water alarms.  You can find reviews on my website or by going to FortrezZ.com
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: sschick77 on March 21, 2011, 02:26:23 pm
That is correct, I'm using Fortrezz for both sensors and shutoff.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 22, 2011, 02:05:14 am
Has anyone tried Firmware Version 1.1.1229-1?  Is this also Beta, and are there any issues to be made aware of before I switch from 1.1.1186?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: garrettwp on March 22, 2011, 02:19:44 am
Please hold off installing any none announced firmwares. There is a reason why we tell everyone to hold off. There are still bugs being worked out.

- Garrett
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 22, 2011, 02:24:36 am
kinda figured, too late.  already started it, can't turn back now. screw it, i'll be a guinea pig.  I tried looking through this forum on anything in regards to the 1.1.1229 firmware and couldn't find any information on it.  I used micasaverde's website which showed me the latest firmware being the 1.1.1229, the dashboard through the GUI of Vera itself informed me that I had the latest being 1.1.1186.  Which I found kinda strange.  oh, well.  My Z Wave Network is small any way, that's okay if anything breaks or isn't supported I'll be sure to post it.  It's the least I can do.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 22, 2011, 06:49:29 pm
update @ 1841, I performed a stress test and heal overnight with the Beta Firmware 1.1.1229 and omg, wow! I'm getting 5 Stars for everything even my locks which I have never seen before.  I usually only have 4 or 5 stars for about 2 of my switches and then about 1 or 2 stars for everything else.  Vera's response time is also a lot faster now, after the firmware update using the "Beta" and a stress test and heal.  I'm just waiting for the other shoe to drop and for something to go wrong, tho.  I'll keep posting my findings and leaving feedback.  So far, I have not noticed any negative impact.

-Just a note, I wouldn't jump on this Beta release just yet because I have no idea what negative impacts lay ahead.  If my Vera bricks itself or stops working I'll be sure to post it.  Is anyone else rock'n this Firmware 1.1.1229?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: pgrover516 on March 22, 2011, 07:00:03 pm
There are known problems with this beta including loss of some functionality, I would not encourage others who may have affected setups to rush into problems. There are indeed significant improvements coming, when the tea is brewed it will be available to all, hopefully frustration free   8)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on March 22, 2011, 09:52:38 pm
It's not liable to brick itself but there is some question over the functionality of 3 in 1 sensors.

You are correct about the Zwave performance and response though as it is nothing short of an amazing difference!

After you updated, did you stay with the 2.78 firmware or update to the 3.20 firmware?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 22, 2011, 10:52:56 pm
@Strangley,

I kinda just updated to 1.1.1229 on a whim through micasaverde's website.  I didn't know if it was a beta release or not until after I had already started it, by then it was too late to turn back.  lol.  I do see that on their website that I can further update the firmware to 1.1.1230.  I don't have a 3 in 1 sensor (yet), so I suppose that is a good thing.  lol.  I don't have any information to go off of as to the difference between .1229 and the .1230 version's.  I suppose that if I run into any issue's I could proceed to 1.1.1230 to see if there is any difference, or any other later Beta version.  I don't mind being a guinea pig.

When you say 2.78 and/or 3.20 firmware by what do you mean? What is the latest Beta firmware version any way? I'd rather be a guinea pig for the latest firmware that's currently being worked on so that if I do report any issues it'll be taken note of and corrected for the next release.  1.1.1229 and 1.1.1230 isn't the latest, so how far down the rabbit hole does this go?
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: oTi@ on March 22, 2011, 11:26:17 pm
Check for announcement on the latest officially released beta here (http://forum.micasaverde.com/index.php?board=4.0).

And most up-to-date release notes are here (http://wiki.micasaverde.com/index.php/Release_Notes).

2.78 is the Z-Wave firmware.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 22, 2011, 11:53:26 pm
@ oTi@ and @ strangely,

thanks to both of you!

Wow, I never clicked on that z wave device icon before.  Mann, i keep learning more and more stuff every day.  Well, right now I am on Z Wave firmware version 2.78 L:1.  I just might try to upgrade the Z Wave chip to firmware 3.20.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: strangely on March 22, 2011, 11:56:33 pm
When you say 2.78 and/or 3.20 firmware by what do you mean?
If you want to go further down the rabbit hole... Prepare to be more confused as 3.20 also equals 452 :)

See below for further confusion, if you want to do this then make sure you understand the risks, and read well!

http://wiki.micasaverde.com/index.php/MigrateTo452

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: garrettwp on March 23, 2011, 01:05:21 am
When you say 2.78 and/or 3.20 firmware by what do you mean?
If you want to go further down the rabbit hole... Prepare to be more confused as 3.20 also equals 452 :)

See below for further confusion, if you want to do this then make sure you understand the risks, and read well!

http://wiki.micasaverde.com/index.php/MigrateTo452



As Strangely mentioned, if you are feeling very risky, look at the documentation for the firmware upgrade of the zwave chip. Some major fixes have been made to the performance and so far things look very good. If you are impressed with your heal report, lets just say the heal will actually heal and correct the zwave routing tables or the devices.

- Garrett
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 23, 2011, 02:06:38 am
yeah, i'm taking the risk.  why not, right?  i was already sitting on beta 1.1.1229 any way, might as well go all the way.  My z wave network is kinda small as it is so i'd rather take the risk now before it grows too large then I wouldn't be so apt in being a guinea pig (LOL).  I am quite impressed with what I have seen so far with the faster response time from 1.1.1229.  Very nice.  Gave me a big fat  ;D.  I don't have a 3 in 1 sensor, so no loss there.

I went ahead and upgraded to .1230, finishing up the heal now.  Then I plan on upgrading the z wave chip to firmware 3.20 (a.k.a. 452 - LMAO!) resetting the Z Wave chip and readding my devices (i'm taking the clean slate route as I think this will be the best approach). 

I don't use an inclusion controller because I have Vera 2 and I use the unit itself to add devices so this won't impact how I set things up.  I hope that I'll still be able to add the Harmony 890 Pro as a secondary controller after migrating from Z Wave 2.78 to Z Wave 3.20.  I don't see how this will have any impact on secondary controllers but you never know.  If I'm unable to use the 890Pro as a secondary controller after upgrading then no biggie.  I'm also wondering if I can get Vera to work with my DVR finally after I do all of this.  I could never get Vera to pull up my Defender's DVR images using the generic camera plugin and using "http://ipaddress:port" - "/GetData.cgi?CH=1".  So, i'll be giving this a try too.  We'll see how things pan out.   :)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: astrowlow on March 24, 2011, 02:58:29 am
I have been reading this thread for a long time. Pondering whether to try the BETA firmware.

My VERA2 system with 10 devices (dimmer/receptacle) and 2 Kwikset locks have nothing but problems. Not able to communicate with my Kwikset lock occasionally (distance between VERA2 and lock is less than 10ft), unable to configure device after a heal operation, etc. My wife thinks that I am crazy spending so much time and money on this.

Oh well, just pulled the trigger for 1229. Upgrade the dongle firmware too.

Wow! OMG! Everything works like a charm. Lock response almost immediately. Every poll return good response.

I think MicasaVerde got it right this time. ;-)





Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: huogas on March 24, 2011, 07:46:01 am
I am Vera2/UI4/1.1.1047

I suppose that there is no way to just  update to Z-Wave version 3.20 without also updating VERA to 1.1.12xx ?

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 25, 2011, 04:06:01 pm
Just an update on my experience thus far with Z FW 452 and UI4 Vera Firmware .1230. 

I was finally able to get my DVR Security Cams to come up through Vera, only by use of the streaming URL option through the Generic Camera Plugin.  I still can't get the jpeg URL function to work correctly (I never could prior to 452 either), I've also tried to change the timeout from 1 through 10 and back again... no dice.  At least it is coming up through the Streaming URL! Making progress, but that's probably more do to with the FW .1230 upgrade then 452. 


On another note, I have not been successful at re-adding the Harmony890 Pro as a secondary controller and being able to use the same Z Wave Devices via the H890Pro or Vera.  This probably has more to do with the Z Wave Firmware "452" or 3.20.  Since the Z Wave network is structured differently with 452 through Vera. 
The odd thing is when I go to add the H890Pro to Vera itself, the H890Pro actually comes back with telling me that it is now a "secondary controller"!!!  For anyone who has ever added an H890Pro to Vera knows that the Harmony remote will always think that its a primary controller. 

Adding the RF Extender and the H890Pro to Vera does work and the remote even tells me that its a secondary controller which is great stuff, however when I go to add the Z Wave switches/devices, the Harmony remote is unable to link/associate the Z Wave device to itself.  It will come back with an error.  When I try to add the Z Wave device to the Harmony remote a second time it actually removes the association of the Z Wave device from Vera.  Using the H890Pro as a Primary Controller is a no go because with 452 you cannot use another device to "include" devices from another controller to Vera.  lol.  I'll have to play with this some and find a way around this, without going back to 2.78.  lmao!
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on March 25, 2011, 04:07:50 pm
@iflyM3,

Are you trying to add the switches/devices via the secondary controller?

If so, SUC/SIS is no longer supported if you are running 4.52

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 25, 2011, 04:16:48 pm
@JOD

oh, yeah... i know. Which is why i won't be able to use the H890Pro as a primary controller to then add devices to Vera. I was trying to use the H890Pro as a secondary controller using Method #2 posted on the Wiki.  http://wiki.micasaverde.com/index.php/Logitech_890Pro (http://wiki.micasaverde.com/index.php/Logitech_890Pro)

I already had the devices added to Vera (primary controller), added the H890Pro to Vera as a secondary controller, then tried to add the same devices that were already added to Vera to the H890Pro.  I did this before with 2.78 Z FW and this method does work.  Just not now with 452.  lol.  The cool thing is now tho, the Harmony actually comes back this time around and says that its a secondary controller.  

Everything is great up to step 11 using Method #2.  

{sry for moving my last post, i thought this thread was more fitting.}   :)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on March 25, 2011, 04:25:17 pm
Quote
sry for moving my last post, i thought this thread was more fitting.}
I wondered what happened. I posted a reply and then I thought I posted in the wrong topic, I deleted my post and then could not find your post, I thought I deleted the entire thread...Sigh of relief..

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: oTi@ on March 25, 2011, 04:34:42 pm
[...]the H890Pro actually comes back with telling me that it is now a "secondary controller"![...]
Wow; MCV must have changed the code then. I don't see anything (yet) about that in the release notes specifically though.

Quote
It will come back with an error.
What's the error say?

Quote
When I try to add the Z Wave device to the Harmony remote a second time it actually removes the association of the Z Wave device from Vera.
Are you sure you were adding them again, and not resetting? (When it fails to add properly, it will suggest to reset the device and say so on the screen.)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on March 25, 2011, 04:47:41 pm
Quote
When I try to add the Z Wave device to the Harmony remote a second time it actually removes the association of the Z Wave device from Vera.
This is similar to a topic under discussion on the beta side regarding the HA09's & HA07's.

JOD.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 25, 2011, 09:31:07 pm
@oTi@

Yes, sir.  The Harmony kicked back a message telling me that it was unable to add the Z Wave device and asked me if I would like to try again.  It didn't refer or mention on the screen about resetting the z wave device.  Although, I do think that is what happened.  When you try to add it again after choosing "yes" for try again, the H890Pro removes the current association from the Z Wave (switch for example) and then associates the Z Wave device to itself (the H890Pro).  When this happens the H890Pro deletes the original association that the Z Wave Switch originally had with Vera (the Primary Controller).  Strange little bit that be.

@JOD
Nice, I'm glad that the Beta Testers have experienced something similar with the HA09's and HA07's.  I'm wondering if it's because of the newer Z Wave Firmware and how it processes/stores the Z Wave Network data.  If you have a legacy controller (utilizing older versions of Z FW) that doesn't process this data in a similar way as Vera does with 452 then those two devices wouldn't be able to co-exist on the same network.  Unless of course, MCV is able to find a work around for this. To allow communication with legacy devices that utilize an older version of the Z Wave Firmware.  

Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: oTi@ on March 25, 2011, 10:00:59 pm
[...]The Harmony [...] asked me if I would like to try again.  It didn't [...] mention [...] resetting the z wave device.  Although, I do think that is what happened.
OK; something definitely changed then. I think I've seen it ask what you described, i.e. 'try again', but also 'reset the device'. Regardless, I don't believe I ever lost the devices in Vera (with 1186).

What you observed is almost as if the Harmony now thinks it is primary, but says secondary. Which is the exact opposite from before.

I hope this gets sorted before the official release, because I'm not looking forward to fiddle with the remote (I have the AVL300) again.
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 25, 2011, 10:55:06 pm
@oTi@

Yes, the .1186 is very solid.  Much slower then .1230, there is a vast improvement in response.  I never had any problems with getting the H890Pro to work with Vera, and I'm sure setting up the AVL300 is practically identical to the Harmony version.  I think it has more to do with the z wave firmware 3.20 aka "452" then anything.  Then again, you do have to update the Vera Firmware in order to be able to use the 452 option.

JOD and the other Beta Testers have come across a similar experience with the HA09's and HA07's so hopefully, they'll bring this to the attention of MCV and then they can correct this for the official release.  

Overall, I am happy with what I am experiencing so far with .1230 and 452.  Heals actually seem to be "healing", the Z Wave Network Topology also seems to be a lot tighter and communication/response time is smoother/faster.  What do you know?  I actually got my Defender DVR Security Cams able to come up through Vera with the streaming url through the generic ip camera plugin using the same exact data that i used before but could never get it to work using Vera FW .1186.  I'm not crazy afterall!  lol!!  :)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: oTi@ on March 25, 2011, 11:24:17 pm
Yes, the .1186 is very solid.  Much slower then .1230, there is a vast improvement in response.
This probably depends on the number of nodes, distance between them, location of Vera, etc. I'm not unhappy with the response in 1186.

Quote
I never had any problems with getting the H890Pro to work with Vera, and I'm sure setting up the AVL300 is practically identical to the Harmony version.
OK; I should be more precise. My fiddling with the remote has everything to do with the remote and the Monster/Harmony software, and nothing with Vera. Like you (with 1230), I had issues with getting it associated with the devices (with 1186), but different. The remote would say OK, but the software would then say it wasn't paired.

Quote
What do you know?  I actually got my Defender DVR Security Cams able to come up through Vera with the streaming url through the generic ip camera plugin using the same exact data that i used before but could never get it to work using Vera FW .1186.
I remember that. No kidding. Good. That's a bit surprising. I wonder what the problem was they fixed.
I recommend you post your findings in your thread (http://forum.micasaverde.com/index.php?topic=5808.0), to close the loop, once there is a new official beta firmware release. :)
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 26, 2011, 12:01:15 am
@oTi@

Done. I closed the loop on the thread and placed it as resolved so its not looking like its still an issue. There is one issue with it as the jpeg url doesnt work but thats fine, at least now i can view the video feed through the streaming url and enable the lights to be turned on when doing so.  thats a big plus. Once there is a definite official release on that firmware I'm going to jump right on it. 
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: iflyM3 on March 27, 2011, 02:58:11 am
@JOD,

Hey, do you know if the issue with trying to add devices to HA07's, HA09's, H89Pro's (when trying to setup a secondary controller) and the Z Wave devices are already added to Vera (being the Primary controller) has been resolved with the Beta Version .1234?

Just curious.   {see above posts in reference to the details - you mentioned that the Beta testers were having issues with the HA07's/HA09's similar to what I was experiencing with the H890Pro}
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: JOD on April 11, 2011, 02:10:26 pm
@iflyM3,
It's presumed there was some data corruption within my system when I reported the issues that would not allow the remotes to fire the scenes. After resetting the network and starting from scratch the HA07's & HA09's work great. I cannot confirm the H89Pro's as I dont have one to test.

JOD.
 
@JOD,

Hey, do you know if the issue with trying to add devices to HA07's, HA09's, H89Pro's (when trying to setup a secondary controller) and the Z Wave devices are already added to Vera (being the Primary controller) has been resolved with the Beta Version .1234?

Just curious.   {see above posts in reference to the details - you mentioned that the Beta testers were having issues with the HA07's/HA09's similar to what I was experiencing with the H890Pro}
Title: Re: Regressions with the 1.1.1183 beta just posted
Post by: Henk on May 06, 2011, 02:39:27 pm
General notice;

When installing the beta firmware (i got 1245) from here: http://forum.micasaverde.com/index.php?topic=5560.0 make sure you have the login to your vera system set to standard (no http login needed).

If you have chosen http authentication YES from the https://cp.mios.com site (settings section) you will get a pop up where you should enter username and password.

The problem is that this pop-up disappears within 10 seconds. So either you need a short and easy username/password, or you need to be able to type REAL fast.

My soltion was to disable te authentication, upgrade and then re-enable the authentication from cp.mios.com

Hope this helps!

Regards, Henk


-------------------------------------------------------------------------------------------------------
edit: running Vera2 @ 1245 now as well as Z-wave firmware 3.20L, 1 Duewi light switch so far, looking to upgrade with blinds sensors and 3in1)