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. 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...
  2. I want to know how to integrate HC3 with Broadlink RM4 PRO? If anyone created Quick apps for Broadlink devices could you please share with me the details?
  3. So, i'm still setting up the HC3. And run into some problems. I have 2 Zwave devices: a 8 button wall switch and a Fibaro multi sensor. The wall switch is configured to run some scene's. And the sensor is for later use, but also "adopted" in the device list. This is the second time in a few days, that the zwave devices stop working. The buttons stop activating the scene's, while when i start the scene manually it still works. The multi sensor shows up with a red cross in the device list. When i noticed this before, i just rebooted the HC3. And then it all works again. How can i troubleshoot this ? The console doesnt tell me anything..
  4. Current version: 1.4.0 Date: 15/03/2021 FUNCTIONS The functions of this Quick App are: Allowing to control Sonos Player from Home Center 3. It does support basic and advanced functions: Basic Transport Control Initiate playback Toogle, Pause or Stop playback Skip to the previous or Next track Basic Rendering Control Get player volume and mute state Set player volume to a specific level and unmute the player if muted Increase or decrease player volume Get or Set or Toggle player mute state (Mute or unmute the player) Get or Set or Toggle player loudness state Device Properties Get or Set group LED state Restart the QA Device Enable Debug Mode See Changelog / Manual for basic and advanced available actions Examples: Set player volume to a specific level and unmute the player if muted. fibaro.call(ID_QUICKAPP, "setVolume", 10, "Master") Increase or decrease player volume. fibaro.call(ID_QUICKAPP, "setRelativeVolume", -5, "Master") Initiate playback. fibaro.call(ID_QUICKAPP, "play") Play a file at volume 10 with snapshot/revert process to restore previous state fibaro.call(ID_QUICKAPP, "playFile", "35HTGV34R7S/CD/Album/song.flac", true, 10) Play a stream at volume 20 & 8s duration with snapshot/revert process to restore previous state fibaro.call(ID_QUICKAPP, "playStream", "https://s3.amazonaws.com/smartapp-media/sonos/bell1.mp3", true, 20, 8000) Version 1.4.0 Tested with Sonos Sonos OS: S2 - Version 13 (number 62186220) Tested with HC3 & HC3Lite v5.050.13 -> v5.063.30 Fix for Sonos firmware version 13 Fix for Sonos ARC getPositionInfo and malformed xmlsoap (hope full supoport soon) Add playNextRadio command to navigate the radios Add play mode control from QA button (loop in NORMAL,REPEAT_ALL,REPEAT_ONE,SHUFFLE_NOREPEAT,SHUFFLE,SHUFFLE_REPEAT_ONE) Fix Radio metadata strange behaviors in some situations Version 1.3.8 Tested with Sonos Sonos OS: S2 - Version 12.2.2 (number 61183220) Improved support for albumArt, now work with Sonos Radio, Amazon Music, Spotify, TuneIn, Music library Add option 'protect' to playFile and playStream for disallow to restart a playing Add Crossfade mode support with getCrossfadeMode, setCrossfadeMode and toggleCrossfadeMode commands Add sleepTimer command Add setPlayMode command, support: NORMAL,REPEAT_ALL,REPEAT_ONE,SHUFFLE_NOREPEAT,SHUFFLE,SHUFFLE_REPEAT_ONE Add selectLineIn command Add in variables panel, "notification" variable to enable or disable the "Device notification error", if disabled QA trace the message in QA console only Various improvement Version 1.3.1 RC Tested with Sonos Software Version: 56.0-76060 / Sonos OS: S2 - Version 12.0.5 & 12.1 Add support to use in block scenes (Play, Pause, Stop, Next, Prev, Set Volume, Set mute) Support for album covers when available (cf. music library) Performance improvement when initiating a playback Improved radio playback and track information Increase the number of supported radio stations (with auto configuration up to 9) Support for Sonos playlists (with auto configuration up to 6 saved queues) Add playFile command Add playStream command Add playSavedQueue command Add startQueue command Add clearQueue command Add seek command Add snapshot command Add revert command Add getListSavedQueues command Add addURIToQueue command Add checkForUpdate command Add getTreble and setTreble commands Add getBass and setBass commands Various Bug fixes (Polling when not configured, parsing ...) Version 1.1.1 Support for TuneIn "My radio stations" (with auto configuration up to 6 radios) Deletion of the variable variable "isConfigured" used by internal FTI Configuration Minor bug fixes (No route to host cause wrong configuration status) Tested with Sonos Software Version:55.1-74250 and 56.0-76060 Performance improvement Version 1.0.3 Fix a problem with internal zoneGroups and ZoneGroupMembers parsing (Thanks to jgab, Alan Klepacz and robw) Version 1.0.2 Minor bug fixes (Thanks to Macschimmi, Bodyart, minsad79) Version 1.0.0 Based on my HC2 virtual Device and completely rewriten for HC3 v5.030.45 or highter Very low latency and more robust device (commands execution, processing) Easy installation with auto configuration assist Support standard capabilities (AVTransport, RenderingControl) Displaying information on the currently playing or media loaded Fully controllable from the LUA scenarios (see available command list) You can download it from the Fibaro market: https://marketplace.fibaro.com/items/sonos-zone-controller hope you will be pleased with it ROADMAP Support for multi-devices in group used for triggering in scene and prepare for group-ungroup Support for TV source (if supporteed by device) Support for Group Support for TTS
  5. [edit] i think i should have placed it in the "Scenes and Interface" section, sorry for that. So, i'm new, newbe, so...dont shoot me I've been reading a lot, on this forum and elsewhere trying to get my Powerview shades connected to a zwave switch. It seems to be much harder to manage then i was hoping for. My head spins around with all the information, code lines and such, Also, none of the info i found seems to be complete. It is all like "do it in LUA", make a QA or a a bunch of code lines. I hope to find some hints, or answers - help with that. So, what i worked out: - The 8 button fysical wall switch works. - The powerview plugin works, and the scene's controlled from the hub work The imported scene's dont work, and need i to make a QA or a LUA scene for that. What i tried: I made a block scene with the switch, and a HUE lamp, converted this to LUA this is the "what if button is pressed" and it works. { conditions = { { id = 21, isTrigger = true, operator = "==", property = "centralSceneEvent", type = "device", value = { keyAttribute = "Pressed", keyId = 1 } } }, operator = "all" } The action part, i made this - but its wrong. local connection = Net.FHttp("192.168.1.35", 80); local command = "/api/scenes?sceneid=25173"; local response, status, errorCode = connection.GET(connection, command); It gives this error: 10.07.2021] [07:00:40] [ERROR] [SCENE4]: (load):1: attempt to index a nil value (global 'Net') I know there is a lost of writing about this on the forum but, I am totally lost in what to do, is this sort of the right way to do it ? Should i do it with a QA ?
  6. Witam serdecznie czy ktoś z was wie cos na temat integracji HC3 z rekuperatorem KAISAI - wyprodukowanym dla KAISAI przez włoską firmę SABIANA . Jeśli ktoś potrafi napisać integracje proszę o kontakt sabianaCloud.yaml
  7. Anybody having success updating motion sensor to 3.4 from 3.3 on HC3? My update is basically forever in this state. Of course I did manual wake up of the device, but still 0%. Any ideas where (some API) to look for more information?
  8. 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.) 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. 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() )
  9. Hi, I'm trying to configure ZXT-600 with my HC3 but I have some challenges/bugs. *Disclaimer - at this moment I'dont want to use any specific AC. I'm doing this as a "dry run" before final installation 1. HC3 without any problem recognize ZXT-600 "devices". ZXT-600 is wotking wit USB power adaptor. 2. I'm trying to configure ZXT-600 based on manual (https://1d7d2411-2e94-4f8c-a95f-87afc2c677d4.filesusr.com/ugd/6dacfa_70e9d19869b44299b27f501fd1673f85.pdf) . At the beginning I added two parameters: - 27 [Set IR Code number from built-in code library 27 (0x1B)] - I choose one of the Mitsubishi - 30 [Set Auto Report Condition Trigger By Room Temperature change 30 (0x1E)] - I choose value what menas based on manual "Auto report if room temperature is different from last report. 1(0x01) = 1°F (0.5°C)" ZXT-600 has been assigned to room Kuchnia/Kitchen (details on below print screen) I used iOS Fibaro application for HC3 and it looks that HC3/ZXT-600 doesn't work ijn proper way. 1. Even when I'm using parameter "Auto report if room temperature is different from last report. 1(0x01) = 1°F (0.5°C)" temperature doesn't change. Mobile application and Fibaro HC3 dashboard present one value (updated during power adaptor has been detached/attached) Is it a bug, malfunction or my lack of knowledge how to configure devices ? 2. I assume that should be possible send IR commnad (on, off, cooling, heating ...) from mobile application->HC3->ZXT-600 to air condition IR receiver. Maybe I'm wrong or I miss something. Unfortunatelly I haven't or I can't see any places in mobile/web applications where I could be do this Please let me know about your thoughts/experience. Thank you
  10. Hello everyone,.. I am pleased to announce that the first version of QA for controlling the iEAST streamer has already been published. It's the Lite version. You can download it here on the Marketplace: https://marketplace.fibaro.com/items/ieast-hc3-lite-player Current version: Lite 1.0.0 Date of publication: 7/08/2020 Last update: 17/08/2020 FUNCTIONS The functions of this Quick App are: Allowing to control iEAST Player from Home Center 3. You can control one device. It does support basic and advanced functions: Basic Control Chose the device preset (radio station/stream) – if your device supported this Initiate playback Button for Playback, Stop, Prvevious and Next track Toggle button, Pause/Playback Button for MUTE (unMUTEd will be when set some volume) Basic Rendering Control Get player volume and mute state Set player volume to a specific level and unmute the player if muted Increase or decrease player volume Get or Set or Toggle player mute state (Mute or unmute the player) Get or Set or Toggle player loudness state Basic Rendering States Get URL stream from device Get Title and Artist from device Get Play status – play/stop/pause/mute Get Volume level Show the QA status QA Properties Enable QA Debug Mode RELEASE NOTES - changelog Version 1.0.0 For HC3 v5.031 Support standard capabilities (PlayerControl, PlayerStatus) Displaying information on the currently playing (with some exceptions) Fully controllable from the LUA scenarios (see available command list) Directly controll the one of three devices For the future Support for select LineIN play mode Support fot Equaliser Toggle for STOP/PLAY MASTER / slave multiroom control support (in the Enhanced version) For more information, visit the Marketplace page: https://marketplace.fibaro.com/items/ieast-hc3-lite-player The description is part of the package. In case of questions, please write eM. EDIT 20200918: For debug some communication problem, pleas visit this post:
  11. QA for Philips Hue devices (for HC3 5.040 GA or above): - support of philips hue lights, switches and sensors (motion, temperature, light) and some ikea lights connected to hue bridge - unlimited number of hue bridges - all logic and setup are centralized in QA HueMain - creating of hue devices via click on buttons in HueMain - a lot of parameters for advanced users - automatic update of all devices in case of new versions - centralized setting of favorite buttons,colors and icons (also possibility to override settings via local variables in every QAs) - power consumption calculation for lights - supported languages: en,cz,de,se,nl,sk,fr,ru,it,pl Installation: 1. Download HueMain.fqa 2. Install HueMain.fqa to HC3 3. In Variables in HueMain you have to setup: - HueBridgeName1 - you can choose any name of your bridge - it can be whatever – allowed characters: a-z, A-Z, 0-9, _ - for example MyBridge1 - HueBridgeIP1 - IP address of your bridge for example 192.168.1.200 - Save variables - HueMain should start if everything is OK 4. And than you have 2 options: a) you know your user in bridge - you can add it to Variables - item HueUser1 ie.vPCj123VmJ18uWSHqpXfidxq5sjsP1q4Wi6DiCm b) you can create user in HueMain - last part - button Create user (you will need physical access to your Hue bridge and press button there) + save/restart 5. HueMain should run (if everything is OK) and show your hue devices in menu 6. You can create QAs for group of lights, lights and sensors in menu in HueMain Files: 1. QA - HueMain HueMain20210307_300.fqa 2. Icons: Icons20200928.zip HOW TO CALL from other QAs or Scenes: -- for calling from other QAs: fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='setscene', deviceID=QAID_HueLight, value='TVmugOA8rAACGGj',transitiontime=0}) -- for calling from scenes (you have to add json.encode): fibaro.call(249, "HueCommands", json.encode{type='Hue', action='setscene', deviceID=500, value="Sb3tQguuEpnV0gO", transitiontime=0}) --[[ -- QAID_HueMain and QAID_HueLight have to be numbers -- light on fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='on', deviceID=QAID_HueLight}) -- light on with transition time fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='on', deviceID=QAID_HueLight, transitiontime=0}) -- light off fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='off', deviceID=QAID_HueLight}) -- light on with transition time fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='off', deviceID=QAID_HueLight, transitiontime=0}) -- light on with setting of brightness (in value), if value<2 then value=100, value=<0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='on_bri', deviceID=QAID_HueLight, value=50}) -- setup of brightness (in value) and also if value is 0 then Light off - in other cases Light on, value=<0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='brightness', deviceID=QAID_HueLight, value=50}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='brightness', deviceID=QAID_HueLight, value=50, transitiontime=0}) -- light toggle based on last refreshed data from hue bridge (fast method, in some cases can be inaccurate) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='toggle', deviceID=QAID_HueLight}) -- light toggle based on new request from hue bridge (slower method but accurate) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='toggle2', deviceID=QAID_HueLight}) -- light toggle based on last refreshed data from hue bridge (fast method, in some cases can be inaccurate), brightness is in value <0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='toggle_bri', deviceID=QAID_HueLight, value=50}) -- light toggle based on new request from hue bridge (slower method but accurate), brightness is in value <0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='toggle_bri2', deviceID=QAID_HueLight, value=50}) -- setup of color (in value), value=<0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='color', deviceID=QAID_HueLight, value=50}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='color', deviceID=QAID_HueLight, value=50, transitiontime=0}) -- setup of saturation (in value), value=<0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='saturation', deviceID=QAID_HueLight, value=50}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='saturation', deviceID=QAID_HueLight, value=50, transitiontime=0}) -- setup of color temperature (in value), value=<0,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='colortemp', deviceID=QAID_HueLight, value=50}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='colortemp', deviceID=QAID_HueLight, value=50, transitiontime=0}) -- setup of color via RGB (in colorR, colorB, colorB <0,254>), brightness is in value=<2,100> fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='colorRGB', deviceID=QAID_HueLight, colorR=10, colorG=200, colorB=100, value=100}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='colorRGB', deviceID=QAID_HueLight, colorR=10, colorG=200, colorB=100, value=50, transitiontime=0}) -- setup of hue light based on global setting in Hue Main for button Color 1 to button Color 5 fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='setcolor', deviceID=QAID_HueLight, typebutton='color1'}) -- setup of hue light based on global setting in Hue Main for favourite button 1 to button 5 fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='setbutton', deviceID=QAID_HueLight, typebutton='button5'}) -- setup of hue light based on standard Philips Hue commands and values fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='set', deviceID=QAID_HueLight, ParamHue={"on":true,"hue":0,"sat":254,"bri":254}}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='set', deviceID=QAID_HueLight, ParamHue={"on":true,"bri":254,"xy":[0.3651,0.3719]}}) -- setup scenes - sceneID is in value fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='setscene', deviceID=QAID_HueLight, value='TVmugOA8rVWCGGj'}) -- setup color loop efect - start fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='colorloopstart', deviceID=QAID_HueLight}) -- setup color loop efect - stop fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='colorloopstop', deviceID=QAID_HueLight}) -- set hue scene for lights fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='setscene', deviceID=QAID_HueLight, value=hueSceneID, transitiontime=0}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='setscene', deviceID=QAID_HueLight, value='TVmugOA8rAACGGj', transitiontime=0}) -- enabling of motion sensor fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='configon', deviceID=QAID_HueMotionSensor}) -- disabling of motion sensor fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='configoff', deviceID=QAID_HueMotionSensor}) -- alerts fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='alerttoggle', deviceID=QAID_HueLight}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='alertstart', deviceID=QAID_HueLight}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='alertstop', deviceID=QAID_HueLight}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='alertstart2colors', deviceID=QAID_HueLight, color='"sat":254, "bri":254, "hue":65535', color2='"sat":254, "bri":254, "hue":46530'}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='alertstart', deviceID=QAID_HueLight, color='"sat":254, "bri":254, "hue":0'}) fibaro.call(QAID_HueMain, "HueCommands", {type='Hue', action='alertstart', deviceID=QAID_HueLight, color='"sat":254, "bri":254, "hue":46530'}) --]] How to add icons where is not direct QA support for icon selection - for example for QA Hue Switches: There is not possible to change icon for switch via user interface but you can do it via my QA: 1. you have to upload icons for hue switch: In HueMain - tab General - add Icon Select your user icons and save it. You don't need to change icon for your HueMain 2. You need to get icon number - user icon has number with 4 digits (I hope that you don't have more 9999 icons currently ) right click on icon in your browser and select save picture - there will be - ie. User1007.png - your icon number is 1007 (in some of icons ie. for lights you can see longer number ie. User1018100.png, always use only first 4 digits - 1018 3. In HueMain - tab Variables - add your icons number to IconSwZLLxxx (default icon is 0) or IconSwZGPxxx based on your hue switch type - btw. you can set also default icons for all your hue devices 4. Save your variables and HueMain will be restarted and your HueQAs will have new nice icons
  12. Does anyone have experience with Foscam on HC3? I do not get a picture in preview. I connect to an external ip. Do I have to use https and install SSL certificate? I did not find the model I have so I had to use "other" I have to use MJPG streaming and use this path http://USR:[email protected]:IP/video.cgi
  13. Hi, From the resources available on the forum I managed to glue QA to support Yamaha Musiccast (tested on R-602N and WX-30 ). The code is certainly not clean and needs patches. Would anyone experienced be interested in helping to refine the QA and adding additional functions before posting it in the forum? Regards Michal
  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. i looks i i have a memory leak in Firmware: 5.070.810 If I reboot it drops to 80%, and if i restore backup, without events - it drops a little more. And after some days its close to 95%. My center is so slow - so it takes 5-10 seconds per update, click. Its close to worthless, im not even close to implement all feature.
  16. Is anyone has succeed to use https connection? I did follow Fibaro's procedure to install certification Download the certificate. In the Windows Start menu search for mmc app and open it. In the MMC (Microsoft Management Console) app go to File > Add/Remove Snap-In. Add Certificate Snap-in: Certificates > Select “Computer account” > Next > Next > OK. Now go to Certificates > Trusted Root Certification Authorities and right-click on “Certificates” Import the certificate. Find the certificate downloaded from the FIBARO Home Center 3. Import it. Done. Your connection with the gateway is now secure. but doesn't work on FIrefox. (Expiration date ?) Any extra steps required to install certification? Interesting it does work with Chrome !!??
  17. I explain, in summer, i put my heat controllers in summer mode. For that i execute this commands: 1. api.post("/devices/"..id.."/action/setThermostatMode", {args = {"ManufacturerSpecific"}}) 2. api.put("/devices/"..id, {parameters = {{id = 2, value = 0, size = 4},{id = 3, value = 1, size = 4}}, useTemplate = true}) 3. api.post("/devices/"..id.."/action/setProtection", {args={"2"}}) 4. api.put("/devices/"..api.get("/devices/"..id).parentId, {properties = {pollingInterval = -1}}) 5. api.put("/devices/"..id, {properties = {saveLogs = false}, enabled = false, visible = false}) (1) I set my heat Controllers in Manufacturer Specific, but after few hours, he return to Heat parameter. For summer, the heat controllers must be fully open. (2) I change the parameters for deactivate OpenWindow notification and other. This command work, but the informations displaying in the HC3 not refresh data... Have a idea for force a "refreshStates" command to HC3 ? (3) It's the same with point (2), he work but not refreshed on HC3. (4) Copy this command normally sended by HC3 when i change the properties of the device. (I don't know what this command is for.) (5) Disabled heat controllers for be sure not be changed by the HC3 in the futur. But after few hours, the heat controllers return to Heat mode... Have you a idea, why heat controllers return to Heat mode after few hours and why when i change the parameters, the HC3 not refresh display data ? P.S. In my script, for be sure the HC3 not interfer with heat Controllers, i have deactivate the climat zones: Thanks for your help !
  18. Dear all. I had an inquiry from a teacher at the Danish electrician education. They will put the HC3 in the curriculum, because smarthomes will be the future.✌️ so... to all the kids learning basic programming - we need a Proof of Concept.. How can I provide a solution where, i from an Internet website can control the something in the HC3, it could be a simple switch. So controlling the HC3 from another network that itself. What the want to achieve it the HC3 is on the home network. Have a website showing video stream with a HC3 controlles Bulb, and a button on the same website that can control the Bulb. Its for Exhibitions getting interest for potentially young students .. No MQTT or other mittleware, it needed to be done direct, like when Alexa, Google assistant is controlling this. No Firewall port forwarding As I see it, I need two moduels, One on the external website and one one at the HC3. Anyone up for helping with a PoC fort this? have some code already? or can structure the design? I think its in Fibaro interest to participate themselves also? Best Regards
  19. Is anyone have experience with setting up garage door device built on smart implant + hc3? Currently it works perfect in my setup but looks like simple light switch, so i looking for any suggestions to turn it to garage door.
  20. Hi, I really need some help. I have 2 soil moisture probes wiring in correctly (I believe) into the RGBW unit. Using a multi meter between the ground an IN1 & IN2 i get 3v and 8v readings. My problem is that no matter what setting I use in HC3 the preview window for each channel always reads zero. Have I got the wrong end of the stick? Please help me! Thanks, mike.
  21. Hi All, I have been searching for a while now on the forum, but have not find the solution to my problem. We do have the danalockV3 and the Fibaro intercom. Both device can be found in the HC3. Now the problem is that when we try to open the Danalock trough the intercom or in a scene, the Danalock doesn't respond to it. If i look in the recent history of the HC3, i can see that the scene has run. As well there is a action that is called Action: Device polling. Does anybody know how i can fix this? Happy to hear your answers. I am new in this world so please be free to ask me if you need more information. Greetings, Thomas
  22. If I restore a dead device connected to the HC3 through the mobile app. Then the device recovers immediately after the push of the button. But if I do the restore by code (in a HC3 QuickApp) then the device does not restore. I use (wakeUpDeadDevice(deviceID)) for this. local parentID = 201 fibaro.wakeUpDeadDevice(parentID) fibaro.sleep(1000) fibaro.call(parentID,'turnOn') Is there any other code similar to the code the mobile app uses?
  23. Hello, I'm trying to "convert" this LUA script in a scene, but my trouble cames from the fact that I don't know how to send an http request in a scene. Here is the script I use in a device (and it works find): local texte = string.format("%s %s", tostring(os.date('%H:%m', os.time() )), "HC3 : This is a test.") local address = string.format("http://192.168.0.0/write?color=%s&bg=%s&t=%s", "black", "white",texte) http:request(address, { options={ method = 'GET' }, success = function(response) print(response.data) end, error = function(error) self:debug('error: ' .. json.encode(error)) end }) The goal, is to send a time stamped notification in a remote web server when a scene is launch, but maybe I'm on a wrong way ? Thanks for your help. Alex.
  24. Configuration: - RGBW led strip connected to RGBW 2 controller + monostable (GIRA) wall switch - HC3 - Fibaro iOS mobile app System by default use "white" colour through mixing only RGB channel from RGBW led strip and white (W) chanell is not use (turned off) . If you want to use white colour from your RGBW led strip you have to define white colour ( #000000) by yourself in fibaro web application. All is fine if you are use such a configuration and use only wall switch. When you changed led colour (i.e. yellow, magenta, blue, green or whatever) through mobile application you will not be able turn on/off led light with your wall switch. It doesn't work any reaction from led strip To "fix" this issue you have to login to web application and choose once again earlier defined white colour ( #000000). Have you ever meet such a problem/bug ? Thank you
  25. Version 1.0.0

    346 downloads

    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 .
×
×
  • Create New...