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

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

  1. Bank Holiday Calc Scene (V 1.2.3a) I started creating a scene where the bank Holidays can be calculated, at the moment Switzerland (alle Kantone), Germany (alle Bundesländer), Austria (alle Bundesländer), United Kingdome (all Countries), France (some Départements), Sweden (whole Country), Ireland (whole Country), Iceland (whole Country), Poland (whole Country), Italy (whole Country), Norway (whole Country), Croatia (whole Country), Netherlands (whole Country), Czech Republic (whole Country, thanks @petr23) are covered. Work in progress for more Countries to come. With t
  2. Main scene FTBE v 1.3.4 Hello everyone! NEW version is OUT! More about scene and download you can find here: WHAT'S NEW: Main scene FTBE 1.3.4 - changed function for time of day calculation and added use of SleepState global to set time of day to morning when Awake regardless of current time Main scene FTBE 1.3.0 - cleaned some bugs, added some more checks to prevent scene from stop running due to errors. Optimized and compacted code, removed unnecessary comments. DemoMode only stops changing timers while user code and schedu
  3. Hi, Here is my working Volvo interface. Most things you can do with your Volvo On Call app, you can also read out and do with the following Scene + VD. To start off, it is using the jT.hometable so if you don't use that, start using that or strip it away in the Scene/VD. You need to add a entry in your jT.hometable called 'volvo' an example looks like this (yes all here is dummy data and also the 'time' one) volvo = { sceneid = 14, lua = 512, vin = 'YOURVINNUMBER', auth = 'Basic dsjkh42euwendeh279eynhsfd8o3yg7bo3redgefdhf' } And add this line because it uses it t
  4. Hi, it is possible to use the jpg-stream of the netatmo welcome in your own lan and without the netatmo api. I've written a scene to detect the correct url for the camera settings of the HC2 over the netatmo api. (See screens) Somebody interested? It is a first beta version because the url could change from times to times. At the moment I don't know and we have to test it. --[[ %% properties %% globals --]] -- DIESE DATEN ANPASSEN local client_id = '563a791369f740XXXXXXX' local client_secret = 'OmHqQ551M6Ww8vbTgGMWXXXXXX' local username = '[email protected]' lo
  5. Fetch data from wunderground.com, send morning and afternoon forecast to your smartphone using Fibaro app, Telegram or Pushover. Data from wunderground.com can be from a PersonalWeatherStation(PWS) or nearest LocationID(LOCID) Example of forecast and pushoptions to use. 1'st value is smartphoneID, 2'nd value is morning forecast, 3'rd is afternoon forecast, 4'th is pushoption smartphoneID_and_fcst ={{281, "06:30", "17:00", "Telegram"},{320, "08:00", "17:00", "Pushover"},{32, "08:00", "17:00", "Fibaro"}} Sending as Pushover message requires an own scene that monitors Pushover varia
  6. This is modification of old scene used by many person. I need my modification because of many (biggest or smallest) problem each time when I upgrade HC2 with new firmware and the problem not happen direct after upgrade, but hours or days after (like my last problem with corrupt z-wave databases or 503 error after restart) . I use 2 scenes: First backup-create.lua for create backup with special description. This scene is called by for ex. Main scene for time based events control one time by week. In this scenes You have parameters: backup_symbol = '!' -- this symbol
  7. Universal alarm v1.0 Hello everyone! Here is one simple scene that can be used for FIRE, FLOOD or OTHER ALARM purpose. When triggered by sensor it will send you popup, push and e-mail notification. It can also activate additional alarm sounders. You can also add additional actions to turn On lights, lower blinds or whatever action you like to happen when alarm is breached and also when sensor get back to safe state. There is no global variables needed! If you use HomeTable then you can just uncomment line where this table is read to the scene.
  8. A while ago, I joined a discussion about controlling a bathroom fan (not a whole house ventilation), by means of a single humidity sensor. This inspired me to clean up my running code and share it with you. VERY IMPORTANT! Only use this script with an Aeotec MultiSensor 6 aka MS6 aka "the square one". I have extensively tested several "MultiSensors" and only MS6 meets its specifications! The older, round MultiSensor and MultiSensor Gen5 have very bad temperature & humidity response (up to 12 percent-point deviation) so they are not good. If I ever find the time, I'll post
  9. Check status of doors and windows v1.0 This simple scene will send push message every time when door or window is opened if global Variable DoorWinCheck is set to "Yes". Usage, we are sitting in garden on the opposite side of our house main entrance door. Turning this scene on and we will be informed every time when somebody opens main door If scene is started manually with RUN button or by other scene or VD then it will check all doors and windows (or just those we put in the list) and will send popup message with the list of opened doors and windows. The rest is up to you. Here
  10. Hi guys, I thought to share a simple scene that can be called to trigger any IFTTT action via the Webhooks service. You can call this scene from any other scene or VD just like the smart message hub i.e. fibaro:startScene(sceneID ,{'TriggerID', 'Value1', 'Value2', 'Value3'}) With this you can do pretty much anything IFTTT is capable of. Some examples of what I am using it for below: - Send myself a message from HC2 to my Facebook Messenger - Control my geothermal heatpump (Nibe heatpumps support IFTTT) - Turn on/off main and guest network on the Asus
  11. 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 --]] -- ##################
  12. Season holiday iscoming so I am happy to share the scene to control the VDs for PHILIPS HUE. That can be used not only for the color lights during holidays, but also for decorative light arrangement in the garden or wherever. The scene is controlling the VDs published by @Sankotronic here : The user settings is very simple. There are three parameters to be entered. 1. timeBRI is the value for the cycle of the brightness change 2. timeHUE is the value for the cycle of the hue cycle 3. lights ={} cont
  13. --- Yamonos 1.0 beta --- -- Automatically turns on a Yamaha Receiver (and switches it to the appropriate input) when a Sonos Connect starts playing. -- It requires a Yamaha Virtual Device that stores the correct power state and input in 2 separate Global Variables -- Known issue: If there are multiple grouped devices, Sonos will keep setting the status to "Playing", even if the devices are paused. -- Feel free to improve it and share it -- adjust the variables section below --[[ %% 526 properties %% 525 properties %% 359 properties %% autostart %% events %% globals --]] local YamahaAVR = 3
  14. Hi everyone. I have few devices that don't react properly to simple "turnOn", "turnOff" actions. Might be Z-wave unresponsive at that time or RF interference or they're too far away from controller or they'e dead. Anyhow when executing fibaro:call(devID,"turnOn") the device doesn't always turning ON (same case for OFF). This phenomena very frustrating especially on predefined events that don't act as expected ( like turn on Fan in bathroom when humidity high, close garage if no presence detected at home, turn on/off water heater according to temperature and etc.) Attached sce
  15. I made a simple standby killer I'd like to share because it might be useful for someone else. The scene is triggered by a delay if house (or room is set to sleep state, I use @Sankotronic Main scene: and my alarm scene: ) But the scene is simple enough to rewrite to your own setup The file: Standby killer.lua On my todo list for this scene: - Add my fire alarm scene ( in case of fire turn off devices) - Add to my room state or main house state VD And looking to @TRicky who I still own a beer for the Hu
  16. I came to share my overflow sensor after the trigger, turn off the faucet, RGBW will blue light, red flash. --[[ %% properties 1671 value %% events %% globals --]] --1671 overflow --1633 Switch valve --1637 RGBW alarm =tonumber(fibaro:getValue(1671, "value")) fibaro:debug(alarm) if(alarm>0) then while(1==1) do fibaro:debug('触发') fibaro:call(1633,"turnOff") fibaro:call(1637, "turnOn") fibaro:call(1637, "setB", "255") fibaro:sleep(500) fibaro:call(1637, "turnOff") fibaro:call(1637, "setR", "255") fibaro:sleep(500
  17. I messed up some code tags so re-posting... Hi Here is my small tutorial on the alarm system code i use to complement the rfid keypad system. Firstly you need to create an 'ALARM' variable with at least 2 values. one variable will be OFF second variable will be FULL (or whatever name you want to give) you could if you wanted create many more variables for different zone eg i have a 3rd called DOWN you then programme the keypads (or any other scene) to change the variable to the alarm mode you want --[[ %% properties 145 value 146 value 159 v
  18. Hi, Here is a stripped down LUA port of the SunCalc JavaScript library by Vladimir Agafonkin (@mourner) https://github.com/mourner/suncalc I've done some minor modifications to the code, mainly due to the fact that the original functions returned the result in radians. Also, the result was negative or positive relative to the South direction, so I converted it to heading in degrees: 0 - North, 90 - East, 180 - South, 270 - West. I've ported just the azimuth and elevation computation (for now). The scene updates 2 simple global variables (must be created
  19. Hello all, I'd like to share the way I set my alarm powered by Fibaro door/ window -sensors and Motion detectors. I use a scene to call this scene. I hope to provide future reference how to run it otherwise. I'm using @Sankotronic scenes so Globals are based on his code I wrote this scene the @Sankotronic way, easy to use and easy to use in more than one way. I use this basic scen to arm the house when we are away and when we go to bed. At the moment I'm writing a scene that checks open zones (door/ windows not closed, breached motion detectors). When done it
  20. Like many others here, I'm frequently plagued by periodic crashes and 503 errors. In my case, I noticed that the memory usage would increase dramatically, to the point where scenes would no longer run, and the web interface wouldn't respond. Only a restart would fix it. I traced it to what I can only think is a memory leak, and I have a suspicion that it's related to the Heating/Cooling Panels. It might be fine for a while, and then for a week or so, I'll get the memory leak problem occur again. I can't be 100% sure, but I'm coming to conclusion that this happens after I've updated the He
  21. Hi All, I'm trying to setup a very simple scene: Requirements: At 20:18 AND when Magnet contact is safe lock door When I configure this in a block scene it doesn't work. It ignores the time trigger and it is immediately closing the lock. What am I doing wrong or is this a bug in Hc2 4.110? Cheers, Landshark EDIT 15/05/17 Unticking the DC Voordeur box as triggering device resolved the problem
  22. Hi, I have been tinkering with my own schedulers for some time now. I know that there are many good examples out there like GEA but I like to write my own code - easier to debug that way . The reason I post here is that I would like to share my experience and code for anyone that wants to play with it. Maybe it can inspire someone to create something more useful for the community...? I'm continuously being inspired and learning things from this community, thanks! Current version: JSched_0_98.lua Warning1: Using this code is on own risk, it is not easy and there are millions
  23. Thought this easy LUA scene to turn off all lights using the new(ish) fibaro:getDevicesId() function might be helpful to others. -- get light id's local ids = fibaro:getDevicesId( { interfaces = { "light", }, properties = { dead = false, }, enabled = true, visible = true, -- optional } ); -- loop through light ids for i, id in ipairs(ids) do fibaro:debug("Turning off " .. fibaro:getName(id)); -- turn light off fibaro:call(id, "turnOff"); end
  24. Hi there, I just released a scene to overwrite heatpanel on public holidays. You need a global variable named holidayToday with the value 1 on public holidays, so the scene will set manual target temperature from sundays heatplan to all your rooms. overwrite you weekday heatplan with the one for sunday. No more manual mode required. Just have a look and translate if necessary: http://www.mkshb.de/heizplan-fuer-feiertage/ Here is todays scene version: --[[ %% properties %% globals holidayToday --]] --------------------------------------------------- --------- V
  25. Multiroom Heating Controller My project was to write a multiroom heating controller to give indipendant control over each room using as much as the built in functionality of Home Center 2 as possible. Starting point: Create multiple rooms in the heating panel in accordance with the Advanced User Guide section 5.9.3 I did have some code to enumerate from these panels and get the following from the JSON files http://yourHC2IPAddress/api/panels/heating & http://yourHC2IPAddress/api/rooms Room Name, Room "Default Thermostat" & Default Temperature Sensor
×
×
  • Create New...