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


Virtual Devices

The category contains virtual devices submitted by users.
Downloading and submission terms have to be accepted.
Types of files accepted: LUA, VFIB, ZIP, TAR, RAR, JSON.
Virtual devices have to be described properly, screen shots are optional.
Support topics are created automatically here Virtual devices
Report topics and files that are no longer supported by authors.
All the files submitted have to be approved by administrators.

82 files

  1. Netatmo Weather Station suite standalone

    Netatmo Weather Station suite standalone
     
    INTRODUCTION
    Netatmo Weather station suite brings complete integration of Netatmo weather station to HC2 users including rain and wind gauges and support for more than one station.
     
    PREREQUISITES
    Fibaro Home Center 2 with firmware 4.160 or greater
    Sankotronic Lab. Emoji VD standalone
    Netatmo Weather station
     
    FEATURES
    Complete integration of Netatmo weather station with HC2 including rain gauge and anemometer
    Support for multiple Netatmo weather stations
    Support for maximum 3 additional indoor modules
    Smart update system that follows Netatmo weather station cloud updates
    Completely independent installation does not require any more Weather State VD or Main scene FTBE
    Netatmo weather station measurements can be shown on Weather State VD and HC2 web GUI and mobile applications by means of Weather State VD and Weather
    provider plugin
    VD has built in multi-language support with 27 languages included (see APPENDIX 1 for the list). VD can use HC selected language or user can select any other available
    language.
    Easy setup for VD icons (on UHASTM compatible version is this even easier)
    Global variables are automatically added, monitored and repaired and does not require user intervention
     
    INSTALLATION
    Please check provided User Manual and video from @MarcoTorino71:
     
    PACKAGE CONTENT
    Netatmo Main module VD Netatmo Outdoor module VD Netatmo Additional indoor module VD Netatmo Wind sensor VD Netatmo Rain sensor VD Netatmo Weather station scene Set of icons for all VD's and scene User manual EN  
    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 ABC VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required.
     
    VERSION HISTORY
    3.3.1 - Scene code changed to get rain amount for past 3 adn 6 hours to better support Irrigation Control VD. All VD's corrected some translations. Rain gauge VD changed labels content to display last 3 hours rain amount 3.3 - Check below version description or consult User manual for more details 3.2 - Corrected rain sensor code and cleaned some bugs in scene. Indoor modules corrected handling of CO2 measurement, improved updating code. 3.0 – This new version is completely redesigned and made independent. Does not require Main scene FTBE and Weather State VD anymore. Updating is now synced with Netatmo cloud so readings are always up to date. 2.0.2 – Code optimized and resolved some bugs   Here is look of the Netatmo Weather set:

     
    Enjoy coding and your new Netatmo weather station suite! 
    Sankotronic
     

    2,626 downloads

       (4 reviews)

    50 comments

    Updated

  2. Odczyt czujników jakości powietrza z AIRLY.EU

    Urządzenie wirtualne odczytująca parametry jakości powietrza z najbliższego czujnika sieci AIRLY.EU
     
    Wirtualne urządzenie odczytuje z ustawień centralki jej współrzędne geograficzne i znajduje najbliższy czujnik w promieniu 5 km.
     
    Jedynym ustawieniem użytkownika jest wpisanie klucza API dla AIRLY.EU w kodzie LUA (jest to odpowiednio opisane).

     

    85 downloads

       (0 reviews)

    0 comments

    Submitted

  3. Philips HUE AIO VD standalone

    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,545 downloads

       (6 reviews)

    99 comments

    Updated

  4. piCorePlayer

    Vertual Device to control piCorePlayer on raspberrypi
     

    14 downloads

       (0 reviews)

    0 comments

    Updated

  5. Quattro.vfib

    Quattro.vfib

    31 downloads

       (0 reviews)

    0 comments

    Submitted

  6. Remotec Multimedia VD

    ZXT-120 is an IR extender for air conditioners, but it can be learned up to 20 defferent ir code for multimedia. The process of learning of zxt-120 is written in its manual, but i want to show a way to use that codes in fibaro HC.
     
    For this purpose we have to change the virtual device IP Address with your HC ip, and write 80 in TCP port box:
     

    You can change the buttons according to your custom multimedia device (here we made a TV control):

    Now you have to change commands for corresponding buttons.
    For example for first button:
     

     
    Authorization code is your username:password in 64Base format. 
     
    admin:admin     =>    YWRtaW46YWRtaW4=
     
    We can learn up to 20 code according to this list:

     
    Use this command for changing mode :
        /api/callAction?deviceID=107&name=setMode&arg1=0
     
    For setting temperature (in cooling mode):
       /api/callAction?deviceID=107&name=setThermostatSetpoint&arg1=2&arg2=23 
     
    For setting temperature (in heating mode):
     /api/callAction?deviceID=107&name=setThermostatSetpoint&arg1=1&arg2=21 
     

    109 downloads

       (0 reviews)

    1 comment

    Submitted

  7. Samsung Air Conditioner

    Since Samsung Plugin doesn't work I decided to write custom Samsung Air Conditioner VD.
     
    Requirements:
    Samsung AC Local PHP server (NAS, RPI, ...)  
    Installation:
    Copy smarthome folder to your php server Edit/rename Bedroom.php, Living room.php files. For each device you need separate file. In each file: enter IP of your AC device enter token of your AC device To get token follow steps 3.1 - 3.5 from this site. Check if your PHP server is working: http://192.168.0.10/smarthome/samsung-ac/Bedroom.php
    Of course change 192.168.0.10 with the IP of your PHP server.
    You should see JSON result with status. Something like this: { "power": "Off", "mode": "Cool", "virusDoctor": "Off", "quiet": "On", "wind": "Fix", "temperature": 22, "currentTemperature": 23, "sleep": 0 } Install Air Conditioner VD Edit Air Conditioner VD:
    Room name must be the same as your PHP file name without .php extension, e.g. Bedroom Enter Address IP of your PHP server, e.g. 192.168.0.10 Port number of your PHP server, usually 80 Add VD icons and enter icons ID at "refresh" button section:
     
    Enjoy...
     

    93 downloads

       (0 reviews)

    0 comments

    Submitted

  8. Shelly_IP101.vfib

    This VD is a interface to the ping_shelly.lua which can also be found here. The IP-address needs to be configured as shown in the image. The port value ("109") is used/misused to set the number of the lua script in your HC2  ("_lua").
    As example here the code for the "on" button:
    local _self=fibaro:getSelfId() local _addr=fibaro:getValue(_self,"IPAddress") local _lua=fibaro:getValue(_self,\"TCPPort\") fibaro:startScene(_lua,{_addr,"on"}) fibaro:sleep(1000) fibaro:startScene(_lua,{_addr}) fibaro:sleep(1000) local _slider = tonumber(fibaro:getGlobalValue("S" .. string.gsub(_addr,"%.","_"))) if (_slider <= 0) then _slider=10 fibaro:startScene(_lua,{_addr,_slider}) end fibaro:call(_self,"setProperty","ui.brightness.value",_slider)  
     

    28 downloads

       (0 reviews)

    0 comments

    Updated

  9. Sleep Timer & Scheduler

    Initially it was supposed to be a simple Sleep Timer, similar to what we have in TV but later I added some new functions and now it is a simple Scheduler and Sleep Timer in one VD.
     

     
    Features:
    Sleep Timer - just set the time after which the device will be turned off or turned on Scheduler - set the time when the the device should be turned on and the time when the the device should be turned off (or in the reverse order - first turn off and then turn on) Filtering devices - you can choose only devices with turnOff action attribute Filtering rooms - you can choose only rooms which have devices with turnOff action attribute _ - change on/off setting time ✔ - add device to schedule ❌ - remove device from schedule; triple click to clear the schedule Refresh button - you don't need to touch it. It's called programmatically Displaying the current schedule Logging the events to debug window: add, remove, turn on, turn off automatic support for plugins with turnOff action attribute support for custom virtual devices and plugins instant turn on/off (VD and plugins also) presenting the current device state ( ⚡ when the device is on, and - when is off)  
    Customization:
    change the VD labels to your own language change the texts in the Refresh button code and in the main code: local lT = { newLine = "<br/>", -- change to "\n" if you use this VD on iOS mobile mainly or " " for Android scheduledDevices = "Scheduled devices" }        Actually there is a problem with breaking lines in labels, so you can choose new line char. More details here.
     
    add your own virtual devices or plugins in main loop code:
    local extraDevices = { -- deviceId, commandOn, parameterOn, commandOff, parameterOff ["335"] = { "pressButton", "2", "pressButton", "3" }, ["339"] = { "setVolume", "20", "setMute", "" }, } icons:
     

     
    Enjoy...

    117 downloads

       (0 reviews)

    2 comments

    Updated

  10. Smarter Coffee VD

    Smarter Coffee VD
     
    Hello friends of Fibaro and a good cup of coffee!!!
     
    When I became proud owner of Smarter coffee machine, I didn't know that Smarter is making smart appliances that are actually not connectible to home automation. I have ask them several times if they plan to publish coffee machine API or what ever is needed so that it can became connected part of our every day smarter home. What is the use of smart coffee machine if you have to grab mobile phone every morning in bed to tell it that you want coffee to be brewed!! The answer was always "maybe soon". So I get tired of waiting!
     
    I was intensively searching the wast land of internet and just few days ago finally stumble on at least some kind of solution provided by Simone Margaritelli the evilsocket and Aden Forshaw. Of course their solution is written in python but for me is unacceptable to have additional server even on small PI just to start coffee machine. So done little experimenting because this coffee machine has really simple commands in bytes where first byte is command and last byte is marking end of command. Here is what evilsocket and Aden found and I provide translation to our LUA language with this little knowledge I have just in case if you want to experiment further or do similar VD for iKittle 2:
     
    -- Smarter coffee commands: command - hexadecimal - decimal format used in LUA -------------------------------------------------------------------------------------- brew = "7" = "7" reset = "\x10" = "\16" get wifi aps = "\xD" = "\13" toggle grind = "\x3c\x7e" = "\60\126" set strength = "\x35%\x7e" = "\53\%\126" where % = 0-2 (weak, mid, strong) set cups = "\x36%\x7e" = "\54\%\126" where % = 1-12 cups set config = "\x38\%1\%2\%3\%4\x7e" = "\56\%1\%2\%3\%4\126" where %1 = strength %2 = cups %3 = mode (grind, filter) %4 = warm time warm % min = "\x3e%\x7e" = "\62\%\126" where % = 1-30 min warm stop = "\x4a\x7e" = "\74\126" -- Smarter coffee response response - hex - decimal counterpart ------------------------------------------------------- brewing or OK = "\x03\x00~" = "\3\0~" already brewing = "\x03\x01~" = "\3\1~" invalid argument = "\x03\x04~" = "\3\4~" no carafe = "\x03\x05~" = "\3\5~" no water = "\x03\x06~" = "\3\6~" low water = "\x03\x07~" = "\3\7~" reset ok = "\x03i~" = "\3i~" -- In LUA backslash \ is used to mark byte in the string so it cannot stand alone or be -- last character in string like this: "\" or this "\56\". ''So this is problem if you want -- to combine different values in string commands like for changing number of cups -- since it is impossible to join "\54\" ..cups.. "\126". 'Only possibility that -- came across my mind is to use table with predefined strings for coffee strenght, -- number of cups and Keep wamring time as listed bellow. local comm = "\56"; local cups = {"\1", "\2","\3", "\4","\5", "\6","\7", "\8","\9", "\10", "\11", "\12"}; local stre = {"\0", "\1","\2"}; local mode = {"\0", "\1"}; local time = {"\5", "\10", "\15", "\20", "\25", "\30", "\35", "\40"} local endb = "\126" -- example of building command for setting coffee machine default settings local command = comm..stre[2]..cups[2]..mode[1]..time[1]..endb I should actually put this part in developer section but here it is for those of you who like to play with it.
     
    So here it is SMARTER COFFEE VD V0.1 first release
     
    Smarter_coffee.vfib.json
     
    To be able to use this VD you will need following devices:
    1) HC2 - VD will work only on HC2 due to LUA code (Will try to do HCL version but will not be with all possibilities as LUA version)
    2) Smarter Coffee machine with latest firmware V 22.0 (will work with older version but you will not be able to stop Keep warming or set it to 40 min)
    3) FGWP smart plug or any other similar. It is needed to monitor coffee machine consumption from which is determined if it is brewing, keep coffee warm or stopped
     
    Also after importing VD to your system you need to setup IP address and TCP port. Since it is not possible to get IP address of your precious coffee machine from original app you will need some other app to find it for you. I used Fing on my iPhone. TCP port is 2081. And it should be entered on advanced tab of the VD:

     
    Before you start using VD first you will need to define some global variables in global variable panel. I was planning to add code to do that part for you, but since Fibaro is constantly changing API on HC I decided to leave this part to you. Besides you can put values of global variables in your language but then you will also have to change few things in code of each button and main loop. Will explain later what to change.
     
    So this are global variables that are needed for Smarter coffee VD to work properly:
     
    First are variables (top part in panel):
    Name of variable - possible value that you must enter when adding (DO NOT leave 0 if is not possible value!!)
    -----------------------------------------------------------------------------------------------------------------------------
    SmarterCups       - possible values: between 1 and 12. Do not leave 0. Keeps number of cups of coffee.
    SmarterStrength  - possible values: 0 - Weak, 1 - Medium or 2 - Strong.  Keeps value of coffee strength
    SmarterWarm      - possible values: 5, 10, 15, 20, 25, 30, 35 and 40. Keeps time for how long coffee will be kept warm
     
    Following are predefined global variables (bottom part in panel):
    Name of variable - possible values that you must enter in order I put them here bellow.  
    -----------------------------------------------------------------------------------------------------------------------------
    SmarterBrewed   - possible values: No, Yes. Used to prevent starting brewing twice in a row. This is filter coffee and filter is better to cleaned after each use.
    SmarterDefaults  - possible values: table that contains coffee machine default values for strength, number of cups, mode (Filter or Grind) and time to Keep warm. You need to define only one value with name Table and then save. Open again to edit and then delete Value2. VD will take care of the rest.
    SmarterMode      - possible values: Filter, Grind. It is self explanatory  
    SmarterPush       - possible values: No, Yes. It is used to send push notification only ones from VD main loop when coffee is ready
    SmarterStatus     - possible values: Ready, Not ready, Brewing, Keep warm, Faulty, No carafe, No water, Low water. Status of the machine.
    SmarterUseDef   - possible values: No, Yes. If using default values then VD needs to restore to those values after brewing is finished.
     
    For global variables SmarterBrewed, SmarterMode and SmarterStatus you can use words in your language but if you do then you will have to change in code as follows:
    -- GLOBAL VARIABLES -- enter names and value mapping of your -- global variables or leave as it is and add to variables panel -- "SmarterStatus" is predefined global variable. Enter your -- name and mapping of values local smarterStatus = "SmarterStatus"; -- change value mapping to corresponds to your values in your global variable local smarterStatusMapping = {ready="Ready", notready="Not ready", brewing="Brewing", warming="Keep Warm", faulty="Faulty", nocarafe="No carafe", nowater="No water", lowater="Low water"}; -- "SmarterMode" is predefined global variable local smarterMode = "SmarterMode"; -- change value mapping to corresponds to your values in your global variable local smarterModeMapping = {filter="Filter", grind="Grind"}; -- "SmarterWarm" is global variable possible value 5 to 40 in -- step of 5 local smarterWarm = "SmarterWarm"; -- "SmarterBrewed" is predefined global variable used to change -- machine status local smarterBrewed = "SmarterBrewed"; -- change value mapping to corresponds to your values in your global variable local smarterBrewedMapping = {Yes="Yes", No="No"}; and this has to be done in all code for each button and main loop!
     
    Next step is to add icons and then do mapping of their IDs in the code. Here are the icons in order and with their names in code:
    Main icon that you will set as default on the VD and all buttons except on button Brew and Keep warm:

    In code is named iconBrewing so you will need ID and also set it up on Brew button:

    In code is named iconWarming so you will need ID and also set it up on Keep warm button:

    in code is named iconNoCarafe so you will need ID:

    in code is named iconLoWater and ID is needed:

    in code is named iconNoWater and ID is needed:

    in code is named iconFilter0 you need ID and it is showing setting for Weak strength and Filter mode:

    in code is named iconFilter1 you need ID and it is showing setting for Middle strength and Filter mode:

    in code is named iconFilter2 ID is needed and it is showing setting for Strong coffee and Filter mode:

    in code is named iconGrind0 ID is needed and it is showing setting for Weak coffee and Grind mode:

    in code is named iconGrind1 Id is needed and it is showing setting for Medium coffee and Grind mode:

    and the last one is named in code iconGrind2 Id needed and is showing setting for Strong coffee and Grind mode:

     
    How to get icon ID is explained many times here on forum so I will skip that. After you get ID of all icons then you need to replace them in main loop and for buttons Brew, Keep warm, Weak, Medium, Strong, Change mode, Reset machine and main loop. Code is well commented and looks like this:
    -- VD ICONS ---------------------------------------------------- -- enter ID numbers of corresponding icons on your system local iconBrewing = 1041; local iconWarming = 1042; local iconNoCarafe = 1044; local iconFilter0 = 1045; local iconFilter1 = 1046; local iconFilter2 = 1047; local iconGrind0 = 1048; local iconGrind1 = 1049; local iconGrind2 = 1050; local iconLoWater = 1051; local iconNoWater = 1052; And before you can start enjoying your coffee there is one more touch that needs to be done. You need to go to main loop code and first setup smart plug ID. Look for this code in main loop:
    -- SMART PLUG -------------------------------------------------- -- enter ID nuber of smart plug to which Smarter cofee is -- connected. Smart plug is the only way to check machine status -- at the present moment so it is needed for proper functioning -- of this VD local plugID = 135; Then if you want to be notified by VD when coffee is ready then find this code and enter ID of your mobile devices to which will be send. You can put as many as you like between brackets {} just separate them by comma eg. {2, 45, 121}:
    -- PUSH NOTIFICATIONS ------------------------------------------ -- define users that will receive push notifications when -- coffee is ready if leaved empty no notification will be send local userID = {} -- enter default flags: 1 - will send, 0 - will not send -- must be same number of flas as users local userFlag = {}; -- enter push message text that will be sent when coffee is -- ready local pushMessage = "Coffee is ready!" -- here you can put code that will change flags to whom push -- notification will be sent function setupUsers() -- here you can put code to dynamically change which users -- will get push notifications if you use flags end If you want to change who will receive push notifications you can use variable userFlag for that. For each userID you can enter 1 to send push notification or 0 not to send. Then you can add some code in function setupUsers() where you can change flags as you wish. For example I use that code to stop receiving push notifications when I'm away from home. If you don't need this feature then just leave brackets empty. And of course you can change message for pushMessage to your language.
     
    And if you want to completely translate VD to your language you just need to check all code for this part:
    -- MESSAGES ---------------------------------------------------- -- enter messages in your language -- response messages from coffee machine local _respBrewing = "Brewing"; local _respAlready = "Already brewing"; local _respInvalid = "Invalid argument"; local _respNocarafe = "No carafe" local _respNowater = "No water"; local _respLowater = "Low water"; local _respResetOK = "Reset OK"; local _respCheck = "Check machine"; local _respFailed = "Transfer failed"; -- command sent by this button local _command = "Brew"; -- coffee machine status messages local _statReady = "Ready"; local _statNotready = "Not ready - fill in coffee"; local _statBrewing = "Already brewing!"; local _statWarming = "Warming coffee!"; local _statFaulty = "Faulty - check machine"; local _statNocarafe = "No carafe - put it back"; local _statLowater = "Warning! - Low water"; local _statNowater = "No water - fill tank"; I try to make it easier for you as much as I could in this four days of development so all messages I collected on beginning of the code. Some buttons have more messages, some don't so you better check them all.
     
    At the end just short explanation how it works. Before first run, you will need to check if settings in VD corresponds to machine settings by checking display on the machine or original app. When this is synced you can start using it.
     
    Before first brewing status of VD must be Ready. If it is not you can press button Reset status to just reset VD or Reset machine to reset all to factory settings. Reseting machine will clear all default settings so you will need to send them again by pressing button Set above as default after you make your favorite choice of strength, cups and mode. This default settings will be always set back after brewing coffee no matter what settings was for the last brew. After brewing coffee status of the VD will be always set to Not ready except if there is No carafe in place, or No water or Low water. After rectifying cause: placing carafe in place, filling water and cleaning filter you will need to press button Reset status to put it back into Ready state. If this is too annoying you can always setup some short scene that you will trigger with some switch, button or swipe or whatever and reset VD to Ready status. If you want to keep coffee warm after brewing you can do that by setting time and then pressing button Set above as default so warming will start immediately after brewing, or you can setup time and then press button Keep warm. If during Keep warm you press button Keep warm again this will stop warming but only with new machine firmware. Keep warming time can be set up to 40 minutes. And that's it!
     
    Enjoy coding and coffee!!!  
     
    EDIT
    Still working on 4.180
     

    65 downloads

       (1 review)

    0 comments

    Updated

  11. SolarEdge Monitor

    ----------==========     SolarEdge Monitor Virtual Device     ==========----------
     
    I want to share my virtual device to monitor SolarEdge solar panels.
    SolarEdge have the possibility to read your system data with API.
     
    What you need is the VD to download and ad into the Fibaro
    Make a LUA scene where you copy the code
     
    The code is based on @jompa68  Consumption Monitor Scene and I have permission to share my version of it with the change/ integrate of SolarEdge
    With this it also supports 
    @AutoFrank SmartMessageHub and
    @Sankotronic Time Based Events Control
     
    First you need the API key that only a admin of the portal can give to you.
    When the SolarEdge was installed at my home I register the system by myself.
    You only need the serial number that is on the invertor
     
    Go to:
    https://monitoring.solaredge.com
    And select new installer Fill in the information needed see example of serial number to fill in  
    Or ask the site admin to enable the API key
     
    To generate a Site API key:
    For most time people will have standard access to the portal and will not be able to set the API Key them self
    Ask your Installer/ manufacturer to enable the API key by these steps or do it yourself.

    In the Site Admin >> Site Access tab >> Access Control tab >> API Access > section:
    Acknowledge reading and agreeing to the SolarEdge API Terms & Conditions. Click Generate API key. Copy the key. Click Save Use the key in all API requests  
    SolarEdge Scene setup
    Line 23 local vDevId > enter the VD id SE_API > Your API Key SE_CLIENT_ID > Your Client ID Line 41 (true or false) and 42 possibility to calculate rates with the the power you get from the solar panels Line 51 refresh rate > set 60 or higher due API data restrictions of SolarEdge setup you push message when and in what way you want, see description in the scene.

    940 downloads

       (4 reviews)

    17 comments

    Submitted

  12. Sonos API Player VD standalone

    Sonos API Player VD v1.0 standalone
     
    INTRODUCTION
    Sonos is the ultimate wireless home sound system that brings brilliant sound to all parts of house, room by room. Sonos API Player VD enables Fibaro Home Center 2 to control Sonos Wi-Fi multi-room speakers and show their status using node-sonos-http-api as mediator between Sonos and Fibaro.
     
    PREREQUISITES
    Fibaro Home Center 2 with firmware 4.620 or greater
    Node.js capable device such as Raspberry PI with installed jishi node-sonos-http-api
    One or more Sonos Wi-Fi multi-room speaker
    Sankotronic Lab. Emoji VD v1.1 or greater
     
    FEATURES
    Support for My Sonos stations and playlists. User can easily get list of My Sonos stations and playlist to VD and start playing from VD or other VD and scene code Support for grouping actions join and leave Support for Spotify, Apple Music and Amazon music Support for text to speech TTS for Google, VoiceRSS and AWS Poly Support for playing clips for e.g. doorbell or alarm functions Supports all standard audio commands PLAY, PAUSE, STOP, PREVIOUS, NEXT, MUTE/UNMUTE, SHUFFLE, REPEAT and CROSSFADE Support for all other functions available by jishi node-sonos-http-api Debug mode with different levels
    Multi language support with 27 languages included (see APPENDIX 1 for the list). VD can use HC2 selected language or user can select any other available language. VD will be automatically translated to the selected language
    Easy setup for VD icons. User can download HC2 Icon Preview VD to easily find icon ID number Global variables are automatically added, monitored and repaired and does not require user intervention  
    INSTALLATION
    Please check provided User Manual
     
    PACKAGE CONTENT Sonos API Player VD v1.0 User manual EN v1.0  
    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 this VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required.
     
    VERSION HISTORY
    1.0 - First public release  
    LOOK AND FEEL
    Peek in spoiler:
    Enjoy coding and your new Sonos API Player VD!
    Sankotronic

    111 downloads

       (0 reviews)

    1 comment

    Submitted

  13. Sonos Remote v1.0.1.vfib

    This is the Sonos Remote V1.0.1 VD device

    367 downloads

       (0 reviews)

    0 comments

    Submitted

  14. SOnos TTS.vfib

    This is the sonos TTS VD file

    237 downloads

       (0 reviews)

    0 comments

    Submitted

  15. sprinkler

    VD to handle sprinklers

    195 downloads

       (0 reviews)

    0 comments

    Submitted

  16. Stan urządzeń - wirtualka

    Bardzo proste urządzenie wirtualne pokazujące stan poszczególnych elementów w centralce. Urządzenie bazuje na:
     
    local selfId = fibaro:getSelfId()
    if fibaro:getValue(xxxx, 'value') == '1' then  
    fibaro:call(selfId, 'setProperty', 'ui.label1.value', 'ON' )
     
    Długo szukałem i nie znalazłem nigdzie dlatego wrzucam dla początkujących. 
    Niebędne do wykorzystania w kumunikatach głosowych lub do zobrazowania stanu w innych aplikacjach np. demopad
     
     

    117 downloads

       (0 reviews)

    0 comments

    Submitted

  17. Stan_ON_OFF.vfib

    Stan_ON_OFF.vfib
    VD pozwala na sprawdzenie stanu urządzeń ON/OFF z możliwością szybkiego ich włączania/wyłączenia

    153 downloads

       (0 reviews)

    1 comment

    Submitted

  18. TIMER_RTV.vfib

    TIMER_RTV.vfib
    Pozwala określić czas wyłączenia dane urządzenia, pokazuje jego aktualny stan, możliwość szybkiego wyłączenia, powiadomienie push na telefon, o zrealizowanym zadaniu.

    121 downloads

       (0 reviews)

    4 comments

    Submitted

  19. Twinkly Light VD

    Twinkly Light VD v1.0
    (standalone version)
    IMPORTANT NOTIFICATION!
    If you plan to continue use this VD with your Twinkly LED then DO NOT update them to latest firmware 2.7.1 because it will stop working!
    Some companies just refuse to understand importance of HA integration and it is just up to some geeks to publish unofficial API and make integration possible.
     
    INTRODUCTION
    Twinkly lights brings amazing effects and most stunning light animations to users fingertips. This beautiful Christmas lights can now be controlled by our Fibaro gateways.
     
    PREREQUISITES
    Fibaro Home Center 2 with firmware 4.120 or higher At least one Twinkly light (1st or 2nd generation) connected to home WiFi network with static IP address setting. VD is tested with 190 RGB LED icicle and 250 RGB LED strings of 2nd generation  and also strings of 1st generation at the time of publishing  
    FEATURES
    User can install multiple instances of VD for as many Twinkly lights he/she might have. Only one scene is needed to be installed for any number of Twinkly Light VD’s Uses local WiFi network connection for control. Provides turning on/off and changing brightness of the Twinkly light.
    Provides control from other code and scenes by using global variable and Update button. Multi language 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) Self adding and checking of global variable data integrity. Automatic repair of global variables without user intervention  
    INSTALLATION
    Please check provided User Manual where all steps are explained in detail and video kindly provided by @MarcoTorino71:
     
    PACKAGE CONTENT
    Twinkly Light VD v1.0 (standalone) 2 icon sets for VD (icicle and strings) Twinkly Light Scene with icon User manual v1.0 EN  
    CREDITS
    The Author wishes to acknowledge the help received from the Fibar Group S.A. in that they have kindly supplied the use of a HC2 for development purposes, free of charge.
    The Author also wishes to thanks to Pavol Babinčák for providing unofficial API reference documentation for Twinkly – Smart decoration LED lights for Christmas. Big thanks to @MarcoTorino71 for video!
     
    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 Twinkly Light VD. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required. 
     
    LEGAL NOTICE
    Twinkly is registered trademark of LEDWORKS SRL registered in Italy and other countries.
     
    VERSION HISTORY
    1.0 - First release of standalone version build on VD code for UHAS™
     
    Here is look of the Twinkly Light VD:
     

     
    Enjoy coding and your new Twinkly Light virtual device!
    Sankotronic  

    140 downloads

       (2 reviews)

    4 comments

    Updated

  20. VD - Switch CCGX Relais .lua

    VD - Switch CCGX Relais .lua
     
    A VD that can switch the AC-Out2 relais of the Victron inverter
    One can not directly switch the Quattro relais,
    therefore I used the “Venus GX Relais 2” (currently NOT used) and connected it to the contacts of the “AUX inputs of the Quattro inverter
    and you have to install an assistant on the Quattro to do the final switching o the Relays.

    33 downloads

       (0 reviews)

    0 comments

    Submitted

  21. VD-BMS.lua

    VD-BMS.lua
     
    This is for Canbus BMS
    I have a BYD Battery monitor.
    Most of the Registers are have only "0" valiues and I extracted only what I found having some values.
     
    -- Unit ID     /DeviceInstance    Remark
    -- 225            512                CAN-bus BMS

    14 downloads

       (0 reviews)

    0 comments

    Submitted

  22. VD-Quattro.lua

    VD-Quattro.lua
     
    -- READ Venus Register 3-63  UNIT ID = 242
     
     
     
     

    20 downloads

       (0 reviews)

    0 comments

    Submitted

  23. VD-Solar-Charger.lua

    VD-Solar-Charger.lua
     
    This extracts all available information from the MPPT charger.
     
    --  Unit ID        Instance in VRM
    --    245            258                Venus GX VE.Direct 1 port (ttyO2)
    --    243            260                Venus GX VE.Direct 2 port (ttyO4)

    19 downloads

       (0 reviews)

    0 comments

    Submitted

  24. VD-Venus.lua

    VD-Venus.lua
     
    Extracts all info from Unit ID 100
     
    -- READ Venus Register 840-846  UNIT ID 100

    18 downloads

       (0 reviews)

    0 comments

    Submitted

  25. VD: MQTT bridge

    0) Create HTTP -> MQTT bridge. (skip if you already have)
     
    $ sudo apt-get install mosquitto mosquitto-clients unzip attached mqtt_php.zip to www root folder, for example, /var/www/html/fibaro/mqtt.php  call from browser http://192.168.1.28/fibaro/mqtt.php where "192.168.1.28" www server where you unzip attached mqtt_php.zip and "fibaro/mqtt.php" path in your www server  here is valid response 1) import attached VD to HC2 MQTT_bridge.vfib 
    change VD params

     
    change url path for HTTP bridge in main loop
     

     
    2) create simple HTML test page
     
    <!DOCTYPE html> <html> <head> <title></title> <meta charset="utf-8" /> </head> <body> <div id="log"></div> <script src="https://code.jquery.com/jquery-3.3.1.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/paho-mqtt/1.0.1/mqttws31.min.js" type="text/javascript"></script> <script type="text/javascript"> (function () { if (!console) { console = {}; } var old = console.log; var logger = document.getElementById('log'); console.log = function (message) { if (typeof message == 'object') { logger.innerHTML += (JSON && JSON.stringify ? JSON.stringify(message) : String(message)) + '<br />'; } else { logger.innerHTML += message + '<br />'; } } })(); // Create a client instance client = new Paho.MQTT.Client("192.168.1.28", 1884, "clientId"); // set callback handlers client.onConnectionLost = onConnectionLost; client.onMessageArrived = onMessageArrived; // connect the client client.connect({ onSuccess: onConnect }); // called when the client connects function onConnect() { // Once a connection has been made, make a subscription and send a message. console.log("onConnect"); // Topic: home/roomID/deviceType/deviceID //client.subscribe("home/#"); // all events from all home //client.subscribe("home/4/#"); // all events from 4 room //client.subscribe("home/4/com.fibaro.binarySwitch/#"); // only binarySwitch events from 4 room client.subscribe("home/+/com.fibaro.binarySwitch/#"); // only binarySwitch events from all home } // called when the client loses its connection function onConnectionLost(responseObject) { if (responseObject.errorCode !== 0) { console.log("onConnectionLost:" + responseObject.errorMessage); } } // called when a message arrives function onMessageArrived(message) { console.log("Message Arrived: " + message.payloadString); console.log("Topic: " + message.destinationName); } </script> </body> </html>  
    please change 192.168.1.28 in code on IP address HTTP MQTT bridge
    locate on this test page
    you should get page like 
     
     
     
    Good luck!
     

    143 downloads

       (0 reviews)

    4 comments

    Submitted


×
×
  • Create New...