Firmware update 7.0.14 (7.0.15 beta it became and then 7.0.15)

At least for some devices that is how Aeotec does it, but only if you buy their Z-Stick. VeraEdge does not support OTA at this time, that I know of.

Yeah, please stop distracting Marc! Every question he has to answer distracts him from fixing bugs or testing new firmware. With a current flow of questions about new firmware on this forum and Vera Facebook new beta won’t be ready even by the end of the year! Please understand that even copy-pasting his standard answer about “significant internal changes at MCV, new beta firmware available at the end of month and bright future afterwards” takes valuable time!

:cry:

Yeah, please stop distracting Marc! Every question he has to answer distracts him from fixing bugs or testing new firmware. With a current flow of questions about new firmware on this forum and Vera Facebook new beta won’t be ready even by the end of the year! Please understand that even copy-pasting his standard answer about “significant internal changes at MCV, new beta firmware available at the end of month and bright future afterwards” takes valuable time!

:'([/quote]

I’ll second that.

I won’t ask (yet at least) when the firmware is coming, but i wonder why they dont say anything when its been promised several times, and when the promised time have come, they just stay silent, as a new customer in the home automation world, this is a bad sign, but customer support have been helpfull, so im still having hopes that everything will be fixed :slight_smile:

It’s not a bad sign, it is software development… in my experience it is never done on time at the quality level you want it.

Getting annoyed by missed dates just gives them incentive to tell you nothing, or give you a ridiculously late date to keep people off their asses.

you guys keep using the word “promise”
You make a promise to a 5 year old.
a targeted release date to folks on the internet should be viewed as “my best guess at the moment”

I second @JasonJoel comments. I work in IT and project delivery dates are almost never met,
it’s just the nature of the beast.

Really, how hard would it be for the social networking representative to say when the promised date comes, “Sorry everyone, we’re working really hard but it’s just not ready yet. We’ll let you know when we have a better estimate.”

Answer: 30 seconds, I know because I just typed it.

Personally, I don’t care when it comes… luckily I’m not suffering any great bugs. GetVera’s lack of interaction with their most steadfast and passionate customers and volunteer developers that they’ve come to depend upon has progressed from hopeful to annoying to disappointing to upsetting to now just plain humorous to me.

So for all the new people on the forum… there is hope. In 2 years you’ll be looking at these same repeated themed threads and chuckling. It doesn’t get better, it just gets funnier.

Because as soon as they say that, the flood of people DEMANDING to know WHEN will start so they can’t win. You only have to see this and many other threads to see this.

I’d feel a lot more comfortable giving an update and leaving it at that than no communication at all.

I may not be as familiar with the technical side, but I am very familiar with customer service. It doesn’t matter how great a product is, if the customer service is bad people will get frustrated quickly.

Maybe I’m just a bit old school.

I’m sorry to say, but not meeting expectations or requirements isn’t magically excused and classed as success because you didn’t give a date for delivery.

We’ve delivered nothing - but that’s okay because we never said when we would! /fistbump

There’s so many areas of life where we don’t accept that kind of excuse and IT isn’t any different. A task with no due date is completed by the due date (never). Commit to a date, work hard to make it, if you need to compromise (deliver something of value but not everything you wanted) do it. If it goes pear shaped - man up, put your tail between your legs and say you missed the target and you’re setting a new target (the only acceptable response to a missed delivery date is a new date).

Don’t sit around feeling good because you never made a commitment in the first place. Because even if you didn’t, your customer had an expectation. Not only did you fail to meet it, you shied away from the fundamental principles that define a professional.

Long story short - make commitments. Be prepared to stand up and make new ones if you miss them. People will respect that more than avoidance.

At the risk og becoming immensely unpopular i have to ask: What is the difference between programming software and repairing or building a car?

you never know exactly what the problem is, can you get the sparepart and maybe there is another problem connected to this problem?

But when you send your car, bike, dishwasher etc. in for repair you expect that they tell you when its ready and keep you updated on delays or best case that it wasn’t as bad. or if someone comes to repair your heating, plumbing or roof you expect the same.

But why does this not apply for IT people? all we want is an idea of when we get the problems fixed, i love that they say, that it will be ready for a certain date, (just like with the car, sometimes something delayed it) so you go out and say it is delayed, “we expect it to be 7 days delayed because there where an interconnected problem”, and that is ok, because people are informed about this, if a company started doing this instead of just staying silent, im sure people would be really happy.

Marc has a hard limit of 3 replies per single thread. So I suggest to start a new one if anyone wants to hear about big internal changes, regular release schedule and beta firmware expected by the end of month… yet again.

PS. This is getting hilarious! ;D

[quote=“Bluesy, post:91, topic:192320”]At the risk og becoming immensely unpopular i have to ask: What is the difference between programming software and repairing or building a car?

you never know exactly what the problem is, can you get the sparepart and maybe there is another problem connected to this problem?

But when you send your car, bike, dishwasher etc. in for repair you expect that they tell you when its ready and keep you updated on delays or best case that it wasn’t as bad. or if someone comes to repair your heating, plumbing or roof you expect the same.

