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

  • 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

Found 9 results

  1. Hello, I have climate shcedule problems with hc3. Now I use HC3 (now 5.140, had the same issue before with previous firmwares too), Heatit z-temp2 thermostat, fibaro relay module. My problem: I can clearly see that the issue is caused by the virtual device Thermostat& Heating zone (plugin used for manual mode). We use the heating in schedule mode, at every temperature change has the same strange thing. For example: From 4-6 pm we ask for 18 celsius, than 6-7pm we ask for 21 celsius, from 7pm again 18celsius. Now at 6pm every time the schedule mode sets the 21 celsius but immidiately after the manual mode turns on (without manually use, we do not touch the thermostat nor the application or anything for climate change) and gives again the 21 pm but with the plugin's parameter it stays for 4hours. So instead of 7pm 18 celsius the system stays on 21 for 3 more hours... Btw... I have so much trouble with HC3. The lights, scenes, heating. It has so many problems... With HC2 everything works just fine and HC3 I have issues from the beginning. I use it since about 6 months and had no sollution for many problems. Hope someone can help me, cause I need to solve this heating problem asap. Thank you!
  2. Version 1.0.3

    1,407 downloads

    UHAS v1.0.3 (Universal Home Automation System) for HC2 UHAS INTRODUCTION UHAS is a set of scenes and Virtual Devices (VD) that provide the following capabilities: Auto translation of all scenes, VD's, predefined global variables, and messages to 31 different languages (19 directly supported by HC2) (NOTE – not all languages are translated, and users are very welcomed to help with translations that are not yet done) Scheduled and repeating events based on time of day, week, month, and season including Scene FTBE which provides repeating and scheduled actions Advanced Notification Center (ANC) brings centralized notifications with support for most popular services like Pushover, Telegram, GroupMe, WhatsApp and Signal, Sonos TTS and LaMetric TIME smart clock notifications Advanced Lighting Control (ALC) with integration for Philips HUE, Nanoleaf, LIFX and Blebox devices (will be provided in separate package) Very Smart Blinds (VSB) automation Presence monitoring and control with geofencing and Netatmo presence Weather state and forecast with notifications and integration for Netatmo weather station and WeatherFlow and Tempest weather stations Home consumption monitoring and recording Appliance monitoring - with notifications Safety alarms fire and flood Security alarm integration ready with provided global variables Irrigation control based on FIBARO devices Scenes ready to use with Fibaro dimmer 2, Fibaro keyFob, Fibaro Swipe, Fibaro Button and Remotec ZRC-90 central scene activation with built in support for ANC HC2 system status notifications, automatic backups and many more... UHAS OVERVIEW UHAS has been developed for the Fibaro Home Centre 2 (HC2) home automation controller, as a series of modules, which are responsible for one particular action or job, and the user can interact with them as a group, or on their own. UHAS provides an advanced Home Automation (HA) set of features, ready to be used out of the box with minimum user effort to set up and run. Running code is provided as part of the system, doing most of the settings for the user or a systems installer. UHAS is primarily intended to be used by users of the Fibaro HC2 system who wish to have fully featured HA without the need to learn LUA programming and spending a lot of time with coding Virtual Devices and scenes. UHAS can also become a part of a mature Fibaro system installation which has developed with many modules to cover more advanced HA and more devices. UHAS Virtual Devices and scenes use proprietary code developed by author. This code is developed to minimise users involvement in installation and setting of the system. Most of the necessary setting is done by the UHAS components and other settings are simplified and minimised as much as possible. This was also possible because all UHAS VD's and scenes use role system that is used to find necessary components for actions to be performed. UHAS Virtual devices category is set automatically during translation or changing of the main icon. This means that most of the VD's should show in proper category in new mobile app as lights, blinds, gates, ambience, climate, safety, security, multimedia, remotes and other. The same goes for scenes, when scenes save their settings after first manual run then also category is set. UHAS PREREQUISITES Fibaro Home Center 2 (HC2) with firmware version 4.120 or higher (recommended but not necessary expanded RAM memory to at least 2Gb) Configured and installed z-wave devices – I.e., light switches, motion sensors, lux detectors etc. INSTALLATION AND UPGRADE NEW USERS - Please download provided UHAS v1.0.3 Installation package and UHAS Installation and User Manual v1.0.3 EN EXISTING USERS - if your UHAS is: Not yet started with installation then please download full package UHAS v1.0.3 Installation package and install. Still on v1.0 or V1.0.1 then please first download UHAS v1.02. upgrade package and install. Lastly download and install UHAS v1.03. upgrade package Installed v1.0.2 then please download UHAS v1.03. upgrade package and install. NOTE - Upgrade instructions are provided in UHAS Installation and User Manual v1.0.3 EN ADDITIONAL NOTE - In UHAS Installation and User Manual v1.0.3 EN instructions for ALC scene upgrade say: UPGRADE INSTRUCTIONS – This upgrade is recommended. To upgrade and keep your ALC Scene settings please copy new code from ALC Scene v1.3.3.lua from line: -- NEW v1.3.3 - copy code from here to the end of scene code to keep your settings above this line to the end of code. The mentioned line I forget to add to the code before making upgrade package, therefore please copy new code from line: -- THE CODE BELOW DOES NOT REQUIRE MODIFICATION BY THE USER to the end of code. Thanks goes to @MiZ for pointing that out 🙏 IMPORTANT NOTE UHAS uses its own unique global code variables. This means that UHAS will NOT influence the current system scenes, scripts, or virtual devices in any way, even if any of Sankotronic’s earlier UHAS beta versions and standalone scenes or VD's (Virtual Devices) are being used. There is no need for any changes to be made to the existing code before the installation of UHAS. The UHAS global variables are created and controlled automatically by the system so that you do not need to maintain them manually. UHAS INSTALLATION PACKAGE CONTENT (29.1Mb) 92 Virtual Devices 53 scenes Icon sets for all the above VD's and scenes THANK YOU! ❤️ I want to BIG thank to @clowg for helping me with translations and writing manual these last days speeding up publishing UHAS. BIG thank to @gucio1234 and his son Cyprian for making logo for UHAS and 3D printed with real gears! I just love it ❤️ I also want to thank many of you who helped during testing of UHAS beta versions and with translations! @clowg, @speedoxx007 ,@Bodyart, @jimicr, @gucio1234, @jompa68, @Sjekke, @robw, @rbhun, @lennypenny, @FunkFib, @MarcoT, @Orgli, @MarcoTorino71 and many others. Your help is greatly appreciated. Apologies to all other not mentioned nice people who contributed in making UHAS. I also want to thank gurus of this forum @petergebruers, @jgab, @cag014, @SmartHomeEddy and others for help with coding in LUA. And of course a BIG thank to Fibaro for providing Home Center 2 and Home Center 3 for developing purposes! BIG THANKS! also to all UHAS users for their donations! Your support is greatly appreciated! 🙏 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 UHAS. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required.
  3. Version 1.3.4

    2,779 downloads

    Main scene FTBE v1.3.4 UPDATE (30 December 2019) Changed only Main scene FTBE code. Changed function for time of day calculation and added use of SleepState global to set time of day to morning when Awake and current time is between midnight and sunrise time. KNOWN ISSUES v1.3.4 Sunrise and Sunset VD will not show correctly default sunrise and sunset time set by user in Main scene in case that that times are used due to problem with HC settings. If sunset time is before sunrise time then user must check that night time is not set to start after sunrise. Sunrise & Sunset VD does not check this time automatically. INTRODUCTION Main scene FTBE is the beating heart of the HA system. It is the only scene necessary to loop endlessly because it is the source of most important events generated on our gateways and that are time based events! It is looping once every minute making sure that our gateways are aware of the current time, part of the day, week, month and season of the year. Many actions done by our gateways are depending on current time like raising or lowering blinds, lighting control, waking up of our home and us, brewing coffee at proper time (this is extremely nice!), reminding us of important events and many other things. This scene will take care of that by changing various global variables at appropriate time thus activating other scenes triggered by them and the user can even configure it to start other scenes or press buttons on VD's at predefined intervals or at scheduled times. PREREQUISITES Fibaro Home Center 2 with firmware 4.110 or greater FEATURES Consists of scene and three VD's. Main scene FTBE loops and takes care of all timers like darkness, time of day, week days, month and season. Can also be setup to run other scenes, activate buttons on VD's or change global variables value at predefined times. VD's are used to set values of timers and show them on HC2 interface Can be setup to send push messages for scheduled execution of scenes and VD's Can track users location and calculate distance from home Darkness can be changed either by user set sunrise and sunset times or by light level measured by devices Part of the used global variables are automatically added to the system by Sunrise & Sunset VD and are automatically repaired INSTALLATION & UPGRADE Please check provided User Manual where all steps are explained in detail and check video from @MarcoTorino71: PACKAGE CONTENT Main scene FTBE v1.3.4 Sunrise & Sunset VD v1.4.0 Home Status VD v1.0 Home Timers VD v1.0.1 Icons for scene and VD's User Manual EN v1.3 CREDITS Many thanks to many Fibaro forum users for help with testing and suggestions for improvements. 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 Main scene FTBE. Please contact the author Sankotronic, on the Fibaro Forum, for any questions or support required.
  4. I have just brought me an HCL, a double relay, and heating controllers with temperature sensors. I wanted to create a system when I am able to run each room on its own heating schedules. For this. I have got the TRVs which have the separate temperature sensors linked to each TRV. .So far I have got the boiler running all the time, with the TRVs running their own schedule via the heating panel. But I am finding that at times, the room is below the temperature desired and the TRV serpoint it still stuck that temperature. What I mean by this is, I want a room to be 23c, but the sensor reporting 21c, and the trv setpoint is till at 23c. Should the set point of the trv be pushed to max in order to get to the temperature required on the temperature sensor. I am also struggling on how I can get the combi boiler to fire when a room is below the desired temperature. Any ideas on how this would be implemented.
  5. Version 1.0.0

    3,497 downloads

    Some of the icons I use for different scenes (e.g., TimeBasedEvent by Sankotronic or a scene for the sun protection in summer time) - - - - - 21.08.2018 - adding some new icons for a "battery check" and a "ambient light" scene - - - - - - - - - - 29.08.2018 - adding some new icons for a "check door/window" scene - - - - - - - - - - 14.09.2018 - adding one new icon for the roller shutter control and some different colored icon to create a variable - - - - - - - - - - 10.12.2019 - adding two new icon for the sleep state and the sleep child state - - - - - RollerShutter Control SunProtection HeatingPlan, TimeBasedEvents, CalcBankHoliday and other DimLight, NightLight, ColorLight AllOff, BabyMood, BatterieCheck, WindowCheck, InventoryCheck Create Variable (in different colors)
  6. Hi everyone, is there any way how to obtain (access) information from HC2 heating schedules in LUA scripts? I need to work with information about what temperature and when it is going to be set in some particular rooms. I can workaround this by making heating schedules sort of static and completely overpass heating panel in HC2, but that would be a bit contra productive, right? Thanks Edit: BTW my first post here, so please be gentle
  7. Version 1.0.0

    337 downloads

    Sankotronic's scene for scheduling time based events (Topic 23510) is a shining example of LUA coding and impeccably documented. It's very powerful and caters for just about every scheduling requirement that you could think of, as well as adding a lot of useful variables that can be used to check whether a scene is running at different periods in the day, week, month, year etc. However, with that power comes a little added complexity, and it's possible that your requirements are much simpler. If you're one of those people and haven't already implemented your own scheduling scene, then that's where this scene may help. SIMPLE TIMER SCENE This scene will simply update global variables, either on a periodic basis, or at selected times of the day. These global variables can then be used to trigger other scenes by adding them to the %% globals section in the header, eg: --[[ %% globals fiveMinuteTimer --]] It will automatically create the global variables, so you don't need to worry about doing this manually. At the beginning of the scene is a table that contains the timers that you want to create, and you should modify this table according to your requirements. For each timer, as well as the timer name, you also specify either: The frequency in seconds that the timer will be triggered, or The set time(s) that the timer will be triggered, in HH:MM format. Two special values for 'sunrise' and 'sunset' can be used to trigger scenes to run at these times. This is the table that you should update: local timers = { timer1 = {name="oneMinuteTimer", frequency=60}, timer2 = {name="fiveMinuteTimer", frequency=300}, timer3 = {name="fifteenMinuteTimer", frequency=900}, timer4 = {name="twelveHourTimer", frequency=43200}, timer5 = {name="garageDoorCheckTimer", setTimes={"20:00", "21:00", "22:00"}}, timer6 = {name="sunriseTimer", setTimes={"sunrise"}}, timer7 = {name="sunsetTimer", setTimes={"sunset"}} } It is recommended that you set on the 'Do not allow alarm to stop scene while alarm is running'. If not, then whenever Fibaro's alarm is triggered, then all your scenes that depend on these timers will stop.
  8. 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.,
  9. How to simplfy the following timer? : if (Mode == 'AUTO') then log("Wait 120 minuter"); -- add this by 120 = 120 x 1 minute = 2 hours after one minute can check temp for i=120,1,-1 do -- 1 minute wait for i=60,1,-1 do fibaro:setGlobal("BathroomSetTemp", FloorBathroomTargetTemp); fibaro:sleep(1000); ; end log("Test Time Delay"); end
×
×
  • Create New...