When will FW4.xxx be working?

[Bamsefar 13]

I just had a brief look into when FW has been released. And the history of FW4.xxx, incl 3.9 test versions is:

1. First Alpha release was back in June 2014

2. First Beta release was around September 2014

3. First Stable release was in January 2015

 

We are now in late April 2016, and although the version number is 4.081BETA, it is still not a fully functioning firmware - compared to FW3.600 which I am still forced to use due to lack of compability on devices that WORKED in 3.600 but still does NOT work in 4.081Beta.

 

That is about 22 months of development, and still not functioning.

 

So how much longer will it take to get Fibaro into a fully working, and STABLE, version that solves all outstanding issues?

 

I see no reason to continue waiting for another 22 months before FW4.xxx becomes better than FW3.600.

 

There need to be certain targets, or at least I will go elsewhere.

[sj3fk3 27]

I just had a brief look into when FW has been released. And the history of FW4.xxx, incl 3.9 test versions is:

1. First Alpha release was back in June 2014

2. First Beta release was around September 2014

3. First Stable release was in January 2015

 

We are now in late April 2016, and although the version number is 4.081BETA, it is still not a fully functioning firmware - compared to FW3.600 which I am still forced to use due to lack of compability on devices that WORKED in 3.600 but still does NOT work in 4.081Beta.

 

That is about 22 months of development, and still not functioning.

 

So how much longer will it take to get Fibaro into a fully working, and STABLE, version that solves all outstanding issues?

 

I see no reason to continue waiting for another 22 months before FW4.xxx becomes better than FW3.600.

 

There need to be certain targets, or at least I will go elsewhere.

 

+1

[Quikdav 15]

+1

[Bamsefar 13]

It's now June 2016 - it's been 2 years (24 months) since first test version of the "new" Firmware 4.xxx (including 3.9xx) - still not working.

 

2 Years of development? Come on now, this is not rocket science is it?

[Sankotronic 2,370]

What do you mean that version 4.xxx is still not working?? I have HC2 with FW 4.080 (always skipping betas) with more than 60 physical devices, around 30 DV and over 40 scenes and all working ok. So can you elaborate your statement?

[Bamsefar 13]

As more threads has documented: There is a lot of errors and still no support for devices that WAS supported in earlier FW in current FW4.xxx.

And this thread is not about my problem, it is about Fibaro not being able to create a fully functional firmware even though they release 82 versions + preversions (3.9xx) - over a period of 2 years.

 

 

If a bank would do this to it's customers, Do You think that bank would survive?

[1152 33]

4.xxx is working, but not as good as we should expect. Z-wave was supposed to have some key capabilites, among them a standard that ensured you can use devices from different manufactures and backward compatiblity . As all HC2 owners are well aware of we were promised "a whole lot of extras and nice tos" on top of that.

 

The stability issue had eventually to be properly addressed and it has taken effort and time. And as pointed out some of us feel like HC2/FW 4.xxx has lost momentum if not traction.

[dcspock 17]

As a practical example: Two years ago I had installed 4 Merten Argus Connect 220 Motion Sensors (from what I know the only Z-Wave-enabled, wired outdoor motion sensores) - worth 400€ - and hade them working perfectly fine in Version 3.600

 

Since early 4.xx they are not working anymore as the template is missing. Contacting support, they aksed me to provide the template - which I did, along with offering my help. Thas was a good year ago - since then, no response to my 4 reminder emails, nothing!

 

This is simply not how to treat customer...