But why does this not apply for IT people? all we want is an idea of when we get the problems fixed, i love that they say, that it will be ready for a certain date, (just like with the car, sometimes something delayed it) so you go out and say it is delayed, “we expect it to be 7 days delayed because there where an interconnected problem”, and that is ok, because people are informed about this, if a company started doing this instead of just staying silent, im sure people would be really happy.[/quote]

code is written on the fly by a person or team of people. bugs happen. just like problems happen in a car.
so you figure out what’s wrong and try to fix it…
imagine if your car had a problem, but there was NO part you could buy to fix it… you had to build one from scratch. not buy one, but you build one.
so your AC compressor goes out or your car’s motherboard. and you must build one from scratch in order to get the car going again.
that’s what coding is like. there isn’t anything off the shelf you can go buy for custom code… it just has to be invented out of thin air.
that stuff doesn’t happen over night. and often while a fix may fix a problem, it ends up breaking 10 other things in the process.
like i said before, it’s just he nature of the beast.

i’m just speaking in general about coding… i have no idea what is going on at mios.

On a serious note I do agree with the last few posts. There is no “magic” in software development, it is all about planning and hard work. I work for a software company and not only we deliver our releases on time most of the time, but also I am fairly certain if we’ve treated our customers and clients like MCV communication wise or turned our customers into guinea pigs - we would be out of business long time ago.

But MCV is still around and this forum is still fairly active, so they must have done something right (IMHO veralite3 and UI5 - truly innovative and low cost home automation system that was also reasonably reliable).

I am a bit worried about increased number of “quitters” (people who are giving up or almost giving up on Vera because of bugs, lack of communications/support from MCV and looking at other systems) recently. While it was always the case after any major release or hardware generation update, MCV never took so long without fixing anything at all, so I think we are in the dangerous waters right now. Expectations are super high for that next release after almost 6 month of silence and MCV track record says they rarely get it right from the first try. Also I believe Marc promised “beta” firmware by the end of April, May month 8) and we all know that “beta” MCV firmware is an “early alpha” in all other companies.
(if you are new, first UI7 beta is still available for download, give it a try and see if you can make anything work and that was a firmware that a lot of new units got shipped with :slight_smile:

[quote=“kornev, post:92, topic:192320”]Marc has a hard limit of 3 replies per single thread. So I suggest to start a new one if anyone wants to hear about big internal changes, regular release schedule and beta firmware expected by the end of month… yet again.

PS. This is getting hilarious! ;D[/quote]

Kornev, have you been reading our private forum rules of engagement book? LOL.

When I have something of value to add, I do, but when I have nothing of value to add, I keep quiet.

We are as eager for the next release as all of you are. When it is ready it will be released.

Personally, I quite agree with the technical choice , product quality , design and operation that offers vera through its box (I have the edge) and UI7 . I am sure that the next update will be great (although I 'm a little afraid to be disappointed so I expect ) .
Despite this, I am quite surprised of the lack of team communication to make us wait . A little teasing as apple or google would be a real plus .
For a regular update a month, I should not mind but , four months without even a small piece of bone to pick , it’s really hard.

I have to disagree with several post at the end of this thread. I do work for a big US company that deliver hardware and software (telecommunication field), and in particular I write the firmware.
We deliver our firmware on time, 95% of the time. 5% of the time we might slip the death line by one week because of some unknown issue, but the delay has never been more than a week.
Here we are talking about the last version delivered January 21, 2016, 5 months is a huge time on consumer electronic.

Marc please listen to me (and to thousand of users). Please let me convince you:
I bought the VeraPlus: I knew it was not ready, but I also was relying on your monthly firmware upgrade.

The firmware upgrade we all demand here has nothing to do with new features. In your webpage I see that you aree planning to control for example the Samsung AC via cloud. We do not need this.
What we need is a fix to several issues we have.
Example the Fibaro motion sensor gen 5 is not supported. I bought 2 that are not working. I know that if I open a support ticket I will get them installed, but why? how long does it take to add the native support in the firmware? I bet it’s not more than 1 day for one person.
Fibaro released a lot of new gen 5 products, how long should we wait before we are able to use them?

Marc, your firmware is based on unix, everything is modular, you can add/remove whatever you want, add the support for several new products in no time, few bug fixes in no time, we do not need new features. In 5 months there have been tons of new zwave products that we are not able to use, a lot of documented bugs that can be easily fixed.
Please, give us the bug fixes you have now, keep your new features for later.

Not sure how many developers Vera Control have? An average developer could fix 5 to 10 bugs in 2 weeks. Not sure why it takes more than 6 months for Vera Control to release a firmware. They should hire Richard (the owner of Veralaert and PLEG) to be they lead architect :‘( :’( :cry:

They are just allowing the suspense to build. It has ready for release for weeks.
OR
Perhaps they got sick of the comments on here and decided to make us all wait.

They are just allowing the suspense to build. It has ready for release for weeks.
OR
Perhaps they got sick of the comments on here and decided to make us all wait.[/quote]
Oh those dastardly evil coders… :slight_smile: