1.0.988 stability issues.

I just updated to firmware version wl500gP_Luup_ui2-1.0.988-1.trx and have found that I no longer have support or have lost stability for the following devices;
Not supported - HomeManageables HM-FS001 - Z-Wave Flood Detection Sensor
3 in 1 motions sensors would not always trigger using either motion or light levels.
VRCS4-1L 4 scene controller no longer triggers a scene.

I removed the devices and added them back in but could not get them to respond. They were all working previously. I ran out of time and reverted back to version 1.0.979 and all are working again except the HomeManageables HM-FS001. We were told this would be supported in the next release but so far it does not seem to be recognized as a water sensor.

I also found that my Vera rebooted many times. Since I have no Internet connection I can’t let this happen because I loose my internal clock and all my timers will be off.

Anyone else having problems with these devices?

HSM100 aka 3 in 1 stopped working as you described. Reverted back to 979.

Question for MCV: In the Wiki here: http://wiki.micasaverde.com/index.php/Firmware_Flash it has a link to 1.0.989

Is that a typo or a newer version of UI2?

My HM-DW001 - Home Manageables ZWave Door Window Sensor also stopped working with 1.0.988.
It might be easier to tell you what is working since the list would be a lot smaller.

I recently purchased the vera2 and itis running both devices without any errors on 1.0.999…I don’t use the dongle to pair them if that helps. the pairing is done through the unit itself.

Is there really a 1.0.999 version now? I’m confused about how MCV handles such releases and why it does not update the ‘Official Announcements’ page since that does reference 1.0.988 even tho the official release is still 1.0.979.

???

They are unofficial releases because they may contain bugs and probably do. Sometimes the functionality of the devices that used to work don’t. It can go either way but it just means it’s in the testing stage. It really depends on what devices you use. Give it a shot and see if it works for you if you have the time.

My bad I mistyped I am using 1.0.998 and it is working well with the devices you are having trouble with . Sorry!

I have the same problems with 3in1 but this is not connected with updateing the firmware. I use 1.988 also, but the problems started, when I connected a new dimmer module. (not a new type but just another one of the same kind I already had in use.)
When I did that, vera started working erratic. Sometimes the lights take 30sec or more to switch on and sometimes the don#t get switched off.
The 3in1 was discovered again with a new ID. Naturally all scenes that I had before using the sensor stopped working. Up to now I have 8 devices but my highest device ID is 95 now. I wounder what happens, when the limit is reached (232 ?) Will I have to make a factory reset and begin again?

Vera is so unreliable, that I started thinking to throw it out, once an for all.
I feel the support has stopped and the unresponsiveness to trouble tickets doesn’t help either.

Cheers
Umtauscher

My highest Device ID is 16726 … Never got an explanation for my strange device IDs from MCV - besides “upgrade to the latest firmware” …

umtauscher
Rolling back to 1.0.979 has solved most of my problems except the HM-FS001 water sensor that never got the support promised and the VRCS4-1L 4 scene controller not turning off an active scene. Try this version as you may find your opinion of Vera somewhat restored. I very much enjoy my Vera despite the glitches along the way, so much so that I just purchased a Schlage LiNK FE599 door lock to add to my collection of 16 other z-wave devices. A comment from MCV on what happened with release 1.0.988 would also help calm people’s nerves. At this point I don’t recommend 1.0.988 unless you like being frustrated.

@JimMac,

thanks for the heads up. Going back to 979 has crossed my mind, but since it doesn’t support the squareconnect app (if it ever comes) I think this is not an option.

I do not blame the z-wave protokoll for MCVs crappy software. So I will stay on this platform but would try to find a professional made controller.

What MCV delivers really is a shame. The only time I got a response from them in an acceptable time frame, was when I filed an compatibility claim - which was denied in the end because MVC stated that the appliance module was not performing correctly.
Be that as it may, in my opinion Vera isn’t either.

Cheers
Umtauscher

[quote=“umtauscher, post:9, topic:165714”]I have the same problems with 3in1 but this is not connected with updateing the firmware. I use 1.988 also, but the problems started, when I connected a new dimmer module. (not a new type but just another one of the same kind I already had in use.)
When I did that, vera started working erratic. Sometimes the lights take 30sec or more to switch on and sometimes the don#t get switched off.[/quote]

I had a similar problem when my network was responding almost instantly and I went to try to add a CA9000 intermatic motion sensor that I still haven’t figured out. After trying to add the sensor and associate it with a light, something was corrupted in the router tables, or whatever, resulting in major slowdowns as you describe. Removing the device(s) did nothing to help, repairing the network with and with out reconfiguring helped slightly, but never returned it to where it was.

All of this is with UI3 because I am testing the SQ Remote app. Now my delay basically happens initially and then goes away for a while. If I pick up SQ Remote and try to operate a light it could take 5 minutes, but after that light finally goes on then everything is responsive and working for a while. I see this in UI3 too, so its not SQ Remote. I am also needing a restart every week or so, where I never had to restart Vera before. It is hard to figure out who/what is at fault when it comes to delays and slowdowns.

