All Activity

Jan how to write in ER7? RULE142: ./include/props.lua:268: Wrong parameter type, string required. Provided param 'nil' is type of nil user:msg = 'Partitie 03 Ramen appartement is BETREDEN!!!!!!!!!!!!'; ^^^^

Sorry in fact everything was working (again) after the reboot but all Fibaro new messages went into the Spam (unwanted) email...Corrected and everything back to normal.

I'm not sure, but sometimes reboot, or recovery helped me, when thing were wrong. I just got into the same problem: a week ago I was still receiving email but now no way. I have not find any reason why... code is: fibaro:call(2,"sendEmail","Dead nodes","La scène 20 vient de redémarrer") I did reboot the HC2 with no success (with or without backup)! I will open a ticket

@ChristianSogaard https://manuals.fibaro.com/home-center-3-quick-apps/, check section about UDP there.

Hi Fibaro team, @[email protected] I would like to request UDP socket support for user-created QuickApps on Home Center 3. Some local integrations depend on UDP-based protocols, discovery, or request/response communication. One example is Nilan Gateway, which uses a local UDP-based Micro Nabto protocol. Without UDP support in QuickApps, these integrations require an external proxy or bridge service, even though the actual device is available on the local network. For many HC3 users, requiring an extra Raspberry Pi, NAS service, or local server defeats the purpose of having the Home Center as the central automation hub. It would be very useful if QuickApps could access a supported UDP API, for example: - create UDP socket - send datagram to host/port - receive datagram responses with timeout - optionally enable broadcast/multicast for discovery Even a limited, sandboxed UDP API would make many local LAN integrations possible without external services. Is UDP socket support for user QuickApps something Fibaro could expose officially in a future firmware release? Thanks.

After "Apply selection", the 429 errors did not appear anymore. I've edited the scenes and button relations, tested, still no errors. Suddenly, after some 30/35 minutes, they came back, but appear to have been triggered by a parsing error: [24.06.2026] [02:46:06] [DEBUG] [QUICKAPP92]: Event: motion Hal sensor [24.06.2026] [02:46:07] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:46:11] [DEBUG] [QUICKAPP92]: Event: light_level Hal sensor [24.06.2026] [02:46:12] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:46:16] [DEBUG] [QUICKAPP92]: Event: motion Hal sensor [24.06.2026] [02:46:17] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:46:20] [DEBUG] [QUICKAPP92]: Event: geofence_client [24.06.2026] [02:46:32] [DEBUG] [QUICKAPP92]: Event: light Hal [24.06.2026] [02:46:33] [DEBUG] [QUICKAPP92]: Event: grouped_light /groups/0 [24.06.2026] [02:46:35] [DEBUG] [QUICKAPP92]: Event: motion Overloop sensor [24.06.2026] [02:46:36] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:46:44] [DEBUG] [QUICKAPP92]: Event: motion Overloop sensor [24.06.2026] [02:46:45] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:46:47] [DEBUG] [QUICKAPP92]: Event: temperature Voordeur sensor [24.06.2026] [02:47:06] [DEBUG] [QUICKAPP92]: Event: light Hal [24.06.2026] [02:47:07] [DEBUG] [QUICKAPP92]: Event: grouped_light /groups/0 [24.06.2026] [02:47:07] [DEBUG] [QUICKAPP92]: Event: grouped_light Hal [24.06.2026] [02:47:07] [DEBUG] [QUICKAPP92]: Event: table: 0xaaaaf7b06b00 [24.06.2026] [02:47:07] [DEBUG] [QUICKAPP92]: Event: grouped_light Staircase [24.06.2026] [02:47:07] [DEBUG] [QUICKAPP92]: Event: scene Dimmed [24.06.2026] [02:47:07] [DEBUG] [QUICKAPP92]: Event: light overloop lamp [24.06.2026] [02:47:20] [DEBUG] [QUICKAPP92]: Event: geofence_client [24.06.2026] [02:47:49] [DEBUG] [QUICKAPP92]: Event: temperature Tuin sensor [24.06.2026] [02:47:56] [DEBUG] [QUICKAPP92]: Event: motion Overloop sensor [24.06.2026] [02:47:57] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:47:59] [DEBUG] [QUICKAPP92]: Event: light_level Overloop sensor [24.06.2026] [02:48:00] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:48:06] [DEBUG] [QUICKAPP92]: Event: motion Overloop sensor [24.06.2026] [02:48:07] [WARNING] [QUICKAPP92]: /eventstream parse: ./include/HueTransport.lua:55: attempt to index a nil value (global 'debug') (retry in 1000ms) [24.06.2026] [02:48:08] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 5s (recent 429s: 1) [24.06.2026] [02:48:08] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 5000ms)[24.06.2026] [02:48:13] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 5000ms)[24.06.2026] [02:48:18] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 10s (recent 429s: 3) [24.06.2026] [02:48:18] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 10000ms) [24.06.2026] [02:48:28] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 20s (recent 429s: 4) [24.06.2026] [02:48:28] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 20000ms) [24.06.2026] [02:48:48] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 40s (recent 429s: 5) [24.06.2026] [02:48:48] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 40000ms) [24.06.2026] [02:49:29] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 40s (recent 429s: 2) [24.06.2026] [02:49:29] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 40000ms)[24.06.2026] [02:50:09] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 40s (recent 429s: 2) [24.06.2026] [02:50:09] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 40000ms)[24.06.2026] [02:50:49] [WARNING] [QUICKAPP92]: Hue bridge 429 from SSE, pausing all traffic for 40s (recent 429s: 2) [24.06.2026] [02:50:49] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 40000ms)

