Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Quick Apps

The category contains Quick Apps submitted by users.
Downloading and submission terms have to be accepted.

Quick Apps have to be described properly, screen shots are optional.
Support topics are created automatically here Quick Apps

Report topics and files that are no longer supported by authors.
All the files submitted have to be approved by administrators.

11 files

  1. HC3: All-in-One QA

    AOQ can control any other Fibaro system HC3, HC2, HCL (master/slave concept) Before migrating your devices to HC3, AOQ could be the solution to make it smooth and simple.
    If you've found yourself with too many Lua and Block scenes and need more automation, this QA is the right solution for you.
    The QA is designated to control and monitor your home system. QA automatically identifies the type of elements in the system. (Z-wave device, Nice, QA device, scene, automatic scene (Block and Lua). Any valid Z-wave,Nice and QA devices property and their values could be monitored, controlled and execute commands accordingly
    AOQ supports custom events, active profile setup and controls alarm zones while every breached zone or sensor in the zone could be identified and execute actions accordingly.
     
    The first time you use All-in-One QA, jM {} hash table must be defined. Each line in the table has two mandatory and two optional fields.
    jM={ {      15,              "137|630",       {timeSlot={“12:00~18:00”},state="value=true",     trueAct={“|230|”, “turnOn”,””}}}   }
               Time span      IDs list                                   Criteria & Rules                                               Action tables
     
    Time span   a period of time (in minutes) within which some activity must be performed by device or scene. Additional two options could be defined:
    time span = 0   defines the line as activity only. time span = ‘negative number’   line is suspended (remarked) IDs list   given list of devices/scenes/QA/global/keywords. Use under score for scene IDs. (“_45”).
    global variable – add an ampersand sign & to System, QA and Local variable names: &varName keyword – add a dollar sign $ to keyword variable: $name Note: To use & and $ characters for other purpose , add % after the character.
    Criteria & Rules  (optional) property, state, time slot, active rules…
    Action tables      (optional) tables of commands to be executed.
     
    To avoid using device IDs  jS2n{} array could be defined. If device ID changed because of re-inclusion it requires to change ID in one place only.
    for example:
    jS2n= {boiler=137, dryer=630, light=230} device name must be included within back apostrophe sign in jM{} hash table.
    Now jM{} hash table above will look like that:
    jM={ { 15,  "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true",     trueAct={“`light`”, “turnOn”,””}}}   }
     
    1. Monitor option
    Some time the scenes or QA devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong.  The monitor option will send an alert in case of defined states are timed out.
    Example to set watchdog timer for devices, scenes, QA devices, global variables and keywords
    jM={     
    {8, "_17|_545",{timeSlot=”10:00~22:00”}},  -- within every 8 min.  between 10am to 10pm, scenes 17, 545 must be active. If not alert sent.
    {3,"134|618|_556|_588"},  -- within  every 3 min. devices 134,618 and scenes 556,588 must be active. If not auto-alert sent.
    {10,”132|145”,{property=”power”}}, -- within every 10 min. devices in list must to report new power value. If not auto-alert sent.
    {30,”470”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent.
    {20,”&HomeStatus|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent.
     
    2. Control option
    Execute actions based on device state, status or value changes. QA supports option like on-line calculations, time modifications, IF THEN and WHEN THEN statements and other features for fully home automation just with one QA (which even doesn’t trigger by the system). 
    Following action tables are available:
    trueAct{} - executed when state status is true. falseAct{} - executed when state status is false. trigAct{} - executed on every value change at any mode, true or false timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true. timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately. InitAct{} - Set of specific actions to be executed on startup only. errAct{} - Set of specific actions to be executed if verification failed. okAct{} - Set of specific actions to be executed if verification succeded.  
    Here is an example of most common scenario, to turn on light when motion sensor breached and turn off light when sensor back to safe after few minutes (3 min. in this example)
    jM={0,”`mSensor`”,{state=”value=true”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}}
    Since no need to turn on light during the day, timeslot could be defined
    jM={0,”`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}}
    But now could be an issue to turn off the light, if sensor breached few seconds before end of timeslot and back to safe is out of defined time slot, falseAct{} won’t be executed. In this case, turning light off action should be part of trueAct{} table
    jM={0,"`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={{“`lightSw`”,”turnOn”,””},{“`lightSw`”,”turnOff”,”180”}}}
    Z-wave devices, global variables and keywords could be defined at several lines (no limit). Scene could be defined one time only.
    For more details please download
    AOQ Advanced User’s Guide - complete instructions and information
    AOQ Quick Guide – syntax format reference and examples
    AOQ HC-WebEye Viewer – AOQ browser viewer guide
     
     QA Advantages:
     
    Debug window view:
    On the first run follow information will be displayed at debugger 
    During normal operation every executed command showed at debugger.
    following data shown for every command:
    jM line number: device name: state value and status by color (green - true  |  pink - false); command executed.
    The debug information has special tag "AOQ<QA-ID>" and "TRACE" / "WARNING" / "ERROR" type for filtering.
    AOQ table preview:
     
    Table's header includes:
    startup time stamp, script current version, scene Name, LED as displayed at HC3 front panel, sunrise/set hours. Current home mode (@home or @vacation) System's current profile mode. Elapsed time Total Z-wave events Min, average and max Z-traffic Table columns are:
    Type – device type (Z.Device, G. Variable, Keyword, QA, luaScene, blockScene). ID: Description – room name: device ID: device name. Z-wave devices sorted by rooms, then by device ID. Battery capable device have green background according to current battery level. If device included in alarm circle icon appears before name. green circle - armed, red circle - breached Value – items current value. Criteria – state of evaluation to determine true or false status. If formula included, the state displayed on green background. in State– elapsed time since last status change. Alert – by default this column isn’t shown. If any devices have been alerted the column will be shown. Please notice that in some cases the device could be alerted, but after while it could back to normal activity. For example, if motion sensor is breached over specified time-span, alert notification will be sent. But after a while the sensor back to safe and alert is canceled, “back to normal” notification will be sent.  At header of alert column shown current number of alerts Time Span – time span to monitor state of items. If time span set to 0, then this line acts as activity, no timeout alerts reported. If time span set to negative number, this line is suspended and no actions executed. Time Slot – Time slot range to execute related actions. Timestamp to execute specific action at specific time. Active (in range) time slot shown in green fonts. trueAct – list of actions to execute when the state is true. falseAct – list of actions to execute when the state is true. trigAct – list of actions when the value changes timeoutAct – list of actions to execute when time-span reached.  Timer will be restarted when device state changed again to true. timeLoopAct – list of actions to execute when time-span reached.  Timer restarted immediately after actions table executions. initAct – list of actions to execute on QA startup. Active Rules – non default defined rules (initOnStartup, Vacation, timeSpanOn, onClock, lineState, trigAll) jM{#} - line number in jM{} hash table jM{ hash table line} – shows device location in jM{} hash table.  
    At the bottom of the table two execution lines show:
    list of up to 60 last executed actions (in order of execution) are displayed. (like CNN news line). list of delayed commands to be executed (and time left to execute)  
    All global variables, their values and last modification time shows below the table.
     

    1,608 downloads

       (1 review)

    6 comments

    Updated

  2. Slaves for HC3

    Those QuickApps intend to use as a slave devices on HC3 to emulate original devices on HC2/HCL or secondary HC3.
    The main purpose is to emulate devices of HC2 controller to create same environment on HC3 before migrating the devices. You can use these devices as standard HC3 devices in Lua, block scenes and QuickApp (triggers and control). After migration you just need to delete slaves and change device IDs in code. To make it easy, recommended to use json Home Table.
    In addition if you intend to keep HC2 or HCL as part of your Home Automation, these slaves provide an option to run your system on HC3 only.
    You can expand your HCL usage by using Lua, block scenes and QA on HC3 to control and monitor devices on HCL.
    Please use slaves according to device functionality. For sensors use SlaveSensor, for dimmers use SlaveDimmer, for RGBW dimmers use SlaveColor or SlaveColorW (option to change white level).
    It's very important to use correct KeyFob slave (sceneActivation or central Scene)
    After downloading the QA, open user_data file and enter credentials, IP and device ID. slaveRate value is in milliseconds and  determines the time rate to fetch the data from original device.
    For example if device on HC2 turned ON, within 700 milliseconds the slave device on HC3 will be turned ON also
     
    Every slave device has an option to stop/start emulation by pressing toggle button .
     

    472 downloads

       (3 reviews)

    0 comments

    Updated

  3. ChildrenOfHue

    It's a "simple" QA that relies on the QuickAppChildren to realise the Hue devices.
    This means that the user interfaces are limited to what are supported by the child app classes.
    Supported Hue device classes:
     
    ZLLSwitch.
    Hue switch with 4 buttons. Creates centralSceneEvents similar to a Fibaro keyFob (com.fibaro.remoteController)
    The interpretation is
         keyId = hueKeyValue // 1000
         keyAttribute = ({"Pressed","HeldDown","Released","Released"})[hueKeyValue % 1000 +1]
    It also supports setValue('value',value) to simulate a key press.
     
    ZLLTemperature.
    Hue temperature sensor. Behaves like a standard fibaro.com.temperatureSensor.
     
    ZLLLightLevel.
    Hue light sensor. Behaves like a standard fibaro.com.lightSensor.
    The device quickAppVariables  'daylight' and 'dark' is updated with resp. Hue attribute.
     
    ZLLPresence
    Hue presence sensor. Behaves like a standard fibaro.com.motionSensor.
     
    Extended color light
    Hue RGB light. Behaves like a fibaro.com.philipsHueLight.
    supports:
    fibaro.call(<id>,"turnOn")
    fibaro.call(<id>,"turnOff")
    fibaro.call(<id>,"toggle")
    fibaro.call(<id>,"setValue",value)                   -- dim value 0..100
       If the value is a table the value is sent directly to the Hue light as a Hue property table. 
      Ex. fibaro.call(<id>,"setValue",{effect='colorloop',bri=50})
            fibaro.call(<id>,"setValue",{startup={customsettings={xy={0.73500005089041,0.26499994910959}}}})
    fibaro.call(<id>,"setColor",red, green,blue).  -- color 0..255
    fibaro.call(<id>,"changeBrightness")             -- brightness 0..255
    fibaro.call(<id>,"changeHue")                        -- 0..65535
    fibaro.call(<id>,"changeSaturation")              -- 0..255
    fibaro.call(<id>,"startLevelIncrease")
    fibaro.call(<id>,"startLevelDecrease")
    fibaro.call(<id>,"stopLevelChange")
    fibaro.call(<id>,"toggleDim",<boolean>) -- Toggle dim direction. true with 'stop'
    The device quickAppVariable  'state' is updated with the Hue state
     
    Dimmable light
    Hue dimmable white light. Behaves like a fibaro.com.multilevelSwitch.
    supports:
    fibaro.call(<id>,"turnOn")
    fibaro.call(<id>,"turnOff")
    fibaro.call(<id>,"toggle")
    fibaro.call(<id>,"setValue",value)                   --- dim value 0..100
       If the value is a table the value is sent directly to the Hue light as a Hue property table. 
    fibaro.call(<id>,"changeBrightness")             -- brightness 0..255
    fibaro.call(<id>,"startLevelIncrease")
    fibaro.call(<id>,"startLevelDecrease")
    fibaro.call(<id>,"stopLevelChange")
    fibaro.call(<id>,"toggleDim",<boolean>) -- Toggle dim direction. true with 'stop'
    The device quickAppVariable  'state' is updated with the Hue state
     
    Color temperature light
    Mapped as a Dimmable light
     
    Color light
    Hue color light. Behaves like a fibaro.com.colorController.
    supports:
    fibaro.call(<id>,"turnOn")
    fibaro.call(<id>,"turnOff")
    fibaro.call(<id>,"toggle")
    fibaro.call(<id>,"setValue",value)                   --- dim value 0..100
       If the value is a table the value is sent directly to the Hue light as a Hue property table. 
    fibaro.call(<id>,"setColor",red, green,blue).  -- color 0..255
    fibaro.call(<id>,"changeBrightness")             -- brightness 0..255
    fibaro.call(<id>,"startLevelIncrease")
    fibaro.call(<id>,"startLevelDecrease")
    fibaro.call(<id>,"stopLevelChange")
    The device quickAppVariable  'state' is updated with the Hue state
    fibaro.call(<id>,"toggleDim",<boolean>) -- Toggle dim direction. true with 'stop'
     
    Room
    Hue light group. 
    Behaves like a fibaro.com.multilevelSwitch.
    fibaro.call(<id>,"turnOn")
    fibaro.call(<id>,"turnOff")
    fibaro.call(<id>,"toggle")
    fibaro.call(<id>,"setValue",value)                   --- dim value 0..100
       If the value is a table the value is sent directly to the Hue group as a Hue property table. 
    fibaro.call(<id>,"changeBrightness")             -- brightness 0..255
    fibaro.call(<id>,"startLevelIncrease")
    fibaro.call(<id>,"startLevelDecrease")
    fibaro.call(<id>,"stopLevelChange")
    fibaro.call(<id>,"setScene",<Hue scene ID or scene name>)
    fibaro.call(<id>,"toggleDim",<boolean>) -- Toggle dim direction. true with 'stop'
     
    Hue CLIPS devices
    CLIPPresence          => com.fibaro.motionSensor          class='ZLLPresence'
    CLIPTemperature.   => com.fibaro.temperatureSensor class='ZLLTemperature'
    CLIPPressure           => com.fibaro.binarySwitch           class='BinarySwitch'
    CLIPHumidity           => com.fibaro.humiditySensor.      class='Humidity'
    CLIPOpenClose.      => com.fibaro.binarySensor.          class='BinarySensor'
     
     
    The startLevelIncrease, startLevelDecrease, and stopLevelChange makes it possible to bind a remote controller that support centralSceneEvent to dim when a button is held down and stop dimming when the button is released.
     
    The lights store their Hue values in a quickAppVariable 'state'.
    This can be retrieved like below and ex. used to set default startup values for Hue lights...
    local function getVar(id,name)   local vars = api.get("/devices/"..id).properties.quickAppVariables or {}   for _,v in ipairs(vars) do     if v.name==name then return v.value end   end end function QuickApp:main()    state = getVar(1435,"state") -- retrieve current color fibaro.call(1435,{startup={customsettings={xy=state.xy}}) -- set as default startup end  

    96 downloads

       (0 reviews)

    3 comments

    Submitted

  4. RFID Programmer (extension should be .fqa not lua)

    This is a small QuickApp that will allow you to programme the Zipato RFID reader whist Fibaro sort out HC3 to do this.
     
    Put you details in the Variables section and then click TagID Push or Pin Push
     
     

    93 downloads

       (0 reviews)

    0 comments

    Submitted

  5. Sonos API Player QA standalone

    Sonos API Player standalone
     
    INTRODUCTION
    Sonos is the ultimate wireless home sound system that brings brilliant sound to all parts of house, room by room. Sonos API Player QA enables Fibaro Home Center 3 to control Sonos Wi-Fi multi-room speakers and show their status using node-sonos-http-api as mediator between Sonos and Fibaro.
     
    PREREQUISITES
    Fibaro Home Center 3, HC3L or Yubii Home with firmware 5.070 or greater
    Node.js capable device such as Raspberry PI with installed jishi node-sonos-http-api
    One or more Sonos Wi-Fi multi-room speaker
     
    FEATURES
    Support for My Sonos stations and playlists. User can easily get list of My Sonos stations and playlist to QA and start playing from QA or other QA and scene code Support for grouping actions join and leave Support for Spotify, Apple Music and Amazon music Support for text to speech TTS for Google, VoiceRSS and AWS Poly Support for playing clips for e.g. doorbell or alarm functions Supports all standard audio commands PLAY, PAUSE, STOP, PREVIOUS, NEXT, MUTE/UNMUTE, SHUFFLE, REPEAT and CROSSFADE Support for all other functions available by jishi node-sonos-http-api User can restart QA device Debug mode with different levels
    Multi language support with 25 languages included (see APPENDIX 1 for the list). QA can use HC3 selected language or user can select any other available language. QA will be automatically translated to the selected language
    User can also setup icons to show current status of the player or leave HC3 default icon  
    INSTALLATION
    Please check provided User Manual
     
    UPGRADE
    To upgrade from version 1.0 to 1.1 please download this file: Sonos API Player QA v1.1 update.zip Unzip it and copy/paste code for each file as named main, common and app
    After saving QA please change settings of QA variables TTSlanguage and/or TTSvoice as necessary.
     
    AVAILABLE DOWNLOAD
    Sonos API Player QA v1.1 User manual EN v1.1  
    TERMS AND CONDITIONS
    Permission to use, copy, modify and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement is hereby granted, provided that the copyright notice, with "Terms and conditions" and "Disclaimer" appear in all copies, modifications and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author.
     
    DISCLAIMER
    This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
    Fibar Group S.A. and their employees are not responsible for support of the ABC VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required.
     
    VERSION HISTORY
    1.1.0 - corrected say and sayall commands language handling error, added Korean language for QA and changed TTS language handling to enable usage of all available languages by selected TTS service. 1.0.0 - First public release  
    Look and feel:
    Enjoy coding and your new Sonos API Player QA!
    Sankotronic

    113 downloads

       (1 review)

    0 comments

    Updated

  6. Netatmo Weather QA

    QuickApp module to integrate of Netatmo Weather devices.
     
    It has support for Main module, Outdoor modules and Indoor modules, Rain gauge and Smart anemometer. It creates child devices (Temperature Sensors, Humidity Sensors, CO2 Sensors, Pressure Sensors, Noise sensors, Rain and Wind sensors) automatically based on information gathered from Netatmo API.
     
    To use it you need to import attached .fqa file into HC3 and provide credentials from Netatmo:
    username - username for your account on Netatmo password - password for account on Netatmo client_id - can be generated at dev.netatmo.com client_secret - can be generated at dev.netatmo.com battery_allone - can be "true" or "false" - to choose between battery interface on dedicated child devices or directly on child devices  
    These values are in "Variables" tab on imported device. Click on Pencil, enter data for that four variables and click "Save". After that you need to create child devices. To do that you have to go to the "Edit & Preview" tab and click on "Get Devices" button.
    If credentials are ok after few seconds you should have created all linked devices for found Netatmo modules. Values for these devices are refreshed every 10s after values updated in Netatmo cloud (more or less at 10min period). QA also has a "Get Measurements" button to manually refresh data.
     
    Important note: 5.030 or newer firmware version on HC3 is needed.
     
    Changelog:
    v2.5.1 - 03/2021 (GSmart+Lazer)
    FIX QuickApp hang after HC3's upgrade to 5.063 firmware Added Czech translation (thanks to petrkl12) Minor fixes & enhancements v2.5 - 07/2020 (Lazer)
    Fix QuickApp crash in case weather station has no additional module v2.4 - 07/2020 (Lazer)
    Add variable to choose between battery interface on dedicated child devices or directly on child devices v2.3 - 06/2020 (Lazer)
    New device types (Rain, Wind, Gust) Add battery levels monitoring (use dedicated child devices) Add alive module monitoring (use Netatmo reachable property to make Fibaro devices appearing dead in the interface) Optimized 10 minutes query interval 10s after Netatmo cloud update Minor fixes & enhancements v2.2 - 06/2020 (GSmart)
    FIX: prevent crash when we doesn't get any data from Netatmo API Added status info on main QA device v2.1 - 05/2020 (GSmart)
    Added support for unit conversion, eg. km/h to m/s Further enhancements in code v2.0 - 04/2020 (GSmart)
    Completely redesigned Getting all data in one request to Netatmo API v1.1 - 04/2020 (GSmart)
    Added support for Wind and Rain modules v1.0 - 04/2020 (GSmart)
    Initial release Supported devices: Base station, Outdoor module, Indoor module

    49 downloads

       (0 reviews)

    0 comments

    Submitted

  7. Synology Switch

    Synology Switch
     
     
    Here is my Quick app for turning off synology nas with the hc3, and using wol (wake on lan for waking it up again)
     
     
     
    First you have to enable wol on your synology nas
     
    What it does:
    It uses code user agents for optaining the servers sid for logging into the server and power down.
     
    Synology api
     
     
    Setup:
    After installing the quickapp, put in your varibles in the varibles window for your nas server in the varible window ,except mac adress, then save.
     
    In this first version you have to put you mac adress as hex int the code window, then save.
    that will be fixed in next version.
    See screen shot what text to search for and replace for putting in your mac address.
     
    Last words:
    test and enjoy.
     
     
    Changelog:
    1.0.0 version is for DSM 6.x
    1.0.1 version is for DSM 7.x 
     

    28 downloads

       (0 reviews)

    0 comments

    Updated

  8. Panasonic comfort Cloud

    Panasonic comfort Cloud app
     
    What it does:
    Control you Panasonic comfort cloud compatible heat pump devices.
    just like the android or apple app, but from you home center 3
    Comfort Cloud
     
     
    installation:
    Upload the quick app to the hc3.
    Go to the variable panel and change the email and password.
    Wait a coble off second then press on button.
     

     
     
    Variable settings:
    for setting start temperature in the aircon modes.

     
    WARNING!!
    Do not set it to a number that larger or smaller than you Panasonic is capable of.
    so do not set cooling start temp to 5 degrees when minimum is 15
    or heat to 65 degrees when max is 30, you get the point.
     
     
     
    Extra fun stuff:
     
    Since there is a thermometer in the inside & outside unit,
    i added two global variables that you can use in other apps
    GlobalVariable('inside heatpump temperature') GlobalVariable('Outside heatpump') Added a function for retrieving energy and more for.
    it can be viewed via the debug buttons.
    located in Oninit and use function QuickApp:getHis()
    Plan is to make a app that just shows energy data and more.
     
     
    Troubleshoot:
    it is crucial that app retrieve token before app runs.
    i have very fast internet 
    so could be that with slow internet that timers have to be adjusted up.
    located in Oninit 
     
    important that they execute in that order!
    fibaro.setTimeout(1500, function() QuickApp:turn1()() end) --token first fibaro.setTimeout(3000, function() QuickApp:turn2() end) --when we got token we can run the rest. fibaro.setTimeout(604800000, function() QuickApp:onInit() end) --token restart every month  
    Full Code on my Github page:
    Code
     
     
    Last words:
    Damn this was hard to make when never haven writing Lua before.
    Enjoy!
     
     

    18 downloads

       (0 reviews)

    0 comments

    Updated

  9. Onkyo 2021-06-23.fqa

    About This File
    Onkyo QuickApp
     
    INTRODUCTION
    Onkyo has a range of network connected Audio/Video receivers that can be controlled via a network UTP connection. This QuickApp provides basic control of the A/V receiver. 
    Tested on an Onkyo TX-NR616. 
    QuickApp should be easy to adapt to other models if required. 
     
    This is my first QuickApp, any suggestion to make it better highly appreciated. 
     
    PREREQUISITES
    Tested on Fibaro Home Center HC3L and Yubii Home with firmware 5.071.52
    An Onkyo AV Receiver  
     
    FEATURES
    Basic On/Off Volume Control Mute On/Off toggle switch 8 Input selectors, label can be customised using variables 4 Listening Modes On/off line status indicator  
    INSTALLATION
    Please check provided User Manual.
    Upload file in the device section. 
     
    AVAILABLE DOWNLOAD
    Onkyo 2021-06-23.fqa Icons - found on the forum and slightly adapted  
    TERMS AND CONDITIONS
    Permission to use, copy, modify and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement is hereby granted, provided that the copyright notice, with "Terms and conditions" and "Disclaimer" appear in all copies, modifications and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author.
     
    DISCLAIMER
    This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.
    Fibar Group S.A. and their employees are not responsible for support of the ABC VD. 
     
    VERSION HISTORY
    1.0.2 - First public release

    32 downloads

       (0 reviews)

    0 comments

    Submitted

  10. QA-Marantz.fqa

    Marantz Remote
     
     
     
    I have adapted the French Denon remote app from french forum to Marantz.
    French Forum
     
    Added bunch of stuff from the attached protocoll.
     
    Added Eco mode On/Off
    Added 11 more Surround sound modes
    Added 10 Sources
     
     
    Upload and edit ip varible to get it working.
    The rest of the varibles should not be changed.
    You can customize the sources buttons names in the edit panel.
     
    If you wanna check code before downloading, you can also visit my repo for this
    Github HC3_Quickapp_Marantz
     

    42 downloads

       (0 reviews)

    0 comments

    Updated

  11. Remote All-in-One

    Contributions & credits @jgab  - fibaroapiHC3.lua (SDK for remote and offline HC3 development)
    @10der - Visual Studio LUA environment.
     
    AOR can control any Fibaro system HC3, HC2, HCL, HC3L, Yubii from your PC using ZeroBrane or Visual Studio Code editors.
    You can use full LUA 5.3  libraries, read/write files, run programs on your PC, to integrate other systems using your own LUA functions.
    HCL users finally can use LUA to control their system without block scenes and limited Virtual devices.
     
    No need to migrate devices or to use master/slave configuration.
     
    Download AOR_ZB.txt (zip) file for ZeroBrane
    Download AOR_VS.txt (zip) file for Microsoft Visual studio
    After download, change the file extension to .zip and extract the file.
     
    By default AOR supports Text-To-Speech on your PC speakers, use it to be alerted on any event you would  like to monitor and to be aware about.
     
    The AOR designated to control and monitor devices across your Fibaro controllers. AOR automatically identifies the type of elements in the systems. (Z-wave device, Nice, QA device, scene, automatic scene (Block and Lua), global variables. Any valid Z-wave,Nice and QA devices property and their values could be monitored, controlled and execute commands accordingly
    AOR supports custom events, active profile setup and controls alarm zones while every breached zone or sensor in the zone could be identified and execute actions accordingly.
    All above executed with no extra load on controllers CPU or RAM... just keep your PC out of sleep mode...
     
    As an example:
    The first time you use All-in-One, jM {} hash table must be defined. Each line in the table has two mandatory and two optional fields.
    jM={ {      15,              "137|630",       {timeSlot={“12:00~18:00”},state="value=true",     trueAct={“|230|”, “turnOn”,””}}}   }
               Time span      IDs list                                   Criteria & Rules                                               Action tables
     
    Time span   a period of time (in minutes) within which some activity must be performed by device or scene. Additional two options could be defined:
    time span = 0   defines the line as activity only.
    time span = ‘negative number’   line is suspended (remarked)
    IDs list   given list of devices/scenes/QA/global/keywords. Use under score for scene IDs. (“_45”).
    global variable – add an ampersand sign & to System, QA and Local variable names: &varName
    keyword – add a dollar sign $ to keyword variable: $name
    Note: To use & and $ characters for other purpose , add % after the character.
    Criteria & Rules  (optional) property, state, time slot, active rules…
    Action tables      (optional) tables of commands to be executed.
     
    To avoid using device IDs  jS2n{} array could be defined. If device ID changed because of re-inclusion it requires to change ID in one place only.
    for example:
    jS2n= {boiler=137'hc3, dryer=630'hc2, light=230'hcl} device name must be included within back apostrophe sign in jM{} hash table.
    Now jM{} hash table above will look like that:
    jM={ { 15,  "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true",     trueAct={“`light`”, “turnOn”,””}}}   }
     
    1. Monitor option
    Some time the scenes,QA and Virtual devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong.  The monitor option will send an alert in case of defined states are timed out.
    Example to set watchdog timer for devices, scenes, QA devices, global variables and keywords
    jM={     
    {8, "_17'hc3|_545'hcl",{timeSlot=”10:00~22:00”}},  -- within every 8 min.  between 10am to 10pm, scenes 17, 545 must be active. If not alert sent.
    {3,"134'hc2|618'hcl|_556'hc3|_588'yubii"},  -- within  every 3 min. devices  in the list and scenes  must be active. If not auto-alert sent.
    {10,”132'hcl|145'hc2”,{property=”power”}}, -- within every 10 min. devices in the list must to report new power value. If not auto-alert sent.
    {30,”470'hc3”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent.
    {20,”&HomeStatus'hcl|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent.
     
    2. Control option
    Execute actions based on device state, status or value changes at any controller and execute actions on others. AOR supports on-line calculations, time modifications, IF THEN and WHEN THEN statements and other features for fully home automation just with one program on your PC (which even doesn’t load the controllers). 
    Following action tables are available:
    trueAct{} - executed when state status is true.
    falseAct{} - executed when state status is false.
    trigAct{} - executed on every value change at any mode, true or false
    timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true.
    timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately.
    InitAct{} - Set of specific actions to be executed on startup only.
    errAct{} - Set of specific actions to be executed if verification failed.
    okAct{} - Set of specific actions to be executed if verification succeded.
     
    Here is an example when motion sensor breached on HC3, turn ON lights in HCL and turn off the light 3 minutes after sensor back to safe.
     
    jM={”150'hc3”,{state=”value=true”,trueAct={“120'hcl”,”turnOn”,””},falseAct={“120'hcl`”,”turnOff”,”180”}}}
     
    3. User LUA function execution
    When device 150 on HC3 breached or goes back to safe run foo function and pass the value as an argument
    jM={"150'hc3", {state="true", trueAct={"foo",  "runFunc, @$id>value"}, falseAct={"foo",  "runFunc, @$id>value"}}},
     
    in user_func.lua file the foo function would look like:
     
    function foo(value)
    if value=="true" then
    ...
    elseif value=="false" then
    ...
    end
    end
     
    For more details please download
    AOR Installation
    AOR Advanced User’s Guide - complete instructions and information
    AOR Quick Reference Guide – syntax format reference and examples
    AOR User functions – write your own code.
    GPS User Guide - location functionality
     
    Microsoft Visual Studio debug console
     
     
    ZeroBrane console output
     
    Web view
     

    54 downloads

       (0 reviews)

    0 comments

    Updated


×
×
  • Create New...