@cw-kid
Been trying to refrain myself from replying but here we go...
Instead of repeating what I have said in the past, my view is that ezlo and its leader have a very different view of the market and possibly do not understand what they bought by merging vera.
But the basics are:
"But what can you do. Both sides have done things to upset the other."
Sorry but one has to put the context as to who is who back in place here. There is no circumstance under which a business owner should ever treat their customers this way. For anyone running a business, if a customer is upset, you should first asking why. Instead the guy keeps doing what upsets his customers and starts insulting and calling them names. That's unprofessional and unheard of.
"I think he feels you are all against the Ezlo platform and its future success and you just want your Vera firmware as is, to hack."
Again, instead of feeling this way, he should be asking why? Being the one who tore down the firmware down to the OS level, I think I can speak of it. Certainly "as is" is incorrect. The whys:
Because it's broken
Most of the fixes are trivial
They significantly improve the vera
They are not fixing it themselves.
Now on the understanding of this home automation market. If you run a market survey, you will see that the vast majority if not all platforms today rely to various degree on community development of external integration, cloud or local, and run on increasingly more powerful hardware. When they bought vera, they inherited a community, a small remnant of hardcore users who have extended the life of the vera to its limits trying to maintain the platform on par with the competition but still somewhat behind. A large number of people have already jumped ship quietly. The most vocal people on the forum are the most loyal supporters of the platform and many stay because of the technical migration barrier to other platforms. I think we were all excited about the prospective of a new hub and an updated platform. I was all in. There are however two bare minimum critical requirements to a new hub:
Functional equivalency, including all the integrations the plugins supported
An ease of migration from a vera installation to the new hub.
Sadly what I have observed is a complete disdain of these basic requirements and a development strategy aiming straight down the toilet (excessive focus on mobile app and cloud base processing, disregard of the critical wireless stacks and repeat of past mistakes in conception of the API) while the current product gets increasingly far behind competitive platforms, including open source ones. I kept an open mind, not being an expert on the software side but expressing a lot of concerns. The increasing amount of spamming of the forum with "exciting breakthroughs" and "pure innovations" of things the community has been able to do and better/faster/simpler for years combined with the release of an underwhelming hardware for the new controller, clearly pointing to a focus on minimum cost at the compromise of extendibility and reliability and you can clearly see my disappointment. That was the last straw for me. I predicted last year that the platform would not be ready in a year because of their approach... look at where they are now.
In the meantime, I have moved my zwave network to z-way. Stunningly, the migration is easier than to go from vera to ezlo and it felt like jumping from the stone age to science fiction. Everything became lighning fast... All my secure class problems and latency issues gone. I can no longer find any unsupported devices... etc... And all of my previous integrations are retained and more. So yeah I can see why he is upset but he can only be so at himself. Taking it out on his most loyal customers is... well you're the judge.
