Fibaro HCL-Light Frozen each day

[Quartz 0]

Hello,

 

I have an Fibaro HCL Light with the last version and my problem is this box frooze each day, i can't connect to it and i must restart it by power down each day ?

 

It is not wifi or networkfk access because i have other camera and wifi product and i can access all time to there.

 

Is there some log to analyse or trouble shoot for Fibaro HCL light ?

 

Reagards.

 

Quartz

[MatsB 1]

Maybe the problem is the internet time update.

Have you tried to set the time manually?

[kunoch 27]

I am facing the same and I restart my HCL twice a day using a dect switch, so I can even remote control it if there is a failure, which happened unfortunately as well between these two power downs. The VD is available in the cook book.

I have set mine to manual time as the drift of the time is not solved by using internet time. I had fibaro look into this some time ago, but without any result. As so many users are facing these freezes it should be really easy to find the root cause (I assume some unhandled exceptions)

Maybe one day the freeze will be solved.

Please report your issues (freeze) in the appropriate System Update sections in the forum, so it is visible:

Please login or register to see this link.

Edited March 20, 2018 by kunoch

[kunoch 27]

duplicate

Edited March 20, 2018 by kunoch

[Javieruco 1]

@Boxer72 Sorry Boxer I have read your post now.

 

I do not know If you need it yet, but I send you. And comment of mail that send me Fibaro:

 

Dear Customer,

Fibaro support provides technical support only in english. Support for remaining languages is planned in the future.

If I understand your HCL is not so stable from some time? There are some parameters which you need to verify.

Please minimize any communication.

Please increase the “Devices polling time interval”. Go to configuration → z wave network and increase the time value to at least 1000.

It is suggested to reduce the frequency of reports processed by HCL. Frequent of energy consumption, temperatur and LUX reports are consuming a lot of CPU load. Reducing the intervals of sending reports can be done by adjusting the parameters of advanced devices – all descriptions you will find in the module instructions on manuals.fibaro.com. It is recommended to increase the time of automatic reports and an immediate report resulting from a change in the read value.

Please increase an individual device polling time.

Please reduce (if applicable) the max running instances of each scene.

If you have a z-wave lock, please delete the module and test it if helped.

Please double check your virtual devices. Some types of configuration may seriously slow down your controller.

Please check your scenes. Try to avoid using “delay” in scenes. Simplify your scenes.

Additionally, you can implement virtual device from attachment to reduce the RAM usage of your HCL.
Just go to device > add or remove device > click “Import virtual device” and use the file attached.
In the general tab of the virtual device use the following:
IP: IP address of your central
Port TCP: 80

Please also go to the advanced setting to correct the IP address.
Notice: YWRtaW46YWRtaW4= it is a login and password (admin:admin) coded in Base64 language.
If you have any different login or password, please use

Please login or register to see this link.

to decode your password.

This device should be use in scene, that will be reboot your HCL every night. In this way it will be reduce RAM usage.
We are very sorry for the inconvenience.

 

Kind regards.

 

Javier

Please login or register to see this attachment.

[Petar Mladenov 0]

These are not solutions. My device has stopped all scenes.
I have removed all Z-Wave devices (which are only Fibro).
I restart it and again the memory is 99%.
Fibro have a general problem with these devices, but they do not want us to understand it from us.
I have been writing to Fibaro for 3 months on the subject, and I have not succeeded.
It's best to get these devices back, and that's a non-serving product, and we serve it by restarting it repeatedly in the day.

First Answer January

Rafał Ciesielski 29 Jan 18

Hello, This is the normal state of things (like for Linux OS). I will try to explain. The whole memory is occupied by the buffer, which means that over time the disk cache grows as much as possible. This is not a problem because if necessary disk cache will be limited. Cash memory is reserved by the system but is not currently used. In his case only 77% it is used at this point. Counter shows the available memory not occupied. Problem with stability can be related with a large number of reports (power / temperature eg.) sent from the devices to the controller or with too complex scenes. Please try to reduce number of reports and temporary turn off some scenes – I am sure that it will help. You can also try to perform a recovery and install once again the system – on fresh os Home Center will operate more efficiently Regards --  Pozdrawiam,  Regards,

Second Answer:

Hello, I have information from the software programmers department that the problem has been found – a patch is currently being prepared, we will try to make it available as soon as possible for Users. Sorry for the inconvenience

--  Pozdrawiam,  Regards,  Rafał Ciesielski  Technical Support Engineer

Joke

Rafał Ciesielski 16 Feb 18

Patch will be made available this month. Sorry for inconvenience. --  Pozdrawiam,  Regards,  Rafał Ciesielski  Technical Support Engineer

Last one:

Rafał Ciesielski 02 Mar 18

Hello, Really sorry for inconvenience. We found one problem but Our engineers still working on fix. We need to be sure that the fix will resolve all problems. I will inform you when I get some more information. We do not have any replacement procedure, in case of return please contact with you re-seller. As a Technical Support we do no handle with it. --  Pozdrawiam,  Regards,