@jgab Thank you very much for your work on YahueV2. I'm new to HC and also discovered that the stock Hue app did not communicate with the bridge pro. So I found your work, installed it and got it up and running. Added one light and in the Preview tab I played with the colours and toggled it on and off. All worked. Until I created a Block scene for the light. I connected the Block scene to trigger on a Walli Controller button 1 press to turn on the light and a second scene to connect to button 2 to turn it off. Nothing happened when I pressed either button on the Controller; the light did not respond. Removed and readded the same light (not a room, just the light itself), again played with color in Preview, all working, connected it back in the Scene/Action and ... nope, no action. Maybe once or twice the Hue light responded to a Controller button press, but no more. I found the Console and selected the QUICKAPP92, the Yahue_Proxy and it reported this: [24.06.2026] [01:22:31] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 3) [24.06.2026] [01:22:31] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:22:31] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:22:31] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms) [24.06.2026] [01:23:32] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 1) [24.06.2026] [01:23:32] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:23:32] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:23:32] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms) [24.06.2026] [01:24:32] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 3) [24.06.2026] [01:24:32] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:24:32] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:24:32] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms)[24.06.2026] [01:25:32] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 3) [24.06.2026] [01:25:32] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:25:32] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:25:32] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms)[24.06.2026] [01:26:29] [TRACE] [QUICKAPP92]: onAction: {"manual":true,"args":[],"deviceId":99,"actionName":"turnOn"} [24.06.2026] [01:26:29] [DEBUG] [QUICKAPP92]: huePUT dropped (bridge cooldown 3s left): /clip/v2/resource/light/cce96469-7fd2-4f7e-8415-e23c59f4bd98 [24.06.2026] [01:26:32] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 3) [24.06.2026] [01:26:32] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:26:32] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:26:32] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms) [24.06.2026] [01:26:35] [TRACE] [QUICKAPP92]: onAction: {"manual":true,"args":[],"deviceId":99,"actionName":"turnOff"} [24.06.2026] [01:26:35] [DEBUG] [QUICKAPP92]: huePUT dropped (bridge cooldown 57s left): /clip/v2/resource/light/cce96469-7fd2-4f7e-8415-e23c59f4bd98 [24.06.2026] [01:27:20] [DEBUG] [QUICKAPP92]: Health-check: refreshing Hue resources [24.06.2026] [01:27:33] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 1) [24.06.2026] [01:27:33] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:27:33] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:27:33] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms) Something is flooding the Hue Bridge Pro. Note the "huePUT dropped". Do I need to turn off or disable a refresh setting? A few minutes later it pulled all devices from the hub, so it seems: [24.06.2026] [01:30:33] [WARNING] [QUICKAPP92]: Hue bridge 429 from GET refresh, pausing all traffic for 60s (recent 429s: 3) [24.06.2026] [01:30:33] [WARNING] [QUICKAPP92]: /clip/v2/resource HTTP error: 429 [24.06.2026] [01:30:33] [WARNING] [QUICKAPP92]: Retry in 60s [24.06.2026] [01:30:33] [WARNING] [QUICKAPP92]: /eventstream: HTTP 429 (retry in 60000ms)[24.06.2026] [01:31:02] [TRACE] [QUICKAPP92]: UIEvent: {"elementName":"dump","values":[],"deviceId":92,"eventType":"onReleased"}[24.06.2026] [01:31:03] [DEBUG] [QUICKAPP92]: ------------------------ [device:066ee960-736a-42d2-a873-0e160d10aa75,Keuken spot 3,LTG002] Meanwhile, I am able to turn the same lights on/off via Home Assistant with Hue integration. What could be causing the "Hue bridge 429 from GET refresh, pausing all traffic for 60s" message? The "Apply selection" button resets the 429 error somehow. I removed the Hue light from Devices and only clicked the "Apply selection" to have it re-added. The bridge is scanned, the light is added. No more errors in the console after that: [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Setup 8304f2d9-6269-4ce1-96d2-28ce3ac48df1 'zone' Staircase [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Setup 9567e3da-51e0-4581-8dfe-9bae0c09ceb5 'zone' Eettafel [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Setup cf7c045d-960f-4b32-a853-9cdd298604fb 'zone' TV wand [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Setup e58bf2b1-952d-4b57-a2c8-9ed062b1bfe6 'zone' TV Ambilight [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Setup f3ce6d30-a99c-4576-a423-ac77b62ea142 'zone' Lichtbak [24.06.2026] [02:09:27] [WARNING] [QUICKAPP92]: Variable sseHeartbeat not found [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Defining QA classes [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Loading existing child UID:'ColorLight:d0ef34e2-85e9-4806-8b04-5c884306b30d' [24.06.2026] [02:09:27] [DEBUG] [CHILD95]: status connected [24.06.2026] [02:09:27] [DEBUG] [CHILD95]: [diag v0.2.65] on=true -> state:=true, value:=100 (lastVal=nil) [24.06.2026] [02:09:27] [DEBUG] [CHILD95]: color xy 255,189,87 [24.06.2026] [02:09:27] [DEBUG] [CHILD95]: [diag v0.2.65] dimming raw=56.13 state=true lastVal:nil->56 value:=56 [24.06.2026] [02:09:27] [DEBUG] [CHILD95]: color_temperature 446 [24.06.2026] [02:09:27] [DEBUG] [QUICKAPP92]: Creating missing child UID:'ColorLight:beabb96c-de54-46a1-a938-d9e0461b635d' [24.06.2026] [02:09:28] [DEBUG] [CHILD100]: status connected [24.06.2026] [02:09:28] [DEBUG] [CHILD100]: [diag v0.2.65] on=false -> state:=false, value:=0 (lastVal=nil) [24.06.2026] [02:09:28] [DEBUG] [CHILD100]: color xy 255,189,86 [24.06.2026] [02:09:28] [DEBUG] [CHILD100]: [diag v0.2.65] dimming raw=1.19 state=false lastVal:nil->1 (state=false, value not written)[24.06.2026] [02:09:28] [DEBUG] [CHILD100]: color_temperature 446 [24.06.2026] [02:09:28] [DEBUG] [QUICKAPP92]: Created new child ID:100, UID:'ColorLight:beabb96c-de54-46a1-a938-d9e0461b635d' [24.06.2026] [02:10:11] [DEBUG] [QUICKAPP92]: Event: temperature Hal sensor [24.06.2026] [02:10:12] [DEBUG] [QUICKAPP92]: Event: geofence_client [24.06.2026] [02:10:39] [DEBUG] [QUICKAPP92]: Event: temperature Fietsenhok sensor [24.06.2026] [02:11:13] [DEBUG] [QUICKAPP92]: Event: geofence_client ... No more "Hue bridge 429 from GET refresh, pausing all traffic for 60s" events. Hue Bridge Pro v1.77.2071353020 YahueV2 v0.2.65

