Why is the core of VERA still so buggy? I cannot even rely on basic functions like Timers and the Value of the Lights on the control screen to be accurate.
I changed from X-10 to ZZWave to gain reliability and VERA is causing the same experience I had with X-10 setup. If the core functions are not stabilized I will quickly be switching back to just using HA07 for Primary control again, at least that was reliable.
It’s officially in Beta, what would you expect?
Beta is testing state of the product.
I suppose because we are paying for that opportunity
not really. Didn’t you get the product for half price because it’s still “Buggy”?
[quote=“325xi, post:2, topic:164198”]It’s officially in Beta, what would you expect?
Beta is testing state of the product.[/quote]
Quite simply at this stage a stable core environment where basic functionality was running and additional “promised” functions were what was in development or being stabilized. Not the buggy core system we have right now.
The Z-Wave core should be stable. We have no known issues with it. Ditto for timers/events. There was a known issue with timers when you choose the ‘after x seconds/minutes’ do [whatever] that the 2nd part of the timer, the [whatever] wouldn’t get executed if you did a ‘save’ in between the 1st action and the 2nd. That has since been fixed for the next firmware. And that is the only confirmed issue with timers I can think of in the past 4 weeks or so. The other issue with events was that events were triggered when sensors went idle, not just when they were activated. That was also fixed.
If you are having general core issues where Z-Wave isn’t working, my thought is that it might be a reliability problem in your Z-Wave network itself, and not caused by Vera. Zensys’s lead engineer in the U.S. uses Vera in his home and lab and we’re stressing it with lots of Z-Wave traffic. We pour over logs and research every time a Z-Wave device doesn’t come on/off like it should, and so far, every time it’s happened, it’s been hardware related, not in Vera’s core software.
Vera’s web-based UI has had some bugs where the java script doesn’t always send the commands. We’ve since re-written the whole UI engine and will release a new firmware in the next day or two that addresses the web issues. What I would propose, Chimpware, is that after this next upgrade, go to ‘advanced’, ‘logs’ and enable versbose logs. Then if something doesn’t work, go to micasaverde.com, click ‘support’ and send an instant message. One of our devs is nearly always at the computer. We’ll look into right away. This next firmware release should fix all known issues, so if you’re having problems, we’ll fix it right away.
Well just as an example of the buggy behaviour I tried to reload one of my controllers today (an HA09). I reset the HA09, added the controller as a secondary controller per the instructions in Vera and Vera now shows 2 controllers added and both have the ! symbol. I reset everything and tried again with the same result.
So I guess adding a controller to the system now requires a bug report? Annoying…
If you take all the effort to run a little search on this forum you’d see this have already been discussed, reasons explained (it’s z-wave, not Vera), and solutions proposed.
You mean the completely conflicting posts on this topic? One where you are quoted as:
“Confirm - it works in 320”
That is the only reason I tried to re-add the HA09.
Even if it has been discussed I was replying to the statement of
“The Z-Wave core should be stable.”
No it isn’t. If I cannot even add a very common controller. This is more like an ALPHA than a BETA IMHO.
And BTW I have not seen anyone discuss the double adding of controllers just the ! symbol issue, which is supposedly resolved.
I have two HA09 and one HA07 - work perfectly.
http://forum.micasaverde.com/index.php?topic=111.msg743#msg743
When you re-add a controller - reset it, and delete the old one
All the basic functionality works ( which means no major problems). Glitch here and there is what beta is all about.
BTW How did you determine what “this stage” is when saying things must be that stable and all the features must be in? Do you have an access to official project plan? And I don’t even mention that promised features aren’t necessary supposed to go into the first official release.
Well just as an example of the buggy behaviour I tried to reload one of my controllers today (an HA09). I reset the HA09, added the controller as a secondary controller per the instructions in Vera and Vera now shows 2 controllers added and both have the ! symbol. I reset everything and tried again with the same result
If you do not do a reset of the Z-Wave handheld controller, you can re-add it over and over again, and it should never appear in there more than once. All that happens is each time you add it, Vera attempts to reconfigure it. So if you add new scenes to it using Vera’s UI, and you want them to get into the handheld, just add it again, and it should be ok.
You get 2 handheld controllers in Vera when you reset it (which clears out the existing house/node id) and re-add it. In this case, Vera has no way of knowing that this is the same controller you previously added. So it appears twice. This is a function of Z-Wave, not of Vera. It’s part of our standard test plan to add the HA07 controllers. This should work ok. If it doesn’t you can always call us or instant message (micasaverde.com, click support), and I’ll look at your logs immediately (if you’re ok enabling tech support access), and, if there’s a bug, we’ll fix it right away. This is core functionality and should work just fine.
I understand your explanation, but I deleted the old controller before re-adding it again after reset. Not sure why this would result in 2 instances on the controller being added. I then tried to delete the extra controller after 2 showed up, and I am unable to delete either instance, so 2 controllers currently show up in Vera.
To add to the list of core areas not functioning properly, I am unable to make a simple edit to a Timer to change the days it works on. I tried editing the timer by clicking the buttons for Saturday and Sunday which are currently unchecked, and then pressing Save. System indicates local data is saved, but when reviewing the timer no changes are made.
I think I am going to switch back to using my HA07, although cumbersome to program, it is rock solid and I can count on the lights not being left on all weekend while I am away. I will check back in the next few months to see if Vera has stabilized to the point that it can at least be used for primary lighting control without a lot of extra work.
Guess that is no longer true, I cannot edit scenes, delete a scene or change basically anything in a scene and have it saved, and others are having the same issue.
I have to agree with Chimpware’s sentiments. I had a working setup for about a week and over time devices just keep going unresponsive. I can’t even delete them. Today I reset my zwave network and went through the pain of repairing only to be met with the same results. My motion detectors do not allow me to set to arm them. I cannot delete the devices. Its really dissapointing. My thermostat does allow me to set temps only enable disable the fan. It won’t read the current state either. This is all with 1.0.456 version of code. I have no real way to diagnose what problems are happening or any way to fix anything since the source code still is not available. I’ve been patiently waiting for a stable release but have yet to see one.
dcowan or chimpware, you’ve mentioned you’ve had these problems for over a month. I’ll publicly confirm right here, if either of you contacts our tech support and gives us access to your logs, I guarantee you, we’ll give you a new firmware that has the problem fixed within 1 week, or else we’ll give you your money back and let you keep Vera. How many manufacturers give you that kind of support? How many other manufactures of a product like this give you direct, instant access to the developers who wrote the code, and turn around fixes, usually in 48 hours or so?
I don’t understand why you post in the forum “I can’t save”, but never contact tech support and give us a chance to fix it. Understand we have 3 testers testing this every day with IE, Firefox, Chrome and Safari. We can’t reproduce the problem. And, afaik, 99% of the users don’t have the problem. So, without being able to see the logs and see what’s going on, it’s almost impossible to fix it.
When you contact us, we’ll update this thread with the progress. We finished the final release already, with the latest videos, and are doing the final battery of tests before we release it. So if you contact us right away (tomorrow morning even), we might be able to get the fix into the final release. I think the problem you’re describing is with Javascript, so early morning is the best time to call us if you’re in the U.S. We have 2 development offices, and our Javascript programmer is in Europe, so he’s in the office until about 9am PST in the U.S. If you don’t reach anyone on instant message chat, just call the support number. That rings in both offices.
Fair enough. I have contacted support three times before on issues that have been fixed. I guess my frustration is with what seems like things dying over time which is hard to troubleshoot. I will start working with support next week and see if we can get the issues resolved.
We just posted a new firmware. Could you see if the problem still exists, and let us know?
Still cannot delete a Timer from a Scene, although now I can change the days of week the Timer applies to so this is now corrected.
Support Request submitted - 302.
Still cannot delete a Timer from a Scene
I used your data and can reproduce this. We’ll fix it on Monday. If you need to delete a timer, send me an email on Tuesday and I’ll give you a link to a firmware that fixes this.
I updated to 1.0.491 and reset to factory defaults. Things seemed better for a time, but then my HSM100 motion sensors stopped working. They have red gears on them. Both say "Job failed: " Also a new problem has cropped up with my 1 camera showing up as 2 devices. Thermostats seem to work better now. And now I have temp and light meter on the motion sensors until they stopped working. How should I proceed from here. Contact support?
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules