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


Search the Community

Showing results for tags 'quickapp'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

  1. This QuickApp reads the PM1, PM2.5, PM4, PM10, Temperature, Humidity and Air Pressure (and calculated absolute Humidity) values directly from a sensor. With this sensor you can measure air quality yourself. This QuickApp will send notifications when PM2.5 or PM10 readings reach a breakpoint. The Air Quality sensor is a DIY setup for less than 50 euro. It is very easy to assemble and ready to make kits are available, see also https://sensor.community/en/sensors/airrohr/ for more info. You can order seperate items from for example AliExpress for the lowest prices, or order a complete set from: https://nettigo.eu/products/sensor-community-kit-sds011-bme280-english-language or https://www.tinytronics.nl/shop/nl/luchtwachters-delft-maak-zelf-een-fijnstofmeter-workshop-kit The Air Quality Sensor has a WiFi interface and Application Programming Interface (API). This QuickApp uses the API to get the measurements available to the Fibaro Homecenter. Changes version 1.2 (11th April 2021) Added support (child devices) for PM1 and PM4 levels (Plantower and Sensirion sensors) Added support for BMP280 sensor Changes version 1.1 (31th Januari 2021) Added support for Plantower Air Quality Sensor (for now without PM1.0) Added Airpressuretext to log of Child Device Airpressure Added Quickapp variable for debug level (1=some, 2=few, 3=all). Recommended default value is 1. Removed QuickApp Variable bme280Sensor (no need for that anymore, works without it) Removed QuickApp Variable path (is now fixed) Changes version 1.0 (23rd January 2021) Added Child Device for Absolute Humidity Added "Refresh" button Changes version 0.5 (23rd October) With the new firmware and API function, solved a small bug in presenting WiFi dBm Changed humidity and air pressure values to zero decimals Added air pressure unit text "hPa" Changed the master device to "Generic Device" Added QuickApp Variable for user defined icon master device Solved a bug preventing creation of QuickApp Variable bme280Sensor Changes version 0.4 (17th October 2020) Added support for BME280 sensor (temperature, humidity and air pressure) Added QuickApp Variable bme280Sensor (true or false) to indicate the presence of a BME280 sensor otherwise a DHT22 sensor is assumed Reduced the amount of labels, now only one label Removed the firmware version from the log under the icon Changes version 0.3 Error message instead of debug message in case of an error Changed method of adding QuickApp variables, so they can be edited Added network error to log (under icon) Changes version 0.2 Changed label6 from "age" to time of the measurement Added automatic creation of child devices for Temperature, Humidity, PM2.5 and PM10 (with great help from @jgab from forum.fibaro.com) Added the value (Temperature, Humidity, PM2.5 and PM10) to the child devices, This can be used in, for instance, extra scenes and shows in the mobile app and dashboard. Added a short text of the air quality (GOOD, SATISFACTORY, etc.) to the icons in the dashboard (with great help of @petergebruers and @10der from forum.fibaro.com) Added the trend (up, down, equal) to the sort text of the air quality My configuration of the DIY air quality sensor: Nova SDS011 air quality sensor NodeMCU ESP8266 V2 opensource WiFi board BME280 temperature, humidity and air pressure sensor See how to simply assemble the air quality sensor yourself: https://sensor.community/en/sensors/airrohr/ See for general informatie about the Air Quality Sensor: https://luftdaten.info See for a map of measurements: https://sensor.community/en/ See for CVS files: https://archive.luftdaten.info See for sources: https://github.com/opendata-stuttgart/ QuickApp variables (mandatory, they will be automatically added with the default values): IPaddress = IP address of your sensor Path = Path behind the IP address, normally /data.json Interval = Number in seconds, the sensor normally is updated every 145 seconds UserID = User id to notify of PM2.5 / PM10 breakpoints bme280Sensor = Use of BME280 temperature, humidity and air pressure sensor, true or false PM2.5 breakpoints 0 - 30 GOOD (Minimal) 31 - 60 SATISFACTORY (Minor breathing discomfort to sensitive people) 61 - 90 MODERATELY POLLUTED Breathing discomfort to asthma patients, elderly and children 91 - 120 POOR (Breathing discomfort to all) 121 - 250 VERY POOR (Respiratory illness on prolonged exposure) 250+ SEVERE (Health impact even on light physical work. Serious impact on people with heart/lung disease) PM10 breakpoints 0 - 50 GOOD (Minimal) 51 - 100 SATISFACTORY (Minor breathing discomport to sensitive people) 101 - 250 MODERATELY POLLUTED Breathing discomfoort to asthma patients, elderly and children 251 - 350 POOR (Breathing discomfort to all) 351 - 430 VERY POOR (Respiratory illness on prolonged exposure) 430+ SEVERE (Health impact even on light physical work. Serious impact on people with heart/lung disease) Download the QuickApp here (download the file and un-zip): https://github.com/GitHub4Eddy/air_quality_sensor/archive/refs/tags/Air_Quality_Sensor_12.zip Or Fibaro Marketplace: https://marketplace.fibaro.com/items/air-quality-sensor How to install: Open the Configuration Interface Go to Settings > Devices Click + Choose Other Device Choose Upload File Choose file from your computer with .fqa
  2. QA for creating HomeTable in global variables in HC3. Why using hometable? Instalation: 1. upload this QA 2. In QA variables you can change name for hometable, name for scenes and time for regular update of hometable 3. In QA -> source files -> ManualData you can add your own data (it will be also saved in final hometable in global variables) How to read data from hometable: -- in case that your name for hometable is default=HomeTable local tbl = fibaro.getGlobalVariable("HomeTable") local HT = json.decode(tbl) -- structure for devices is <room>.<deviceName> local idQA_TV=HT.LivingRoom.TV -- structure for scenes is <ScenesName>.<sceneName> -- default value for <ScenesName> is Scenes local idSc_Lights=HT.Scenes.Lights -- structure for your own inputs from ManualData local myValue1=HT.myData1.myNameValue1 -- 0 local myValue2=HT.myData1.myNameValue2 -- "default value" Names for rooms, devices and scenes are corrected by following replaces: {["%."]="",["-"]="",["%("]="",["%)"]="",["&"]="",[":"]="",["%["]="",["%]"]="",["%+"]="",["%%"]="",["%/"]="",["%$"]=""} {["Á"]="A",["Ä"]="A",["Ą"]="A",["À"]="A",["Â"]="A",["Č"]="C",["Ć"]="C",["Ç"]="C",["Ď"]="D",["É"]="E",["Ě"]="E",["Ë"]="E",["Ę"]="E",["È"]="E",["Ê"]="E",["Í"]="I",["Ï"]="I",["Î"]="I",["Ĺ"]="L",["Ľ"]="L",["Ł"]="L",["Ň"]="N",["Ń"]="N",["Ó"]="O",["Ô"]="O",["Ö"]="O",["Ő"]="O",["Œ"]="O",["Ŕ"]="R",["Ř"]="R", ["Š"]="S",["Ś"]="S",["Ť"]="T",["Ú"]="U",["Ů"]="U",["Ü"]="U",["Ű"]="U",["Ù"]="U",["Û"]="U",["Ý"]="Y",["Ÿ"]="Y",["Ž"]="Z",["Ż"]="Z",["Ź"]="Z",["á"]="a",["ä"]="a",["ą"]="a",["à"]="a",["â"]="a",["č"]="c",["ć"]="c",["ç"]="c",["ď"]="d",["é"]="e",["ě"]="e",["ë"]="e",["ę"]="e",["è"]="e",["ê"]="e",["í"]="i",["ï"]="i",["î"]="i",["ĺ"]="l",["ľ"]="l",["ł"]="l",["ň"]="n",["ń"]="n",["ó"]="o",["ö"]="o",["ô"]="o",["ő"]="o",["œ"]="o",["ř"]="r",["ŕ"]="r",["š"]="s",["ś"]="s",["ť"]="t",["ú"]="u",["ů"]="u",["ü"]="u",["ű"]="u",["ù"]="u",["û"]="u",["ý"]="y",["ÿ"]="y",["ž"]="z",["ż"]="z",["ź"]="z"} Hometable in global variables will be overwrite only if newly generated hometable will be different. Version of QA HomeTable: 0.12 - 21.1.2021 HomeTable.fqa
  3. QA for full control of PC from HC3 (On, Off, Restart, Sleep and Hibernate states) You will need: 1. PC is connected via Fibaro wall plug (or other device with power measurement) 2. installed application Switch Off 3.5.1 from Airytec on your computer http://www.airytec.com/en/switch-off/get.aspx 3. In Switch Off application - go to menu -> Options -> Remote -> Edit web interface settings -> you have to define your port ie. 28100 and password 4. In PC firewall you have to allow Incoming rule for TCP port that you have defined in SwitchOff application ie.28100 5. Working WakeOnLAN (WOL) on your PC (allowed in PC BIOS and on your net card) Installation: 1. Upload this QA to HC3 2. In QA variables you have to define: - PC_DevID : ID of your PC power plug in HC3 - PCAirytecPort: port define for web interface in SwitchOff application from Airytec - PCAirytecPassw: password define for web interface in SwitchOff application from Airytec - PC_IP_Address: IP address of your PC ie. 192.168.1.10 - PC_MacAddress: MacAddress of your PC for WakeOnLAN (WOL) ie. 4B:BC:24:D1:E5:25 - PC_WOL_Port: Port for WakeOnLAN (WOL) - usually 9 - Level<xxx>PC : power in W for showing correct PC state: power >= LevelRunPC PC state: running power >= LevelSleepPC PC state: sleeping power >= LevelHiberPC PC state: hibernating power >= LevelOffPC PC state: off power = 0 PC state: fully off (power>0 to LevelOffPC also means PC state: off) QA PC version: 0.20 - 13.2.2021 PC.fqa
  4. QA for Netio power sockets devices. https://www.netio-products.com/en Tested for NETIO 4All and NETIO 4C Installation: 1. In Netio you have to allow JSON API and setup user and password for READ-WRITE: 2. Name, password and IP address you have to add to Variables in QA and save it. (LoginName=Username, LoginPassword=Password) 3. You can also create child devices for every socket. Netio QA version: 0.50 - 13.2.2021 Netio.fqa NetioIcons.zip
  5. This QuickApp reads the PM2.5, PM10, Temperature, Humidity and Airpressure values directly from a sensor somewhere in this world That sensor doesn't have to be your own sensor, any sensor can be used, just find one in your neighborhood For locating the sensor(ID's) in your neighborhood see: https://sensor.community/en/ Select two (!) SensorID's, one for PM2.5 and PM10 values and one for Temperature, Humidity and Airpressure values The PM2.5, PM10, Temperature, Humidity, Absolute Humidity and Airpressure readings are stored in the value of six (child) devices, so you can read the value from your own scenes This QuickApp will send notifications when PM2.5 or PM10 readings reach a breakpoint (if userID ~= 0) Absolute humidity is the measure of water vapor (moisture) in the air, regardless of temperature. It is expressed as grams of moisture per cubic meter of air (g/m3) See also https://luftdaten.info See also for CVS files: https://archive.luftdaten.info See also https://github.com/opendata-stuttgart/ API documentation: https://github.com/opendata-stuttgart/meta/wiki/EN-APIs QuickApp variables (mandatory, they will be automatically added with the default values): sensorID1 = [number] SensorID for PM2.5 and PM10 values, your own sensor or from someone else, 13463 is an example sensorID2 = [number] SensorID for Temperature, Humidity and Airpressure values, your own sensor or from someone else, 13464 is an example interval = [number] in seconds time to get the sensor data from sensor.community timeout = [number] in seconds for http timeout userID = [number] userID to notify of PM2.5 / PM10 breakpoints debugLevel = [number] Debug logging (1=some, 2=few, 3=all) (default = 1) icon = [numbber] User defined icon number (add the icon via an other device and lookup the number) Version 1.0 (7th February 2021) Added Child Devices for Temperature, Humidity, Absolute Humidity and Airpressure Changed the quickapp variable SensorID to two variables, one for PM values and one for Temperature, Humidity and Airpressure values Added Quickapp variable for debug level (1=some, 2=few, 3=all). Recommended default value is 1. Added QuickApp Variable for user defined icon master device-- Added Airpressure Text in log of Airpressure Child Device Removed QuickApp Variable address, there was no need to change it by user Added values for Temperature, Humidity, Absolute Humidity and Airpressure to the lables Added values for Country, Latitude and Longitude to the labels Added Sensor ID to the log below the value Added "Refresh" button Added extra check for empty data return from Sensor Community Version 0.4 (19th August 2020] Added child devices for PM2.5 and PM10 Added time of measurement, adjusted to your timezone Added Timeout QuickApp variable with high http timeout value to prevent errors Error message instead off debug message in case of an error Changed method of adding QuickApp variables, so they can be edited Version 0.3 (15th June 2020) Link to CVS files added in comment Fixed some typos Fixed breakpoint check 0 - 30 and 0 - 50 notifications Fixed retrieve of json data Version 0.2 (14th June 2020) Link to API documentation added Solved bug / crash: Better selection of the first part of the apiResult Changed some debugging logica Added UserID (mandatory) for sending push notifications Added push notifications based on the PM2.5 and PM10 breakpoints Solved bud / crash if there only was one reading from the api, most of the time there are two readings (last 5 minutes) Version 0.1 (13th June 2020) Initial version Suggestions are welcome. If someone feels the need to improve the QuickApp, you are very welcome. Download the QuickApp here (download the file and un-zip): https://github.com/GitHub4Eddy/sensor_community/archive/sensor_community_1.zip or Fibaro Marketplace: https://marketplace.fibaro.com/items/sensor-community How to install: Open the Configuration Interface Go to Settings > Devices Click + Choose Other Device Choose Upload File Choose file from your computer with .fqa
  6. 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
  7. Hello, Did someone know if its possible to get outside temperature in garden (Tuin) room? I have installed YR weather. Can i do it with a scene or is it not possible? Thanks.
  8. Hello, I found a project who reverse engineered the Wi-Fi protocol from the Mertik controller connected to my fireplace. Yeay! ? With the following (simplified) NodeJS code I can send the standby command to my fireplace: var net = require('net'); const prefix = '0233303330333033303830' var msg = "3136303003"; var packet = Buffer.from(prefix + msg, 'hex'); var client = new net.Socket(); client.connect(2000, '192.168.1.1'); client.write(packet); I know how to open a socket in HC3 QA but I don't get how to convert the message to a RAW buffer. The JavaScript line does it with Buffer.from(prefix + msg, 'hex'); Does some LUA god know how to convert the message in QA LUA for the HC3?
  9. Hi In a Quick App UI i can define a slider. https://manuals.fibaro.com/home-center-3-quick-apps/ function QuickApp:updateViewSample() self:updateView("label1", "text", "Device on") -- updating the text for 'label1'. self:updateView("button1", "text", "on") -- updating the text for 'button1'. self:updateView("slider1", "value", "99") -- updating the text for 'slider1'. end Is there a way to set properties on the slider - if i want to pre-define that that value accepted should be 0-5 ?
  10. Hello, Does anyone already re-made the QuickApp for Siren Gen5? I want to use the different sounds of the Siren like in the HC2 with the VD.
  11. How are y'all updating your QuickApps? If it's just a one instance, it's easy; that's the one I'm working on. But I have my app 7 times in HC3 and going manually over all and copy-pasting new code seems pretty dumb.
  12. Is there a way to get a notification into a QuickApp whenever given devices changes? I.e. register for changes from device ID xyz using callback in "init" method of QuickApp and then when the value changes the callback method will be called. I know I can poll the device every now and then, but polling seems to be waste of resources given a simple callback style programming would solve it nicely.
  13. Locally I can place the current class (self) in a variable and call an Object in this class. This code is working (localy): function QuickApp:onInit() local sender = {value='Yes', class=self} sender.class:localPrintValue(sender.value) end function QuickApp:localPrintValue(value) if value == nil then value = 'No' end self:debug('Can I print this : '..value) end [15.09.2020] [13:22:42] [DEBUG] [QUICKAPP105]: Can I print this : Yes If I send this variable to another class using fibaro.call(id, 'action', variable) , the call disappears into the darkness. Calling the Object in the other class(QuickApp) results in calling the nil value? !!! This next code is (because of the class=self) not working: fibaro.call(qaID,"updateMyProperty", {value=newValue, class=self}) function QuickApp:updateMyProperty (sender) local value = 0 if type(sender) == 'table' then -- Call comes from elsewhere.. value = sender.value self:debug('Device updated from: '..tostring(sender.class.id)..'.'..tostring(sender.class.name)..' with value: '..tostring(value)) else value = sender self:debug('local call, with value: '..tostring(value)) end end This is a pity because I would like to indicate in the called class where the call was coming from. Now I solve this by sending a table with : sender = {id=self.id, name=self.name, value=newValue}. Do I do something wrong? or has Fibaro disabled the oop function for sending object classes?
  14. Hello, I have a problem. After some time, when playing is stopped, Quickapp can't refresh fcPlayerStates and prompts :error fcPlayerStates: "Operation canceled". I'm using your app since 2 weeks or so, and that's the first situation of debug error. Similar situation was appaired when ieast device was disable and disconnected. Bart
  15. I am creating a QA to list doors that are still open when I switch on the alarm. And I want to display the doors that are still open on the QA interface, one below the other. I have been trying to insert a return character in the text to be inserted in the label with self:updateView() in order to achieve a nice list of doors. But whatever I try to insert in the string to be displayed (\n, \r, string.char(13), <br \> etc) the separate lines remain on one line in the label. What is the correct procedure to insert a CR in this case? Or is there an alternative like dynamically adding labels to the QA? Thanks
  16. Is there a way to cancel "callback" scheduled using `setTimeout` in QuickApp? Something like i.e. `clearTimeout` known from JS world? The `setTimeout` does not seem to return a value, but maybe there's some trick.
  17. Hi, I'm new to Fibaro (HC3) and just finding my way around things. I've seen some reference in other forums that Quick Apps (buttons / controls) are not currently available in the Home Center mobile app - is this correct and still the case? Seems like a pretty basic requirement to be able to use Quick Apps doesn't it, or am I missing something? Otherwise, what is the point of them and how do you use them from your mobile other than building individual scenes for each action you want to take with it? Is anyone aware of a mobile app update on the horizon soon which will allow control of Quick Apps from the mobile app UI? Thanks
  18. Hello I wrote a QuickApp for controlling my Sony Bravia TV but I can´t find it in the Android app?
  19. Good evening everyone, .. I'm sending the first "taste" of the upcoming plug-in for iEAST. The purpose is to be able to establish LUA actions on the plugin and control the streamer from HC3 and its elements (tested by scene control from the NodON button). The primary purpose of this "Lite" application is to easily configure 6 Internet radio presets and name them so that a less knowledgeable user does not have to interfere with the code. As a bonus, there is control of this stream player, for example from a DLNA source. By no means does the app have any ambition to replace the original smart app on the phone / tablet. QuckApp is still in the BETA phase. I have test buttons here and some ready-made buttons for future use (master / slave multiroom, etc.). Furthermore, the test buttons "Test" for DEBUG (listing variables and JSON decoded values). I may need to modify the code, so I'll be happy if you test it and possibly send some info. I need to resolve some things about JSON some request. Still a picture, I'm working on the documentation. eM. Edit: Edited image description - Picture with Artist: Unknown, without the URL stream - this is real SLAVE speaker (you can configure from his own APP) - Picture with ERROR - some error with streamer Slave2 (not connected to the LAN) - Picture with Artist: ACDC - Actualy playing music from NAS - playing on the slave1 streamer - Picture with Artist: Unknown - Internet Radio from public stream - playing on the master streamer Configuration point Edit: 20200621 - New look. I'm just finishing the documentation before the release. The FCx3 button is switchable depending on the DEBUG mode. The play/pause button is a toggle switch.
  20. Hi, Would like to have a quickapp that would enable me to start or stop a scene with a button. I tried fibaro.scene("execute", {id}) or fibaro.scene("kill", {id}) But it doesn't work and don't stop and restart the scene. The scene i want to trigger or stop is a move detection in a room to start ligne. I would sometime like this automation not being activated and stop from a QA that is controling all room parameter. thanks for the support
  21. For watering our plants I develop a Virtual Device with HC2 using control buttons to open a valve during 15, 30, 45 and 60sec. I also had a emergency STOP button to close the valve immediately within the same VD. When I reproduce the same with HC3, it is not possible to call the STOP button (interrupt) untill the watering in progress is not completed. Any help? (and not entionning those buttons are not displayed on the portable Android/IOS...)
  22. I am trying to get a list of sections in house, to use in a QA. From my browser I can do a http request like: http://IP_HC3/api/sections to get this list. Is there a way to do this directly with a fibaro function? Can't find anything in the API docs.
  23. I have set a variable for a QuickApp in the web interface. Now I want to retrieve that variable with self:getVariable("varname") It return nil however. How come? What am I doing wrong?
  24. Being completely new to Fibaro (just bought a HC3) but not to domotica and programming I am not able to find the info I need to do the following: Receive a http request from my Synology Surveillance Station telling HC3 that camera movement has occurred and then set a zone to breached and trigger an alarm. I was thinking of creating a QuickApp device of type binary sensor and turn that on with an http GET request from the surveillance station. This part works fine: when I send the request I can catch it in Quickapp:turnOn() Can see that by checking a debug message. But now.... How do I get this device to set the zone to breached? I've tried to test it in a scene, using state "Detected" but that doesn't react to the turnOn. The updateProperty("state", true) or updateProperty("state", "Detected") methods also didn't work. Big problem here is imo the lack of documentation (at least I can't find it) E.g. where can I find a list of properties and built-in methods of the QuickApp class? The page at https://manuals.fibaro.com/home-center-3-quick-apps/ certainly does not contain all these properties and methods, doesn't it? Can anyone point me in the right direction?
×
×
  • Create New...