Search the Community

A thread to share some coding techniques for QuickApps? Because QAs are "long running scenes" (they don't have to be loaded and restarted for every event) - it is actually worthwhile to build up a library of "nice to have" code and include them in QAs. Here is Fibaro's manual for QuickApps. Here is Fibaro's manual for creating QuickAppChild devices Here is Fibaro's manual for using MQTT client Here is Fibaro's manual for WebSocket client List of posts: Introduction to the QuickApp anatomy - tutorial Part 1. Lua functions and object-oriented programming. (QuickApp is a OO class, so we need that base) Part 2. The basic QuickApp functions and what they do... and how. Part 3. More on QuickApp event handling - interaction with the UI and fibaro.call(<quickApp>,"name",...) Part 4. QuickAppChildren and how to raise them... what makes them tick? Also a tutorial on using classes in QuickApps here... All functions and variables available in the QuickApp Lua environment Logging functions (replacement for color/html tags + tostring for customised data structure) Shared functions calls between QuickApps (Here is an improved version) Off-line HC3api to use fibaro.* calls on PCs/Linux/Mac (fibaroapiHC3.lua) Polling for triggers in a QuickApps (like fibaro.getSourceTrigger()) Here is another method using a helper QA Patching 'setTimeout' so you get an error message if the function crashes A generic template for a QuickApp A simple code-lock QuickApp (demonstrating the UI with buttons) A QuickApp for scheduling user profiles (demonstrates UI buttons that change labels/text to present options) It doesn't' actually schedules the profile yet. (here is a working version) Structuring a QuickApp using event handlers to cope with asynchronous calls - like when using net.HTTPClient() instead of FHTTP(). looping with setInterval (without drifting) A QD reporting if other QDs are crashing (leveraging the "polling for triggers" code) Coding and debugging HC3 QuickApps offline using PC/Mac/Linux and a Lua IDE (and auto-creating a proxy on the HC3) An example of a QuickApp that download and installs scenes and QuickApps from a repository (files in a flat format) Coding and debugging of HC3 scenes using fibaroapiHC3.lua (not strictly about QuickApps but related) - can speed-up time A more complex QD that reads Google calendars or iPhone calendars and schedule custom events (uses the QuickApp structure for asynchronous calls in a previous tip) A substitute for Lua's loadstring() Here is another method of loading code dynamically into a QA Creating proxy devices on the HC3 to share devices between HC2 and HC3 A "webhook" QD - pushing events to external apps Adding interfaces to QA's - ex. power and battery and updating the properties (updates the little battery and power icon UI) @tinman Using '/plugin/publishEvent' to emit 'centralSceneEvent' (and a few other) .... Ex. keyfob QA by @tinman QA Toolbox. A modular toolbox of add-on functions to QAs that makes it easier to develop QAs 'basic' - Generic QA functions for loggin, loading modules, and management - used by all other modules. (some documentation) 'childs' - QA functions to easily manage quickAppChild devices. Loading, saving state, getting UI events etc. 'events' - QA functions for defining event handlers and structuring your code accordingly. Makes it easy to setup timers in various ways... 'triggers' QA functions for recieving triggers like Scenes do. The events module will receive triggers if loaded, but own handler can be defined. 'rpc' - QA functions for declaring (synchronous) remote functions from other QAs files - QA functionality for copying files between QAs pubsub - QA functions for event publish/subscribe... ui - QA functions for manipulation the UI elements of a QA lua parser/compiler - QA function for emulating loadstring and evaluating Lua expression from strings profiler - Functions for timing code used in QA Reading label/button/slider values. Sha2.lib crypto libs for HC3 (MD5, HMAC, SHA-1, SHA-224, SHA-256, SHA-512/224, SHA-512/256, SHA-384, SHA-512, SHA3-224, SHA3-256, SHA3-384, SHA3-512, SHAKE128, SHAKE256) @tinman aes crypto lib @tinman List of HC3 device types and interfaces @tinman Readers note. I started to call QuickApp devices for QDs (as in QuickApp Device, thought QAs sounded like Question and Answers). So, I use the word QD here and there but I'm not religious about it...

HC3 Menu A macOS menu bar app to control your Fibaro Home Center 3 from the top of your screen — toggle lights, dim, open shutters, set thermostats, see sensor values, and get notifications when things change. Highlights Devices grouped by Room → Type, plus a re-orderable Favorites list. Switches, dimmers, shutters, thermostats, sensors, scenes, alarm/profiles. Three notification streams: device state changes, attention (battery/dead/breach), QA errors & crashes. Live Debug-messages window with filter, severity picker, follow-tail, copy, and Copy QA id for the selected row. Configurable global hotkey to drop the menu from anywhere. Optional daily auto-check for new releases. Signed & notarized DMG; in-app crash reporter. Install Download the latest HC3-Menu-x.y.z-arm64.dmg or HC3-Menu-x.y.z-x86_64.dmg from the Releases page. Open the DMG and drag HC3 Menu into the Applications folder. Launch HC3 Menu from Applications. A house icon appears in the menu bar. Allow Local Network access The first time HC3 Menu tries to reach your HC3, macOS should pop up: Click Allow, then quit HC3 Menu (⌘Q) and launch it again — macOS only applies the new permission to a freshly started process. If you missed the prompt or connections fail with "No route to host" (errno 65): Open System Settings → Privacy & Security → Local Network and toggle HC3 Menu on, then quit and relaunch. If HC3 Menu isn't in the list, reset its privacy state in Terminal: tccutil reset All com.jangabrielsson.hc3menu open "/Applications/HC3 Menu.app" Then click Refresh in the menu so it tries to connect again and re-triggers the prompt. Connect to your HC3 Open the menu and choose Preferences…, then on the Connection tab fill in: Host — your HC3's IP address (e.g. 192.168.1.50) User / Password — an HC3 account with API access PIN (optional) — required only if your HC3 enforces a PIN for certain actions Click Save. The menu will populate within a second or two. Using HC3 Menu Click the house icon in the menu bar. Favorites — your starred devices, always at the top. Rooms — devices grouped by room, then by type within each room. Plus (when present on your HC3) Alarm, Profiles, Scenes, Attention, Activity, Debug messages, Diagnostics. Inside each device submenu: Switches — click the row to toggle on/off. Dimmers — click the row to toggle on/off; Set value… opens a slider/input for 0–100 %. Shutters — Open / Close / Stop. Thermostats — set heating mode and target temperature. Sensors — read-only value (temperature, lux, humidity, motion…). ☆ Add to favorites / ★ Remove from favorites — manage favorites per device. Notifications Three independent notification streams, all toggleable from the Notifications submenu in the menu bar: Device state changes — In Preferences → Notifications, tick the Notify column for any device whose state changes you want delivered to Notification Center (e.g. front door opened, motion in garage). Attention — Battery-low, dead devices, sensor breach, alarm partition state changes. De-duplicated so you don't get spammed each poll cycle. QA errors & crashes — QuickApp error/fatal debug messages (per-QA throttled) and HC3 PluginProcessCrashedEvent events. Favorites Star a device with ☆ Add to favorites in any device submenu. Manage the list in Preferences → Favorites: Drag rows to reorder — the order is reflected in the menu bar's Favorites submenu. Select a row + Remove to unstar it. Global hotkey Open the menu from anywhere with a configurable chord (default ⌃⌥⌘H). Toggle it on from the menu (or Preferences → Shortcuts) and click Record… to set your own combo. Debug log window Activity → Debug messages → Open window opens a live log of all QuickApp debug/trace/warning/error messages with filter, severity picker, follow-tail, copy, and Copy QA id to grab the QuickApp's id from the selected row (the HC3 web UI has no stable per-QA URL, so we copy the id instead of opening a browser). If a QuickApp itself crashes on the HC3, a one-time notification fires and the crash is recorded in the Activity list. Crash reporter If HC3 Menu itself hits an unhandled exception, the traceback is written to ~/.hc3menu/crash.log and a one-time notification appears. Use Show crash log from the menu to inspect it. Check for updates Check for updates… fetches the latest GitHub release and opens the download page if a newer version is available. Enable Auto-check daily in the same submenu to have HC3 Menu poll once per day in the background; it only surfaces UI when something newer actually exists. Where settings are stored ~/.hc3menu/.env — host, user, password, PIN (plain text; chmod 600 recommended). ~/.hc3menu/config.json — favorites and notification rules. To start fresh, quit HC3 Menu and rm -rf ~/.hc3menu. Troubleshooting Problem Try "No route to host" / errno 65 Allow Local Network access (see above), then quit and relaunch. Menu shows nothing / "HC3 connection failed" Verify host/user/password in Preferences. From Terminal: curl -u user:pass http://<host>/api/settings/info Want to see logs tail -f ~/Library/Logs/HC3\ Menu/*.log For developers HC3 Menu is open source (MIT) — Python + rumps + PyObjC. If you want to run from source, hack on it, or build your own DMG, see docs/DEVELOPING.md. License MIT — see LICENSE. Personal-use build, signed and notarized for distribution. No warranty. Not affiliated with Fibaro.

scheduler.lua Repo & Code: https://github.com/jangabrielsson/scheduler A Lua port of the Python schedule library by Daniel Bader — job scheduling for humans. Designed for plua and Fibaro HC3 QuickApps, but works in plain Lua too. schedule.every(10).minutes:do_(job) schedule.every().hour:do_(job) schedule.every().day:at("10:30"):do_(job) schedule.every(5):to(10).minutes:do_(job) schedule.every().monday:do_(job) schedule.every().wednesday:at("13:15"):do_(job) schedule.every().minute:at(":17"):do_(job) schedule.every().day:at_sunrise():do_(job) schedule.every().day:at_sunset(-15 * 60):do_(job) -- 15 min before sunset Why a port? The Python schedule API is a fluent builder pattern that reads almost like English. Lua's metatables (specifically __index as a function) let us reproduce both the bare-property chaining (.minutes, .day, .monday) and the method chaining (:at(...), :to(...), :tag(...)) without the user having to type extra parentheses. Two execution models are provided: Mode Use when Polling — schedule.run_pending() Plain Lua, your own event loop Reactive — schedule.start() plua / HC3 / anything with setTimeout Plain interval jobs are drift-free (anchored to their first scheduled fire). Wall-clock anchored jobs (:at("HH:MM"), weekday jobs) are tied to local time and self-correct. Installation plua / Fibaro HC3 QuickApp There's no require in QA context, so scheduler.lua installs itself onto fibaro.schedule when loaded via the multi-file directive: --%%name:My QA --%%type:com.fibaro.binarySwitch --%%file:scheduler.lua,scheduler function QuickApp:onInit() local schedule = fibaro.schedule schedule.every(30).seconds:do_(function() self:debug("tick") end) schedule.every().day:at("06:30"):do_(function() self:turnOn() end) schedule.start() end Plain Lua local schedule = require("scheduler") schedule.every(10).minutes:do_(function() print("tick") end) while true do schedule.run_pending() os.execute("sleep 1") end Differences vs. the Python original No timezone support. All times use os.time() / os.date() in local time. The Python version's at(time, tz=...) is not implemented. do is a Lua keyword, so the method is :do_(fn, ...) (with a trailing underscore) instead of Python's .do(fn, ...). Property access uses ., not :. In Lua you cannot write obj:property without a call. So: every().monday ✅ (property) every():monday ❌ (Lua syntax error) every().day:at("10:30") ✅ (.day is a property, :at is a method) Two execution models. The Python version only has polling. This port adds :start() / :stop() for native setTimeout-based scheduling. until_() instead of until (Lua keyword). Grammar / chaining cheat sheet schedule.every([N]) -- start a new job, N defaults to 1 [:to(M)] -- random interval N..M (method) .UNIT -- (property, no parens) one of: -- .second .seconds -- .minute .minutes -- .hour .hours -- .day .days -- .week .weeks | .WEEKDAY -- (property) one of: -- .monday .tuesday .wednesday .thursday -- .friday .saturday .sunday -- (implies .weeks) [:at("HH:MM[:SS]")] -- (method) wall-clock anchor; -- ":MM" or ":SS" for hour/minute units | :at_sunrise([off]) -- (method) anchor to sunrise (+ offset seconds) | :at_sunset([off]) -- (method) anchor to sunset (+ offset seconds) | :at_sunrise_twilight([off]) | :at_sunset_twilight([off]) [:tag(...)] -- (method) attach one or more tag values [:until_(when)] -- (method) deadline; see below :do_(fn, ...) -- (method) register fn(args...) and start Singular forms (.second, .minute, .hour, .day, .week) require an interval of 1; using every(2).minute raises IntervalError. Weekdays require interval of 1 (every().monday, never every(2).monday). at() format depends on the unit: Unit Format .day / weekday HH:MM or HH:MM:SS .hour :MM, MM:SS, or :MM:SS .minute :SS until_(when) accepts: a number — epoch seconds (large), or seconds-from-now (small) "YYYY-MM-DD HH:MM:SS" (or without seconds, or just date) "HH:MM" / "HH:MM:SS" — today Examples Time-based intervals schedule.every(10).seconds:do_(job) schedule.every(2).hours:do_(job) schedule.every().day:do_(job) schedule.every(3).days:do_(job) Wall-clock times schedule.every().day:at("10:30"):do_(job) -- daily at 10:30 schedule.every().hour:at(":15"):do_(job) -- every hour at xx:15 schedule.every().minute:at(":30"):do_(job) -- every minute at :30 schedule.every().monday:at("08:00"):do_(job) -- Mondays 08:00 Randomized intervals schedule.every(5):to(10).minutes:do_(job) -- N in [5,10] min schedule.every(1):to(5).hours:do_(job) Sunrise & sunset Sun events are computed per upcoming day (so future days use the correct sunrise/sunset for that date, not today's value). On HC3 the location is read automatically from api.get("/settings/location"). Elsewhere, set it once: schedule.set_location(59.33, 18.07) -- lat, lon Then: schedule.every().day:at_sunrise():do_(open_blinds) schedule.every().day:at_sunset():do_(turn_on_lights) -- offsets are in seconds, may be negative schedule.every().day:at_sunset(-15 * 60):do_(prep_lights) -- 15 min before sunset schedule.every().day:at_sunrise(30 * 60):do_(morning) -- 30 min after sunrise -- civil twilight variants schedule.every().day:at_sunset_twilight():do_(close_shutters) schedule.every().day:at_sunrise_twilight():do_(stop_outdoor_lights) -- combine with weekday schedule.every().sunday:at_sunset():do_(weekly_recap) -- raw values (seconds since midnight, for the local date of `time`) local sr, ss, srt, sst = schedule.sunCalc() -- today local sr2 = schedule.sunCalc(os.time() + 7*86400) -- a week from now Sun-based jobs require interval 1 and either .day or a weekday property. They return a useful next-run because _schedule_next_run scans the next 14 calendar days for the first matching event in the future. Passing arguments local function notify(channel, msg) print(channel, msg) end schedule.every(2).hours:do_(notify, "ALERT", "heartbeat") Tags & bulk cancellation schedule.every(30).minutes:tag("housekeeping"):do_(cleanup) schedule.every(45).minutes:tag("housekeeping","weekly"):do_(report) schedule.get_jobs("housekeeping") -- returns matching jobs schedule.clear("housekeeping") -- cancels all matching jobs schedule.clear() -- cancels everything Self-cancelling job Return schedule.CancelJob from the function to unschedule it: local n = 0 schedule.every(1).minutes:do_(function() n = n + 1 if n >= 5 then return schedule.CancelJob end end) Deadline schedule.every(10).minutes :until_("2026-12-31 23:59") -- absolute :do_(job) schedule.every(5).seconds :until_(60) -- 60 seconds from now :do_(job) schedule.every().hour :until_("23:00") -- today at 23:00 :do_(job) Inspection schedule.next_run() -- epoch of next run, or nil schedule.idle_seconds() -- seconds until next run, or nil schedule.get_jobs() -- list of all jobs print(tostring(job)) -- human-readable job description Running -- plua / HC3 (reactive, setTimeout-based, drift-free) schedule.start() -- plain Lua (polling) while true do schedule.run_pending() os.execute("sleep 1") end -- run all jobs once, ignoring schedule schedule.run_all() schedule.run_all(2) -- with 2s delay between Multiple schedulers The module-level schedule.every, schedule.run_pending, etc. all use a shared default scheduler. You can also create independent ones: local s1 = schedule.Scheduler.new() local s2 = schedule.Scheduler.new() s1:every(10).seconds:do_(job_a) s2:every(1).minutes:do_(job_b) s1:start(); s2:start() API reference Module-level (default scheduler) Function Description schedule.every([n]) Start a new job, returns a Job schedule.run_pending() Run any due jobs (polling mode) schedule.run_all([delay]) Run all jobs immediately, optionally with delay between schedule.get_jobs([tag]) List all jobs (optionally filtered by tag) schedule.clear([tag]) Cancel all jobs (or all with matching tag) schedule.cancel_job(job) Cancel a specific job schedule.next_run([tag]) Epoch of next run, or nil schedule.idle_seconds() Seconds until next run, or nil schedule.start() Begin reactive (setTimeout) execution schedule.stop() Stop reactive execution and clear timers schedule.jobs() Direct access to the list of jobs schedule.CancelJob Sentinel — return from a job to unschedule it Job methods (all chainable, return the job) Method Description :to(latest) Use a random interval in [interval, latest] :at("HH:MM[:SS]") Anchor to a wall-clock time :at_sunrise([offset]) Anchor to sunrise (offset in seconds, may be negative) :at_sunset([offset]) Anchor to sunset :at_sunrise_twilight([offset]) Anchor to civil-twilight sunrise :at_sunset_twilight([offset]) Anchor to civil-twilight sunset :tag(...) Attach one or more tags :until_(when) Set a deadline after which the job is cancelled :do_(fn, ...) Register the function and start the job Job properties (no parens) Units: .second(s), .minute(s), .hour(s), .day(s), .week(s) Weekdays: .monday, .tuesday, .wednesday, .thursday, .friday, .saturday, .sunday Scheduler class schedule.Scheduler.new() returns a fresh instance with the same methods as the module-level functions (using :), e.g. s:every(2):minutes, s:run_pending(), s:start(), etc. Sun helpers Function Description schedule.set_location(lat, lon) Set the lat/lon used for sun calculations (auto-read from api.get("/settings/location") on HC3) schedule.sunCalc([time]) Returns sunrise, sunset, sunrise_twilight, sunset_twilight as seconds-since-midnight on the local date of time (default os.time()). Returns -1 for an event if the sun never rises/sets that day. Testing lua test_scheduler.lua # plain-Lua smoke test plua --fibaro QA_scheduler.lua # full QA demo (uses speed.lua to fast-forward 24h) QA_scheduler.lua exercises ~10 features and uses speed.lua (also in this repo) to compress a 24-hour simulation into seconds by hijacking setTimeout and os.time. Credits Original library: schedule by Daniel Bader and contributors — MIT-licensed. Inspirations cited by the original: Adam Wiggins' "Rethinking Cron" The Ruby clockwork module Lua port by Jan Gabrielsson, 2026.

I am encountering an issue with encrypted QuickApps on my Home Center 3 (Firmware 5.200 & 5.201.18). When I create a new QuickApp and add a button to the UI, the following happens: I save the QuickApp. I download it using the "encrypted" option. After uploading the same file again, the UI button is gone. Interestingly, any underlying code (if I put there any) still works perfectly, but the user interface is completely missing.

I begin... When I turned on the HC3 the box offers me the Z-Wave Engine 3.0 or 2.0? I have no knowledge, but by default I took 3.0 because the most recent version. Only did I make the right choice? I have browsed the forum, and many prefer 2.0, and there is no way to switch between the two protocols. It is necessary to go through a factory reset, and start from scratch. As I am starting out, and I only have two Walli Roller Shutter FGWREU-111. it's not too bad for me to start from scratch. I can't use the dsk key? Is this the cause of the Z-Wave Engine 3.0? But you HC3 poccésseur, what did you take? Thanks for your help.

Hello, I'm a newbee with Fibaro. I have a Fibaro Home Center 3, and created my Fibaro ID. Once I try to integrate Fibaro into Google home, the link is not created between them 2. I tried several times, I do not have any error message... But Fibaro is not added as a service into Google home (neither as a device...). I searched for tips in the web, but nothing I found gives a solution. Do you have any idea on how to proceed ? Thank you for your help.

I tried to add zigbee buttons to HC3. I can see added device, I can use in a scene , but when I press button , nothing happens. Seems like action was not detected. Any idea ? Any experience ? Thanks.

Is anyone has succeed to use https connection? I did follow Fibaro's procedure to install certification Download the certificate. In the Windows Start menu search for mmc app and open it. In the MMC (Microsoft Management Console) app go to File > Add/Remove Snap-In. Add Certificate Snap-in: Certificates > Select “Computer account” > Next > Next > OK. Now go to Certificates > Trusted Root Certification Authorities and right-click on “Certificates” Import the certificate. Find the certificate downloaded from the FIBARO Home Center 3. Import it. Done. Your connection with the gateway is now secure. but doesn't work on FIrefox. (Expiration date ?) Any extra steps required to install certification? Interesting it does work with Chrome !!??

Generic Fibaro HC3 Alarm system Hi Luabuilder Sharing is Caring I have see a lot of talk using Fibaro HC3 for Alarm system. I love the idea - i want that, so i tried to describe what a Generic Alarm system should be build of. Several people already tipped in with things they made og thoughts they have, issues they identified. Why invent the wheel when great tuff already has been made. @jgab has created the EventRunner4 and ChildrenOfHUE - All-in-one QA framework for HC3 - this can be used for arming and disarming the alarm - An example is provided here @10derand @JcBorgs described issue about HC3 is missing the "disable alarmExclude" - a “pre-check” for sensors before arming ALARM is needed What a good way to solve this - I way thinking of enhancing the doorstatus QA (below) ? And @FBerges already shared his version of an alarm system @Mateo created a Siren Quick APP And probably many more worked on their own solution to create a ALARM SYSTEM. Please tip IN if there is elementary features ? - that is missing for a generic HC3 Alarm! How would you structure this? ? - ONE Quick APP with everything, Variable for customising? or a QA with Scenes and Eventrunner4? Another useful idea that could be used, is the status for open windows and doors. This QA changes the Color in the matrix Bulb when a door or windows is opened. Doorstatus.fqa @10der learned me about getting the sensor possibilities with print(json.encode((api.get("/devices/hierarchy")))) com.fibaro.windowSensor com.fibaro.doorWindowSensor com.fibaro.doorSensor Perhaps some of the forum experts could create some overall structure and point the learners in right direction? ? ? Desired Functionality In case of alarm not armed Geofence • Ongoing control - have all users left the house? Message on Telephone (s) that the house is empty and the alarm is not active For ARMING the Alarm • Message on Telephone (s) about which windows are not closed. Message format Section, room, Sensor Message on Telephone (s) about which doors are not closed Message format Section, room, Sensor Message on Phone (s) When alarm is active and which Zone. Message could be Fibaro APP push, or Telegram Delay to get out the door Use a Keypad like Matrix for ARM - ala triple cut on one button and subsequently double click on another. This feature is already made by @Jgab in Eventrunner4 Use Fibaro APP for ARM LED/Bulb for show Status ARMED – I will probably use MATRIX ZDB LED in the perimeter to changes to RED By Disarm the Alarm Message on Phone (s) alarm is deactivated and if other Zones are active LED/Bulb for show Status DisARMED – I will probably use MATRIX ZDB LED in the perimeter to changes to GREEN, but could be a HUE Bulb Use Matrix for DisARM - like triple cut on one button and subsequently double click on another. This feature is already made by @jgab in Eventrunner4 Use Fibaro APP for DisARM For Alarm ACTIVE Internal sirens are triggered External sirens are triggered Light with alarm status, flashes 1 Hz SONOS speech - sound. Could be by using the Quick App - Sonos Zone Controller Message on Telephone about which device has triggered alarm - Section, room, Sensor

Hi all ! I would like to update another QA's label. In this case, it's QA with ID 95 and the label is called Doors. Does anyone know if this is possible and what that code might look like. function QuickApp:onInit() self:debug("QuickApp:OnInit") self:updateView("Doors open", "text", Doors) -- would like to update QA ID 95 end

I see that many users have a problem with ZigBee, frequently all devices showed disconnected and don't work anymore. If "standard" actions (like disconnecting/reconnecting power, reloading latest backup) don't help, here some steps that could help to recover and no need to reinclude all devices again. 1. Reset Zigbee Network 2. Include any ZIgBee device that in use in your system to initiate ZigBee network. Wait about 2 minutes and verify that included ZigBee device is working properly. Don't worry it will work later with the original ID, no need to change any code 3. reboot the system with your latest working backup 4. At the beginning you might see that all ZigBee devices are still disconnecting. Please wait several minutes till the system will stabilize ZigBee communication (could take up to 10 minutes) Now all ZigBee devices should work properly as before. This procedure helped me to recover at least 7 times. In some cases, just one (or more, but not all of them) ZigBee device become unstable, meaning takes time to turn ON/OFF and frequently shown as disconnected. I suggest solving the problem as following: 1. Create a backup 2. Reinclude the device 3. Reload saved backup The device should work using his original ID. No need to change scenes or code. Hope it helps

I've a number of roller shutter 2's operating Venetian blinds and they are working perfectly, and have for many years. Today I have moved one of them from my HC2 to my HC3. Set the mode to Venetian, ran calibration. I can open and close the blind but have no control over the slat position. That is in the Yubii app and the HC3 GUI, the slider is there so I know the blind mode is correct, but it does nothing. The relays in the roller shutter do nothing, not even a click. Just in case the issue is the GUI I've writen a block scene to move the slat position, still nothing. I have another 10 blinds to move over and this is not a great start.

Hi I notice all devices have a message in the icon saying whether a device is off or on or disconnected etc. I am wondering what dictates which type of message is displayed, as some show a time since last activation which I find most useful and would like to replicate to others. I thought it might be linked to 'Role' or 'Type' in basic parameters but not all devices show the same options in the dropdowns in order to experiment. Any advice?

Hello, I would like to use my HC3 in parallel with my HC2, i.e. as the main device and the HC2 only as a secondary device, so that I can move the individual actuators one after the other, or possibly replace them with Zegbee actuators. Do I have to activate the HC3 on this page first? “https://home.fibaro.com/cmh/device/list” I was thinking about linking the two together until everything has been moved, or even leaving the HC2 running as a secondary device if I can't move individual actuators. Do I then add the HC2 to the HC3 as a slave device? So far, the HC3 does not allow this.

I red lots of feeds but I cant find one single, not complicate device wakeup script for HC3. Im not programmer but I can work with not complicated code.. I have this few lines from older threads in fibaro forum. I have something like this: --[[ %% autostart %% globals --]] fibaro:getvalue(107, ´dead´) to wake up: fibaro:call(107, "wakeupdeaddevice" OR fibaro:wakeUpDeadDevice(107, 1); But I cant go through.. shows error (load):1: Assertion failed: Expected number BUT HOW to get functional little script from these lines... THANK YOU very much for any idea.

In the process of setting up an HC3 5.160.42 with some devices previously used on an HC2 system. My problem is with the jpg file of the 'send photo to user' by email action. I'm using the same camera URL as in the HC2 and the preview shows fine, and the scene triggers fine, but the emailed attached file won't open in anything, and appears empty (shows 0kb in properties). Anyone experienced this issue?

Hi all, I've recently purchased a HC3 and was hoping to be able to migrate from my existing HCL but when I attempted to do this via my Fibaro cloud account I got the notification "At least two gateways are required to copy backup from one device to another". Referring to the Online Fibaro user documentation for migration I read "Migration from Home Center Lite to Home Center 3 - Contact FIBARO Support and ask for setting your Home Center Lite as the artificial donor." So, I raised a support ticket with Fibaro. I guess I have two questions: 1: Am I completely reliant on fibro support to assist here or can I complete the migration without them? 2: I raised the support ticket a week ago - just received an automated response but nothing subsequently & the ticket status has not changed. Does anyone know what Service level agreements they are working to? Thanks in advance for any help

I had an issue with some Z-wave devices that insists to be disconnected from HC3. Have tried to relocate HC3 (as much as possible w/o irritating my wife) without success, always had some disconnected devices. But during the relocation have noticed that in some specific spot all devices have been connected. The problem to achieve full coverage, requires accuracy of ONE millimeter! Have tried to understand, why? I have my own SMS system connected to HC3 and when a specific corner of HC3 has touched the antenna (accidently) I have a good coverage. So.... I took a piece of metal and actually stuck it under HC3 like antenna (see below), now I have an excellent coverage. It's sound like a joke, but it's not a joke at all. After that have found an image of HC3 board, and YES, the Z-wave antenna is actually located on that corner of the box. Of course, will try to get a proper 868Mhz antenna to attach instead of current solution, but hey! it does the job. By the way did the same for Zigbee antenna also and again, a good improvement. There is a good logic behind that. Since HC3 has internal on-board printed antennas, any piece of metal could work as extender. Of course, it should be placed correctly otherwise it will cause interference. Let's say it's like wireless charging that we are using daily for our phones, as you know you should place the phone in very specific area. Here the actual image (please forgive me for the mess, the cost of moving the equipment around) In addition, I recommend using Z-wave repeater NEO Coolcam Z-Wave EU Repeater Sensor Compatible Zwave System 700 Series Home Automation - AliExpress It does work very well (not like AoenLabs extender which always shown as unconfigured device on all Fibaro systems). This extender configured and all parameters could be defined. Best repeater I ever had. I am very curios if it helps to others... please let me know if it works for you too.

Is it possible to disable the default push notification to the app when an alarm is triggered? I currently get "An alarm was detected on partition xxx" message as soon as an alarm partition is activated. I want to disable this. Reason is my scene plays an entry beep allowing time for someone to enter and put in their code. Therefore if the alarm is cancelled before say 60 seconds, I don't want to get the notification. The problem with the entry delay is that there is no way to trigger a scene and play the sound so the entry delay in the panel is pointless. I want to just handle the push notification in the code rather than get the one automatically. Thanks!

Cześć, Od 2 wersji firmware'u wstecz zauważyłem znaczące opóźnienia działania sieci z-wave a może tylko tak mi się wydaje i zwolniła cała centralka Home Center 3. Do centralki mam podłączonych 44 urządzeń z-wave i ich liczba w ostatnim czasie nie zmieniła się, za to robiłem upgrade do wcześniejszej wersji beta oraz do aktualnej 5.170.13. Jak wcześniej wyzwolenie akcji przez scenę lub bezpośrednio z panelu www trwało ok. 0,5-1s to teraz trwa ok. 5s. Co jak widać jest znaczącym pogorszeniem funkcjonowania, szczególnie jest to denerwujące jak ma się zapalić światło z czujnika ruchu. Restart centralki nie pomaga, rekonfiguracja siatki mesh wygląda jakby się nie robiła. Obciążenie centralki to: 10-20% CPU 70% RAM 30% pamięć Sądzę, że to wina firmware'u gdyż zaobserwowałem zaraz po wgraniu ostatniej wersji beta, myślałem, że w następnej wersji będzie to poprawione ale widać, że działa tak samo wolno.

Hello, I'm using HC3 and I have purchased the above Camera recently. My simple questions are: 1. How to connect the camera directly to my HC3, in terms of configurations? (I don't know how to get MJPEG & JPEG path) 2. Do I must have NVR? (preferred without) Tnx

I am progressively excluding my HC2 devices and migrating them to HC3, but I have a bunch that seem to not be responding to triple clicks...this was for exclusion initially, but then on re-inclusion after I managed to exclude after the 20th try for one dimmer. I think there are/could be multiple causes here: Dodgy switch wiring (there was one light that was finicky even on a directly wired setup and it took ages to even unpair) Devices not where I think they are - behind switchplate - I've already found a few by moving the HC3 closer to the ceiling or pulling a downlight out and seeing a Fibaro device come trailing behind it Connected to S2 instead of S1 by lazy sparkies (possible, unverified) Devices behind brick external walls/internal insulation, and now part of a much populated HC2 network I plan to wait for a dry/cooler day (aussie summer) to trapse my HC3 around the house to likely candidate points, but it would be easier if I could rely on extenders, a secondary controller (Aeotec Gen 7 with Silicon Labs PC controller*), or even just find the devices myself withmy Aeotec Gen 5 stick, running as a sniffer might be a better approach. My questions are: Would a sniffer on a USB stick (small, internal antenna) be of any use to try to triangulate the device's location? (I was thinking to monitor the RSSI or something) If so, does an excluded/factory fresh device send any z wave signals when interacted with via S1 switches? (I have at least one that is now excluded but still in an unknown location with an unresponsive triple click) Do exclusions get passed and processed network wide? Or only in direct range of controller? The 'remove' function lacks an NWI flag. I have added some extenders in the general areas I am having issues, without much change. Can exclusions and inclusions get passedand processed by a secondary controller? If so, do you need to run the process on the secondary (in my case through Silicon labs PC Controller),or start the exclusion on the HC3 and trust the secondary will mediate? Would powering down my HC2, Zniffer, Secondary controller make it easier for the HC3 to find devices through a normal include? *Not sure if relevant, but: All of these 'can't exclude' devices are functioning fine on the HC2 network, though I know each one I exclude changes and limits the mess on that network. I am running Engine v 3 on the HC3. None of the diminishing HC2 networking are security connected, but pretty much all of the HC3 network has been included as S0 or S1. The 700 series controller is behaving a bit odd as a secondary for the HC3 compared to the HC2. It's definitely getting included, finding devices etc, but any mapping and node tracing functions seem to get null results or error out. (the standard APIs also get nulls when tracing last route on the HC3 - I need to use the new engine API to get those details....but I didn't think the silicon labs devices would know/care about that?