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



More search options

  • 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

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

Found 38 results

  1. Hello to all, I am pleased to announce that the quickapp "Sonos Zone Controller" is now available (This is a first fully rewritten version based on my HC2 Sonos Remote VD) Current version: 1.1.1 Date: 03/05/2020 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") 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 Performance improvement when initiating a playback & Improved track information Support for saved playlists (saved queue list) Support for PlayMode Support for Queue fonctionnalities Support for LineIn and TV source (if supported by device) Support for multi-devices in group used for triggering in scene and prepare for group-ungroup Support for EQ (treble & bass) Support for Group Support for TTS (TextToSpeech)
  2. knuth

    HC3 LUA vs HC2

    In making the transfer from HC2 to HC3 based on a cloud backup (update 4.581 Beta) it is stated that "scenes will not be moved and need to be created again". That's OK, but it would be helpful when planning the transfer to know what the differences are (in syntax and available functions) between the two LUA versions. I know that the new LUA editor is documented in https://manuals.fibaro.com/home-center-3-lua-scenes/ . What I would hope to see in addition, is a side by side comparison of all the crucial differences, to enable a pre-edit of the old LUA scenes before entering them into the new editor. Something like this: If you used this in HC2 LUA: You need to do this in HC3 LUA: fibaro.debug("txt") fibaro.debug("tag", "txt") os.time() ??? etc. If we all contribute to such a table as we identify all the differences, we may be able to help each other prepare for HC3. Not all differences can easily be summarized in the simple two-column format above, however. For the new definition of conditions and triggers, it seems it would be more appropriate to give a few examples of old codes (with triggers) converted to new codes. PS: I haven't even decided to buy the HC3 yet! But getting a feel for the amount of re-programming needed to convert my scene is an important factor in making that decision. The suggested table is now shown in a pdf file attached to this post, see below. It is regularly updated as new contributions are posted. LUA HC2 vs HC3.pdf
  3. A thread to share some coding techniques for QuickApps? Because QD's 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 QDs. 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 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... 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 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...
  4. Hello, Can anyone tell me how changing, from a QA, the devices parameters? I do have a Neo CoolCam Siren + a Aeon Labs one that I would like to configure from a QA before ringing it. The idea is to configure it to a gentle music when someone ringing, or as an horrible sound in case of breach or security alert I do have tested this, which was natural but that has no impact on the device parameter: function QuickApp:uionOnReleased(event) local deviceID = 292 fibaro.call(deviceID, "setParameter", 37, 2, 1) -- Device 37 | byte syze: 2 | expected value:1 end I have tried to adapt former VD code from HC2, but no way to adapt it local selfId = fibaro:getSelfId(); local port = fibaro:get(selfId, 'TCPPort'); fibaro:debug(port) HC2 = Net.FHttp("127.0.0.1", 11111) jtable = '{"properties":{"parameters":[{"id":1,"size":1,"value":1}]}}' HC2:PUT("/api/devices/" ..port ,jtable) and i'm then stuck looks like i'm sharing the issue (or lets call it "question") with @FBerges Thanks in advance for any recommendation or QA example have a good week end
  5. I have moved to the HC3 and trying to work out how the LUA programming works. The HC2 programming seemed a lot more logical and I am struggling to work out how to convert some of my old routines over. One of the first routines is remotes. Setting this up by blocks wouldn't work as it looks like I'd have to setup a scene for each button for each remote. Could someone help tell me how to convert this simple program into a HC3 computable version? --[[%% properties13 sceneActivation%% globals--]]local buttonPressed = fibaro:getValue(13, "sceneActivation")if ( tonumber(buttonPressed) == 1) thenfibaro:debug("MiniMote button 1 pressed")elseif ( tonumber(buttonPressed) == 2) thenfibaro:debug("MiniMote button 2 pressed")elseif ( tonumber(buttonPressed) == 3) thenfibaro:call(4, "turnOn")fibaro:debug("MiniMote button 3 pressed - Light ON")elseif ( tonumber(buttonPressed) == 4) thenfibaro:call(4, "turnOff")fibaro:debug("MiniMote button 4 pressed - Light OFF")elseif ( tonumber(buttonPressed) == 5) thenfibaro:debug("MiniMote button 5 pressed")elseif ( tonumber(buttonPressed) == 6) thenfibaro:debug("MiniMote button 6 pressed")elseif ( tonumber(buttonPressed) == 7) thenfibaro:debug("MiniMote button 7 pressed")elseif ( tonumber(buttonPressed) == 😎 thenfibaro:debug("MiniMote button 8 pressed")elsefibaro:debug("No response")end Thanks
  6. Hi All, Please guide me to right way to get args in scene on HC3 HC2 code to get scene args was: local args = fibaro:args() on HC3 it not working now Tried: local args = fibaro.args() -> got error: attempt to call a nil value (field 'args') local args = fibaro:args(). -> got error: attempt to call a nil value (method 'args') LUA editor don't show any functions containing "args".... Help, please... Thanks
  7. 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 QDs offline and have made a fibaroapi.lua file that can be included to emulate the fibaro calls and call out to the HC3. fibaroapiHC3.lua: fibaroapiHC3.lua (v0.98) The code is updated weekly so please make sure you have the latest... It's similar to the old fibaroapi for the HC2 in a thread started by @riemers but with more extensive support to create a better "offline experience"... 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 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. 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. 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. 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. And lastly, it makes it fun to develop code for the HC3 To get going define hc3_emulator.credentials = {ip=<HC3_IP>, user=<username>, pwd=<password>} and include dofile("fibaroapiHC3.lua") An example can look like if dofile then dofile("fibaroapiHC3.lua") hc3_emulator.credentials = {ip="192.168.1.X", user="<user>", pwd="<password>"} end function QuickApp:onInit() fibaro.call(88,"turnOn") -- turns on device 88 on your HC3 end if dofile then hc3_emulator.start{ -- Start emulator poll=1000, -- Poll for triggers from the HC3 every 1s } end We wrap the emulator specific stuff inside "if dofile 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. 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.95) 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.emitCustomEvent(name) fibaro.wakeUpDeadDevice(deviceID) fibaro.sleep(ms) net.HTTPClient() net.TCPSocket() 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) <mqttclient>:addEventListener(message,handler) <mqttclient>:subscribe(topic, options) <mqttclient>:unsubscribe(topics, options) <mqttclient>:publish(topic, payload, options) <mqttclient>::disconnect(options) plugin.mainDeviceId class QuickAppBase class QuickApp class QuickAppChild 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='device', id=<number>, property=<string>, value=<value>} {type='global-variable', property=<string>, value=<value>} {type='date', property="cron", value={ <time> }} {type='date', property="sunset", value={ <time> }} {type='date', property="sunrise", value={ <time> }} {type='manual', property='execute'} {type='custom-event', name=<string>} {type='device' property='centralSceneEvent', id=<number>, value={keyId=<number>, keyAttribute=<string>}} json.encode(expr) json.decode(string) fhc3_emulator.start{ -- start QuickApp/Scene id=<QuickApp ID>, -- default 999 poll=<poll intervall>, -- default false. Interval i ms to poll for new rigger from the HC3. 1000-2000 is reasonable... type=<type>, -- default "com.fibaro.binarySwitch" speed=<speedtime>, -- default false proxy=<boolean> -- default false. Creates a proxy on the HC3, ignore id. quickApp=<boolean> -- default false. Connects to an existing quickapp on the HC3 with given id UI=<UI table>, -- default {} quickvars=<table>, -- default {} loadDB=<boolean> -- If true tries to load resource database (only if offline==true) } hc3_emulator.createQuickApp{ -- creates and deploys QuickApp on HC3 name=<string>, type=<string>, code=<string>, UI=<table>, quickvars=<table>, dryrun=<boolean> } hc3_emulator.createProxy(<name>,<type>,<UI>,<quickVars>) -- create QuickApp proxy on HC3 (usually called with fibaro._start) hc3_emulator.post(ev,t) -- post event/sourceTrigger hc3_emulator.offline = <boolean> -- Set to true in beginning of file if running simulated devices.. hc3_emulator.createDevice(deviceID,deviceType) -- Create an offline device of a given type. When offline device are also autocreated of type binarySwitch. More doc on this is coming hc3_emulator.copyFromHC3() -- Downloads resources from HC3 and stores in HC3sdk.db 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 ("ssl.https") require("socket.http") require("socket") require("ltn12") They are pretty standard lua libraries - based on LuaSocket. If someone manage to get it running in VisualStudio I would be interested to know. Any improvements are happily received (in code) and credits will be due granted. Links to notable post 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. 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. A 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)
  8. Hi, i add Aeotec multisensor 6 to my HC3 but it seems not working properly. I try to add and remove 3 times. After installation "wake up interval" is set to 0s and i cant change it. Automatic updates working only for PIR sensor. Temperature, luminance, humidity, uv is not auto updated at all (now for almost 10 hours). I setup thresholds to low values and manual wake up device to sync this settings. Nothing help ... Even threshold for temperature is impossible to change to normal value (eg. 1C). Default value after installation is set to 131097.6 C and after change and sync is always reset to this value. Have someone similar issues with Aeotec multisensor 6? It is device or hc3 related problem?
  9. Hi, has anybody experienced issue with Wall Plug device working fine in Devices List on HC3 (being able to switch ON/OFF, see power consumption) but cannot choose the device in Block Scenes as it is not listed as device in the room?
  10. Function Request: Within block scene, it would be good to have the option within Simple Message Block to select: Log Output as a drop down within Simple Massage Output type: Debug, Error, Warning, Trace Message This will allow people to send a message into the Log during the flow of the Block Scene.
  11. I can't get a scene to work if I add a time interval. It looks ok but is not working and I don't know what I do wrong. It works if I remove the Time Range block... Please help!
  12. I want to activate a manual scene (Vaatwas Timer (number 2 in the picture)) with my ZRC-90. In this case I created a scene (Timer Vaatwas Active (number 1 in the picture)) that should activate the manual scene "Vaatwas Timer". The scene “Vaatwas Timer” is a manual scene and set to a certain time. I do not want this scene to be active every day at the programmed time and therefore I only want it to be active after I push and hold button 8 on my ZRC-90. As soon as I push button 8 the other scene is activated and does not wait until the time that is set in the scene. What do I need to do so that when I’ve pushed the botton, the scene “Vaatwas Timer” is active but not triggerd and turns on my dishwasher immediately. Short: when I hold down button 8 on my ZRC-90 I want my dishwasher (connected to the powerplug “Vaatwas PP2") to start at 23:30 the day I push the button and not immediately Button 8 hold --> activate Scene "Vaatwas Timer" --> Scene starts dishwasher at 23:30 as set in the scene
  13. After adding Aeotec multisensor 6 to the HC3 the HC3 recognizes the Aetec MS6. The MS6 does not send any values. All remains at 0. HC3 does come up with a template for the parameters however changing the parameters is impossible, they remain at 0. Thanks, Willem Bousema Switching from HC2 to HC3
  14. Witajcie, czy może ktoś pomóc w konfiguracji kamery w HC3. Po wpisaniu adresu w całości w przeglądarce działa bez problemu. Po skonfigurowaniu kamery w HC3 występuje błąd: Jak wciskam link poniżej obrazu to otwiera mi się normalny obraz z kamery. Konfiguracja wygląda tak: Kamera to Dahua.
  15. 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
  16. Hi, Would like to have a quickapp that would enable me to start or stop a scene with a button. I tried fibaro.scene("execute", {id}) or fibaro.scene("kill", {id}) But it doesn't work and don't stop and restart the scene. The scene i want to trigger or stop is a move detection in a room to start ligne. I would sometime like this automation not being activated and stop from a QA that is controling all room parameter. thanks for the support
  17. Hello, After a parameter change of a MultiSensor the 'busy indicator' kept circling without saving parameters so I rebooted the HC3. After the reboot all Leds on the front of the HC3 are solid copper except for the Security LED that is blinking. After that manual reboot my HC3 is not visible anymore in software. Nowhere. - Not in the Fibaro Finder - Not in the DHCP Client list of my Router - In the Fibaro Remote Acces website ( https://dom.fibaro.com/cmh/home-center/list) it is visible but in Red with a red cross icon. - In the HC3 configuration interface (COMPONENTS.DEVICE-LIST.MAIN-HEADER.LOCAL-LIST) nothing appears (icon keeps rotating). The procedures in the manual are not clear for me: -1- Using the (+) Recovery button it says "Put in Recovery mode". I did this but how can I see/know it is in recovery mode when I have no User Interface? -2- Hold for xx seconds when network-icon and wif-icon are blinking = they never blink except during startup. They also do not blink after holding the (+) button for 20 s. This means I do not get a change to reset the network settings or switch between Dynamic and static IP. Because the IP address stays invisble I can not find a way to do a factory reset because I have no User Interface. Can someone help me to get my HC3 up and running again? How can I factory reset the HC3 when I have no interface at all? Thank you in advance for your support.
  18. For watering our plants I develop a Virtual Device with HC2 using control buttons to open a valve during 15, 30, 45 and 60sec. I also had a emergency STOP button to close the valve immediately within the same VD. When I reproduce the same with HC3, it is not possible to call the STOP button (interrupt) untill the watering in progress is not completed. Any help? (and not entionning those buttons are not displayed on the portable Android/IOS...)
  19. New HC3 on its way: Do I Migrate my HC2 via the transfer process or setup everything from new? I am sure many people are asking what are the pro's and con#'s of each route: Migrating Pros - Known: Sections, rooms and icons will be migrated Z-Wave devices assigned to the rooms and their icons parameters of these devices Cameras not created via plugins associations Migration Con's - Won't be transferred Scenes plugins virtual devices cameras via plugins schedules (watering & climate) Questions: If a device is transferred, does HC3 tell the device to use 500 series communications automatically and will HC2 put the device in secure mode? (All my Heating Controllers (Fibaro Thermostats) are not in secure mode as you cannot upgrade if they are in secure mode Can I force Secure mode of a device that is transferred or do I have to remove it and re-add it to enable secure mode? Are my LUA scenes compatible (Cut and Paste [Changing deviceid as needed] from HC2 to HC3)? What are the other Pro's and Con's people have seen? Any pit-falls to watch out for?
  20. Hi all, is anyone of you using an HC3 (Version 5.030.45) and able to add a Fibaro Walli Dimmer? When I start the inclusion on my HC3/ Walli Dimmer I only get the following message in the log and one new Device (191) without any child devices...so I'm not able to control the dimmer. [13.04.2020] [15:08:36] [TRACE] [ZWAVE]: Home Center in learning mode [13.04.2020] [15:08:50] [TRACE] [ZWAVE]: Device added[13.04.2020] [15:08:50] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [13.04.2020] [15:08:53] [TRACE] [ZWAVE]: Requesting neighbours done. [13.04.2020] [15:08:53] [TRACE] [ZWAVE]: Add node status protocol done [13.04.2020] [15:08:54] [TRACE] [ZWAVE]: Adding devices complete I'm wondering if this is a a Problem with the HC3 or if the Walli Dimmer is broken in some way. Thanks Cheers and happy Easter
  21. How can i stop propagation of current scene. Eg. if luminescence is not high enough for some action i want to stop otherwise continue. local lum = fibaro.getValue(88, 'value') if lum > 50 then -- return, exit, quit, fibaro.kill() ... something to end propagation of current scnet end -- rest of code here ... EDIT: in Home center 3
  22. Hi, is there a way to export (for backup purposes) scenes? All scenes or just Lua scenes would be enough for me.
  23. cag014

    HC-WebEye

    Version 2.0

    154 downloads

    This is JavaScript code, which displays debug information (in parallel to code development) at full screen on desktop (supports HC2 and HC3 controllers) Main purpose is to support scenes where debug information is in HTML format, like All-in-One Scene, Z-wave monitor/viewer, Z-Range analyzer . All other formats will be displayed in same format as in debugger window. Since HTML format is not supported by HC3 and debugger window is too small, it could be a helpful alternative for better view and debug your code. In many cases variables values include a lot of information (like jSON table) and it couldn't be reviewed by HC interface, this application offers to display Global variables (including QuickApp variables) on "big" screen. Follow information and features are supported: Display debug information of selected scene. (HC2) Display scenes debug information filtered by messages tags including levels (trace, warning,error). (HC3). Note: Currently all scenes print info in same debugger. Issue reported to Fibaro Group - in Progress. Start scene. (HC2/3) VD main and buttons' debug information. (HC2) Select and Press VD button. (HC2) Display current value of selected global variable. (HC2/3) QuickApp debug information. (HC3) . Note: Currently when debug info is loaded it clears debug info from HC3 debugger window. Display current value of selected QuickApp variable. (HC3) Turn On/Off (toggle method) QuickApp (HC3) Select and Press QuickApp button. (HC3) Note: Since HC3 doesn't support HTML format anymore, this is the only option to view and analyze information on upcoming All-in-One Scene and Z-wave monitor applications. After downloading the file please remove .txt extension. Currently supported browser are Firefox, Chrome or IE browsers. Recently Java Scripts are blocked by Cross-Origin Resource Sharing (CORS) mechanism, please download Disable CORS file for further instructions how to disable CORS. How it works: Before execution, open the file to define HC IP-address and HC3 transfer protocol at User Configurable Parameters // ============= USER CONFIGURABLE PARAMETERS ================ var hcip={"HC3":"192.68.0.10","HC2":"10.0.0.69"} var protocol={"HC3":"https"} On first run, login information will be required. (To keep your credentials secured, login data is not stored in file ) Application interface is very simple and self-guided. Select controller: HC2 or HC3 Select item : Scene, V Device, Variable, QuicpApp... Select item of previous selected section. Press "Reload" button to load debug information. By checking debug checkbox, API executed commands are shown. 1. If scene selected "Start" button appears. 2. If V Device selected list of available buttons shown and "Press" button appears. 3. If QuickAppDevice selected, list of available buttons shown. "Press" and "Toggle" buttons appear. By pressing "Toggle" button, QuickApp will turned ON or OFF in sequential order. 4. If Variables selected,list of available variables shown. By selecting the variable, his current value displayed.
  24. Hi, Having recently purchased a HC3 to 'upgrade' from my Vera 3 controller I am now starting to get ready to transfer my devices (95% of them are Fibaro) across to the HC3 manually. I have successfully setup the HC3 and updated the software and it runs well. I have included a few spare devices, switches, and dimmers to familiarize myself with include exclude process. My Vera setup has 4 RGBW controllers on it running block scenes (I'm not a programmer yet!!) all working well. I have purchased several RGBW2 controllers for additional rooms in my house. So, after the latest software update to the HC3 I decided to connect one of the RGBW2 controllers. I assumed it would work like the RGBW on Vera controllers. In as much as I do not have any switches connected and control them through the app or a scene. I have added the RGBW2 and find that I cannot get any of the LED strip to turn on (unless I momentarily connect ground to one of the 4 inputs) in which case all the colours and white are correctly functioning (hardware eliminated). My understanding was that I could choose from the predefined or my own (I was able to add) colour palette or run one of the pre-defined scenes storm rainbow etc. I am confident the devices installed correctly is there a test I can run? I notice that even when I triggered the lights manually by bridging the inputs to ground no power in watts was showing? Unfortunately, I do not yet have another module included on the HC3 that reports power they are all older dimmers or switches. Is this because of configuration? I do have a few questions do I need to setup default parameters on the RGBW2 module? I did try changing some of the parameters as per the manual but my HC3 doesn't seem to accept this and I just getting a spinning wheel when it is trying to update. If anyone can put me in the right direction to get started even if this is by reading and understanding I am prepared to invest my time. I have just been investigating this further and I think that the issue is maybe because both the RGBW2 devices that I have included onto the network have all their parameters set to 0. looking at other modules I have included shows that they have what looks like their default set of parameters. However manually selecting the default value for each parameter just gives me a spinning wheel see above. Update: After doing another reconfigure, I left the module overnight this completed successfully. However, all parameters are zero! Although it appears in the android app as expected and responds and selects the scene / colour brightness etc. One unit I could maybe suspect as faulty but two brand new units behaving identically - No. Can anyone suggest a way of sending the parameters? Thanks,
  25. Hi everybody, I seem to be stuck in my search how to implement a (large) mobile popup, triggered in a LUA scene in HC3. I found this example for HC2: https://manuals.fibaro.com/knowledge-base-browse/how-to-create-mobile-pop-up/ This is actually what I want to create, a large popup with buttons and actions connected to it. But the example (obviously) does not work in HC3. I am using the following code and the fibaro.homeCenter.notificationService.publish function with type set to MobilePopupNotification as described in https://manuals.fibaro.com/home-center-3-lua-scenes/ local function popupMessage(message) local request = { type = "MobilePopupNotification", priority = "warning", data = { title = "Door(s) Open", text = message, } } local response, code = fibaro.homeCenter.notificationService.publish(request) fibaro.debug("Scene109", json.encode(response)) fibaro.debug("Scene109", code) end The debug responses are: for response: {"data":{"title":"Door(s) Open","buttons":[],"text":"Alarm in kelder en begane grond armed"},"created":1586512755,"type":"MobilePopupNotification","id":208,"priority":"warning","wasRead":false,"canBeDeleted":true} for code: 200 My Notification page in the web interface displays the warning as "Notification title" but no mobile notification is received. I also had this scene running with fibaro.alert() but that did not give me the desired large popup, only a smal one with limited text and not button options. BTW: I couldn't get the button functionality to work in any way. Tried arrays, objects, array of objects, object of objects etc but always got an error code 400 or simply a load error code ((load):34: unexpected symbol near '[') So, can anybody point me in the right direction, or tell me if what I want is possible in HC3? Thanks a lot
×
×
  • Create New...