"Serious problem detected"

[SDeath 68]

I transferred my entire config to a backup HC3 I had laying around, there is a chance this might solve the issues.
I really hope so.
I'll report back my findings.

[ppeterr 206]

12 minutes ago, SDeath said:

I transferred my entire config to a backup HC3 I had laying around, there is a chance this might solve the issues.
I really hope so.
I'll report back my findings.

 

But the main question, are they different hardware revisions?

[SDeath 68]

Probably not, but I think this issue is related or the same:

Please login or register to see this link.

Please login or register to see this link.

 

In "Network Lost" Alex did the same thing and that solved the problems he had, I had a spare HC3 laying around anyway so I thought I'd give it a try.
I just have to try anything since Fibaro doesn't want to solve the issue, and this makes the HC3 almost unworkable.

So before I sue them I just have to try this.

[Alex 32]

2 hours ago, ppeterr said:

 

But the main question, are they different hardware revisions?

Can somebody make a detail picture of the hardware (or creating a list) so one could check for differences?

Specially the old one from @SDeath can be analysed.

 

Of course it would be easier if "somebody" tells us that there are/might be differences or not

[SDeath 68]

My old one is just out of warranty, just over 2 years old. 
The newer one is just over 1 year old so not going to open that one until out of warranty. 
I could open the older one. 
The model number is the same, I would expect a different number with a newer revision. 

[SDeath 68]

Pictures:

Please login or register to see this link.

 

As to be expected the boards contain revision numbers so this could very well be a hardware issue, but since my newer HC3 is still within warranty I don't want to open that up.

[SmartHomeEddy 1,005]

Nice pictures, I never took a look at the board. Thanks. 

[SDeath 68]

So far so good.
But still very early.

After reading the release notes of the 5.141 Beta they returned the error message:
 

Quote

Other
Added a notification for automatic system restore in case of instability.

 

[SDeath 68]

Still running fine on the new HC3.
Seems like this is hardware related.
I have added the old HC3 as a slave gateway with no devices, but still than it has reset already 1 time in a week time.

Edited June 12, 2023 by SDeath

[ppeterr 206]

4 hours ago, SDeath said:

Still running fine on the new HC3.
Seems like this is hardware related.
I have added the old HC3 as a gateway with no devices, but still than it has reset already 1 time in a week time.

 

 

I think it would be good if the gentlemen and ladies of fibaro were a little more transparent about this problem...

[SDeath 68]

Exactly, a good company would offer to replace the faulty HC3 even when it’s out of warranty. 
A thank you for everything that I have done to make this brand in the past 10 years. For all the users I have helped in the early years, all the coding I did for everybody so they could pick up the HC environment easier. 
And what do I get, they just ghost me and everybody else who has this problem. 
A good brand would want to deliver a good product and replace the faulty ones. 

[SDeath 68]

Luckily there are also companies that do appreciate the effort a community puts in, a group of beta testers, they are rewarded with freebees and get free products worth €4000 to beta test and make the firmware the best there is for the end user. 
That’s how you appreciate the test group and build a brand to be the best there is.

 

I had to buy 2x HC3 to get one stable system. 
Fibaro/Nice just doesn’t care and just give you the middle finger by ignoring you. 

Edited June 12, 2023 by SDeath

[henri-allauch-13190 10]

 

I am also in the same case. I have an HC3 which since the beginning has random reboots. Sometimes twice a day or twice a week It has happened twice that she has gone 30 days without incident. I have repeatedly opened tickets and sent dumps to support. The answers: Do a recovery or install the new firmware. Fibaro said on this forum to know how to reproduce the problem and work on it day and night. The latest version erased the message but the random reboots remain present. I bought a new hc3 box a month ago. I transferred the box.old to the box.new. For the moment no incident on the box.new and already a reboot on the box.old Which has no zwave devices and just 2 QA. It is too early to affirm conclusions but we are several in the same situation.

 

@SDeath I had reported having the same issues in this post in December 29, 2021

[SDeath 68]

Yeah it’s a big shame Fibaro has given up on fixing this. 
Before this thread started I already reported it 6! months before. 

[SDeath 68]

Apparently they didn't give up yet, m.roszak send me a PM after my messages, and said they did solve 90% of the causes for this issue and where working on the last 10%.

Mine is in those last 10%.
They claim they do have the solution for the last 10% as well.

They where stress testing that solution according to them.

 

They modified my broken HC3 and it's in for a long test to see if things have become stable now.
I have it again configured as a Slave gateway with nothing on it.
And I will report back regularly if things are stable now.

[ppeterr 206]

On 6/13/2023 at 3:58 PM, SDeath said:

They modified my broken HC3 and it's in for a long test to see if things have become stable now.
 

 

 

 

I would like to believe that they are fully working on it, and although you are now a kind of conduit of the status around the problem that I think is present with many more users. It's something positive. Let me be clear, my system does not have the problem, but if I read between the lines, and perhaps you can explain. Do they have a good result with a hardware modified system.

 

So hardware?

 

This is taking to long without any statement directly from fibaro.

 

@m.roszak Can you perhaps clarify a few things?

Edited June 14, 2023 by ppeterr

[SDeath 68]

@ppeterr I fully agree they should reply here as well with details about the cause of the issue. 
It is a firmware change they did to my broken HC3. 
To my experiences it appears a hardware issue that is solved or not present in later revisions. They are using a firmware change to fix the issue. But they haven’t told me what they changed, only that it is a small change with potentially a big impact. 

[SDeath 68]

So my new HC3 started to show the same behavior as my old, and starting to reboot/loose network connection for a few minutes.
I have asked Fibaro to apply the same fix as my old HC3 to test and see if that solves the problem too.

[Neo Andersson 230]

I don't know if i am in that 10% with my system and with several other installations, but the unexpected errors are still happening..Sometimes the system reboots after it, sometimes it stucks and i need to unplug the HC3.

Very very frustrating..Mostly in our installations where I can't really do anything, just to tell my customers, that problem will be solved...I am telling this to them almost a year...

[SDeath 68]

I feel you and asked Fibaro for sn explanation about the cause of this. They will discus if an official explanation is required. 
But if you are fully up to date with updates and still have the issue I suspect you are in the 10% and I am getting the idea it’s more widespread then everybody knows or willing to admit. 
Let’s hope this fix is the final fix and things finally become stable after 2 years with this issue.