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



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 24 results

  1. Version 3.1

    2,005 downloads

    Philips HUE AIO VD v3.1 (standalone version) With Philips HUE preview VD v1.1 - brings easier setup and support for multiple Philips HUE bridges INTRODUCTION Philips HUE lighting brings colorful way of lighting experience. More about this lights you can find here https://www2.meethue.com/en-us Philips HUE AIO VD is All In One solution for HC2 owners to control Philips HUE lighting with support for all types of HUE lamps made by Philips and some other manufacturers. PREREQUISITES Fibaro Home Center 2 with firmware 4.120 or greater (tested up to 4.540) Philips HUE bridge V1 (round) with firmware up to 01041302 (released 05 February 2018) or Philips HUE bridge V2 (square) with firmware up to 1901181309 (released 07 February 2019) FEATURES Consists of two VD's: Philips HUE Preview VD which connects to Philips HUE bridge and downloads information of all lights and groups of lights and greatly simplifies installation of Philips HUE AIO VD that controls individual HUE bulbs or group of bulbs. Also added unreachable icon for Philips HUE bridge v1. Philips HUE Preview VD has button for generating authorization username and for easy connection to Philips HUE bridge Support for multiple HUE bridges and most of the Philips HUE bulbs including bulbs from other manufacturers that can be connected to HUE bridge. HUE AIO VD recognizes different types of bulbs like multicolor, white ambience and dimmable and enables proper controls Can control brightness, hue, saturation, color temperature and transition speed that can be set from instant to 10 seconds duration Buttons to activate colorloop efect and Alerts Multilanguage support with 27 languages included. VD's can use HC2 selected language or user can select any other available language. VD will be automatically translated to the selected language (visible after refreshing page on browser or refreshing network data on Fibaro mobile application) Easy setup for VD icons that will also setup icons for all buttons and sliders of the VD. (on UHASTM compatible version is even more easier to setup VD icons with Icon Preview VD) On HUE AIO VD user can setup separated on and off button or have on/off toggle button Self adding of global variables needed and global variable data integrity checking Automatic repair of global variables without user intervention New approach to programming other code to control this VD enables future upgrades without needing to change that code. (See more about that in User Manual provided) INSTALLATION Please check provided User Manual where all steps are explained in detail and this video made by @MarcoTorino71: PACKAGE CONTENT Philips HUE Preview VD v1.1 standalone Philips HUE AIO VD v3.1 standalone Icon pack Philips HUE E27 bulb indoor Icon pack Philips HUE E27 bulb outdoor Icon pack Philips HUE GU10 bulb indoor Icon pack Philips HUE GU10 bulb outdoor Icon pack Philips HUE LED strip indoor User Manual v1.1 EN CREDITS Many thanks to BodyArt, gucio1234 and many other Fibaro forum users for help with testing, translations and user manual. TERMS AND CONDITIONS Permission to use, copy, modify and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement is hereby granted, provided that the copyright notice, with "Terms and conditions" and "Disclaimer" appear in all copies, modifications and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author. DISCLAIMER This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. Fibar Group S.A. and their employees are not responsible for support of the Philips HUE AIO VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required. LEGAL NOTICE HUE is registered trademark of Philips Lighting Holding B.V. registered internationally. LATEST NEWS 1 April 2019 Philips HUE bridge firmware new version 1901181309 is out. If you upgrade to this latest firmware Philips HUE AIO VD will continue function properly. VERSION HISTORY 3.1 - Corrected bug that was causing HUE AIO VD main loop to stop with error if user set light or group ID that does not exists on HUE bridge. Also corrected bug that was not updating list correctly after first scan if user removed or added light or group on HUE bridge. 3.0 - All In One solution, one VD for all types of bulbs and for control of individual light or group of lights with supporting Philips HUE Preview VD. 2.1 - added Philips HUE White dimmable VD of same version as color version. 2.1 - Corrected error handling when HUE bridge is not reachable. 2.0 - Added On/Off button; two version available: 2.0m with Main loop refresh or 2.0b with button refresh for systems with more than 15 HUE lamps to improve response and reduce network traffic; changing brightness, color or Saturation sliders now immediately refreshes VD status; code improved so users can easier setup necessary data 1.5 - Added sliders for color (hue) and Saturation, VD is now getting ID & TCP port setting from VD general tab 1.0 - Changing icons based on the brightness level, Changing icons based on HUE lights state (unreachable/error); Error handling for HUE response data, status information in the bottom bar of the VD; detailed comments in LUA code, main loop refresh code added Here is a new look of Philips HUE AIO VD and companion Philips HUE Preview VD: Enjoy coding and your new Philips HUE virtual device! Sankotronic PS This solution is only for HC2. If you have HCL then please check @AkilliYuva.com solution here:
  2. 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 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 HueMain20200928_255.fqa 2. Icons: Icons20200928.zip
  3. Version 1.0.0

    6,142 downloads

    Some of the standard icons i customised to get a better look and feel for my HC2 - - - - - 11.07.2018 - adding some new icons for a unicorn led lamp - - - - - - - - - - 29.08.2018 - adding some new icons for different temperatur sensors - - - - - Some icons for the on/off state of different devices i used with a Fibaro Wall Plug Icons for a Bora BIA extraction hood Icons for a MCO MH7 Different icons and colors for a Philips Hue Iris black or if somebody used the older Philips LivingColors (clear/black) Unicorn led lamp (an upcoming project) Different combination of alertings Some states of the day Fibaro CO Sensor Fibaro Smoke Sensor Fibaro Flood Sensor Fibaro Motion Sensor Some other temperature sensors
  4. Guest

    Very Smart Lights scene

    Version 1.4.3

    2,713 downloads

    Very Smart Lights™ v1.4.3 Hello everyone! I am so excited! Very Smart Lights™ scene just get smarter!!! Thanks to all of you for valuable feedback and requests! We are listening and acting! So here it is, completely rewritten, smarter, better scene to control your home lighting! NEW UPDATE v1.4.3 (09 Apr 2019) This update brings support for Philips HUE AIO VD v3.0 standalone! I have updated instructions for setting up HUE AIO VD in scene code and also I have optimized a bit code. This scene can still work with HUE VD old versions but I humbly recommend upgrading HUE VD to the latest version. UPDATE HISTORY 1.4.2 (11 Jan 18) Two updates in one day! In v1.4.2 corrected code for HUE plugin lights. Problem was that scene was turning on HUE plugin lights at brightness 1 even brightness was set to 0 to keep them Off. Thanks to @shingoo for pointing out this bug! 1.4.1 (11 Jan18) - Corrected bug that was causing scene to stop working if RGBW lights are controlled and useIndoorLights and indoorLightsDim where set to Yes. Many thanks to @AndrewB82 for reporting this bug! 1.4.0 (20. Jan 17) - What is new: Darkness is not used anymore for turning On lights and dim low levels. Only TimeOfDay is now used for that purpose. Added support for different types of Philips HUE light VD. Scene now supports HUE color ambience, HUE white ambience and HUE white dimmable only bulbs and VDs. Also added support for customized HUE VD. Support for HUE plugin remain same. It is now possible to mix different types of HUE VD since now you have to define VD type for each HUE light. Ambient color settings can now be stored also for White ambience bulbs. Also added default color setting for this bulbs! Added two new global variables for Cooking and for Mealtime that can be used to define different brightness levels and to keep lights On as long as this variables are set to Yes if added to extraGlobalName. Corrected dimming of RGBW lights when useRGBWcolor is set to Yes. Also RGBW lights will now turn on when dim low is set on defined settings. Corrected duration timer compensation with PIRwindowTime. Now is properly calculated and warning displayed if duration setting is lower than PIRwindowTime. Now lights will always turn on for the duration of motion sensor breach time. Corrected scene behavior when PresentState and SleepState are changed. When PresentState is changed to Home or Holiday scene will turn on lights when motion is detected or dim low if set for that part of day. Same is when SleepState change from Sleep to Awake. When PresentState is set to Holiday scene can be controlled by global variable triggers Global variable SleepState added to scene header global triggers so now scene will turn Off or dim low lights when SleepState is set to Sleep or turn on or dim low lights when set to Awake! It is not needed any more to manually run VLS scene to do that! Completely rewritten code for turning On/Off lights and added error handling so now you will know if there is some mistake in settings for quick correction. If you don't use special condition for HolidayLights then you don't need to setup flags anymore. If any of special conditions is not used like IndoorLightsDim and use is set to No then you don't even need to add this global variable to variable panel! Added debugging for lights handling so if there is any problems you can turn lightdebug to true and see how each light is controlled and what brightness setting is used for each defined light. Refined other debugging messages and added more colors for easier reading and fault finding. 1.3.5 (09. Jan 17) - Corrected that scene turn off switch lights if user set valSWT to 0. Corrected that scene turn off RGBW lights if program is running or color is enabled if dimRGB is set to 0. Added ProjectorState global variable that can be used to additionally setup lighting for movie time with projector. So now you can have two different setup to watch movies! Don't forget to put CinemaState and ProjectorState to extraGlobalName to keep lights at predefined values! 1.3.4 (09. Jan 17) - resolved bug for keepDimSleep setting that logic was reversed. Now if set to true will keep lights dimmed and false will turn them off when SleepState is set to sleep. Rectified situation when scene not turning lights on at all if not using light sensors. Corrected dimOff logic to properly dim or turn off lights depending on settings. Cleaned code of some other bugs found during testing. Also removed ™ and © symbols from code because some users reported trouble with these on Windows 10. 1.3.3 (06. Jan 17) - resolved bug that was preventing extra timer using jompa68 Alarm clock from proper functioning. Extended dimOff function so now lights can be dimmed low during all day and also all night regardless of SleepState depending on your settings. Corrected scene behavior when sleepingName and PresentState global variables value changes and added debugging messages. 1.3.2 (30. Dec 16) - Added support for latest version of jompa68 Alarm clock 3.0.0. Added possibility to define two different dimming levels for Evening and Night time if there is no movement in room and lights are set to dim instead switch off. Corrected bug for turning on RGBW lights if program and color set to No. Added some basic checking of user settings if HolidayLights flag, Brightness and dimOff values are missing. Corrected how scene handles ambilight settings. dim and off ambilight changed to one setting dimOffAmbilight and it must be set to Yes to use settings. keepAmbilight is just setting if you want to keep color when motion detected or use defalut colors. Even if you do not keep colors while in room they will still revert to color when no movement detected. 1.3.1 (25. Dec 16)- Corrected usage of dimAmbilight and offAmbilight so that only color and saturation is remembered while brightness is set by scene setting corrected Alarm clock timer to check if it is turned Off to not keep lights on. 1.3 (First public release) - Added ambilight selection so that scene remembers previous status of the HUE lamps to dim back when no motion in the room, or even leave settings after turning them off. It is also possible to select if HUE lamps will raise brightness in ambilight colors or to default settings when there is motion in the room. Now every lamp can be set to different light level for every used situation like (hoilday lights, guests, cinema, etc.) and for every part of the day. SCENE DESCRIPTION You need one copy of this scene for each room or space. One room can have two scenes if needed to control two different groups of lights, but one scene is not supposed to control lighting in more than one room! Here is short description (new 09. Jan 17, thanks to @clowg): How it works: This scene uses Darkness and TimeOfDay global variables to change brightness of the lights when there is motion in the room and same times to dim lights when there is no motion if that option is turned on. TimeOfDay can have four different values Morning, Day, Evening and Night. Darkness can have two values Light and Dark. They both change values according to sunrise and sunset times and are very important for proper functioning of VSL scene. I recommend installing Main scene for time based events control with Sunrise & Sunset virtual device to ensure proper handling of this two important global variables. More info about Main scene you can find on provided link. You do not need to change the LightStatus, nor times when Morning, Day, Evening and Night starts. Once these values are set, the Main scene will move those times according to the sunrise and sunset times. Day duration is changing throughout the whole year and the Main scene and Sunrise & Sunset VD will make sure that everything else is following these times! SCENE SPECIFICATION SCENE IS CONTROLLED BY ANY NUMBER OF MOTION, LIGHT AND DOOR/WINDOW SENSORS AND GLOBAL VARIABLES - With this scene lights can be controlled by any number of motion sensors, light sensors, door/window sensors and global variables that can be mirror of the motion sensors from other alarm systems or used to mimic lights while you enjoy your vacation. - Light level (lux) is calculated if used more than one light sensor. - If lights are turned On but lux level reaches turning Off threshold then lights will turn off no matter what other condition keeps them on (motion, extra devices or globals, extra timers). LIGHT DEVICES THAT CAN BE CONTROLLED Tested and can control any number and any combination of this types of light control devices: 1) Philips HUE virtual device - pls check --> Philips HUE Color & White ambience VD 2) Philips HUE plugin 3) FIBARO Dimmer 2 4) FIBARO single/double switch 5) FIBARO RGBW module including programs, color RGB/RGBW and white only 6) FIBARO smart plug Not tested but can possibly control devices from other manufacturers. (need your feedback!) For FIBARO RGBW module you can define seven different programs for each day of the week and time of day when you want program to be run. LIGHT BRIGHTNESS AND DURATION CONTROL Light brightness for each individual light can be set and duration (ONLY ONE FOR ALL LIGHTS!) can be defined by these conditions: 1) Guests time 2) Cooking time 3) Mealtime 4) Projector movie time (NEW v1.3.5) 5) Cinema time 6) Holiday time 7) Indoor lights time 😎 Sleep/Awake 9) Time of day All this states can be fully configured or just switched off and use only Time of day condition. EXTRA DEVICE AND/OR GLOBAL VARIABLE CONDITION CHECK Extra device value or/and power consumption and global variable check gives you ability to disable switching off lights for as long as status of device and/or global variable meets defined value. For example: 1) If working table smart plug consumption is greater than 10W then keep lights on 2) if bathroom door is closed then keep lights on 4) if TV is on can be checked by global variable status or smart plug then keep lights in living room on and dimmed. 5) if outside is day but overcast and/or raining then set global variable and keep lights in kitchen always on EXTRA TIMERS User can define extra timer that will keep lights on for predefined time. For example you can keep light on for defined time eg. 1 hour after alarm clock wakes you up. Control is done by using alarm clock global variable setting. TIMER TO TURN ON ANY DEVICE/SCENE/CHANGE VALUE TO GLOBAL VARIABLE AFTER PREDEFINED TIME Scene has timer that can start up any number of devices and/or scenes and/or change global variables value if it is running longer than predefined time. For example if you stay longer in bathroom so scene is running longer than 5 minutes then it can start up extraction fan and also start scene that will stop fan after predefined time and also after 10 minutes in bathroom change global variable value which will in return send push notification to your loved one that you are currently really busy INSTALLATION GUIDE Please check this video made by @MarcoTorino71: Since I did a lot of comments and instructions in scene itself what and how to setup I will just use some examples here to give some more information. But first of all there are some global variables that must be added to global variable panel before scene can run correctly so here they are: GLOBAL VARIABLES DEFINITION All following global variables are predefined global variables to be added in lower part of variable panel! Possible values can be set in your language and then mapped to values in english used in scene code! 1) TimeOfDay - possible values "Morning", "Day", "Evening", "Night". This global variable value is controlled by Main scene for time based events control. TimeOfDay condition will be override by all conditions bellow. If useTimeOfDay is set to "No" then you need to setup Awake brightness settings. 2) PresentState - possible values "Home", "Away", "Holiday". This global variable value is controlled on my HC2 with scenes that are run when we leave or come back home. Those scenes are actually responsible for more actions than just change value of this global variable but about them some other time. You need to take care to change value of this global variable. 3) LightState - possible values "Auto" and "Manual". This variable value is set by virtual device. If value is set to Auto then Very Smart Lights™ scenes are enabled and will control lighting as needed. If value is set to Manual then Very Smart Light™ scenes will be disabled and light can be controlled old fashion way with wall switches only. You need to make simple VD to change value of this variable. 4) GuestState - possible values "Yes" and "No". Value is changed either with VD or scene that is run when guests arrive. If set to Yes then lights will be set to predefined brightness level and can also be kept On during guests visit. This condition also has highest priority and will override all other conditions if set yo Yes. 5) CookingState - possible values "Yes" and "No". Value is changed either with VD or scene that is run when you are busy in the kitchen. When set to Yes it will override other conditions bellow. 6) MealState - possible values "Yes" and "No". Value is changed either with VD or scene that is run when you are having launch or dinner. When set to Yes it will override other conditions bellow. 7) ProjectorState - possible values "Yes" and "No". Variable value is set by VD or scene that controls movie projector and other devices connected. As above variable if ProjectorState is set to Yes then scene will adjust light brightness to desirable levels. When set to Yes it will override other conditions bellow. 😎 CinemaState - possible values "Yes" and "No". Variable value is set by VD or scene that controls TV and other devices connected to TV. As above variables if CinemaState is set to Yes then scene will adjust light brightness to desirable levels. When set to Yes it will override other conditions bellow. 9) HolidayLights - possible values "On" and "Off". Variable value is set by VD Holiday Lights v1.0. If value is set to On then lights will be dimmed to predefined brightness. Also scene will stop control selected lights which holidayFlag is set to 1 so that they can be controlled by some other scene or VD like HUE lamps changing colors. When set to Yes it will override other conditions bellow. If it is set to Off then other conditions will apply and scene will take over control of all lights even holidayFlag is set to 1. With all those Christmas lights blinking in color we don't want to spoil that atmosphere with main light turned on to maximum brightness so you can set special brightness level of dimmer lights and select not to turn on some of the switch lights, also you can choose some of the HUE lamps or any other lamp not to be controlled any more with Very Smart Light™ scene but use another scene to control their color or brightness change or even some of the nice mobile applications! Here you can download Holiday Lights VD that will change value of this global variable and turn on/off holiday (Christmas) lights: [VD] Holiday Lights [Christmas Lights], 10) IndoorLightsDim - possible values "Yes" and "No". This variable can be set by VD or scene. I used it to dim indoor lights during summer time to keep insects that are provoked by lights to enter our house through open windows and doors. So if set to Yes then lights in the house will stay dimmed to sleep brightness levels. This condition will be override by all conditions above. 11) SleepState - possible values "Awake" and "Sleep" . This global variable value is controlled on my HC2 with two scenes. One is "Good morning" and is activated either by Alarm clock ACWUT (AlarmClock + WakeUpTime) - version 3.0.0 made by @jompa68 or manually with swipe or dimmer switch. Other one is "Good night" scene that is activated either by swipe or dimmer switch. This global is used only to change light brightness during sleep time. If you want to disable lights turning on then see bellow global variable SleepXxxxx! 12) SleepXxxxx - possible values "Yes" and "No". In name of this variable use room name instead of Xxxxx. You can define this variable for bedrooms and living room if you use it sometimes as bedroom like SleepLiving, SleepMaster, SleepRoom1, etc. You need to add name of this global variable to local variable sleepingName. In comparison to "SleepState" which puts to sleep entire house or apartment this one is used to put to sleep only one room. So it can be used to turn living room into bedroom, or to disable lights in children rooms so they can go sleep earlier and we don't have to put entire house to sleep. If value is set to "Yes" then it disables smart light and immediately turns lights of. If set to "No" enables smart light and also turn on lights immediately if there was motion in the room. In our children bedrooms I setup dimmer 2 switch 2 to start scene on 1 click which then press button on VD to change state of this variable from "No" to "Yes" and vice versa so they can switch off lighting themselves. Put also this global variable under the scene header section %% globals! If you don't need it then just leave empty quotes.Value of this global variables can be changed to Yes or Sleep by simple VD with one label that will show status and one button to change status: All following global variables are global variables to be added in upper part of variable panel! 12) Darkness - global variable (upper part of variable panel) with possible values 0 for day time (Light) and 1 for night time (Dark). Value is changed at adjusted time for sunrise and sunset time. This variable is also controlled by Main scene for time based events control Now when all needed global variables are defined in variable panel it is time to copy paste code to new scene and configure it. So let see through examples how to set this scene to control our lighting. Here is part of code where you can setup global variables names and make mapping of your values with corresponding values in code. Also you can define which of the extra conditions for light brightness levels you like to use by setting use variable either to Yes to use condition or No to not use. Using this above global variables for different conditions allow us to automate change of lights status and it happens automatically without needing us to intervene. That's what home automation is about! Bellow is example of global variables setup for living room that can be also transformed to bed room:
  5. Version 2.0.1

    202 downloads

    Nanoleaf Aurora VD v2.0.1 (standalone version) INTRODUCTION Nanoleaf Aurora light panels https://nanoleaf.me/en/ brings new way of lighting experience. Nanoleaf Aurora VD enables Fibaro Home Center 2 to control this lights and show their status. This is new updated version. PREREQUISITES Fibaro Home Center 2 with firmware 4.120 or higher (tested up to 4.530) Nanoleaf Aurora starter kit with firmware 1.5.1 up to 3.0.6 FEATURES Control brightness, hue, saturation, color temperature and activate Aurora effects VD automatically updates list of the available effects when added or deleted with Nanoleaf mobile application Scroll with buttons through available effects on VD and activate Selected and running effect type can now be recognized by small icon in front of the effect name. Support for Rhythm module. VD automatically recognizes if Rhythm module is attached to Aurora light and enables selection of input between built in microphone or aux input. Use Process button to control Aurora light by other scenes and VD Built in button for generating authorization token for easy connection to Aurora light Multilanguage support with 27 languages. VD will be automatically translated to HC selected language or user can select any other available language. Easy setup for VD icons with automatic setup of icons for buttons and sliders too. (UHAS™ compatible version has even more easier icon setup) User can setup VD to have separated on and off buttons or to have toggle on/off button Light can be turned on/off with buttons and brightness slider. Even if brightness slider is used to turn off Aurora light, VD remembers last brightness settings so if light is turned back on with button it will be turned on at last brightness level. Self adding and checking of global variable data integrity. Automatic repair of global variables without user intervention New approach to programming other code to control this VD enables future upgrades without needing to change that code. (See more about that in User Manual provided) INSTALLATION Please check provided User Manual where all steps are explained in detail and this video made by @MarcoTorino71: UPGRADE To upgrade from v2.0 to v2.0.1 just paste provided code in package over old Main loop code and redo settings To upgrade from v1.0s and v1.1 to version 2.0.1 just delete old version and import new version of VD. PACKAGE CONTENT Nanoleaf Aurora VD v2.0.1 (standalone) Icons for VD User manual v1.3 EN CREDITS Many thanks to gucio1234 and BodyArt from forum.fibaro.com for help with testing, translations and manual. TERMS AND CONDITIONS Permission to use, copy, modify, and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement, is hereby granted, provided that the copyright notice, with "Terms and Conditions" and "Disclaimer" appear in all copies, modifications, and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author. DISCLAIMER This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. Fibar Group S.A. and their employees are not responsible for support of the Nanoleaf Aurora VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required. LEGAL NOTICE Nanoleaf and Aurora are registered trademarks or trademarks of Nanoleaf Energy Technology ShenZhen Limited registered in PR China and other countries. LATEST NEWS 1 April 2019 Nanoleaf Aurora light panels latest firmware update 3.0.8 is out. If you upgrade to this latest firmware Nanoleaf Aurora VD v2.0 will not be able to show VD main icon for effects anymore due to color mode type name "effects" changed to "effect". Even if effect is selected VD will have icon set for solid color. Other functionality of the VD remained intact and will function properly with this latest firmware. 12 September 2019 Nanoleaf Aurora VD is working with the latest Aurora firmware 3.2.0. Problem from 1 April this year with icon functionality is solved! VERSION HISTORY 2.0.1 - Corrected bug in VD main loop that prevented saving updated effect 2.0 - Code rewritten to enable recognizing type of the running and selected effect. Further optimized part of the code and cleaned some bugs. 1.1 - Corrected some bugs in code and replaced light unreachable icon 1.0 - First release of standalone version build on code of VD for UHAS™ Here is look of the Nanoleaf Aurora VD: Enjoy coding and your new Nanoleaf Aurora virtual device! Sankotronic
  6. Hi guys I ask for Lua scene to control the lights automatically into star's by motion detection bt problem not for that The problem is I want that scene work between 6 pm to 7am and if motion detection don't detect any move then turn off light after 20 minutes Any one hare can help my to do that And Thanks for every one
  7. Hi gents, quite a bummer that my old account has gone missing but what to do. Back to the point. I intend to create a LiFX virtual device as I have a few LiFX bulbs around my home and I can't really integrate them with Fibaro. I've also checked LiFX community and they said: I tried to connect my Lifx bulbs with the HC2. Now it works! I found a lot of information on the subject of http requests in the pages of this forum. Here you find how I did it: You need to use the new firmware version on Lifx bulbs (version 2.0) - we can do the update in the app on Android. Register on https://cloud.lifx.com , search the "settings" and register a new "token" for the API. You can find all the API information that exists on http://developer.lifx.com/ Create a new scene in HC2 and put for example: Adapt your LUA code. For authorization: Take your lifx cloud token, add a ":" and encrypt it in base64 ( https://www.base64encode.org/ ) That's all, good luck At this point, I'm a bit lost. Any ideas on what he wants to say with adapt your LUA code? local http = net . HTTPClient () http : request ( 'https://api.lifx.com/v1beta1/lights/group%3ASchlafzimmer/power.json?selector=group%3ASchlafzimmer&state=on' , { options = { method = 'PUT' , headers = { [ 'Authorization' ] = 'Basic Y2YxM2FjODJkZDcyYjRmZmZiYTAwOGQ4ZDUxMTE2ZWQ4ZTdlMTE0ZTJjYWU4YWMzZjI5NzUwMTEyMjBmMTk0Nzo =' } }, success = function ( response ) fibaro : debug ( response . data ) end , error = function ( err ) fibaro : debug ( "Error:" .. err ) end }) this bit was missing
  8. Hey! I just recently bought FIBARO Home Center 2 and some smart z-wave products. Still have a lot to learn! I've created 2 easy scenes: 1) when motion sensor detects motion then my kitchen's lamp goes ON; 2) when it does not detect motion for 30 sec then the lamp goes OFF. It works fine, but my question is how can I make this happening ONLY between 5.00-6.00?
  9. Version 1.3.1

    281 downloads

    VD YEELIGHT MANAGER Originally released on domotique-fibaro.fr v. 1.3.0 - 14/01/2018 I present the VD Yeelight Manager which, as its name suggests, allows you to integrate Yeelight products with the HC2. To be very precise, I only have a Bedside Lamp and I have not tested this VD with other products. However, since the API is generic, there are no reasons that it does not work too. The only limit, I did not integrate in the DV management of the background light since the Bedside Lamp does not have such a light. To use it, simply enter the IP of the Yeelight in the IP field of the DV, and the port in the Port field of the DV (the port used by the Yeelights is 55443). You can add or change elements of the virtual device according to your needs (the white light bulb does not need, for example, anything related to color management), as long as the TCP Connection and Transmission buttons keep their respective names (btnTCPConnection and btnTransmission). Yeelight Manager will find them himself by these names. In order to be able to manage a Yeelight 'almost' like a module, simply insert in the scene or the code of the button or Main Loop the following code: _y={credits='Yeelight Controller v. 1.3.0 - Copyright 2018 Olivier Meyer - GNU GPLv3',global='y_yeelight_global',item='y_yeelight_',props={power=true,bright=true,ct=true,rgb=true,hue=true,sat=true,color_mode=true,flowing=true,delayoff=true,flow_params=true,music_on=true,name=true,bg_power=true,bg_flowing=true,bg_flow_params=true,bg_ct=true,bg_lmode=true,bg_bright=true,bg_rgb=true,bg_hue=true,bg_sat=true,nl_br=true},f=fibaro,debug=function(s,m,c)s.f:debug(string.format('<span style="color:%s;">%s</span>', c, m))end,here=function(s)local h=type(s.f.getSelfId)=='nil' if h then return h,__fibaroSceneId else return h,s.f:getSelfId(),_elementID_ end end,log=function(s)local h=s:here()if h then local a=s.f:args()if a then if a[1].yeelight then s:debug(a[1].debug,a[1].color);s:debug(a[1].command,a[1].color);os.exit()end end end end,getBtn=function(s,i,n)local c,r=0,api.get('/devices/'..tostring(i))['properties']['rows'] local x=#r for a=1,x do local y=#r[a].elements for b=1,y do c=c+1 if n==r[a].elements[b].name then return c end end end s:debug('[Yeelight] Unable to locate button '..n..', check virtual device '..i,'Tomato');return nil end,build=function(s,m,p)local c='{"id":1, "method":"'..m..'", "params":['for i=1,#p do if type(p[i])=="number"then c=c..p[i]else c=c..'"'..p[i]..'"'end;if i~=#p then c=c..', 'end end;c=c..']}\r\n'return c end,load=function(s,v)local g=s.f:getGlobalValue(v)if string.len(g or '')>0 then local d=json.decode(g)if d and type(d)=='table'then return d else s:debug('[Yeelight] Unable to process data, check variable','Tomato')end else s:debug('[Yeelight] No data found!','Tomato')end return nil end,set=function(s,i,d)local g=s:load(s.global)if g[tostring(i)]then local a,b,c=s:here();g[tostring(i)].scene=a;g[tostring(i)].id=b;g[tostring(i)].button=c;g[tostring(i)].command=d;s.f:setGlobal(s.global,json.encode(g))end end,call=function(s,i,m,p)local b=s:getBtn(i,'btnTransmission')if b==nil then return nil end;local c=s:build(m,p)s:set(i,c)s.f:call(i,'pressButton',b)end,getValue=function(s,i,p,g)if s:checkP(p) then if type(g)~='table' then g=s:load(s.item..i)end if g.properties then if g.properties[p] then if g.properties[p].value then return g.properties[p].value end end end s:debug('[Yeelight] Unable to get value of '..tostring(p)..', please check variable.','Tomato');end return nil end,getModificationTime=function(s,i,p,g)if s:checkP(p) then if type(g)~='table' then g=s:load(s.item..i)end if g.properties then if g.properties[p] then if g.properties[p].modificationTime then return g.properties[p].modificationTime end end end s:debug('[Yeelight] Unable to get modification time of '..tostring(p)..', please check variable.','Tomato');end return nil end,get=function(s,i,p)local g=s:load(s.item..i);return s:getValue(i,p,g),s:getModificationTime(i,p,g)end,getStatus=function(s,i)local g=s:load(s.item..i)if g then if g.status then return g.status end end return nil end,getLastChange=function(s,i)local g=s:load(s.item..i)if g then if g.last then return g.last end end return nil end,checkP=function(s,p)if not s.props[p] then s:debug('[Yeelight] '..p..' is not an existing property!','Tomato') return false end return true end} _y:log() This code above offers the following functions: _y:call(id, method, params) which allows to send a command to the lamp. The various buttons of the VD give examples. To go further, please have a look at the Yeelight API documentation : Yeelight_Inter-Operation_Spec.pdf _y:get(id, property) which does exactly the same thing as fibaro:get() _y:getValue(id, property) which does exactly the same thing as fibaro:getValue() _y:getModificationTime(id, property) which does exactly the same thing as fibaro:getModificationTime() _y:getStatus(id) which returns "online" if the lamp is connected to the wifi network, and "offline" otherwise _y:getLastChange(id) which returns a table containing the properties that have just been modified and their new value The logs generated by the call () function are displayed in the debug zone of the scene (do not forget the _y: log () line and allow enough instances) or in the button or main loop of the virtual module from which the function was used. To use these lamps as scene triggers, the VD automatically creates a global variable y_yeelight_XXX, where XXX is the ID of the VD. This global variable contains all the properties of the lamp and is updated in real time. For example, to start a scene when a Yeelight is turned on: --[[ %% globals y_yeelight_XXX --]] _y={credits='Yeelight Controller v. 1.3.0 - Copyright 2018 Olivier Meyer - GNU GPLv3',global='y_yeelight_global',item='y_yeelight_',props={power=true,bright=true,ct=true,rgb=true,hue=true,sat=true,color_mode=true,flowing=true,delayoff=true,flow_params=true,music_on=true,name=true,bg_power=true,bg_flowing=true,bg_flow_params=true,bg_ct=true,bg_lmode=true,bg_bright=true,bg_rgb=true,bg_hue=true,bg_sat=true,nl_br=true},f=fibaro,debug=function(s,m,c)s.f:debug(string.format('<span style="color:%s;">%s</span>', c, m))end,here=function(s)local h=type(s.f.getSelfId)=='nil' if h then return h,__fibaroSceneId else return h,s.f:getSelfId(),_elementID_ end end,log=function(s)local h=s:here()if h then local a=s.f:args()if a then if a[1].yeelight then s:debug(a[1].debug,a[1].color);s:debug(a[1].command,a[1].color);os.exit()end end end end,getBtn=function(s,i,n)local c,r=0,api.get('/devices/'..tostring(i))['properties']['rows'] local x=#r for a=1,x do local y=#r[a].elements for b=1,y do c=c+1 if n==r[a].elements[b].name then return c end end end s:debug('[Yeelight] Unable to locate button '..n..', check virtual device '..i,'Tomato');return nil end,build=function(s,m,p)local c='{"id":1, "method":"'..m..'", "params":['for i=1,#p do if type(p[i])=="number"then c=c..p[i]else c=c..'"'..p[i]..'"'end;if i~=#p then c=c..', 'end end;c=c..']}\r\n'return c end,load=function(s,v)local g=s.f:getGlobalValue(v)if string.len(g or '')>0 then local d=json.decode(g)if d and type(d)=='table'then return d else s:debug('[Yeelight] Unable to process data, check variable','Tomato')end else s:debug('[Yeelight] No data found!','Tomato')end return nil end,set=function(s,i,d)local g=s:load(s.global)if g[tostring(i)]then local a,b,c=s:here();g[tostring(i)].scene=a;g[tostring(i)].id=b;g[tostring(i)].button=c;g[tostring(i)].command=d;s.f:setGlobal(s.global,json.encode(g))end end,call=function(s,i,m,p)local b=s:getBtn(i,'btnTransmission')if b==nil then return nil end;local c=s:build(m,p)s:set(i,c)s.f:call(i,'pressButton',b)end,getValue=function(s,i,p,g)if s:checkP(p) then if type(g)~='table' then g=s:load(s.item..i)end if g.properties then if g.properties[p] then if g.properties[p].value then return g.properties[p].value end end end s:debug('[Yeelight] Unable to get value of '..tostring(p)..', please check variable.','Tomato');end return nil end,getModificationTime=function(s,i,p,g)if s:checkP(p) then if type(g)~='table' then g=s:load(s.item..i)end if g.properties then if g.properties[p] then if g.properties[p].modificationTime then return g.properties[p].modificationTime end end end s:debug('[Yeelight] Unable to get modification time of '..tostring(p)..', please check variable.','Tomato');end return nil end,get=function(s,i,p)local g=s:load(s.item..i);return s:getValue(i,p,g),s:getModificationTime(i,p,g)end,getStatus=function(s,i)local g=s:load(s.item..i)if g then if g.status then return g.status end end return nil end,getLastChange=function(s,i)local g=s:load(s.item..i)if g then if g.last then return g.last end end return nil end,checkP=function(s,p)if not s.props[p] then s:debug('[Yeelight] '..p..' is not an existing property!','Tomato') return false end return true end} _y:log() local function run() --executed on light on end local trigger = fibaro:getSourceTrigger() if trigger.type == "global" then if trigger.name == "y_yeelight_XXX" then if _y:getLastChange(XXX)["power"] == "on" then run() end end end
  10. Version 1.0.1

    90 downloads

    Nanoleaf Canvas VD v1.0.1 (standalone version) INTRODUCTION Nanoleaf Canvas light panels https://nanoleaf.me/en/ brings new way of lighting experience. Nanoleaf Cavas VD enables Fibaro Home Center 2 to control this lights and show their status. PREREQUISITES Fibaro Home Center 2 with firmware 4.530 (can work on older versions same as Nanoleaf Aurora VD down to 4.120) Nanoleaf Canvas starter kit with firmware 1.1.0 or greater FEATURES Enables HC2 to control Nanoleaf Canvas lights and show their status Control brightness, hue, saturation, color temperature and activate Canvas effects VD automatically updates list of the available effects when added or deleted with Nanoleaf mobile application Scroll with buttons through available effects on VD and activate Selected and running effect type can now be recognized by small icon in front of the effect name. Canvas control light panel has built in Rhythm module and there is no AUX input available. Rhythm module is automatically activated when rhythm effect is activated Use Process button to control Canvas light by other scenes and VD Built in button for generating authorization token for easy connection to Canvas light Multilanguage support with 27 languages. VD will be automatically translated to HC selected language or user can select any other available language. Easy setup for VD icons with automatic setup of icons for buttons and sliders too. (UHAS™ compatible version has even more easier icon setup) User can setup VD to have separated on and off buttons or to have toggle on/off button Light can be turned on/off with buttons and brightness slider. Even if brightness slider is used to turn off Aurora light, VD remembers last brightness settings so if light is turned back on with button it will be turned on at last brightness level. Self adding and checking of global variable data integrity. Automatic repair of global variables without user intervention New approach to programming other code to control this VD enables future upgrades without needing to change that code. (See more about that in User Manual provided) INSTALLATION Please check provided User Manual where all steps are explained in detail. PACKAGE CONTENT Nanoleaf Canvas VD v1.0.1 (standalone) Icons for VD User manual v1.1 EN CREDITS Many thanks to @gucio1234 and @Bodyart from forum.fibaro.com for help with testing, translations and manual. TERMS AND CONDITIONS Permission to use, copy, modify, and distribute this software and its documentation for educational, research, personal use and non-profit purposes, without fee and without a signed licensing agreement, is hereby granted, provided that the copyright notice, with "Terms and Conditions" and "Disclaimer" appear in all copies, modifications, and distributions. It is strictly forbidden to sell, rent, lease and/or lend this software for profit without prior consent from the Author. DISCLAIMER This software is provided by copyright owner "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author and distributor be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. Fibar Group S.A. and their employees are not responsible for support of the Nanoleaf Aurora VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required. LEGAL NOTICE Nanoleaf and Canvas are registered trademarks or trademarks of Nanoleaf Energy Technology ShenZhen Limited registered in PR China and other countries. NEWS 1 April 2019 Nanoleaf Canvas light panels latest firmware update v1.2.0 is out. If you upgrade to this latest firmware Nanoleaf Canvas VD v1.0 functionality will remain intact and will continue function properly. 12 September 2019 Canvas VD is working flawlessly with Canvas latest firmware version 1.5.0 VERSION HISTORY 1.0.1 - Corrected bug in VD main loop that prevented saving updated effect 1.0 - First release of standalone version build on code of VD for UHAS™ Here is look of the Nanoleaf Canvas VD: Enjoy coding and your new Nanoleaf Canvas virtual device! Sankotronic
  11. Hello, i am controlling my garden lights with 2 scenes, one for sunset and one for sunrise. And it’s working perfectly I usually have lights dimmed at 30%. I would like to know if it’s possible to add a scene where, if there is a motion it will increase the lights by 30% or to put it to max level for 3 minutes and then back to the previous condition. Another scene could also work, if there is a motion lights up to 100%, and when if there is no motion for 3 minutes lights to 30%. in both cases I would like this scene to work only between 22:00 and 07:00. is it possible to make such a scene ? Thanks in advance !
  12. Guest

    Nanoleaf Canvas light icon set

    Version 1.0

    36 downloads

    Nanoleaf new Canvas light square panels are just amazing. Here is icon set for this light panels. Same icon pack is included in Nanoleaf Canvas VD that can be downloaded here: Forum download Nanoleaf Canvas VD
  13. Hi, In our hallway of about 8m long we have lights that we want to be activated by motion detection. I have two PIR’s installed to make sure I get acurate motion detection at any location in the hallway. Lights are connected to a dimmer2 (pulse switched). when PIR is breached a scene is triggered. Scene will switch on the light at predefined level and loop until PIR is safe and timer that I set reached 0. At 0 lights will be switched off. This works. Problem1; When motion is detected (Seen by the light of the mulitisensorPIR) it takes 1-2seconds before lights switches on. I read online that delay can be caused because communication between dimmer2 and PIRs goes thru HC2. Can I link 2 pir to one dimmer2 and have a timeout function? Goal is to have communication without hc2 being involved(faster). Problem2 I sometimes have a 5 secs late response. even if I just arrive home and nothing is in use yet. any ideas? problem3 In hc2 I set max scenes to 4 instances for this scene, though still I get the ‘error too many tuns.’ in the code I abort when scene is triggered while lights on, though still I get notifications that max amount of a running instance for this scene has reached. What to do to get rid of scene errors max instances reached? Note increase the number of simultanious instances results in strange behavior, late on, off when needed. Thanks jules
  14. Hi I am completely new to Fibaro and currently considering wiring up my newly renovated house with 35 dimmers and switches for each and every light circuit. The dimmer 2 and switch 2 look really good on paper and seem to do exactly what i need for basic light automation. I even ordered one and tried one on a test circut and it worked well. But what I worry about is that it needs to be really reliable. I simply cannot have the situation where I need to trouble shoot the system every few weeks, or work out why some of them are no longer found by the controller - these are the kinds of things I have been reading about. I'm dreading the situation where a simple wall switch does not turn the light on anymore , and I have to waste time to troubleshoot. Although I am very technically minded, I don't want something so simple like a light give me a headache - if this is not mature yet, I don't want it. Especially the physical switches that are directly connnected to the Fibaro need to work rock solid and near 100% reliable. The physical switches must work even in case the controller is out of action for whatever reason. If the software control, the remote access or the scenes have some issues now and again that's ok for me. It would be great of some of you could comment on long term reliability with the dimmers and switches, is it mature enough to use it throughout the house, I mean on EVERY circuit? Thanks in advance for your valuable experiences Felix
  15. One thing that I'm especially happy with is the way the heatingpanel functions in relation to setting different temperatures at specific times. It's very intuitive and easy to operate for the "!non-technical" user. How about making a similary looking and functioning panel for lighting??????? It's allready there for humididty. Such a feature would make the whole system much more userfriendly.,
  16. For my grandmother I did a little DIY-project: Incoming calls (via Fritz!Box) are additionally signalled visually by a cheap/simple alarm light combined with a simple actor (i.e. Wall Plug). As long as there's an incoming call, the light is flashing. When the call is accepted or refused or cancelled, it stops flashing. In your Fritz!Box the call monitor has to be enabled and a global variable ("FritzBoxStatus") has to be defined in your HC2. (See German siio.de for further details) --[[ %% properties %% events %% globals FritzBoxStatus --]] -- ######################################################################### -- ## Visual signaling of incoming calls via Fritz!Box (Orgli 2017-12-31) ## -- ######################################################################### -- Call monitor has to be enabled in the Fritz!Box. -- Global variable "FritzBoxStatus" has to be defined. -- Get current status of the Fritz!Box (here: "RING"). local startSource = fibaro:getSourceTrigger(); if ( ( tostring(fibaro:getGlobalValue("FritzBoxStatus")) == "RING") or startSource["type"] == "other" ) then -- Replace "[XX]" with the ID of your actor/device (more devices separated with ",") -- to be turned on. You can also change the action turnOn/turnOff. fibaro:call([XX], "turnOn") else -- Replace "[XX]" with the ID of your actor/device (more devices separated with ",") -- to be turned off. You can also change the action turnOn/turnOff. fibaro:call([XX], "turnOff"); end
  17. Hi I want to build a conditional scene as follows: If daypart ="state" (Ex: Evening) and main light at a specific room are on for more than defined time (ex: >=30sec) then turn other lights\devices on appreciate your support Ran
  18. Hello, Am searching for true image automation, i need help to do this. Any body please help me out.,,.............
  19. Hello, Tell me, knowing guys) I wrote a scene that tracks the state of light in the room and passes it to a global variable. But this scene constantly reports that too many instances are running ( The room has a physical switch that, depending on this global variable, turns off or turns on the light in the opposite direction. Maybe there is a more elegant way to write this scene? Thanks ) --[[ %% autostart %% properties 15 value -- main light 23 value -- window light 21 value -- inner light 97 value -- outer light %% events %% globals --]] fibaro:debug("Scene START at " .. os.date("%c")) num = fibaro:countScenes() fibaro:debug(num.." scenes running") local startSource = fibaro:getSourceTrigger(); if (fibaro:countScenes() > 1) then fibaro:debug("Too many Scenes running up") fibaro:abort() end while true do if ( tonumber(fibaro:getValue(15, "value")) > 0 -- main light or tonumber(fibaro:getValue(23, "value")) > 0 -- window light or tonumber(fibaro:getValue(21, "value")) > 0 -- inner light or tonumber(fibaro:getValue(97, "value")) > 0 -- outer light or startSource["type"] == "other") then fibaro:setGlobal("LivingLight", "On"); --fibaro:debug("On..."); else fibaro:setGlobal("LivingLight", "Off"); --fibaro:debug("Off..."); end fibaro:sleep(3000) end
  20. Hi, Have this strange issue for the 3rd time this year. One of my dimmers will not turn off, this has happened several times before on different devices sometimes on several at the same time. Rebooting HC2 does not help. Pushing the wall switch makes it turn off shortly but it turns on again a couple seconds later. Any ideas?
  21. Does anyone know if fibaro has any compatible bulbs that you can change the colors with the HC2 GUI (without using LUA)?
  22. Distance check is a LUA script to turn on the lights when you’re coming home, for example to turn on the garden light. It uses the GPS functionality of the Fibaro HC2. The script tries to manage the delays or the errors that sometimes there are acquiring the user's location by the Fibaro/GPS and it requires an interval of 1 minute for the Fibaro HC2 parameter "How frequently GPS position from the user’s iPhone should be collected". It has been tested in scenario where you are some kilometers away from home and you are going to home. How it works. You can define four areas: large area and small area, gap area and extra large area. The area are circles around the location of the house. When you enter in the large area the light is turned on and a timer is started. If you reach the small area before the timer has expired the light will be “confirmed on” otherwise the light will be turned off. Perhaps you was not going to home but you have entered in the large area for a while. When the light is “confirmed on” by the first timer a second timer is started. If you exit from the small area before that this timer has expired the light will be turned off. This second timer avoids that the light remains on when, for example, you pass near the house (inside the small area) without to stop at the house. If you remains in the small area the script will continue to run to check when you will go away from home just to reset at the condition where it checks when you area arriving to home. The reset happens when you will be out of the “large area + a gap distance”. Large area + gap distance define the gap area. The gap area is to avoid that the script switches exactly on large area border when you are going away from home. Infact it could be that the road you are on goes in and out from the large area or that the FIBARO GPS reports different values (greater or less than large area radius) when you are next to the large area border. So, without the gap area the script could turn on the light when you are going away from home. It is important to note that even though the script should erroneously turned on the light when you are going away from home the light will be turned off after the first timer is expired since you will not enter in the small area. Anyway the gap area avoids this kind of error and it is used only when you are going away from home. Link for script (ZIP file) and documentation (PDF) download: http://domotica.gposta.it
  23. Doug

    Motion Sensor

    Hi I have just installed a HC2 with version 4.056. I have added some Danfoss radiator thermostats which went fine, except a couple come up with crosses sometimes. The main issue is with the motion sensors. Both are recording temperature but neither is measuring the light level at all. I have seen a couple of other topics on this, but no recent ones and wondered if this has been resolved. Doug.
  24. I have installed a Qubino dimmer, and added it in fibaro web console. Fibaro detects the dimmer, but also another device which it thinks is a motion sensor. When I switch the dimmer "ON" in fibaro, the light goes on, however it blinks on and off every second, and after that I can't make it stop blinking no matter what I do in fibaro. Even when I switch off the current to the dimmer/light, and then turn it on again, the blinking instantly starts again. This happened with version 3.x of fibaro (think it was 3.5 or something, can't remember), and then same thing after upgrade to version 4.035. I deleted and readded the dimmer in fibaro. As far as I understand, the Qubino dimmer should work fine with fibaro, and specificly with latest fibaro version, for which one of the updates notes was "added Qubino dimmer template". So what can I do? /Gabriel
×
×
  • Create New...