Over 30 seconds response (fixed) Starting Services (fixed)

[Weider 1]

I can't take this anymore. There hasn't been a period where I didn't have issues with HC3.

Support was no help at all. Basically just repeating what I did and not even taking the time to check if it worked.

And for support asking me to upgrade to BETA firmware really didn't give me much trust in the support.

 

5 hours I've been battling the HC3 right now and after every possible thing I've tried I've now gone to recovering system. 

After that for some odd reason the password did't work and now I'm locked out for 30 minutes.

 

I'm exhausted. Its unstable as hell, getting some strange critical or serious errors. While the interface is fast, everything Z-wave related is just horrible. Devices take up to 30 seconds to respond, mesh reconfiguration can't even get neighbors from devices 4 meters away, every single time after reboot I had to do a power cycle or it would be stuck at Starting Services and now even that doesn't help.

 

The only way to get into the system is by doing a restore and then after a reboot I'm stuck at Starting Services again.

 

 

HC2 worked fine, but this now is just the worst experience I've had with a device EVER.

 

 

I am now going to try downgrading, but I can't really find a list of older firmware, just came across a link on the forum from a post from october 2021.

 

-----------------

 

 Slow responding (The first one is actually something I'd call fast now days) devices are about 5m away, if even:

 

Mesh reconfiguration not working:

 

 

Edited March 2, 2022 by Weider

[Weider 1]

Ok, downgrading helped, now I ONLY have to power cycle after each reboot for it to completely start up. Recently noticed this "Error while booting system".

 

Forgot to mention in main post, mesh configuration does nothing for me. Sometimes if I do a complete mesh reconfiguration right after reboot it will do a couple of devices, with lots of fails and then just stop after a couple. Doing specific devices in mesh reconfiguration does absolutely nothing. Console log is completely empty.

Edited March 1, 2022 by Weider

[SmartHomeEddy 878]

1 hour ago, Weider said:

Forgot to mention in main post, mesh configuration does nothing for me.

 

Which Z-wave version are you running, the new beta of stable current version?

[Weider 1]

41 minutes ago, SmartHomeEddy said:

 

Which Z-wave version are you running, the new beta of stable current version?

 v. 4.33 

Please login or register to see this attachment.

Edited March 1, 2022 by Weider

[Guest]

11 hours ago, Weider said:

I can't take this anymore. There hasn't been a period where I didn't have issues with HC3.

Support was no help at all. Basically just repeating what I did and not even taking the time to check if it worked.

And for support asking me to upgrade to BETA firmware really didn't give me much trust in the support.

Move to something else.. Have been a Fibaro customer for 10 years..and received same treatment as you mentioned on both HC2 and HC3. 

Moved to HA a few months back and a complete new world was revealed!

11 hours ago, Weider said:

 

 

[Weider 1]

Reconfigure mesh only works right after I reboot and only if I select whole network. And then I get this...

 

Please login or register to see this code.

 

Edited March 1, 2022 by Weider

[SmartHomeEddy 878]

23 minutes ago, Weider said:

 v. 4.33 

Please login or register to see this attachment.

 

 

Please check the z-wave version like this:

 

On 1/11/2022 at 5:24 PM, tinman said:

are you using the new or old zwave engine? If you don't know the version, check the settings -> zwave, if you see "Smart Start" it is he new beta vesion, if you don't se anything with Smart Start then you are on old production engine.

 

Please login or register to see this link.

 

...

[Weider 1]

  

46 minutes ago, SmartHomeEddy said:

 

 

Please check the z-wave version like this:

 

 

 

I don't see Smart Start. So old version.

Edited March 1, 2022 by Weider

[Weider 1]

This is such a horrible experience, I just wanna throw it at the wall. Never been so frustrated with a device in my life.

There isn't 1 single thing that works as expected when it comes to Z-wave comunication. The device is 1 wall away, like 5 meters and it takes 30 seconds or more to respond.

Fibaro, sorry, but this is the last time you fool me. I'm going to give 1 more chance to support then I'm done with this.

 

Slow responding (The first one is actually something I'd call fast now days) devices are about 5m away, if even:

 

Mesh reconfiguration not working:

 

Edited March 1, 2022 by Weider

[m.roszak 536]

Mesh reconfiguration is protocol function, we just call it.
It if fails it means that ZW chip respond with fail.

The main cause of it may be really high network load.
How many devices are you using? 
Have you modified the parameters of the devices related to reporting the states and sensors/meters values?

Your problem is probably related to devices and network configuration.

Please share ticket number on support, I will consult it with the support team. 

[Weider 1]

17 minutes ago, m.roszak said:

Mesh reconfiguration is protocol function, we just call it.
It if fails it means that ZW chip respond with fail.

The main cause of it may be really high network load.
How many devices are you using? 
Have you modified the parameters of the devices related to reporting the states and sensors/meters values?

Your problem is probably related to devices and network configuration.

Please share ticket number on support, I will consult it with the support team. 

Hi! Thanks!

 

I have 38 Z-wave devices, 13 sensors and switches and 2 dimmers.

All sensors are used mainly for motion, Aeotec multisensor 6 on 220v, no associations, everything goes through scenes. 

Here are the parameters:

Please login or register to see this attachment.

 

 

Ticket ID is: 171093

Everything for remote support already opened and ports written in the ticket.

Edited March 1, 2022 by Weider

[m.roszak 536]

Generally 38 devices in not very much.

As for Aoetec devices, I do not trust them to work according to parameters. Sorry, I just don't.
We will check the logs and verify which devices stresses out the network.

Have you turned on the polling on the devices to get readings more often?

Regards,
Michał 

[Weider 1]

I actually had polling disabled on all devices to reduce traffic.

I also now changed parameter 40 on the Aoetec devices to disabled, since I notced it didn't like the high threshold %, hopefully the timers will at least work then.

 

 

Going to enable polling on the switches.

 

EDIT: Just before I went to enable polling the response is MUCH faster now. You mentioning that Aoetec doesn't honor parameters and noticing that it didn't save some of the high thresholds I set parameter 40 to disabled and looks like everything is much faster now.

Still every now and then a hickup after going through all the switches, but I would almost call it instant now! Maybe still check the logs, you have full access on support side.

 

EDIT#2: Reboot also seemed to work without a power cycle now. Might just be one in a 100 that it happens but I'm really hopeful now! Just got a rush of energy ?

 

EDIT#3: 

Please login or register to see this code.

 

 

WOOO, screw you Aeotec, if it weren't for the 220v support I'd ditch all of ya'll.

 

 

We really need some kind of way to diagnose network traffic in HC3

Edited March 1, 2022 by Weider

[Sjakie 138]

6 Aotech sensors on 230V No problem at all!!!

//Sjakie

[Weider 1]

In any case the sensors were the problem, sending to many updates, not changing the threshold to max and was at min. Basically spamming the network. 13 of them constantly sending something, might have been the problem.

[m.roszak 536]

I am glad that we were able to quickly pinpoint the issue.
 

1 hour ago, Sjakie said:

6 Aotech sensors on 230V No problem at all!!!

It is possible, I just don't trust the parameters there as they can work, be ignored or do something different that expected.
You have an example above

So, generally - the fault is not always on controller side (does not matter if its Fibaro's or not). 

I hope that we will be able to give you some additional tools to diagnose the network and pinpoint the issues like the one from this topic. 

[Flash 102]

5 hours ago, Weider said:

All sensors are used mainly for motion Aeotec multisensor 6 on 220v

Had 2 of them MS 6. Also a lot of trouble and response from network. Both MS 6 exactly the same parameter setting. Due to advice of the experts here a bought a Zniffer.
During sniffing a found out that one device was flooding the network with data. Removed the particular MS 6 from the network and everything got more stable and responsive.

I'm NOT saying that this is the cause with you're network. But without any good diagnostic tool it's very difficult to pinpoint the problem.

 

These topics helped a lot.

 

Please login or register to see this spoiler.