new beta - as bad as can could be

[afendikov 37]

updated to new beta today (5.071.52) and very disappointed.

I'm sure that it need to be named as 5.071.5xx - because it show 500, 502, 503 error every 5-10 minutes....

check screenshots.

 

very disappointed.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

[systemfel 21]

i have got this too  503 errors . and wifi is bad too only 10 mb ! i think this have too doo whit the wifi ..

[A.Socha 133]

please contact with our support

[jakub.jezek 370]

@afendikov, does it appear in random or during some action? If its latter, then can you make video and send it to Fibaro support? It is beta so unstability is expected (atleast from my case) and this could help polish normal non-beta release.

[ArjanC 1]

i've got the same issue with this update. after reboot the HC3 works for about a minute and then it crashed.
Contacted support for this issue.

[afendikov 37]

 

4 hours ago, jakub.jezek said:

@afendikov, does it appear in random or during some action? If its latter, then can you make video and send it to Fibaro support? It is beta so unstability is expected (atleast from my case) and this could help polish normal non-beta release.

it appears between switching tabs.

Beta stayed through night and I checked “system up-time” on at the morning and it was 7 minutes , so it’s constantly restarting during night

 

so, I switched back to stable version 

[Guest Rafal_ll]

Unfortunately, I cannot test this version.
I had to go back to the stable version
Sorry, but the previous speakers are right
it is not appropriate
Restart every few minutes

[A.Socha 133]

There is 0 ticked about that problem, checked today before leaving work

[seiken 0]

beta works sort of ok for me but is a bit slow when adding new z-wave products, (changing the include time is really  buggy, (i have now 107 z-wave devices on it)

Sonos Heos doesn't work, it finds the speakers but nothing can be done with them. (using denon heos 250 and 150)

had my light in 2 rooms turn on without me doing anything,  after turning them of it seems ok

[vacpav 0]

Well, I can only say that this beta is total scrap - not working at all as it crashes couple of seconds after boot.

[A.Socha 133]

less words more action i hope in Monday see tickets from you on support

[akatar 208]

40 minutes ago, A.Socha said:

less words more action i hope in Monday see tickets from you on support

i don't think it's wise for me to start testing, there is no update for the slave unit.....

 

Please login or register to see this attachment.

[Firefreak 16]

Guess I was lucky then. Mine works just fine after updating.

[Symbiot78 2]

same here. Mine seems to work fine.

[Sjakie 156]

Fellow HC3-ers,

Update done without backup option, manual back up made.

Update is running now 2 hours I did not notice any problem.

//Sjakie

[SmartHomeEddy 1,005]

@Sjakie you daredevil ? 

[Sjakie 156]

Hahahha,

Yep its not my habbit to go beta!

I hope that in this FW the memory will behave better.

Running 45%

Restart 40%

At the moment

Will see after ....days

//Sjakie

[ArjanC 1]

On 6/18/2021 at 11:23 PM, A.Socha said:

less words more action i hope in Monday see tickets from you on support

FIBARO Benelux Support
Status: In behandeling
Case nummer: 8331

 

My ticket was resolved by the Benelux support team (revert to older firmware)

[m.roszak 763]

Eh, reverting will do not help to find the cause

Please pm me if anyone experiencing crashing after boot-up.

Regards,
Michał  

[harthoofd 16]

What I am struggling with, is that most of the times when there are updates new, and not small, issues arise. This was with the HC2, and with the HC3.  I have a general question here:

- why are a microsoft/apple/google and also smaller companies able to publish 'ready' products? and why does Fibaro not succeed in this? 

- how is it possible that features are never fully ready? e.g.  the energy panel? How can it be that users complain that that completely uses full CPU? this kind of easy to identify errors should be out of published firmware.

 

Part of the answer is, that there is a dedicated software team, with all best efforts and intentions, but that there is not enough capacity for all features/requests, and then also squash all bugs cq test software. 

 

A bit further reasoning here:

- Fibaro sells itself as a premium product

- Zwave is expense, zigbee is cheap

- Unclear user focus of Fibaro: professional implementation companies or well informed end-users 

- Yubi? Fibaro? Nice? Zwave? Zigbee? All used in marketing campagnes - but nothing works perfectly in the system.

- Software/firmware updates by Fibaro show each time a lot of issues (which are eventually fixed, but would expect essential issues to be fixed in max a week of time, not 1.5 months of waiting). 

 

Based on this, if Fibaro ever wants to make a fist against google Home, Alexa, Vera, Zipato, Mi Home etc, I do really think that Fibaro as a firm should step up its game, and prioritize stable software development on their ecosystem.  As currently, I do see a shift in balance of and  ecosystems (as what friends/family use), what they use, and also in what I would recommend them. But in my opinion this all starts with having good quality software, without long-lasting issues. 

 

Lastly: I am a big fan of Fibaro, and that is exactly why I would like to see that Fibaro acts on issues ;).  It would be nice if a Fibaro person could respond on this.