[Boxer72 0]

On 5.4.2018 at 12:28 PM, Javieruco said:

@Boxer72 Sorry Boxer I have read your post now.

 

I do not know If you need it yet, but I send you. And comment of mail that send me Fibaro:

 

Dear Customer,

Fibaro support provides technical support only in english. Support for remaining languages is planned in the future.

If I understand your HCL is not so stable from some time? There are some parameters which you need to verify.

Please minimize any communication.

Please increase the “Devices polling time interval”. Go to configuration → z wave network and increase the time value to at least 1000.

It is suggested to reduce the frequency of reports processed by HCL. Frequent of energy consumption, temperatur and LUX reports are consuming a lot of CPU load. Reducing the intervals of sending reports can be done by adjusting the parameters of advanced devices – all descriptions you will find in the module instructions on manuals.fibaro.com. It is recommended to increase the time of automatic reports and an immediate report resulting from a change in the read value.

Please increase an individual device polling time.

Please reduce (if applicable) the max running instances of each scene.

If you have a z-wave lock, please delete the module and test it if helped.

Please double check your virtual devices. Some types of configuration may seriously slow down your controller.

Please check your scenes. Try to avoid using “delay” in scenes. Simplify your scenes.

Additionally, you can implement virtual device from attachment to reduce the RAM usage of your HCL.
Just go to device > add or remove device > click “Import virtual device” and use the file attached.
In the general tab of the virtual device use the following:
IP: IP address of your central
Port TCP: 80

Please also go to the advanced setting to correct the IP address.
Notice: YWRtaW46YWRtaW4= it is a login and password (admin:admin) coded in Base64 language.
If you have any different login or password, please use

Please login or register to see this link.

to decode your password.

This device should be use in scene, that will be reboot your HCL every night. In this way it will be reduce RAM usage.
We are very sorry for the inconvenience.

 

Kind regards.

 

Javier

Please login or register to see this attachment.

Thanks @Javieruco today I installed the VD for autoreboot, and I think it runs fine with scheduled reboot at 0500 every night - let's see if it works the coming days. I have also removed timers, increased report frequency as recommended - but it is a bit try-and-see because I do not really know what causes the freezing. Is there no way to get a error report helping me to understand where my issues are located? 

On 7.4.2018 at 7:20 AM, Petar Mladenov said:

These are not solutions. My device has stopped all scenes.
I have removed all Z-Wave devices (which are only Fibro).
I restart it and again the memory is 99%.
Fibro have a general problem with these devices, but they do not want us to understand it from us.
I have been writing to Fibaro for 3 months on the subject, and I have not succeeded.
It's best to get these devices back, and that's a non-serving product, and we serve it by restarting it repeatedly in the day.

First Answer January

Rafał Ciesielski 29 Jan 18

Hello, This is the normal state of things (like for Linux OS). I will try to explain. The whole memory is occupied by the buffer, which means that over time the disk cache grows as much as possible. This is not a problem because if necessary disk cache will be limited. Cash memory is reserved by the system but is not currently used. In his case only 77% it is used at this point. Counter shows the available memory not occupied. Problem with stability can be related with a large number of reports (power / temperature eg.) sent from the devices to the controller or with too complex scenes. Please try to reduce number of reports and temporary turn off some scenes – I am sure that it will help. You can also try to perform a recovery and install once again the system – on fresh os Home Center will operate more efficiently Regards --  Pozdrawiam,  Regards,

Second Answer:

Hello, I have information from the software programmers department that the problem has been found – a patch is currently being prepared, we will try to make it available as soon as possible for Users. Sorry for the inconvenience

--  Pozdrawiam,  Regards,  Rafał Ciesielski  Technical Support Engineer

Joke

Rafał Ciesielski 16 Feb 18

Patch will be made available this month. Sorry for inconvenience. --  Pozdrawiam,  Regards,  Rafał Ciesielski  Technical Support Engineer

Last one:

Rafał Ciesielski 02 Mar 18

Hello, Really sorry for inconvenience. We found one problem but Our engineers still working on fix. We need to be sure that the fix will resolve all problems. I will inform you when I get some more information. We do not have any replacement procedure, in case of return please contact with you re-seller. As a Technical Support we do no handle with it. --  Pozdrawiam,  Regards,

@Petar Mladenov, your answers from fibaro are very interesting - I understand they are working on some solution. Please inform us when you get any more from them! 

[Javieruco 1]

Please login or register to see this link.

I am completally agree with you.

 

I have used the virtual dvice to reboot the HLC, and I have created two, one at 5 am an other to reboot at 5 pm, but sometime the HLC its frozen yet, so it imposile that its Works.

 

Other solution is to put a device that swich off and swich on the electricity, but It si a really botched job. The HLC must Works with out anything.

 

In my case, some times the HLC Works for 20hs ando other times is frozen each hour... it is maddening...

 

But the worst is Fibaro do not give us a solution...

 

 

[Quartz 0]

Hello All,

 