Today, the connection to my ZigBee devices magically came back all of a sudden. I wonder how long it will last. Of course, this is on the older firmware version (5.200). With 5.210 installed, I waited over a week hoping that the HC3 would restore the connection. You’re right @MAC71 They added ZigBee support five years ago, and since then, almost no fixes or improvements have been made. Unfortunately, it’s not even possible to replace everything with Z-Wave devices. And even if it were possible, their design and performance leave a lot to be desired (for example, I have great ZigBee motion sensors that have been running on a single watch battery for two years now!). Sometimes, when I’m at friends’ houses, I look jealous at their Home Assistant setups but I know it would take a lot of time to migrate over 100 devices and scenes to Home Assistant.

Hello again and thx tinman, I have done some testing and found the following: accessControlEvent does NOT work as a scene trigger on ZW3 (as you mentioned) centralSceneEvent works fine for both buttons (11 and 12) when parameter 1 = 2 (central scene mode) So for now I can using centralSceneEvent for both ARM (button 11) and DISARM (button 12) without PIN code The only thing I am missing is the PIN security for DISARM, which was possible with accessControlEvent on ZW2. Do you know if Is there any plan to fix accessControlEvent as a scene trigger on ZW3? Or is there any other workaround to use PIN + button for DISARM on ZW3? Thanks!

