Search the Community

THIS IS THE NEW QUARTER-HOURLY VERSION This QuickApp calculates the cheapest prices for using appliances based on the hourly Tibber energy prices. This QuickApp is especially useful for appliances (like charging your car and washing the dishes) that need to run once a day, within a timeframe and during some hours. You can use more than one instance of this QuickApp if you need more than one appliance to start in the cheapest hour but not within the same timeslot. IMPORTANT This QuickApp needs the Tibber Monitor QuickApp (THE NEW QUARTER-HOURLY VERSION) to run on your HC3. Tibber today and tomorrow prices The tomorrow prices are available from 13:00 hour. If the tomorrow prices aren't available yet and the timeslot is (partially) tomorrow, a temporary calculation and start-stop plan is made with the today prices, until the tomorrow prices are available. If the start time plus duration is (partially) tomorrow, for example start time 22:00 and duration 2 hours, the calculation can be made from 13:00 hour when the tomorrow prices are available. At 22:00 the binary switch will turn ON and at 00:00 the binary switch will turn OFF. You would still have to create a script, triggers by this binary switch, to actually turn on the charging of your car, or turn on the dishwasher. QuickApp logics onInit() getQuickAppVariables() --> Get all Quickapp Variables or create them createVariables() --> Create all Variables checkPrice() --> Determine the cheapest cycle of hours missionControl() --> The central loop If Tibber main device doesn't exists --> disable QuickApp If current hour is hour to start --> turn the switch ON If current hour is hour to stop --> turn the switch OFF If current hour is 12:00 --> Check for QuickApp update If current hour is 13:00 (and timeSlotStart isn't due) --> checkPrice() with extra wait time intervalOffset to check the prices again to calculate with the tomorrow prices and to plan a new start and stop hour If current hour is the end of the timeslot --> checkPrice() to check the prices again to plan a new start and stop hour If current hour is 00 and the timeslot doesn't goes through midnight (timeSlotStart < timeSlotEnd) --> checkPrice() to transfer the tomorrow prices to todays prices If current hour is 00 and the timeslot goes through midnight (timeSlotStart > timeSlotEnd) --> Only change tomorrow prices to today prices and today prices to yesterday prices updateLabels() --> Update the labels calculateNextInterval() --> Calculate the next interval for missionControl() missionControl() --> etc. DISCLAIMERS Use this QuickApp at your own risk. You are responsible for ensuring that the information provided via this QuickApp do not contain errors. Tibber is a registered trademark being the property of TIBBER. TIBBER reserves all rights to the registered trademarks. Information which is published on TIBBER’s websites belongs to TIBBER or is used with the permission of the rights holder. Making of copies, presentations, distribution, display or any other transfer of the information on the website to the public is, except for strictly private use, prohibited unless done with the consent of TIBBER. Published material on dedicated TIBBER press websites, intended for public use, is exempt from the consent requirement. Also see: https://tibber.com/en/legal-notice Tibber API documentation: https://developer.tibber.com/docs/guides/calling-api Tibber API explorer: https://developer.tibber.com/explorer Tibber status: https://status.tibber.com Variables (mandatory and created automatically) tibberMain = The Tibber Monitor main device number language = Preferred language (default = English (en)) (supported languages are English (en), Dutch (nl), German (de), Swedish (se) and Norwegian (no)) durationTime = How many time [ormat 00:00] should the switch be ON (not more than 24 hours) timeSlotStart = At which time [ormat 00:00] should the timeslot start timeSlotEnd = At what time [format 00:00] should the timeslot end showTax = If true then the shown prices will include all taxes (default = true) setGlobalVar = true or false, whether you want tu use the Global Variables to store the start and end time (default = false) intervalOffset = The offset time in seconds to the interval for tomorrowPrices (default 60 seconds) debugLevel = Number (1=some, 2=few, 3=all (default = 1) Changes version 2.1 (23rd November 2025) Solved a tiny bug with the check for a new version. Changes version 2.0 (14th September 2025) QUARTER-HOURLY PRICES: Adjusted the Tibber Trigger QuickApp to the quarter-hourly prices. Tibber Trigger doesn't use the Tibber Monitor childs anymore, but now uses two Tibber Monitor global variables, one for all the today prices and one for all the tomorrow prices. Added lots of small improvements, like: Extra: at midnight when the timeslot is running, tomorrow prices change to today prices and today prices change to yesterday prices. Added extra handling of existance of the global variables for today en tomorrow prices. Added the date of the last price check to the labels. Added a new QuickApp variable showTax. If true then the prices will include all taxes (default = true), otherwise without taxes. Changes version 1.1 (15th January 2025) Changed the maximum durationHours to 24 hours (it was 23 hours) Added start and end time to the log text Changes version 1.0 (20th June 2024) Added two global variables for the time ON and time OFF. To use them, set the QuickApp variable setGlobalVar to true. Added an extra check at midnight if the timeslot doesn't goes through midnight (timeSlotStart < timeSlotEnd) to transfer the tomorrow prices to todays prices (after midnight) Solved a bug with a timeslot starting at the next day 23:00. Changed the label layout in case the prices aren't available yet. Changed the time tomorrow prices calculations will take place to hh:mm:ss in stead of "13:00 (+310 seconds)" Changes version 0.3 (19th March 2024) Solved a small bug when timeslot end was greater than 23 hours Changes version 0.2 (15th February 2024) Optimized calculations and turnOn/TurnOff Added translations for Dutch (nl), German (de), Swedish (se) and Norwegian (no) Initial (beta) version 0.1 (11th February 2024) Initial beta version Download the QuickApp here: Tibber_Trigger-21.fqax or from the Fibaro Marketplace: https://marketplace.fibaro.com/items/tibber-trigger How to install Open the Configuration Interface Go to Settings > Devices Click + Choose Other Device Choose Upload File Choose file from your computer with .fqax And enter the Tibber Monitor devicenumber in the tibberMain quickApp variable.

Hi FIBARO community! I'am hoping someone can help me out with something. I wrote a little quick app with VD to set a global variable on UI. We use both Yubii app on our iPhones and the dashboard in browser on our MacBooks. So, I'd like, that my VD device looks like the "factory" design... For example: In app, in the ROOMS view the device's icon is on the left side, the name of device with less size font and the main value of this device is on the right side. Same than the "factory look" device, like on the 1st attached app pic, the "Hőmérséklet" device is a factory device (Fibaro Motion Sensor's temperature sensor), the "Célhőmérséklet" device is mine VD. Or in browser view on the tiles the device's icon is on the left upper corner, the name of device with less size font in center position and the main value of this device is in center position, with big blue font. Same than the "factory look" device, like on the 2nd attached dashboard pic in browser, the "Hőmérséklet" device is a factory device (Fibaro Motion Sensor's temperature sensor), the "Célhőmérséklet" device is mine VD. Is there any solution to make it, or it's remain a dream for me? Thanx: Laszlo

