All Activity

I pushed v0.2.69. It has 2 main fixes. - buttons and options sensors don't republish their events when the QA starts up (thanks @_Marian_) - a new logic to keep the event stream open. Sometimes the event stream opened to the Hue hub goes stale and it's hard/impossible to find out from the net.HTTPClient code. Now there is a quickAppVariable 'watchdog' that can be set to 'time' or 'poll' - 'time', means that we monitor the socket and if we don't get any event for x seconds we restart the QA tand reconnects. - 'poll', means that if we haven't got any events for x seconds we poke the hub so it emits an event, if no event back we restart the QA: The time x is set by the quickAppVariable 'watchtime'. The default for 'watchdog' is 'time' The default for 'watchtime' is 1800 for time, and 60 for poll. The default is 'time' now to mimic the old behavior, but I would recommend people to try out poll as it is more effective and responsive if the stream goes stale.

Thanks, I do believe I know what the problem is. Will have a look at it...

Hi, I'm running a Hue Dimmer Switch through Yahue v2 on HC3, and I'm seeing a reproducible issue: roughly every 30 minutes, during what looks like a periodic reconnect/resync cycle, button 4 fires a full Pressed → Released sequence even though nobody touched the switch. Buttons 1–3 do not show this behavior — they're correctly reset to idle. Example from my log (this pattern repeats every ~30 minutes, all day): [08:11:37] status connected [08:11:37] button:1 _ _ [08:11:37] button:2 _ _ [08:11:37] button:3 _ _ [08:11:37] battery 100 [08:11:37] status connected [08:11:37] battery 100 [08:11:37] button:4 _ _ [08:11:38] button:4 Pressed initial_press [08:11:38] button:4 Released Note that buttons 1, 2, and 3 all reset cleanly to _ _ during the resync, but button 4 gets an extra Pressed initial_press / Released pair about 1 second after its own _ _ reset. This exactly matches the last button I physically pressed on the dimmer (button 4, hours earlier) — so it looks like the resync logic is somehow re-emitting the last "active" button state as a fresh press instead of just resetting it to idle like the others. This causes real problems downstream: I have an HC3 scene bound to button 4 (hub.scene("execute", ...)) that gets triggered every 30 minutes by this phantom event, forcing my target scene to run repeatedly without any real button press. Is this a known issue? Happy to provide more logs or test a fix if useful. Thanks!

The gateway has no effect on the device's alarm activation - this is a problem with the device itself. It is possible that one of the sensor components is contaminated/dirty or damaged.

Ah okay, thanks. I tried writing something based on what m.roszak proposed: I removed the device selection from the QA and hardcoded the devices instead, added a "Home_Presence" variable and a trigger counter block (useful for multiple manual activations—it caps at 2; does that make sense? Who knows!), and finally implemented dynamic icon switching. Everything works except the geofencing.☹️ The code comments are in Italian—please bear with me. They’re more for my own benefit than for yours, since you all know a lot more about this than I do.🤭 Geofence_iPhone_1147.fqa

Hi @GasDeKu, I'm referring to my own quick app. It will be available for download after I preform thorough testing.

The problem was identified and reported to the technical department.

Further discussion of the issue has been moved to a private channel. After identifying the cause or resolving the issue, the appropriate information will be published.

Thanks for the support. Which quick app are you referring to? I tried geofence_event.fqa and v2 but to no avail.

I have the same problems sometimes too. WHat I miss is haveing a notification in HC3 why this did occur? In my opinion it should be no problem if the code inside of the smoke sensor desiced to enable alarm having a message sent to the controller also including thew reaons for this alarm... But normally I do see nothing in the HC3 (no message, grpahs are looking fine and so on).

@Support FIBARO, take a look at this please. It should report the hcName defined in the settigs of the hub, for some reason its being swapped with serial number as you report. I confirm on my system that it "reverts" to the serial number by itself - don't know the reason

Hi @m.roszak, I use location panel to get location settings for my HC3 and I notice inconsistency in reporting HC3 name. Most of the time reported name is actually serial number of the HC3. After I changed name of my HC3, for some time this new given name was reported, but then after some time again serial number. Since in the returned json: [ { "id": 219, "name": "HC3-xxxxxxxxx", "latitude": 00.386733293331616, "longitude": 00.471836863604455, "radius": 150, "address": "Xxxxxxxx, Croatia", "created": 1783151231, "modified": 1783151231, "home": true } ] there is a "name" and not "serialNo", shouldn't actually contain user given name? Also, since users can add another location, what those other locations can be used for? I guess, I can add location of my work and then get triggers when I arrive at work?

can do it with the swagger api I think:

Hi. How does the neighbor option look on a Z-Wave 3 engine? In the old version, you could refresh the neighbor list, but in Z-Wave 3 there's no such option... How does it work now if you want to move a device to another place? Will the device handle it on its own? Does it check neighbors on its own from time to time? Or do you have to manually add it again?

@m.roszak, Because there is no z-wave device with those options. Can you add this device FP300 Zigbee. It's a real game changer it has pir and mmWave. Tip if possible also the enter and leave option, what is missing in the FP1 Thanks in advance

That is going to be due to Fibaro's implementation of the Zigbee protocol. Not much you can do natively in HC3 - Zigbee devices either work or they don't. There are no editable parameters etc

I‘ve included the Aquara FP300 zigbee occupancy sensor, but it only shows temperature, illuminance, but no occupancy - any ideas? Thanks!

I‘ve been a bit too hasty with my previous comment - the plugin is still not working 😟

Hello everyone, Yesterday and today i started seeing all my customer's and my own Fibaro Home Centers unavailable and in an inconsistent state. On my own i had to reverse to a previous backup and reverse version to 5.200. All my cstomer's Fibaro Home Centers are unavaible and would like to know if this an isolated case or not. Thank you.

Hi @GasDeKu, Geofencing on HC3 with Apple iPhones working flawlessly for me for two months now. I have made Quick app which listen to events received from iPhones and acts accordingly:

Hi everyone, I'm reviving the discussion because I thought hc3 was finally able to handle this damned geofencing, but at least for me, I just can't seem to figure it out. Since I'm completely new to LUA, I created a Presence_Home variable set to 0, followed by a phone tracking scene (two iPhone 16-inch models), and then two more block scenes to deactivate and reactivate the alarm. For the phone tracing scene, I relied on AI help because I don't have your expertise. The device ID numbers are those obtained from the yhubii user modification app. Until now, I've been using Google Home (with the Fibaro plugin) with a simple scene created in the app. Do you have any suggestions?

Please download and run to identify LQV and LQI. Will be helpful if you can post your table later.

Thanks. I think I followed the VSCode setup from github but tbh, was jumping around between this topic and github alot!

Jeg har en eldre homecenter 2, har nå kjøpt en home fenter 3 lite, og ønsker å få overført mest mulig fra 2 til 3, hvordan gjør jeg det?

But isn't stepValue the same as fibaro.call(id, "setValue", fibaro.getValue(id, "value")+5) ?