As a first measure, I did recreate the token - no change for the better!

I also experience the same issue from time to time – the Tedee plugin stops working. Removing and re-adding the plugin fixes the problem, but it would be nice if it worked continuously without requiring any intervention. While quickly searching the Tedee API documentation for the word “expired”, I found some references to token expiration. So perhaps the token expires after some time and the plugin is unable to refresh it properly?

Documentation showing differences on the API side (like parameters) is here: @Smarti as for the logs, yeap - those are mostly cutted out due the fact that in most cases those did not do anything worth mentioning. The errors of any action ( ex. issue with setting the association or the parameter is reported right away with the red toast in the interface).

There is also build-in log level setting in the quickapps: function QuickApp:onInit() self.logLevel = ERROR self:debug("this debug should not be visible in console") self:error("this error should be visible in console") end self.logLevel one of following constants: NONE, ERROR, WARNING, DEBUG, TRACE

Hi, I have enabled remote access now. HC3-00000454 Im not home at the moment but please check if you can resolve the issue without having to go back to ZW2 engine. Br Jimmie

Hi, We'd like to get back to the topic we discussed earlier and take a closer look at it. Would it be possible for you to share the hub with us for analysis? Please also let us know which device (deviceId) we can use for testing. Enable full remote access as well so that we can investigate the issue thoroughly. Thanks, and we'll be waiting for your update. BR

Hi @Brytho I have never had an active reconfigure button on my HC3. Fibaro's version/installation of Zigbee has always been 'Beta' even after all these years. Here in Australia, we don't have the variety of Zwave devices like in Europe so I am a heavy user of Zigbee as well. I have found that a lot of the time when my items drop off the network, like you are seeing, if i put my HC3 into pairing mode for Zigbee and wake up the Zigbee item, it usually will rejoin the network. I THINK the issue for me is when a battery powered device drops that it breaks the mesh connection, leading to further dropouts - then I go through the process as described; I'll be solid again for a long period of time until it happens again. I know it's far from a perfect solution, but we have all been sold down the river on the HC3 and its multi-protocol capabilities or lack there of (marketing material in Aust said Zigbee and 433mhz) It's my opinion that Zigbee will never be a full, stable component of my HC3 set up. so we either need to put up with these workarounds or bite the bullet and rebuild on another platform. just my $0.02c worth

I have an old FGMS001 (firmware 3.3) motion sensor that works perfectly which I use to control my blinds on one side of my house. My sun sensor (from Somfy) stopped working and I thought that I would replace it with another Fibaro motion sensor. But the new one dosn't work as expected (and differently from the old one). It reports lux up to ~15000 but above that it starts to report 0? I thought that the fsensor was broken and got a repalement for. But is does exactly the same?! The new one has frimware 3.4. I have tried the old one besides the new one and the old one reports lux above 15000 while the new one is at zero when there are to much light. Any configuration I can do to help this situation? (I don't think setting 40/42 will help for this and I have tried to alter them but without any improvement)

I noticed today that the Tedee lock plugin no longer works - neither scenes nor direct interaction via device preview. It neither locks nor unlocks anymore. Locking/unlocking directly from the Tedee app works - as well as via the Home Assistant integration. Can you please have a look into that issue? Thanks!

I've tried it this way, and it's working: local QuickApp_trace = QuickApp.trace function QuickApp:trace(val1, ...) if val1 == "onAction: " then return end QuickApp_trace(self, val1, ...) end

I forgot the val1 in hub.trace(QUICKAPP..self.id,val1,...)

This is clearly not a 3rd-party device issue. It is a crash of the HC3 internal Zigbee coordinator. The fact that the "Reconfigure" button is grayed out in your own UI proves that the internal backend process is dead or unresponsive. Please escalate this ticket to the R&D. This is an internal firmware bug, not an external vendor issue. Regards

Thank you very much, of course it works! I can’t believe I didn’t think of such a simple idea. I was sure it was going through some internal hub mechanism, and yet here we are.

Redefine the trace function in your QuickApp: function QuickApp:trace(val1,...) if val1 ~= "onAction: " then hub.trace(QUICKAPP..self.id,...) end end

It is possible to make a slave HC2 and the master is HC2 also. can you please help me how to solve this.

Hi, Unfortunately, we are unable to resolve this issue on our side. This functionality relies on integrations and services provided by third-party vendors, and therefore its operation is outside of our direct control. As a result, we are unable to make changes to it or guarantee its proper functionality. Best regards