Just going to start on Quickapps to rewrite my VDs from HC2. Unfortunately, the HC2 died, so I have to do it again from memory. The first thing that's not clear is the type - what their capabilities and limits are. Second is - for a door sensor, you are allowed to put on buttons and labels - when does that make sense ? I need to make these (as I had them before in HC2). Any ideas, pitfalls would be appreciated Virtual Device to replace switches that are being used to provide sensor information. I have motion sensors using standard PIRs around the house connected to fibaro relays. In HC2 there was always the danger that a user would turn the relay off. I also have relays being used to monitor the tripping of some Circuit Breakers. I am also using relays to monitor the current state of power on the 3 phases and the state of the generator. In HC2, the VD was being updated by scenes that fired on sensor status change. Do I still have to do this, or does the code now run only when the QuickApp is opened by the user ? Combos - I had garage door devices that combined sensor and door action Blind Control VD - I had two buttons for each room (open/close). Where the buttons had code under them so the blind would only close if the window/door was NOT open. Then I was pressing buttons on this VD from other scenes to open/close blinds. This meant that the logic for open/close blinds was in one place. For instance, if there was a storm warning, the blinds would not close at night - in case there was no power in the morning. It also gave the family a compact device to control all blinds. Can I still activate the buttons on the QuickApps from scenes ? Numerous Variable Control VDs that overrode the parameters used in scenes, such as time of activation or "pool closed for cleaning", or "party in progress", or "Storm warning", Select which blinds would be controlled automatically etc A Dangerous Control VD to turn on/off cold-water, sewage system, the two hot water cylinders, starting/stopping generator etc. Is it still true that unicode pictures are not allowed anymore ? I also had Overview VDs, One for the status of all doors, one for all windows, and another for all motion sensors. The Mobile app gives the total, but it doesn't seem to give any details. Have I missed something, or do I still have to code these as QuickApps.