I just bought an HSM100, so I hope it works on my VEra…I’ll let you know.

shady
If you got anything working with 1.988 consider yourself lucky. I also found timers and scene triggers to be very very slow to react.
I usually don’t mind testing new version as they are released and have learnt to keep a very fresh backup of all my devices/scenes as well as the dongle data. When all hell breaks loose I usually do a router recovery using the last reliable (subjective) release just to make sure nothing is left behind after a restore of my data. Call me paranoid but so far this has worked and made testing tolerable, almost fun (yah I know I’m a sucker for punishment). What I don’t like is the silence from MCV. If 1.0.988 is a bad release pull it and let people know before an uprising occurs, I don’t like wasting my time more than any of you do.

I quickly got away from UI3 and stayed with UI2 so I don’t know how that GUI works with the HSM100. What I can tell you is that they work very well with UI2 & 1.0.979, great devices!

I feel, that there are so many bugs in that software that MCV themselves don’t know where to begin fixing.
The same happens to myself when I try to wrap experiences together to file bug reports. It’s just to erratic to report. I wouldn’t know where to begin:

[ul][li]The lag is one thing - 5-30 seconds[/li]
[li]commands not received are another - esp. from motion sensor[/li]
[li]the power consumption plugin simply does nothing - an alert is never sent, no
matter what I set it to[/li]
[li]Vera without internet does not work[/li]
[li]already known devices are discovered as new - randomly[/li]
[li]my merten 506004 does not work properly - compatibility claim refused[/li]
[li]GC100 plugin gets reinstalled from time to time, no matter how often I uninstall it[/li]
[li]Simple logic in sceenes is not implemented. (Quite odd for an automation device?!?)[/li]
[li]Plugins are updated by MCV without users consent[/li][/ul]

And that’s just what comes to mind in 5 minutes. Anybody who wants to add to that list?
Sorry

Umtauscher

To add just a few remarks from the management perspective concerning firmware releases:

[ul][li]No formal release notes (http://wiki.micasaverde.com/index.php/Vera_Luup_Releases)[/li]
[li]Inconsistent information about latest UI2 firmware version: wiki: 1.0.989, forum: 1.0.988[/li]
[li]Although V1.0.988 is advertised as the latest UI2 (beta?) firmware, the “last official stable” UI2 firmware release is 1.0.979 (http://forum.micasaverde.com/index.php?topic=3171.0) …
[/li][/ul]

We are testing a new firmware for most of the issues encountered after release 988 and seems like most of them were solved.

[ul][quote=“umtauscher, post:15, topic:165714”][list][li]The lag is one thing - 5-30 seconds[/li][/list][/quote]
We haven’t experiencing any lag of this kind when controlling devices, even directly or using Vera as a secondary controller.

Aaron fixed some problems with the sensors and they are included in the new release

Javier is working to polish this function and release it in a stable version.

Vera works without internet connection, the only(and quite important) inconvenience is the fact that Vera doesn’t have an internal clock…

This was fixed in an early firmware

Aaron explained to you in an email about the Merten and also asked you to do something and report back to us and see what we can do about it, but you didn’t

We were unable to reproduce this

This topic has started to intensify a few week back and we stepped into action and Javier is working on implementing this.

We will add a check button so users can opt for the auto-update.[/ul]

[/quote]

Great! Now that’s the kind of feedback we need to hear. A little more information would top it off;
Will this new firmware add the HomeManageables HM-FS001 - Z-Wave Flood Detection Sensor?
Did you find a problem with deactivating an active scene on the VRCS4-1L 4 scene controller?

I must agree with MCV that Vera does work properly without an Internet connection. For those like me who do not have and Internet connection it would be nice to have the ability through the “update” menu to update the firmware from a connected computer’s hard drive or USB port.

Nice that you have some of the issues fixed, but I have to disagree on some of you comments:

Well I haven’t with 979 either. But there are other people on this forum who are experiencing the same thing. Maybe you should try harder to reproduce.

Yes, if you tenet into vera and set the time properly and you don’t have any power outage. There is no way to set the time with the user interface. The install/uninstall plugin screen doesn’t work either.

… and seems to have made it back into 988. Sorry

Yes I did, twice. And you yourself told me you forwarded this to Aaron! And thats where it stands now!

Do you have an GC100 in your network? I entered it’s ip address once and since then it keeps coming back.

Maybe you should add a new device to you test installation and see what happens.

Umtauscher

The beta 989 solved all the sensor issue I had

http://download.findvera.com/betafirmware/ftp/wl500gP_Luup_ui2-1.0.989-1.trx

I think that this company has a great product with great potential, Vera is a fairly cheap product compared to other option (if you take into account the hardware they sell Vera at a very aggressive price!)

so for now I am happy and I will stick with the firmware I have that work for me and go back as needed if newer version get buggy!

I personally dislike the UI3 since it doesn’t offer some kind of dashboard and I hope that having 2 UI like this will be manageable, if not I will again be happy with what I already have in UI2…