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…[/quote]
Thanks for the info. I have been facing unstable door sensor problem with 1.0.988 and it’s now solved in 1.0.989. Been spending the last two days trying to find out what is the problem.
I also notice that there is also a 1.0.991 beta firmware. Does anyone know what is the fix for?
MCV do you have a readme file for each beta release. That’ll be very help!
Umtauscher, I’m not sure why Ovidiu said the problem with the gc-100 re-installing is not reproducible. We don’t have a ‘blacklist’ mechanism in our plug and play scripts to stop them from auto-installing devices discovered on the network. I just created a bug report to implement this; http://bugs.micasaverde.com/view.php?id=983
In the meantime, if you put an exit at the top of /usr/bin/cmh_Pnp that will stop the plug and play mechanism from auto-installing ip devices when they request their ip address.
but my GC has a fixed ip-address and Vera doesn’t pose as dhcp server either. So it must some be other mechanism that works here - at least not requesting an ip-address.
Will the change you proposed fix the problem anyway?
Thanks
I followed your advice and it seems all my lags are gone. So could it be that cmh_PnP is causing this trouble?
I would be happy if anyone else with performance problems could try this as well and report back. Thanks
I followed the description of Micasaverde in the above post and placed an exit command at the beginning of the cmh_PnP file.
If you are not familiar with linux, I don’t recommend following that path and wait for an update of the firmware.