"Serious problem detected"

[juwi2 2]

@SDeath  Thank you for the Update.

@m.roszak: What could speedup the analysis? More Logs, more time, extra money?
I don't want to be satisfied with hoping that the problem will be solved at some point in the future.
In our company, we always put the customer's needs first, and we're on a good course with that. I am firmly convinced that Fibaro also takes customer wishes into account at the highest level, because that is what makes a company successful in the long term.

Yours sincerly
Juwi

[m.roszak 763]

We are working on it on high priority.
We have new lead and looking into right now.

New logs, more time, extra money - not needed, we are reproducing this on our test farm and really working around the clock to find the solution. 

[juwi2 2]

Hello @m.roszak,
thank you very much for your update. I think I speak for everyone concerned: we all appreciate it very much.

Best regards
Juwi

[Alex 32]

My system is running stable for 12 days now... I am glad now.

Before the latest update I had about two restarts per week.

So the update did help me at least.

[SDeath 68]

@m.roszak I do appreciate it Michał but I also have to be critical because this error is happening for well over a year now.

@Alex If your system is running stable for multiple months maybe you can make that assumption, but I have seen these restarts ranging from a few hours between to multiple weeks in between.
So for me I am not sure if the update helped for you.
For me it definitely didn't help.

[henri-allauch-13190 10]

 

I stayed in 5.120.10. I had reboots with the message on average 3 times a week.

Since the last reboot I am at 13 days without Problem.

It has already happened to me to stay 25 days without problem.

So to know if it's solved we really need to be able to clearly explain the origin of this blocking / crash

Hoping that Fibaro succeeds

[marbe 23]

I have the same experience, the problem has been occurring for a very long time, FW 5.130 certainly did not solve the problem. I see over 20 occurrences of this error in the system log over the last 3 months. Fortunately, this critical error usually resolves itself with a reboot, other critical errors are worse...

[petrmikes 10]

I have same issue for more than 6 months… It is little bit crazy that issue is 1year old… hope to quick solving

[mjahed 3]

persists with firmware 5.130.64 

[emielstroeve 22]

rebooting every 2-3 days... Im also on 5.130.64

[Alex 32]

For me it looks like a quickapp device changes the time window of these errors.

If I enable this quickapp device the error occurs between 1 and 7 days.

If this is deactivated I can run the system for at least 25 days (didn't test it longer than this).

 

Without the hotfix I had problems with disabled quickapp also, so the latest hotfix did improve/fix something

[emielstroeve 22]

which QA do you think is involved?

[Alex 32]

9 hours ago, emielstroeve said:

which QA do you think is involved?

The one for Shelly Plug (

)

[SDeath 68]

I did a factory reset and a restore to the last backup today, the errors where getting out of hand last couple of days.

Multiple crashes and also for longer duration (entire night), and not coming back online.
Hopefully this helps a bit again.
Nothing changed in the last few days so no reason for it to increase.

Luckily the factory reset and restore is a easy enough process that works flawless.

I don't use the Shelly QA also.

[SDeath 68]

The first crash happened a week after the factory reset so not really a improvement.
I have had several resets again in the last week, some lasting for several hours until the system came back online before the factory reset.

We are now almost 2 months along from the last update with a "new lead".

 

This really is getting very frustrating!!!

What is the status of this now @m.roszak @A.Socha @trob??

[SDeath 68]

FYI:
 

2 hours ago, m.roszak said:

Yes, team responsible for OS part of the system has promising new lead which is being investigated for few weeks now. 

 

[jprobbe 0]

hello, I too have more and more regular reboots.

It becomes unbearable.

I am losing confidence in this solution for which I have invested a lot.

@fibaro support: Where are you on your investigations?

 

[SDeath 68]

I think they just removed the message in one of the newer firmwares in the notification area, because it doesn't show anymore but the HC3 still crashes/restarts every x number of days.
That's one way to "solve" an issue that you can't fix. 🤔

[MVG16 0]

I have the same experience. The problem is not solved, it is swept under the carpet. It makes me think that Fibaro gave up and now hopes that users will be so naive to think "what you don't see is no longer there". Very unprofessional!

[SDeath 68]

Poor decision if it is.

But they must be very tired by now "working around the clock" since at least December 2022 to fix this "high priority issue".
So disappointed in them.