Overheating HC2 with Scenes

[Guest Cirion]

Last week I found out that I can control my under floor heating quite easy by turning off the circulation pumps when not needed.

Since there is a separate pump for indoor, snowsmelter and to/from heatpump.

So I started to create Scenes to turn on/off different pumps.

To my horror, the HC2 started overheating. The Android App looked like it was working, but nothing whas reacting to the commands. Webpage was unreachable and when I went to check the HC2 it was almost to hot to touch.

I turned off the HC2 and unplugged the power to let it cool down. It does a normal shutdown with a single press on the power button.

3-4 hours later, it was overheated again. Room temp is round 15-20 degrees. It's in a room with the ventilation, boiler and so on...

Turned it off again, and same 3-4 hours later overheated. The fourth time it overheated, after cooling it down I logged in, and disabeled the newly created scenes. And it has not overheated for 2 days.

[Guest Kuuno]

hi

this seems like something again in scene engine. i think that it will be only fixed in the next big release as there will be new scene engine

can you share some scene pictures you use to look little deeper?

Kuuno

[Guest Cirion]

I have found out exactly what overheats the HC2 and makes it slow and unresponsive.

It's the use of the RED S field in rules.

I use that a lot!

For example in my bathrooms I make a rule for auto off:

Light == ON

Then

Light == OFF 300 S

That turns off the light after 5 minutes if the light is on.

I have experienced slow/unresponsive HC2 a lot since I started making those rules. But I did not expect it to be them until I started controlling my Boiler, floorheating pump and snowsmelter pump.

Whenever someone turns on a light with a Auto off rule like above the HC2 is SLOOOOW! Until the ligth is off.

Now the problem came when I startet using even longer delays.

Since my boiler uses the same heatpump as the floorheating and snowsmelter I don't usually need to have it on to have enough hotwater. So instead of going outside, down the stairs, in to my technical room, and plugging the boiler cable every time I think I will need more hotwater (lots of sleepover visitors og bubblebath), I now control it with a 3KW module.

Since I forget to turn it off and it's enough to just have it on for 1 hour at a time, I made the same rule:

Boiler == ON

Then

Boiler == OFF 3600 S

Now I have a slow and unreponsive HC2 for 1 hour every time I activate the Boiler.

And for the pumps it was even worse.

Snowsmelter == ON

Then

Snowsmelter == OFF 7200

The killer ones where these 2:

Time 05:30

Then

Floorpump == ON

And

Floorpump == OFF 10800 S

Time 15:00

Then

Floorpump == ON

And

Floorpump == OFF 25200 S

Can anyone tell me how to make a better Auto OFF rule that does not overheat the HC2 or will all change in V3?

[Guest Cirion]

I have now disabeled all Auto OFF rules on my HC2 and the Android remote is as quick as it once was...

[JohnnyC 7]

For the last 2 create a separate "off" scene at the actual time rather than the delay. As this is essentially a fixed time you should be able to do this.

It doesn't help with the others though as these are delays after an input which could occur at any time.

This is being addressed in the new scene engine and the original recommendation was to not have long delays in scenes (no more than 360 s) but even this creates issues

[Guest Cirion]

Yes, the timed ones I did change to one scene for off and one scene for on again. No delays. My HC2 seems a lot quicker now.

I guess I will have to wait for V3 to use Auto off lights.

Better than overheating my HC2.

[Guest Cirion]

My HC2 stopped overheating, but still crashed once a day.

I had to delete a few more scenes to remove all automation except for the 4 timed on/off events.

Now the HC2 has been running for 2 days 4 hours with no crash.

[seiq 32]

Sorry to dig up an old thread, but I think I may be having the same issue, 4 years later...

I added 3 motion sensors to a HC2 that has been running fine for 6 months. The sensors trigger a LUA scene each to automatically turn on and off lights using the setTimeout() function which I think would be similar to what is happening in block scenes with time delays. The HC2 has become unresponsive (and incredibly hot!) requiring power cycling ever since. I first thought it was the warmer summer temperatures causing the overheat and lockup until I found this thread.

 

Can anyone confirm if this problem had ever been fixed? Or does no-one use delays?

Edited January 8, 2017 by seiq
typo

[wpeeters 30]

7 hours ago, seiq said:

Sorry to dig up an old thread, but I think I may be having the same issue, 4 years later...

I added 3 motion sensors to a HC2 that has been running fine for 6 months. The sensors trigger a LUA scene each to automatically turn on and off lights using the setTimeout() function which I think would be similar to what is happening in block scenes with time delays. The HC2 has become unresponsive (and incredibly hot!) requiring power cycling ever since. I first thought it was the warmer summer temperatures causing the overheat and lockup until I found this thread.

 

Can anyone confirm if this problem had ever been fixed? Or does no-one use delays?

 

Once this old thread popped up again .... Last week I was playing around with my Fibaro RGBW controller. I adapted some scenes for my alarm and use the RGBW controller to have visual feedback of the status of the alarm. Therefore I've added some delays as well. Since then, my HCL is unstable again. Before, it was running several times around 20 days without any problem (reboot initiated by general power shutdown because of electricitiy works).

[Sankotronic 2,370]

That is why I use loops instead of this delay functions. I have only one scene that loops indefinitely and takes care of all time based events and 12 Very Smart Light scenes that loop only when necessary, all the rest is running only when needed and no problems mentioned above. You can find links to this scenes in my signature  

[wpeeters 30]

@Sankotronic I know. I read all your posts  Even if I don't have HC2. I have HCL (wrong choise at purchase). But it does what it needs to do. However only with my most recent implementations I ran into problems again.
Strange to notice that behavior is simular as the one from Seig. The only difference is that is not warming up. Anyway, I removed one delay. I'll check if it behave better now.

[seiq 32]

On 1/9/2017 at 8:17 PM, Sankotronic said:

That is why I use loops instead of this delay functions. I have only one scene that loops indefinitely and takes care of all time based events and 12 Very Smart Light scenes that loop only when necessary, all the rest is running only when needed and no problems mentioned above. You can find links to this scenes in my signature  

Yeah I've seen your scripts and they are quite in depth!  These motion scenes only run the delay when necessary in the same manner that your Very Smart Lights script does once light levels, people home, sleeping, overrides, etc have been checked.

 

Please login or register to see this code.

sourceTrigger.deviceID = motion sensor

ids = table of device/light ids to turn on/off {100, 101, 102, etc}

 

Basically the lightsOff() function keeps calling itself after recalculating the required sleep time and checking if its ok to turn the lights off. setTimeout() *should* be similar to running fibaro:sleep() + lightsOff().

 

Funny the system hasn't locked up the last few days (touch wood!) which have had cooler weather. Maybe it is a temperature overheating problem...