z-wave re-starts every hour

[rio1965 3]

I saw the following messages in the console:

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Z-wave start

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Initializing Z-Wave

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Opening port

 

This happens every hour. Does anybody have an idea, what the issue is?

[Ini 0]

Hey 

Please login or register to see this link.

 

We’d like to review this case in more detail. Please send the serial number of your hub in a private message and make sure support access is enabled. This will help us diagnose the issue more efficiently.

 

Best regards,

Ines

[lux 14]

Try a different power supply

[cag014 731]

On 11/3/2025 at 12:05 PM, rio1965 said:

I saw the following messages in the console:

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Z-wave start

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Initializing Z-Wave

[01.11.2025] [16:20:58] [TRACE] [ZWAVE]: Opening port

 

This happens every hour. Does anybody have an idea, what the issue is?

First of all, after updating to firmware 5.190, many users have reported periodic restarts on this forum.

 

I have the same problem after updating to version 5.190, although in my case the restarts occur every few days rather than every hour.

Fibaro support told me that everything points to a communication problem between the chips on the main board and the RF board, although this could also be related to power supply issues.

I also have another HC3, and after updating it, the same restart behavior has been observed.

Since I’ve seen the same behavior on two different HC3 units, it points more to a firmware‑level rather than a single faulty controller.

 

Since I don’t have advanced tools to diagnose the issue, I can only share my observations. My hunch is that, at least in my case, the problem is related to the setInterval() function.

As far as I know, setInterval runs indefinitely until explicitly cleared with clearInterval. Each interval consumes CPU and memory, and over time this can overwhelm the HC3’s resources.

The problem becomes worse when you restart a QuickApp that starts setInterval again and again.

According to the documentation, restarting a QA should clear its event handlers (sandbox). However, in practice, each restart may leave behind “orphaned” tasks for a short time. If you restart several times in quick succession, the controller can be flooded with multiple overlapping intervals. When many intervals (old and new) are running at once (especially with short delays) the CPU spikes, and the firmware watchdog process may freeze the UI or trigger a soft restart to recover.

After replacing my use of setInterval with hub.setTimeout, I haven’t experienced any restarts for the last two weeks.

I don’t know if you’re using setInterval, but I’d recommend avoiding it.

 

 

 

Edited November 4, 2025 by cag014

[RalfLuchs 0]

Same Problem here with the Meshnet Reconfigurations... 5.190.38. Every 3 Minutes and then the System does not Respond and lost Actions!!!

[10.11.2025] [20:27:39] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:29:04] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:29:06] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:29:27] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:29:27] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:29:27] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:31:22] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:32:15] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:32:15] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:34:28] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:35:25] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:35:25] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:37:38] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:38:36] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:38:36] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:40:49] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:41:48] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:41:48] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:44:03] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:44:59] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:44:59] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:47:14] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:48:09] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:48:09] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:50:24] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:51:20] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:51:20] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:53:34] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:54:31] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:54:31] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:56:44] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [20:57:42] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [20:57:42] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [20:59:58] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [21:00:52] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [21:00:52] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [21:03:06] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [21:04:03] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [21:04:03] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [21:06:16] [TRACE] [ZWAVE]: Z-wave start
[10.11.2025] [21:07:36] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [21:07:47] [TRACE] [ZWAVE]: Initializing Z-Wave
[10.11.2025] [21:10:33] [TRACE] [ZWAVE]: Opening port
[10.11.2025] [21:10:33] [TRACE] [ZWAVE]: Initializing Z-Wave
 

[cag014 731]

Try to recover latest backup... 3 minutes probably enough time to start the recovery process

 

[RalfLuchs 0]

Hi Together

After 2 Days of Building the Meshnet every 3 Hours it has stopped. Why ever...

[SmartHomeEddy 1,005]

7 minutes ago, RalfLuchs said:

After 2 Days of Building the Meshnet every 3 Hours it has stopped. Why ever...

 

After the restore?

[RalfLuchs 0]

The Problem every 1 Hour is still here...

 

[13.12.2025] [07:38:07] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [07:38:07] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [07:38:07] [TRACE] [ZWAVE]: Opening port[13.12.2025] [08:39:07] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [08:39:07] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [08:39:07] [TRACE] [ZWAVE]: Opening port[13.12.2025] [09:39:45] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [09:39:45] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [09:39:45] [TRACE] [ZWAVE]: Opening port[13.12.2025] [10:40:31] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [10:40:31] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [10:40:31] [TRACE] [ZWAVE]: Opening port[13.12.2025] [11:41:19] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [11:41:19] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [11:41:19] [TRACE] [ZWAVE]: Opening port[13.12.2025] [12:42:26] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [12:42:26] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [12:42:26] [TRACE] [ZWAVE]: Opening port[13.12.2025] [13:43:31] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [13:43:31] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [13:43:31] [TRACE] [ZWAVE]: Opening port[13.12.2025] [14:44:40] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [14:44:40] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [14:44:40] [TRACE] [ZWAVE]: Opening port[13.12.2025] [15:45:10] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [15:45:10] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [15:45:10] [TRACE] [ZWAVE]: Opening port[13.12.2025] [16:46:01] [TRACE] [ZWAVE]: Z-wave start[13.12.2025] [16:46:01] [TRACE] [ZWAVE]: Initializing Z-Wave[13.12.2025] [16:46:01] [TRACE] [ZWAVE]: Opening port

[Smarti 0]

Hi, I have found this topic after asking in the main forum and was directed, that I have to search for the issues in every update it seems. 

 

The reboots of the HC3, its really bad because it kills everything. Its not a complete reboot, but only the services, but all running apps, all runing scenes everything dies. 

 

From my research, it is in controlling the RGBW 1 modules. The modules are in Input/Output mode because they are controlling led lights. I have checked the codes and there are no setIntervals in the code, I use everywhere fibaro.setTimeout

 

Does anyone of you, have this issue ? Also, I have noticed that one of the modules, even after reconfig, they are lightened up in the "devices" as if it would be new or something.

 

Please login or register to see this attachment.

 

I have tried to edit the mode of the rgbw to RGBW and unhid the lights, but no success. I think there is maybe some problem with the rgbw showing 0% but the lights are on. I turn off the scenes controlling the rgbw. I have no reboots. When I activate even one of the light scenes, it reboots. I have the same program, and same led strips on rgbw2 modules, and nothing happens. 

 

 

 

 

 

[Smarti 0]

Hello,

 

Since the issue is here for too long, is there someone, that is able to check the logs or something from the unit. I have already changed the modules from RGBW1 to RGBW2 in hopes it is the issue. The issue comes now less often but still is here. I am able to know/catch the logs cca 1 minute after the reboot.