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 'hc3'.

  • 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. Hi all... I am trying to remove a z-wave device from my HC3. I don't have the device anymore, but when i try to remove it in the menu it goes in to removing menu countdown. I can't push any buttons because i don't have the device anymore. How can i get rid of the device in my home center 3.
  2. 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...
  3. Hi Team, I try to develop some QuickApp on my HC3, but I have an problem with the http request : When I call an API (here switchbot api), the external API respond me an 403 error... The probleme isn't the API because the same request with an little php script works... I have tried much methods but I get only the response code 403. Recently, I have downloaded an quickapp on the marketplace. All review on it are good but for me, it's doesn't work. When I see the console logs, I can see the 403 error code from this downloaded QuickApp too. Do you have an idea for my problem ? You can find my function code here : function QuickApp:GetDeviceList() self.http = net.HTTPClient({timeout=10*1000}) local apikey = self:getVariable("apikey"); self:debug(apikey); --For debug an my token is successfuly loaded local address = "https://api.switch-bot.com/v1.0/devices" --local address = "http://10.0.10.10:1880/debug" self.http:request(address, { options = { headers = { ["Authorization"] = apikey, ["Content-Type"] = "application/json; charset=utf8", ["Accept"] = "application/json", ["User-agent"] = "Mozilla/5.0" --For try but no change }, checkCertificate = false, method = 'POST' }, success = function(response) self:debug(response.status); --return : 403 self:debug(response.data); --return: nothing self:debug(response.headers);--return: array self:debug(message); --return: nil end, }); end
  4. I have 16 Philip Hue lamps in my house being managed from HC3. Last month I changed the connection from using a hue bridge to using the new direct integration with HC3 using Zigbee protocol. I now experience that status of the lamps (on/off intensity and color) is NOT correctly displayed any longer in Yubii and/or HC3 Website. A lamp that I can see physically is turned ON appears in the UX as turned OFF. And if I try to turn it ON it says "Unit XXXX turned ON" but nothing happens in real life. And if I refresh the page the lamp still displays status OFF!! To make things really weird, I can still turn the lamps on/off them from my block scenes. I have rebootet my HC3 and also tried to disable all firewall settings just to be sure. Anyone got a clue on how to troubleshoot this? I can st
  5. zxt-120, does anyone know how to get this working with HC3 running latest software. 5.130.64
  6. Hi Everyone, Newbie here. I have successfully installed a smart implant to control by garage door. It acts as a push button. My problems: 1 - I would like to have the HC3 web interface (or yubi) to display a push (momentary) switch icon instead of a on/off switch icon, is it possible? 2 - I only have a small number of available icons in HC3, for exemple I can select for my smart implant a bulb icon or a siren icon, but not a garage door icon. Is there a way to solve this? 3 - Last but not least, I would like to get information about when the garage door is open and when it is closed, without using any existing hardware. I imagine that it could be possible to have some kind of seen or quick app that would do the following: - set up a variable somewhere called "status" - when switch is activated the first time set status to 1, when it is activated the second time it sets the status to 0, and so on... is there an easy way to do this and get some kind of icon displaying the status of the garage door? Thank you in advance
  7. Cześć, Czy ktoś ma pomysł jak ustawić Aoetec Siren 6 tak, aby alarm nieprzerwanie się powtarzał do momentu rozbrojenia alarmu? Wczoraj miałem naruszenie czujki (na szczęście przez psa) i alarm włączył się tylko na 35s i cisza. Ja się obudziłem, ale reszta domowników już nie. A co jeśli jeden "dzwonek" nas nie obudzi podczas prawdziwego włamania? Jaka jest funkcja w LUA, aby powtarzać czynność do momentu spełnienia określonego warunku. (czy ten kod posiada cos jak elseif ?)
  8. I am sharing my experience with Replacing HC3L connected as slave gateway as there's no clear guide to follow, hoping that someone have solution for it. with many attempts using different approaches, ALL FAILED. Attempt1 - from connect gateways Tab: -clicking on the replace device on the list showing on screenshot, -it asks for new gateway IP, then i got error 409 conflict , or error 409 OK. i have made sure that new gateway on the same firmware 5.130.64 as the one need to be replaced. Attempt2- i made sure that system A/B on new gateway is on 5.130.64 which identical to the one i need to replace, but still getting the same error. Attempt3- i tried to upload the backup of slave gateway manually to new one but it's refusing to upload it. Attempt4- for testing purpose factory reset one salve gateway from the connected list, and started the replace, it completed the process but no devices restored on the gateway... Anyone can help with correct procedure of replacing HC3L connected as slave gateway?
  9. Cześć, Dzisiaj mam problem z dostępem zdalnym do mojej centralki HC3. Niby łączy się ale nie widać większości rzeczy zarówno przez aplikację Yubii jak i przez stronę www. Nie reagują też skróty do scen przy pomocy widgetów. Co prawda jestem teraz w miejscu z bardzo kiepskim dostępem do internetu ale nie wierzę, że do zdalnego dostępu jest potrzebne łącze szybsze niż 20/10 Mbit/s. Chyba, że dzisiaj są ogólne problemy z dostępem z poza sieci lokalnej.
  10. fibaroapiHC3.lua (Note: The new version of the emulator has gone through extensive rewrite and is stabilising (0.300). The old version of the emulator is here fibaroapiHC3_classic.lua.) I'm currently working on a new emulator, TQAE, and have moved all my development to that - please check it out... It's a rewrite with the learnings I have made coding fibaroapiHC3.lua... This is a thread for the fibaroapiHC3.lua sdk that is under development (keeping it separate from the HC3 QuickApps coding - tips and tricks thread) I've started to run and test HC3 QuickApps offline and have made a fibaroapi.lua file that can be included to emulate the fibaro calls and call out to the HC3. This means that a whole QA can be developed offline, debugged and verified before deploying to the HC3. Something that significantly reduces the development process. It's an emulation so it's not 100% but it will cater for 99.99% of the needs to catch bugs, get decent error messages when things doesn't work (like timers). Be able to set breakpoints and inspect states etc. It's complete enough to run the most demanding QuickApps that I have found on the forum so far... If it runs in the emulator and it doesn't run on the HC3 or vice versa I will prioritise to fix it. Latest version here fibaroapiHC3.lua (v0.311) The code is updated weekly so please make sure you have the latest... It was inspired by the old fibaroapi for the HC2 in a thread started by @riemers but has evolved with more extensive support to create a better debugging and "offline experience"... in fact, it's really an HC3 emulator now. The video is an earlier version of the emulator but the principles are more or less the same. Note the nice tooltip and autocompletion of fibaro commands we get with the fibaroapiHC3plugin for ZBS. Enable English subtitles to see instructions... Some benefits: Use a modern development environment such as ZeroBrane Studio (free for Mac/PC/Linux, HC3 plugin here) on your laptop/PC to develop and debug QuickApps and Scenes. Here is a good introduction to Lua (using ZeroBrane) Step through code, inspect Lua variables, set break-points etc - all that is possible in a good IDE. Faster to pin-point errors as the error messages are better than on the HC3 - stack-traces etc. Advanced timer info (setTimeout) warning of late timers and from where the offending function was called if a timer function crashes. Info from where an eronous json.encode was called from in your code so you can easily find the error (instead of seeing a line from deep inside the json encoder) Use the whole Fibaro API fibaro.call etc and net.HTTPClient(), setTimeout(), json.ecode/decode, QuickApp self:functions like self:getVariable, self:updateView Support for MQTT client and QuickApp child devices Both QuickApps and Scenes are supported. Scenes support most conditions and are triggered by real triggers from the HC3 or simulated triggers. Speed up clock to run faster than real time, to watch a Scene or QuickApp over days/weeks/months in seconds. Start at any given time and date - test if your scene behaves on week-ends ? Automatically create a proxy QuickApp on the HC3 that sends UI clicks back to the code your are running and displays self:updateView updates. This way you can test the QuickApp UI (buttons etc) and still debug the main code on your PC. Develop and run multi-file QuickApps, allowing you to build up a library of common code to share between your QAs. Run completely disconnected from the HC3 simulating devices and other resources (now you can take your coding with you on your vacation ) There is a possibility to download resource definitions from the HC3 and use them (devices, globals etc) while running disconnected. Load multiple QAs/Scenes into the emulator at the same time to debug interaction patterns between QAs (or just run all your QAs offline and use the HC3 as a wave GW ) Telnet into the running emulator to capture logs or issue Lua commands like turning on/off devices at runtime to test you QA/Scene. Move the code as-is over to the HC3 when it runs in the emulator - and it will most likely run on the HC3. Scenes needs to be moved to conditions/actions part on the HC3 - may automat that in the future. Oh, and an emulated Web GUI for the quickApp so you can try out button/slider clicks without connecting to the HC3. And lastly, it makes it fun to develop code for the HC3 To get going download the fibaroapiHC3.lua and put in in the working directory where you code your QA(s) If you run ZerobraneStudio (recommended) paste this and run if dofile and not hc3_emulator then dofile("fibaroapiHC3.lua") end--hc3 hc3_emulator.downloadPlugin() hc3_emulator.downloadAssets() Please note the 'end--hc3' that ends the 'if dofile and not hc3_emulator then' statement. It requires the '--end' comment so I can recognise it. Also, you need to set the Lua interpreter to version 5.3 (In ZBS, Menu ; Project -> Lua Interpreter -> Lua 5.3) It will install the. ZBS plugin in ~/.zbstudio/packages and some code templates in ~/.zbstudio/hc3emu/ (Restart ZBS for the plugin to. be installed) Create a Lua file and create a header + QA/scene code. An example of a minimal QA can look like if dofile and not hc3_emulator then hc3_emulator = { name = "My QA", poll=1000, -- Poll for triggers from the HC3 every 1s credentials = {ip="192.168.1.X", user="<user>", pwd="<password>"} } dofile("fibaroapiHC3.lua") end--hc3 function QuickApp:onInit() fibaro.call(88,"turnOn") -- turns on device 88 on your HC3 end We wrap the emulator specific stuff inside "if dofile and not hc3_emulator then .... end" as the symbol 'dofile' is not defined on the HC3 and will thus be false and not include the code - This means that we can take the code as-is and paste it into the HC3 and it works. Note the credentials that contains the IP, username and password so that the emulator can access the HC3 box. If you use ZBS and the plugin there is an Edit-HC3 SDK templates-> menu that will insert a standard QA and Scene header + code in the current buffer. Most of the functions are there and will be improved over time. There are support for net.HTTPClient() and setTimeout/clearTimeout and api.* There are support for getting triggers and events from the HC3 Support for auto-creating a QuickApp proxy with UI elements that sends events back to the code being debugged. There are support for both QuickApps and Scenes (with conditions) Currently supported (v 0.300) fibaro.debug(type,str) fibaro.warning(type,str) fibaro.trace(type,str) fibaro.error(type,str) fibaro.call(deviceID, actionName, ...) fibaro.getType(deviceID) fibaro.getValue(deviceID, propertyName) fibaro.getName(deviceID) fibaro.get(deviceID,propertyName) fibaro.getGlobalVariable(varName) fibaro.setGlobalVariable(varName ,value) fibaro.getRoomName(roomID) fibaro.getRoomID(deviceID) fibaro.getRoomNameByDeviceID(deviceID) fibaro.getSectionID(deviceID) fibaro.getIds(devices) fibaro.getAllDeviceIds() fibaro.getDevicesID(filter) fibaro.scene(action, sceneIDs) fibaro.profile(profile_id, action) fibaro.callGroupAction(action,args) fibaro.alert(alert_type, user_ids, notification_content) fibaro.alarm(partition_id, action) fibaro.setTimeout(ms, func) fibaro.clearTimeout(ref) fibaro.setInterval(ms, func) fibaro.clearInterval(ref) fibaro.emitCustomEvent(name) fibaro.wakeUpDeadDevice(deviceID) fibaro.sleep(ms) net.HTTPClient() net.TCPSocket() net.UDPSocket() net.WebSocketClient() -- needs extra download net.WebSocketClientTLS() -- needs extra download api.get(call) api.put(call <, data>) api.post(call <, data>) api.delete(call <, data>) setTimeout(func, ms) clearTimeout(ref) setInterval(func, ms) clearInterval(ref) mqtt.Client.connect(uri, options) -- needs extra download <mqttclient>:addEventListener(message,handler) <mqttclient>:subscribe(topic, options) <mqttclient>:unsubscribe(topics, options) <mqttclient>:publish(topic, payload, options) <mqttclient>::disconnect(options) plugin.mainDeviceId plugin.deleteDevice(deviceId) plugin.restart(deviceId) plugin.getProperty(id,prop) plugin.getChildDevices(id) plugin.createChildDevice(prop) class QuickAppBase class QuickApp class QuickAppChild json.encode(expr) json.decode(string) QuickApp:onInit() -- called at startup if defined QuickApp - self:setVariable(name,value) QuickApp - self:getVariable(name) QuickApp - self:debug(...) QuickApp - self:updateView(elm,type,value) QuickApp - self:updateProperty() QuickApp - self:createChildDevice(props,device) QuickApp - self:initChildDevices(table) sourceTrigger - scene trigger Supported scene events: {type='alarm', id=<id>, property='armed', value=<value>} {type='alarm', id=<id>, property='breached', value=<value>} {type='alarm', property='homeArmed', value=<value>} {type='alarm', property='homeBreached', value=<value>} {type='weather', property=<prop>, value=<value>, old=<value>} {type='global-variable', property=<name>, value=<value>, old=<value>} {type='device', id=<id>, property=<property>, value=<value>, old=<value>} {type='device', id=<id>, property='centralSceneEvent', value={keyId=<value>, keyAttribute=<value>}} {type='device', id=<id>, property='accessControlEvent', value=<value>} {type='device', id=<id>, property='sceneActivationEvent', value=<value>} {type='profile', property='activeProfile', value=<value>, old=<value>} {type='location', id=<uid>,property=<locationId>, value=<geofenceAction>, timestamp=<timestamp>} {type='custom-event', name=<name>} {type='UpdateReadyEvent', value=_} {type='onlineEvent', value=<bool>} Some of the parameters that affect the behaviour of the emulator and can be set in the header are: hc3_emulator.name=<string> -- Name of QuickApp, default "QuickApp" hc3_emulator.id=<QuickApp ID> -- ID of QuickApp. Normally let emulator asign ID. (usually 999 for non-proxy QA) hc3_emulator.poll=<poll interval> -- Time in ms to poll the HC3 for triggers. default false hc3_emulator.type=<type> -- default "com.fibaro.binarySwitch" hc3_emulator.speed=<speedtime> -- If not false, time in hours the emulator should speed. default false hc3_emulator.proxy=<boolean> -- If true create HC3 procy. default false hc3_emulator.UI=<UI table> -- Table defining buttons/sliders/labels. default {} hc3_emulator.quickVars=<table> -- Table with values to assign quickAppVariables. default {}, hc3_emulator.offline=<boolean> -- If true run offline with simulated devices. default false hc3_emulator.autocreate=<boolean> -- Autocreate local resources hc3_emulator.apiHTTPS=<boolean> -- If true use https to call HC3 REST apis. default false hc3_emulator.deploy=<boolean>, -- If true deploy code to HC3 instead of running it. default false hc3_emulator.assetDirectory=<string> -- Directory where assets shoud be downloaded (ZBS). Default ~/.zbstudio/hc3emu hc3_emulator.resourceFile=<string> -- When doing a resource download, use this file as default. hc3_emulator.db=<boolean/string>, -- If true load a "resource download" from hc3_emulator.resourceFile or string hc3_emulator.htmlDebug=<boolean> -- Try to convert html tags to ZBS console cmds (i.e. colors) hc3_emulator.terminalPort=<boolean> -- Port used for socket/telnet interface hc3_emulator.webPort=<number> -- Port used for web UI and events from HC3 hc3_emulator.HC3_logmessages=<boolean> -- Defult false. If true will push log messages to the HC3 also. hc3_emulator.supressTrigger -- Make the emulator ignore certain events from the HC3, like = PluginChangedViewEvent hc3_emulator.negativeTimeout=<boolean> -- Allow specification of negative timeout for setTimeout (will fire immediatly) hc3_emulator.strictClass=<boolean> -- Strict class semantics, requiring initializers hc3_emulator.consoleColors=<table> -- Maps fibaro.debug/self:debug etc to color (debug.color enables color debugging) hc3_emulator.sysConsoleColors=<table> -- Maps colors used for system logs hc3_emulator.userdataType=<boolean> -- If true intercepts type(...) to return 'userdata' for our Lua classes. Some apps checks this... Some useful emulator functions: hc3_emulator.setOffline(<boolean>,<boolean>) -- hc3_emulator.getIPaddress() -- Return HC3 IP address hc3_emulator.prettyJsonFormat(<table>) -- Return json formatted string of Lua table hc3_emulator.postTrigger(<event>,[<time ms>]) -- Posts a trigger to the emulator... hc3_emulator.loadScene(...) -- Load scene from file or HC3... hc3_emulator.loadQA(...) -- Load QA from file or HC3... hc3_emulator.downloadPlugin() -- (ZBS). Default ~/.zbstudio/packages hc3_emulator.downloadAssets() -- (ZBS). Default ~/.zbstudio/hc3emu hc3_emulator.downloadResources([<filename>]) -- Downloads a "backup" of HC3 resources hc3_emulator.loadResources([<filename>]) -- ...that can be loaded as "local" resources for the emulator. Some debug flags that can be set with hc3_emulator.debug.<flag>=<value> fibaro=false, -- Logs calls to fibaro api trigger=true, -- Logs incoming triggers from HC3 or internal emulator timers=nil, -- Logs low level info on timers being called, very noisy. refreshloop=false, -- Logs evertime refreshloop receives events mqtt=true, -- Logs mqtt message and callbacks http=false, -- Logs all net.HTTPClient():request. ALso includes the time the request took api=false, -- Logs all api request to the HC3 onAction=true, -- Logs call to onAction (incoming fibaro.calls etc UIEvent=true, -- Logs incoming UIEvents, from GUI elements zbsplug=true, -- Logs call from ZBS plugin calls webServer=false, -- Logs requests to /web/ including headers webServerReq=false, -- Logs requests to /web/ excluding headers files=false, -- Logs files loaded and run color=true, -- Logs in console using ANSI colors (see hc3_emulator.consoleColors for mapping) locl=true, -- Log creation of local devices breakOnInit=<boolean> -- Tries to set breakpoint on QuickApp:onInit (mobdebug) breakOnLoad=<boolean> -- Tries to set breakpoint on first line in loaded file (mobdebug) breakOnError=<boolean> -- Tries to break after error (makes it easier to look at call stack etc) ctx=false, -- Logs Lua context switches timersSched=false, -- Logs when timers are scheduled timersWarn=0.500, -- Logs when timers are called late or setTimeout with time < 0 timersExtra=true, -- Adds extra info to timers, like from where it's called and definition of function (small time penalty) In the example in the beginning, the HC3 credentials are listed in the header. If you don't want that (it's easy to forget it and share the code with your passwords in plain sights<9 you can create a credentials.lua file with your secret stuff and it will be automatically included by the SDK. The format should be return { ip="2912.168.77", user="admin", pwd="admin", mySecret="hgskjfhgjhgkdfh" } It returns a Lua table with the relevant keys. ip, user,and pwd is used to log into the HC3. We have added another key here to 'mySecret'. Assume that you want you QA to have a defined quickAppVariable with the value of mySecret. It could be the password to log into an external services. Then you can do like this if dofile and not hc3_emulator then hc3_emulator = { name="My QA", quickVars = {["password"]="$CREDS.mySecret"}, This define a quickAppVariable with the name 'password' and it fetches the key 'mySecret' from the credentials table and uses that as the value. When you QA starts up you can do self:getVarible('password') and it will return the credential. This is useful as not to litter your code with visible credentials. NOTE. Be aware that if you deploy the real QA with hc3_emulator.deploy=true or using the menu commands with the plugin, the deployed QA will have the quickAppVariable defined and if you upload that for sharing people will see your credential. If someone wants to try this in another IDE than Zerobrane that I use (like Visual Studio) the only thing that could be an issue is to have access to the Lua libraries require("socket") -- LuaSocket require("socket.url") -- LuaSocket require("socket.headers") -- LuaSocket require("ltn12") -- LuaSocket require("mime") -- LuaSocket require("lfs") -- LuaFileSystem They are pretty standard lua libraries - based on LuaSocket. @10der has managed to run it under Visual Studio on Windows. Here is an updated library/project map to work with the latest version of the emulator vscode_fibaro_bin.zip. Note that you should update the fibaroapiHC3.lua file provided i the archive when new are released as I will not update this archive for every new release. @petergebruers also have some tips. Any improvements are happily received (in code) and credits will be due granted. Links to notable post Here is a description of the various way to use the emulator when developing code (high-level) Some in-depth posts Running "Offline" (TBD) Running in "Mix mode". Mixing real devices and locally emulated devices (TBD) Running with a "Proxy QA" (TBD) Using real QA as "Proxy" (TBD) Downloading HC3 resources to file and emulate them locally (TBD) Running standard Lua with access to HC3 functions (developing management scripts etc) (TBD) Loading multiple QAs/Scenes and run them in parallel in the emulator (also getting QAs/Scenes from the HC3 and install them in emulator on the fly...) (TBD) Running faster than real-time and manipulating start dates (TBD) A ZeroBrane plugin to make life easier while debugging A post introducing the SDK with QuickApps. A post introducing the SDK with Scenes. Scene support is not complete. Creating and debugging multi-file QuickApps The debug flags that can be set are described The new dynamic load functions to run multiple QAs/Scenes in the emulator are described Telneting into the emulator to capture logs and issuing Lua calls <here> (nice way to test your code) Using the Web GUI Debugging setTimeout code and tracking timers. MQTT support. Another post with running a scene completly without being connected to the HC3. Some notes on the implementation of the SDK - if you would like to hack on it A collection of QA's I developed with the SDK - which means that they can be run offline ChildrenOfHue. A QA that creates QA children devices for your Hue devices (It's the Hue QA I use myself these day) iOSLocator. An iOS geopresence QA. iCal (iOS,Google) QA Telegram QA. Event watcher QA. Helper QA to get/subscribe on event triggers Vonage/Nexmo SMS service. Send SMS. Changelog: v 0.67 - numerous bug fixes caused by the restructuring. hc3_emulator.start{startTime="07:00 4/5/2000"} - will start the simulation at the given time. v 0.68 - fibaro.debug behaves more like original. v 0.70 - better offline support and speeding. v 0.72 - More offline and support for downloading HC3 resources to be used while running disconnected from the HC3 v 0.73 - Various speed-time related bugs v 0.75 - Better http sync behaviour. Set hc3_emulator.asyncHTTP=true to get some pseudo asynchronous behaviour v 0.77 - Support for 5.030.45. Initial support for childDevices and fixes for the changed handling of UI events v 0.78 - UI fix. Name of callbacks defaults to button.."Clicked", unless you have a onReleased=name or onChanged=name in the UI table struct. v 0.80 - Fixed bug in self:getVariable and self:setVariable v 0.81 - Better quickVariables handling for proxies, and self.childDevices list updated when children are deleted. v 0.83 - self:getVariable returns the empty string "" if the variable does not exists according to the latest behaviour on the HC3... 'class' is not redefined if available from Luabind... However, I've not had a chance to test if it's 100% compatible yet... v 0.84 - Initial support for mqtt. You need to have installed https://github.com/xHasKx/luamqtt so that require("mqtt") works from fibaroapiHC3.lua. I have tried to mimic the HC3 mqtt api but I have not really used mqtt that much so if someone uses it with fibaroapiHC3.lua and discovers if stuff is not compatible with the HC3 implementation please let me know and we fix it. v 0.85 - Compatibility fix for function 'class' to adhere more closely to the HC3/luabind version v 0.90 - Cleanup of code, Better handling of children and QuickApps, ZBS color output with ansi escapes; hc3_emulator.colorDebug=true v 0.93 - New model for QuickApp proxies. Better child device compatibility. v 0.95 - Various bug fixes - log prints more in line with HC3 log console. fibaro.emitCustomEvent bug fix. v 0.98 - First support for backup/download/upload with the ZeroBrane plugin (another post here) v 0.99 - Better trigger handling and new way to include SDK in your QA/scene code. No hc3_emulator.start at the end. v 0.100 - Web GUI emulator for QuickApps. New format for using credentials.lua. Bug fixes... v 0.102 - Better handling of children and their quickAppVariables v 0.104 - Rewrite of offline mode. Better web UI support. v 0.105 - Support for new QA file format (proxies work again) v 0.106 - Added support for net.UDPSocket() v 0.109 - UDPSocket bug fix. ( @10der), property() support for class() - much harder than it looks... v 0.110 - Oops, serious bug in 'class' affecting ...everything. Hopefully fixed. v 0.111 - Removed unnecessary os.exit(). urlencode api calls ( @10der) v 0.112 - UDP fixes. ( @10der) v 0.114 - Bug fix (global 'self' escaped) v 0.115 - Bug in url encode for api calls. UDPSocket :bind(ip,port) function added. v 0.116 - :bind(ip,port) really fixed.... v 0.117 - startup fix v 0.119 - "Softer os.exit()" - better compatibility with Visual Studio (thanks @10der) v 0.120 - Debugger friendly QuickApp class (no __index). First version of file/backup v 0.121 - api.get bug fix. Faster proxy/deploy. v 0.123 - QuickApp:setVariable bug (thanks @10der) v 0.124 - fibaro.clearTimeout added, MQTT fixes. v 0.125 - fibaro.alarm() was buggy - fixed. Set self.USERPIN to pincode to allow fibaro.alarm("disarm") to be allowed from emulator. v 0.126 - fix __fibaro_get_device() ( @10der) v 0.128 - fix sort order of triggers. Default room in offline mode ( @10der) v 0.130 - fix UI handling ( @rangee. More UI options. v 0.131 - fix uiCallbacks not always updating when updating proxy v 0.135 - fixes... v 0.137 - TCPSocket fixes v 0.138 - setTimeout for negative times are inserted in the queue.... i.e. will execute as soon as possible. v 0.140 - fixed bug with setInterval (clearInterval within a setInterval function didn't work...) v 0.141 - fix bug in net.TCPClient() v 0.145 - bug in printout of sockets... stricter class constructor requirements v 0.148 - MQTT event format bug ( @jayrock) v 0.150 - Initial websocket support. Need to download wsLua_ER.lua from my github and put in project directory. v 0.152 - support fibaroapiHC3plug.lua v0.4 v 0.155 - bugfixes. v 0.156 - html color bugfix v 0.198 - New version of emulator with better support for everything. Thanks to @petrkl12 that has been a guinea pig and helped in debugging the code. v 0.200 - Fixed bug in speedTime. plugin.restart() now restarts the QA in a correct way. v 0.299 - Major rewrite of the HC3 API - cleaner architecture and prepared for being split into sub-files (I'm approaching 10k lines now). Note 'end--hc3' required to end header. v 0.300 - Bugfixes from v0.299 v 0.301 - Better/simpler class definition - easier to debug/step into classes (avoiding __index unless class uses property() )
  11. I don't know if this is normal operation or not, but it seems to me that the antifreeze is configured at 10°C by default. How long has it been freezing at 10°C? Why is it not programmed at 0.5°C which would be more logical? The problem is that I sleep with the window open. And when the temperature drops below 10°C in the room, the valve opens the radiator which leads to a huge loss of energy. I tried to manually set the valve to 4°C, but on the dashboard it still says 10°C... So I had to dismantle the heat regulator in my room... Will this be fixed? What can we do while we wait for this issue to be resolved?
  12. I'm unable to add Zigbee devices to my HC3. When I click to add a Zigbee device, the HC3 console shows Waiting for adding process to start. After 3 minutes, it updates to Timeout for adding devices expired. I'm using two different Aqara Temperature and Humidity sensors and both have the same results. Fibaro support keeps telling me to try again or reset the Aqara sensor, but I'm suspicious of the HC3 itself. The messages in the HC3 console seem to imply that the HC3 is trying to go into adding mode, but that it hangs there. Can anyone confirm this? I'd be interested to learn what the console says when all goes as it should.
  13. Guest

    HC3 rel. Humidity

    Hello, im looking for a HC3 Script which switch a Bathroom Fan on/off with dependency relative humindity. I found a HC2 Script from kapitano1 (https://forum.siio.de/t/lua-taupunktlueftung-im-keller/5206) My Lua skill is very low, so i tried to change the code to hc3 and add my ids. The script will run correctly when humidInAbs - humidOutAbs > 1 but the switch off fan code is not correct. And sorry for my english, but it is not my native language; i tried my best. Can anyone correct it please? Debug: 28.08.2020] [12:44:00] [DEBUG] [SCENE218]: - 28.08.2020 12:44:00 AußenTemp 21.59°C rel. Feuchtigkeit 57.0% [28.08.2020] [12:44:00] [DEBUG] [SCENE218]: - 28.08.2020 12:44:00 absolute Luftfeuchtigkeit Außen 10.969697021231g/m³ [28.08.2020] [12:44:00] [DEBUG] [SCENE218]: - 28.08.2020 12:44:00 InnenTemp 25.4°C rel. Feuchtigkeit 51.0% [28.08.2020] [12:44:00] [DEBUG] [SCENE218]: - 28.08.2020 12:44:00 absolute Luftfeuchtigkeit Innen 12.211619119493g/m³ [28.08.2020] [12:49:00] [ERROR] [SCENE218]: Declaration: { conditions = { { type = "date", property = "cron", operator = "match", value = {"*", "*", "*", "*", "*", "*"}, isTrigger = true } }, operator = "all" } Action: local date = os.date("%d.%m.%Y %H:%M:%S", os.time()) local EXP = tonumber("2.71828182845904523536028747135266249775724709369995") local pressure = fibaro.getValue(425, "value") -- Luftdruck local tempOut = fibaro.getValue(422, "value") -- Außentemperatur local humidOut = fibaro.getValue(424, "value") -- Feuchtigkeit local tempIn = fibaro.getValue(120, "value") --Temp local humidIn = fibaro.getValue(122, "value") -- Luftfeuchtigkeit local timeout_min = 5 -- Wartezeit local I1 = tonumber(tempOut) -- Temperatur (in °C) local I2 = tonumber(humidOut) -- Relative Luftfeuchtigkeit (in %) local I3 = tonumber(pressure) -- Aktueller Luftdruck (in Millibar) local I4 = tonumber(tempIn) -- Temperatur (in °C) local I5 = tonumber(humidIn) -- Relative Luftfeuchtigkeit (in %) local humidOutAbs local humidInAbs local run = 0 function actionToHigh() -- Aktionen bei Erkennung zu hoher Luftfeuchtigkeit fibaro.call(148, "turnOn") end function actionToLow() -- Aktionen bei Erkennung zu niedriger Luftfeuchtigkeit fibaro.call(148, "turnOff") end -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- Werte Draußen -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ function Voutside() --print(" - " ..date .. " AußenTemp " ..tempOut .. "°C rel. Feuchtigkeit " ..humidOut.. "%") humidOutAbs = 0.622 * I2/100 * (1.01325 * 10^(5.426651 - 2005.1 / (I1 + 273.15) + 0.00013869 * ((I1 + 273.15) * (I1 + 273.15) - 293700) / (I1 + 273.15) * (10^(0.000000000011965 * ((I1 + 273.15) * (I1 + 273.15) - 293700) * ((I1 + 273.15) * (I1 + 273.15) - 293700)) - 1) - 0.0044 * 10^((-0.0057148 * (374.11 - I1)^1.25))) + (((I1 + 273.15) / 647.3) - 0.422) * (0.577 - ((I1 + 273.15) / 647.3)) * EXP^(0.000000000011965 * ((I1 + 273.15) * (I1 + 273.15) - 293700) * ((I1 + 273.15) * (I1 + 273.15) - 293700)) * 0.00980665) / (I3/1000 - I2/100 * (1.01325 * 10^(5.426651 - 2005.1 / (I1 + 273.15) + 0.00013869 * ((I1 + 273.15) * (I1 + 273.15) - 293700) / (I1 + 273.15) * (10^(0.000000000011965 * ((I1 + 273.15) * (I1 + 273.15) - 293700) * ((I1 + 273.15) * (I1 + 273.15) - 293700)) - 1) - 0.0044 * 10^((-0.0057148 * (374.11 - I1)^1.25))) + (((I1 + 273.15) / 647.3) - 0.422) * (0.577 - ((I1 + 273.15) / 647.3)) * EXP^(0.000000000011965 * ((I1 + 273.15) * (I1 + 273.15) - 293700) * ((I1 + 273.15) * (I1 + 273.15) - 293700)) * 0.00980665)) * I3/1000 * 100000000 / ((I1 + 273.15) * 287.1) --print(" - " ..date .. " absolute Luftfeuchtigkeit Außen " ..humidOutAbs.. "g/m³") end function Vinside() -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -- Werte Drinnen -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --print(" - " ..date .. " InnenTemp " ..tempIn .. "°C rel. Feuchtigkeit " ..humidIn.. "%") humidInAbs = 0.622 * I5/100 * (1.01325 * 10^(5.426651 - 2005.1 / (I4 + 273.15) + 0.00013869 * ((I4 + 273.15) * (I4 + 273.15) - 293700) / (I4 + 273.15) * (10^(0.000000000011965 * ((I4 + 273.15) * (I4 + 273.15) - 293700) * ((I4 + 273.15) * (I4 + 273.15) - 293700)) - 1) - 0.0044 * 10^((-0.0057148 * (374.11 - I4)^1.25))) + (((I4 + 273.15) / 647.3) - 0.422) * (0.577 - ((I4 + 273.15) / 647.3)) * EXP^(0.000000000011965 * ((I4 + 273.15) * (I4 + 273.15) - 293700) * ((I4 + 273.15) * (I4 + 273.15) - 293700)) * 0.00980665) / (I3/1000 - I5/100 * (1.01325 * 10^(5.426651 - 2005.1 / (I4 + 273.15) + 0.00013869 * ((I4 + 273.15) * (I4 + 273.15) - 293700) / (I4 + 273.15) * (10^(0.000000000011965 * ((I4 + 273.15) * (I4 + 273.15) - 293700) * ((I4 + 273.15) * (I4 + 273.15) - 293700)) - 1) - 0.0044 * 10^((-0.0057148 * (374.11 - I4)^1.25))) + (((I4 + 273.15) / 647.3) - 0.422) * (0.577 - ((I4 + 273.15) / 647.3)) * EXP^(0.000000000011965 * ((I4 + 273.15) * (I4 + 273.15) - 293700) * ((I4 + 273.15) * (I4 + 273.15) - 293700)) * 0.00980665)) * I3/1000 * 100000000 / ((I4 + 273.15) * 287.1) --print(" - " ..date .. " absolute Luftfeuchtigkeit Innen " ..humidInAbs.. "g/m³") -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ end Voutside() Vinside() --if (humidInAbs > humidOutAbs) then if (humidInAbs - humidOutAbs) > 1 then print(" - " ..date .. " Bad 1.OG lüften!") actionToHigh() print(" - " ..date .. " AußenTemp " ..tempOut .. "°C rel. Feuchtigkeit " ..humidOut.. "%") print(" - " ..date .. " absolute Luftfeuchtigkeit Außen " ..humidOutAbs.. "g/m³") print(" - " ..date .. " InnenTemp " ..tempIn .. "°C rel. Feuchtigkeit " ..humidIn.. "%") print(" - " ..date .. " absolute Luftfeuchtigkeit Innen " ..humidInAbs.. "g/m³") fibaro.sleep(timeout_min*60*1000) else actionToLow() print(" - " ..date .. " Bad 1.OG nicht lüften") run = 0 end
  14. 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.
  15. Cześć! Czy ktoś z was korzysta równolegle w 1 mieszkaniu z automatyki Fibaro i Home Assistant? Aktualnie mam centralę HC3 z 40 urządzeniami fizycznymi z-wave, 4 kamery IP, oraz kilkanaście zarządzalnych urządzeń z dostępem przez www czy aplikacje. Dodatkowo całość jest sterowana przez 69 scen automatycznych oraz głosowo przez integrację z Amazon Alexa. Zastanawiam się czy równolegle nie postawić Home Assistant (mam akurat na to mocnego NASa z wolnymi zasobami) aby uruchomić część integracji i jakiegoś ciekawego dashboardu. Na pewno centrala HC3 zostanie ze mną już na wiele lat do obsługi urządzeń z-wave i innych, planuję także w przyszłości jeszcze rozbudować system o nowe urządzenia i funkcjonalności. Chciałbym pozbyć się przede wszystkim używania kilku różnych aplikacji w telefonie do obsługi różnych urządzeń, dążę do stworzenia pełnej automatyzacji i zarządzania głosowego gdy zajdzie taka potrzeba. Czy Fibaro umożliwia wymianę danych z Home Assistant (np. do przesyłania danych z czujników temperatury)?
  16. I am having an issue with my HC3 and it is basically useless at the moment. After a reboot on the weekend it went into recovery mode. I have a ticket in with Fibaro suppot, but bot had any communication from them for a couple of days. I thought I would post here hoping someone may be aboe to help. I will post what I have sent to Fibaro hopefully someone can give me some usefull advice.
  17. This is a Quickapp script for HC3. I am trying to get this to work in a VD on HC2. Is it possible, or do I have to do it together with a scene to make it work? Can anyone help? function QuickApp:onInit() self:updateProperty("unit", "kr/kWh") self.refresh = 60 -- in seconds local function loop() self:webrequest(); setTimeout(loop,self.refresh * 1000) end if self.username ~= "changeme" then loop() end end function QuickApp:webrequest() local tid = os.date("%R") local minutt = os.date("%M") --OPPDATERER STRØMPRIS OG SNITT HVER TIME if (minutt == "00") then self:OppdaterPris(); self:OppdaterSnitt(); end end function QuickApp:OppdaterPris() --Opprette lokale variable local GammelStrompris = fibaro.get(126,"value") local NyStrompris --Definerer http local http = net.HTTPClient(); --Definerer strengen Payload til å være kommando til tibber local payload = '{"query": "{viewer {homes {currentSubscription{priceInfo{current{total}}}}}}", "variables": null, "operationName": null}'; --API.POST til Tibber-- http : request('https://api.tibber.com/v1-beta/gql', { options = { method = "POST", headers = { ['Authorization'] = '.........', --Min Tibber ID her. ['Content-Type'] = 'application/json' }, data = payload -- Query. }, success = function(response) --fibaro.debug (response.data) --Verifiser at en har fått response.data. Dette er data som en har fått fra Tibber local data = json.decode(response.data); --fjernet local under??? NyStrompris = json.encode(data.data.viewer.homes[1].currentSubscription.priceInfo.current.total); self:updateProperty("value", tonumber(NyStrompris)) --print("OK") end, error = function(err) fibaro.debug ("Error:" .. err) end }); end function QuickApp:OppdaterSnitt() --Definerer http local http = net.HTTPClient(); --Definerer strengen average til å være kommando til tibber local average = '{"query": "{viewer {homes {currentSubscription{priceRating{daily{entries{total}}}}}}}", "variables": null, "operationName": null}'; --API.POST Til Tibber http : request ('https://api.tibber.com/v1-beta/gql', { options = { method = "POST", headers = { ['Authorization'] = '...............', --Min Tibber ID her. ['Content-Type'] = 'application/json' }, data = average -- Query }, success = function(response) --fibaro.debug(response.data) --Verifiser at en har fått response.data. Dette er data som en har fått fra Tibber local data = json.decode(response.data); local Nypris = tostring(json.encode(data.data.viewer.homes[1].currentSubscription.priceRating.daily.entries[31].total)); self:updateProperty("log", tostring(Nypris)) end, } ) end
  18. Hi All! I have created a loop in a QA and need to detect if a button (from a 8-button device, Scene Master - ZRC-90 - Remotec) has been singleclick or dubbleclick and which one Normaly I simple use this: { conditions = { { id = 162, isTrigger = true, operator = "anyValue", property = "centralSceneEvent", type = "device" } }, operator = "any" } local trigger = sourceTrigger if (trigger.value.keyId==1 and trigger.value.keyAttribute=="Pressed" ) But in this case we do not have this device as a "sourceTrigger" I have tried diffrent ways but can not get it to work function QuickApp:loop(KeyCodeQA) local trigger = hub.getValue(162, "value") if (trigger.keyId==1 and trigger.keyAttribute=="Pressed" ) end
  19. Using HC3, I have a manual scene to initialise variables and hardware etc. What's a good way to get feedback on its result - whether it succeeded or failed? Checking the Debug Log would be a hassle. In HC2 it wasn't a problem as the debug info was right there without having to select tag and type.
  20. I'm asking the forum for support regarding the creation of software documentation in HC3. (please answer yes/no) I propose to create a button in the /app/settings/general/main location, which would make a documentation in the text format as similar as possible (included a graphical side) to the HC3 programming area in LUA scenes. The file name should be DocFIBYYYYMMDDTime.LUA. It would be used for comparison with older versions of the software in Visual Studio Code (Microsoft). I really appreciate the HC3 system. However, my customers and I lack a documentation of all scenes in the text format in one file. This collection would allow me and my customers to rewiev the previous data to remind ourselves the original state of the software and settings. When our system doesn't work, I would like to find what I have changed before or what have gone wrong. By comparing the original documentation with the new one, I would have an immediate overview. Furthermore, this documentation could be useful to search for the ID numbers in the scenes. As you probably know, sometimes we are forced to remove and add the ID again. This causes the ID to be renumbered. As a result of it, it is necessary to replace the old ID numerical codes with the new ones in all scenes. When renumbering the ID of, for example a three-phase electricity meter, it has to make 32 times. The structure of the documentation is described in the "BLOCK Scheme" below. An example of the documentation is given in the "Example of documentation" below. Experts may program in other languages and make extensive use of APIs, but the system is not intended for them, but for the general public. The public needs outputs perhaps more than experts. I would be grateful if FIBARO looked into this as soon as possible. With thanks for your cooperation ing. Petr Boltík "BLOCK Scheme the documentation" procedure CreateTXT(DocFIBYYYYMMDDTime.LUA); var i,sceneMAX: Integer; BlockScene: boolean; begin for i := 1 to SceneMAX do --the main passage if exists(scene[i]) then begin if BlockScene then TraslateBlockToLUA; SaveNumber and NameScene; Save DECLARATIONS (Conditions/Triggers) scene; Save "---------------------------------"; Save ACTIONS scene; end; for i := 1 to QuickUPMAX do --passage QuickUp if exists(QuickUP[i]) then begin SaveNumber and NameQuickUP; SaveDevice??? SaveMain; end; for i := 1 to rowDocumentTXTMAX do --passage control on exist ID and SC begin if search ID (not exists in systém HC3) then begin changetxt "IDXXX" on IDXXXNotexists or IDXXXERROR end; if search Scene( not exists in systém HC3) then begin changetxt "SCXXX" on SCXXXNotexists or SCXXXERROR end; end; for i := 1 to IDMAX do --passage ADD params ID begin SaveNumber and NameID; Save name Params and value; end; end; "Example of documentation": --SC46 on device >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> table = { isTrigger = true, operator = "match", property = "cron", type = "date", value = { "0", "*", "*", "*", "*", "*" } } -------------------------------------------------- local currentHod = os.date("*t").hour hub.call(467NOTEXIST, "turnOff") hub.call(468, "turnOff") hub.call(469, "turnOff") hub.call(470, "turnOff") if (currentHod == 0) then --hub.call(470, "turnOn") --zahrada vzadu elseif (currentHod == 1) then hub.call(467NOTEXIST, "turnOn") elseif (currentHod == 2) then hub.call(469, "turnOn") elseif (currentHod == 12) then hub.call(470, "turnOn") end --SC47 off device >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> table = { isTrigger = true, operator = "match", property = "cron", type = "date", value = { "0", "*", "*", "*", "*", "*" } } -------------------------------------------------- --local currentHod = os.date("*t").hour hub.call(467NOTEXIST, "turnOff") hub.call(468, "turnOff") hub.call(469, "turnOff") hub.call(470, "turnOff") --SC48 on device >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ...
  21. Has anyone tried to send notifications from the HC3 controller via Signal communicator? Is there any solution for integration with this communicator?
  22. I am currently using HC2 and will be migrating to HC3 which I have and is live with 2 devices. I need to rewrite my scenes and VDs etc. Question - will there be any interference between the devices owned by HC2 and the ones owned by HC3 ? The reason I am asking is that the whole stuff is so flaky. Devices used to go dead all the time. After literally 5 years of contacting suppliers, installers, support and engineers, I finally figured out the main problem in my network. My conclusion/assumption is. It turns out that 2 devices had removed themselves from the "control panel" as the support call it. I had not realized this as we never tried controlling them from the app or scenes. And devices around these were using them for hopping messages, which the HC rejected. Once I re-enrolled these two (after searching for them all over the house), everything has been running sweet, for the first time in 5 years. I would call this extremely flaky thinking, process and code !!!! And I am beginning to think that I might be up for more pain from similar stupidity happening between the two HCs.
  23. is it possible to integrate Proscenic devices with the Fibaro system? I currently have a Proscenic 808C humidifier that can be controlled by a remote control and an application. https://www.proscenic.com/pl/808c-humidifier-p0134.html This humidifier has a built-in wi-fi radio module. It would be nice to control it directly from Fibaro via Quick Apps.
  24. I've just upgraded from HCL to HC3 and added the first of 14 FGR221 roller shutters controllers (FGR221 firmware and HC3 Beta firmware are both up to date). However, After adding the shutter device, it will not move up or down via the app (parameter updated in settings to single momentary S1). I have poisitioning normally set to on, but even with it off, nothing happens. I have manually controlled via S1 the shutter up to 3 cycles to ensure it is calibrated but still no joy! I added the shutter device back to the HCL and everything works fine. Am I missing something here? The HCL is unstable and it needs to be reset every 4 days so I need a more stable working solution with the HC3.
  25. Hi, I'm new to LUA but I am trying to read the current value of R and assign it to B. I basically have 2 white strips and 2 sets of downlights, assigned to the RGBW channels. I want the 2 sets of strips to copy each other and the 2 sets of downlights to copy each other, so if I dim one strip, it mimicks on the other strip and if I dim one set of downlights it mimicks on the other set of downlights. So I want to read the current value of R and assign it to B and read the current state of G and assign it to W. Thanks in advance!
×
×
  • Create New...