For me, i 'm in a case, i restart my light fibaro box 2 time in a day, if have less scene, only Alarm On and Alarm Off, it's running but if during week-end i run specific scene like Light On - Off in different part of my home at different hours, it's crash and can't access to my box, all alarm on etc dosen't detect intrusion, in fact this box don't serv me, nothing it's the same.. .

 

I think we must all reopen our case in Fibaro Support to make pression on this firm and said we know other users are in the same case.

 

Best regards and joined the battle please to have an OS is working with this fibaro light box.

14 hours ago, Boxer72 said:

Rafał Ciesielski 

Hello Rafal,

 

I i understand your are Ingenior in Fibaro Group, we need to have support and way to check what's wrong and know in wich time do you solve this problem ?

 

We are many users to have this same frozen problem on your fibaro light box.

 

In my case, i restart my light fibaro box 2 time in a day, if have less scene, only Alarm On and Alarm Off, it's running but if during week-end i run specific scene like Light On - Off in different part of my home at different hours, it's crash and can't access to my box, all alarm on etc dosen't detect intrusion, in fact this box don't serv me, nothing it's the same.. .

 

Thank you for your solution proposal and regards.

 

Quartz

[vmuscariello 6]

On 9/4/2018 at 11:51 AM, Quartz said:

Hello All,

 

For me, i 'm in a case, i restart my light fibaro box 2 time in a day, if have less scene, only Alarm On and Alarm Off, it's running but if during week-end i run specific scene like Light On - Off in different part of my home at different hours, it's crash and can't access to my box, all alarm on etc dosen't detect intrusion, in fact this box don't serv me, nothing it's the same.. .

 

I think we must all reopen our case in Fibaro Support to make pression on this firm and said we know other users are in the same case.

 

Best regards and joined the battle please to have an OS is working with this fibaro light box.

Hello Rafal,

 

I i understand your are Ingenior in Fibaro Group, we need to have support and way to check what's wrong and know in wich time do you solve this problem ?

 

We are many users to have this same frozen problem on your fibaro light box.

 

In my case, i restart my light fibaro box 2 time in a day, if have less scene, only Alarm On and Alarm Off, it's running but if during week-end i run specific scene like Light On - Off in different part of my home at different hours, it's crash and can't access to my box, all alarm on etc dosen't detect intrusion, in fact this box don't serv me, nothing it's the same.. .

 

Thank you for your solution proposal and regards.

 

Quartz

 

[lighscan 2]

More then a month later and the HCL still sucks big time.

[fratei 0]

Hi everyone, I have recently purchased the HCL and have been following this thread since I also thought was having freeze issues with the device.

In my case the device Z-Wave network keeps working, which means the HCL is actually not frozen but I do loose every single day network connectivity to it and the only way I've found to be able to connect to its IP address is through a reboot.

 

It would be great to hear from Fibaro more than workarounds (e.g. creating Virtual Devices or even worst, purchasing some sort of binary devices that disconnects/reconnects power so the device reboots).

 

Currently I only have 3 roller shutter devices connected and will not further invest on this unless these issues are resolved.

[Javieruco 1]

After reopen the case with Fibaro, and have been attended by a Technical Support Engineer from Fibaro, and lead his recomendations and did everything that he told me (open ports to access they, etc).

 

His solution was to install by them a "wachdog". This is the last email:

 

“I have implemented watchdog in your HCL – it automatically “wakes up” all services after failure. Now it works. One thing is worth mentionig here – please do not reboot your HCL from now on in order not to loose watchdog. It should be fine from now on. It is way more that casual virtual device that is not going to work after such failure. Watchdog is better.”

 

It is fine if you do not swich of the HCL but this is imposible because sometimes the I have to do it, and in this moment the wachdog is out and you can't instal,l must do it they, so It is not a solution.

 

Tired from this I have bought in Amazon a devide that cut the electricity several times in a day in my HCL and now its works always, but insist this it is not a solution... I will think seriously to continious with Fibaro system... probably I will change the brand.

 

Kind regards,

 

Javier

[fratei 0]

On 6/1/2018 at 11:55 AM, fratei said:

Hi everyone, I have recently purchased the HCL and have been following this thread since I also thought was having freeze issues with the device.

In my case the device Z-Wave network keeps working, which means the HCL is actually not frozen but I do loose every single day network connectivity to it and the only way I've found to be able to connect to its IP address is through a reboot.

 

It would be great to hear from Fibaro more than workarounds (e.g. creating Virtual Devices or even worst, purchasing some sort of binary devices that disconnects/reconnects power so the device reboots).

 

Currently I only have 3 roller shutter devices connected and will not further invest on this unless these issues are resolved.

 

Hi, just to provide a quick update. Since posting the above I went to try some configuration changes with the HCL and increased “Devices polling time interval” to 1000 and disabled "Set Date and Time" automatically. The last 10 days the device worked flawlessly without loosing connectivity. Next I'll try to re-enable the automatic time sync with Internet to see if the HCL still works properly.

 

Again, this with only 3 roller shutter devices connected.