Jump to content

Search the Community

Showing results for tags 'scene'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • 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

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

  1. Version 3.0

    580 downloads

    Netatmo Weather Station VD-scene standalone INTRODUCTION Netatmo Weather station VD-scene 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 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 PACKAGE CONTENT Netatmo Indoor Base module VD (main) 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.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 VD-scene! Sankotronic
  2. I have a smoke alarm (FireAngel ST-630 with Sprue Z-wave-module) which I would like to trigger switching off a relay when an alarm is given. Basically, there are two ways to make one device trigger another, associations or scenes. Using association has the advantage of being independent of the HC2 gateway, so that is what I was looking for at first. The supplier of the alarm tells me, however, that association will not work in this case, since the appropriate association group uses a "sensor notification reports and not a set command". I am a little out of my depth here, and would appreciate any comments. The complete documentation for the device is enclosed. There is no Fibaro template for this device, but I do not expect that to make a difference. Do you agree with the supplier that association to a switch or relay is not possible in this case? What is a good and simple way to set up a scene for this function: 'If smoke alarm on device xxx then set switch yyy to "off"?' Sprue-Z-Wave-Module-Developer-Pack-2017.pdf
  3. 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 is scene code: --[[ %% properties 125 value 159 value %% globals --]] --[[ --------------------------------------------- -- CHECK DOOR/WINDOWS FOR OPEN/CLOSE STATE -- --------------------------------------------- Copyright © 2016 by Zoran Sankovic - Sankotronic Version 1.0 This scene will be triggered when any door or window is opened or closed if its ID is added above in scene header %% properties section and will send you push notification which one. If it is run manually or started with RUN button or called by VD or other scene then it will check all doors and windows that are added in winDoorID table variable and send you a popup message with the list of all doors and windows openned. This scene requires following global variables: DoorWinCheck - values: "Yes", "No" - set by VD You can enter name of your variable for that purpouse and even map your values to work properly. --]] -- PART OF CODE FOR USERS TO EDIT AND SETUP --------------------------------- -- GLOBAL VARIABLES -- enter names and value mapping of your global variables -- or leave as it is and add to variables panel -- enter name of your global variable and map values local doorWinCheck = "DoorWinCheck"; local doorWinMapping = {Yes="Yes", No="No"}; -- SENSORS, USERS, NOTIFICATIONS setup -------------------------------------- -- enter in this table IDs of all window and door sensors separated by comma -- that you want to be checked when scene is started manually or by another -- scene or VD local winDoorID = {125, 159}; -- define users to send push messages, replace with your user ID local userID = {10, 204, 210}; -- flag for each user; if 1 then send notifications else if 0 do not send notifications local userFlag = {1, 1, 1}; -- setup local variables for notifications -- popup notification title local popupTitle = "Door/Window status"; -- opoup notification subtitle usually contain time when is sent local popupSubtitle = "%H:%M:%S | %d.%m.%Y."; -- message if found any door or window opened local foundOpenedMessage = "Following doors/windows are open:"; -- message if found all doors/windows closed local foundAllClosedMessage = "All doors/windows are closed!"; -- text for button to close popup notification local buttonCaption = "OK"; -- url path to icon to show on popup message local imgUrl = "" -- DEBUGGING VARIABLES --------------------------------------------------- -- setup debugging, true is turned on, false turned off. local deBug = true; -- DEFINE FLAGS - in this section add code to change users flags ----------------- -- END OF CODE PART FOR USERS TO EDIT AND SETUP -------------------------- -- BELLOW CODE NO NEED TO MODIFY BY USER --------------------------------- local OpenWinDoor = ""; local opened = false; local sourceTrigger = fibaro:getSourceTrigger(); local doorWin = fibaro:getGlobalValue(doorWinCheck); -- send push notifications! function sendPush(message) if #userID > 0 then for i = 1, #userID do if userFlag[i] == 1 then fibaro:call(userID[i], "sendPush", message); -- Send message to flagged users end end end end function sendPopup(open, Info) if open then typeInfo = "Warning"; titleInfo = foundOpenedMessage; else typeInfo = "Success"; titleInfo = foundAllClosedMessage; end ------------------------------------- POPUP MESSAGE HomeCenter.PopupService.publish({ -- title (required) title = popupTitle, -- subtitle(optional), e.g. time and date of the pop-up call subtitle = os.date(popupSubtitle), -- content header (optional) contentTitle = titleInfo, -- content (required) contentBody = Info, -- notification image (assigned from the variable) img = "", -- type of the pop-up type = typeInfo, -- buttons definition buttons = { { caption = buttonCaption, sceneId = 0 } } }) end if (sourceTrigger["type"] == "property") then if (doorWin == doorWinMapping.Yes) then local WinDoorID = tonumber(sourceTrigger['deviceID']) local status = tonumber(fibaro:getValue(WinDoorID, "value")) if (status == 1) then local room = fibaro:getRoomNameByDeviceID(WinDoorID); local deviceName = fibaro:getName(WinDoorID); if deBug then fibaro:debug(room..' ' .. deviceName .. ' is opened.') end local pushMessage = room..' ' .. deviceName .. ' is opened.' sendPush(pushMessage); else local deviceName = fibaro:getName(WinDoorID); local room = fibaro:getRoomNameByDeviceID(WinDoorID); if deBug then fibaro:debug(room..' ' .. deviceName .. ' is closed.') end end end elseif (sourceTrigger["type"] == "other") then for i = 1, #winDoorID do if tonumber(fibaro:getValue(winDoorID[i], "value")) == 1 then opened = true; OpenWinDoor = OpenWinDoor .. fibaro:getRoomNameByDeviceID(winDoorID[i]) .." ".. fibaro:getName(winDoorID[i]) .. "\n"; if deBug then fibaro:debug("It is open: "..fibaro:getRoomNameByDeviceID(winDoorID[i]) .." ".. fibaro:getName(winDoorID[i])) end end end if not opened then OpenWinDoor = "All Closed!" end; sendPopup(opened, OpenWinDoor); end fibaro:abort(); global variable DoorWinCheck can be changed by virtual device which have one label and one button. Here is code that goes to button: local selfId = fibaro:getSelfId() -- enter name of your global variable and map values local doorWinCheck = "DoorWinCheck"; local doorWinMapping = {Yes="Yes", No="No"}; if fibaro:getGlobalValue(doorWinCheck) == doorWinMapping.Yes then fibaro:setGlobal(doorWinCheck, doorWinMapping.No) fibaro:call(selfId, "setProperty", "ui.lblDoorWinCheck.value", "No") fibaro:call(selfId, "setProperty", "currentIcon", 402); -- import icon to HC and check ID else fibaro:setGlobal(doorWinCheck, doorWinMapping.Yes) fibaro:call(selfId, "setProperty", "ui.lblDoorWinCheck.value", "Yes") fibaro:call(selfId, "setProperty", "currentIcon", 401); -- import icon to HC and check ID end And if you want you can add this code to Main loop: local selfId = fibaro:getSelfId() -- enter name of your global variable and map values local doorWinCheck = "DoorWinCheck"; local doorWinMapping = {Yes="Yes", No="No"}; if fibaro:getGlobalValue(doorWinCheck) == doorWinMapping.Yes then fibaro:call(selfId, "setProperty", "ui.lblDoorWinCheck.value", "Yes") fibaro:call(selfId, "setProperty", "currentIcon", 401); else fibaro:call(selfId, "setProperty", "ui.lblDoorWinCheck.value", "No") fibaro:call(selfId, "setProperty", "currentIcon", 402); end fibaro:sleep(3000); Don't forget to change name for label from label1 to lblDoorWinCheck or vice-versa. Here is also picture of DV and icons to use for scene and VD: EDIT : New version 1.0 with some changes for users to easier setup. Now you can use existing variable and values you just need to enter name of your variable and map your values to Yes and No for checking and sending push notification when door or window is opened. Also changed push notifications so that users are defined in table variable userID. userFlag defines if user will get notification set by 1, or not set with 0. You can add your part of code to change flags, see example: -- DEFINE FLAGS - in this section add code to change users flags ----------------- local momAway = "MomAway"; local momAwayMapping = {Yes="Yes", No="No"}; if momAway ~= "" then if fibaro:getGlobalValue(momAway) == momAwayMapping.Yes then userFlag[3] = 0; userFlag[4] = 0; end end -- END OF CODE PART FOR USERS TO EDIT AND SETUP -------------------------- Enjoy coding!
  4. Sankotronic

    [SCENE] Main scene FTBE v1.3.0

    Main scene FTBE v 1.3.0 Hello everyone! NEW version is OUT! More about scene and download you can find here: WHAT'S NEW: 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 scheduled events will continue to execute. Darkness can now be changed by measured lux level or global variable that is set to lux value measured by light measuring devices placed outside. Scene is now running on setTimeout function instead on sleep for better timing and also aligns to 0 seconds or exact minute. Sunrise & Sunset VD v1.4.0 - Modified main loop code to better handle global variables. Variables are now automatically repaired and are not reset to default settings after HC2 reboot. Added variable SunriseIcon to store VD icon ID and now when main icon for VD is set also all button icons are set automatically. Home Status VD v1.1 - Added variable HomeStatIcon to store VD icon ID and now when main icon for VD is set also all button icons are set automatically. Added label that shows most important values on VD when closed. Home Timers VD v1.1 - Added variable HomeTimersIcon to store VD icon ID and now when main icon for VD is set also all button icons are set automatically. Added label that shows most important values on VD when closed. NOTE - This version is compatible with previous versions so need to do any changes in your current code of other scenes and VD's. REQUEST - If you like my work and found it useful please give me support by rating and writing short review. Thank you! PS Dear friends from Slovakia you can find this scene and VD translated to your language here: HomeSystem.sk
  5. Hello guys, before the 4.520 update I used to have a scene which used to restart the HC2 but with the new update it doesn't work anymore and I cant figure this out. I could use some help from you guys. Thank you! Below is the code of the script. --[[ %% properties %% events %% globals --]] -- specify user and passwort in clear text local user = '' local password = '' function encbase64(data) local b='ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/'; return ((data:gsub('.', function(x) local r,b='',x:byte() for i=8,1,-1 do r=r..(b%2^i-b%2^(i-1)>0 and '1' or '0') end return r; end)..'0000'):gsub('%d%d%d?%d?%d?%d?', function(x) if (#x < 6) then return '' end local c=0 for i=1,6 do c=c+(x:sub(i,i)=='1' and 2^(6-i) or 0) end return b:sub(c+1,c+1) end)..({ '', '==', '=' })[#data%3+1]) end local http = net.HTTPClient(); http:request('http://127.0.0.1/services/system/reboot.php',{ options = { method = 'GET', headers = { ["Authorization"] = 'Basic '.. encbase64(user .. ':' .. password) } }, success = function(response) end, error = function(err) fibaro:debug("Error: " .. err) end })
  6. Sankotronic

    Sankotronic scene icon pack 2

    Version 1.0

    68 downloads

    This is second package of the icons for scenes if you like this type of design.
  7. I created several scenes where the timer functions to start the scene is being used. But none of them works. Any idea where should be the problem? See the pictures attached. Thanx for any adwise. HC2, FW 4.056,
  8. Hi all, I have an issue trying to make and HTTPS POST request from my LUA scnene in Fibaro HC. I am getting "short read" error with the URL "https://api2.magicair.tion.ru/idsrv/oauth2/token" This is my scene: ============================================= --[[ %% properties %% events %% globals --]] local authData = "username=XXX&password=YYY" function doTest() print('Test!') local requestUrl = "https://api2.magicair.tion.ru/idsrv/oauth2/token" local httpClient = net.HTTPClient() httpClient:request(requestUrl, { options = { method = "POST", headers = { ["Content-Type"] = "application/x-www-form-urlencoded", ["Content-Length"] = tostring(authData:len()) }, data = authData, timeout = 5000 }, success = function (response) fibaro:debug (response.data) end, error = function (err) fibaro:debug ("Error: " .. err) end }) setTimeout(doTest, 5*1000) end print('Script start...') doTest() ============================================= I am getting the following in my log: [DEBUG] 15:16:52: Script start... [DEBUG] 15:16:52: Test! [DEBUG] 15:16:52: Error: short read I have been trying to play with headers, data format, timeouts and all parameters I could find, however I always get the same error with the provided URL. Other HTTPS URLS I tried with GET method works just fine. Also I have been trying to do the same with cURL and it works fine with the exact same set of headers and payload (with full credentials string, of course). So the issue is somehow connected with this specific URL: "https://api2.magicair.tion.ru/idsrv/oauth2/token" The Internet is saying that short read problem in HTTPClient request might be related to ciphering protocols mismatch between the client and server. So there could be some parameter regulating this? 2 main versions, which I see: 1. Some tricky param is required to form the correct HTTPS request. 2. Some bug / missing feature in HTTPClient implementation in HC2. Anyway I am stuck and need the help from the community and HC developers. Has anyone seen something similar? Any clues? Please help! Many thanks in advance. PS Using the latest FW 4.51 of Fibaro Come Center 2
  9. Sankotronic

    Main scene FTBE

    Version 1.3.0

    707 downloads

    Main scene FTBE v1.3.0 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 PACKAGE CONTENT Main scene FTBE v1.3.0 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 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.
  10. Hi there! After latest update (or may be one before) my scene not triggered on motion state. I have Fibaro motion sensor and Fibaro wall plug. Only magic scene works. My own - no. Yes, it has Automatic flag and work when I press Run. I try to create new scene but the same. All the scenes and devices assigned to same room. What the problem?
  11. Cannon_82

    Some icons for different scenes

    Version 1.0.0

    1248 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 - - - - - RollerShutter Control SunProtection HeatingPlan, TimeBasedEvents, CalcBankHoliday and other DimLight, NightLight, ColorLight AllOff, BabyMood, BatterieCheck, WindowCheck, InventoryCheck Create Variable (in different colors)
  12. lucifer1976

    PROBLEM WITH GPS AND SCENES

    HI, SORRY FOR MY POOR ENGLISH IN ADVANCE I HAVE A HCL LITE UPDATED TO LAST VERSION AND TWO ANDROID PHONE WITH FIBARO APP UPDATED TO LAST VERSION, GPS ACTIVATED ON SMARTPHONES AND SCENE SET ON PRIVILEGE ON BOTH USERS GPS LOCATION ON FIBARO IS OK AND I SEE TRACKING OF FIBARO FAMILY AS YOU CAN SEE IN THE NEXT IMAGE. I TRIED TO MODIFY PRECISION ON FIBARO APPS AND TIME TO TRACK GPS IN FIBARO USERS, NOTHING CHANGE IT DOESN'T WORK look 7st image I CAN'T USE THE GPS FUNCTIONS, I TRY TO ARM MY SENSORS WHEN ALL OF THE SMARTPHONE ARE AWAY HOME, I TRIED WITH TWO WAYS THE FIRST: FIRST WAY (CAN'T WORK) -DECLARE A VARIABLE CASA=1 (image 1) -CREATE A SCENE (image 2) -CREATE A SECOND SCENE (image 3) SECOND WAY (CAN'T WORK) -DECLARE TWO VARIABLE (TERESA AND RICCARDO) (image 1) -CREATE THREE SCENES (image 4-5-6) CAN YOU HELP ME UNDERSTAND WHAT IS WRONG, I READ OF A LOT OF PEOPLE HAVE PROBLEMS WITH GEOFENCING THANK YOU IN ADVANCE AND SORRY FOR MY POOR ENGLISH
  13. Hi, I am using and maintaining some 50s scene on my HC2. I am developing mostly in ZeroBrane. Well so far so good. But the most anoying thing is that there is no way to "upload" scene to the HC2. Ideally this could be done from the development environment. So my question is: Is anybody using such a feature? And if yes, how? If not, I am currently looking into integrating such a feature in a GIT workflow, as git hook. So if there is any interst I would look further into it. While I have already a plan (REST/put with a decent JSON content, retrieving information from the lua script) I have still some questions, or could need some help. Even if it is just "testing". So if you there are any comments on this, just contact me. Best regards, Theo
  14. Sankotronic

    Sankotronic scene icon pack 1

    Version 1.0.0

    396 downloads

    This is first package of the icons for scenes if you like this type of design.
  15. I have an issue trying to make and HTTPS POST request. I am getting "short read" error with the URL "https://api2.magicair.tion.ru/idsrv/oauth2/token" This is my scene: ============================================= --[[ %% properties %% events %% globals --]] local authData = "username=XXX&password=YYY" function doTest() print('Test!') local requestUrl = "https://api2.magicair.tion.ru/idsrv/oauth2/token" local httpClient = net.HTTPClient() httpClient:request(requestUrl, { options = { method = "POST", headers = { ["Content-Type"] = "application/x-www-form-urlencoded", ["Content-Length"] = tostring(authData:len()) }, data = authData, timeout = 5000 }, success = function (response) fibaro:debug (response.data) end, error = function (err) fibaro:debug ("Error: " .. err) end }) setTimeout(doTest, 5*1000) end print('Script start...') doTest() ============================================= I am getting the following in my log: [DEBUG] 15:16:52: Script start... [DEBUG] 15:16:52: Test! [DEBUG] 15:16:52: Error: short read I have been trying to play with headers, data format, timeouts and all parameters I could find, however I always get the same error with the provided URL. Other HTTPS URLS I tried with GET method works just fine. Also I have been trying to do the same with cURL and it works fine with the exact same set of headers and payload (with full credentials string, of course). So the issue is somehow connected with this specific URL: "https://api2.magicair.tion.ru/idsrv/oauth2/token" The Internet is saying that short read problem in HTTPClient request might be related to ciphering protocols mismatch between the client and server. So there could be some parameter regulating this? 2 main versions, which I see: 1. Some tricky param is required to form the correct HTTPS request. 2. Some bug / missing feature in HTTPClient implementation in HC2. Anyway I am stuck and need the help from the community and HC developers. Help!
  16. I am new to LUA and have been automating my heating. I wanted to be able to create a scene that triggered the manual mode for some of the heating panels. I wanted to share the code with this forum - I am aware there is a similar thread but I found copying the code (and modifying) did not work. The LUA code below works for three rooms (just copy the section to a new section for another room), sets the Temperature to 21 for 3 hours from the current time --[[ %% properties %% events %% globals --]] local ManualTemp = 20 local ManualTime = (os.time()+3*60*60) -- 3 hours -- Repeat for each room that you want to set a manual temperature in. -- Office local IdPanel = 21 local panel = api.get("/panels/heating/" .. IdPanel) panel.properties.handTemperature = (ManualTemp) panel.properties.handTimestamp = (ManualTime) api.put("/panels/heating/" ..IdPanel, panel) -- Kitchen ID 18 local IdPanel = 18 local panel = api.get("/panels/heating/" .. IdPanel) panel.properties.handTemperature = (ManualTemp) panel.properties.handTimestamp = (ManualTime) api.put("/panels/heating/" ..IdPanel, panel)
  17. Can I get some help on this one please. I don't understand why my conditions are not working. The setup that I want is. If the light is under 10 lux and either the motion sensor detects or the Garage door opens. then the lights turn on. But what is happening at the moment is, the sensor is behaving as expected. i.e if the light is above 10 lux the sensor won't trigger but if it is bellow it will. But if the garage door opens it triggers no mater what the lux. Any help would be greatly appreciated. Scene attached. Thanks
  18. Julegeita

    Lights wont turn on

    Hi! I have been using HC2 for 2 years now. I have 3 scenes, in which i use when i leave the house or come home. 1. Nobody home - Turns off all lights, and turns the heating down on multiple devices. WORKS 2. Gone Away - The same as nr 1 but more extensive heat management. WORKS 3. Came Home - This has the problem. I use this to turn on the heat again, and to turn off some general lighting. The heating works like it should, no problem, everything get the SetTemperature that it should. The problem is the lighting. You can see them turn on in the Interface for a second, then they all fall to off again. If i run the scene multiple times, it may eventually turn them on. I have tried the following: - Changed the triggers to and from a device's state, to a variable. No change, and why should it? The scene never fails to trigger, just to work properly. - Changed the scene from using my premade "general lights" scene and instead, configuring all the lights by themselves. Even if i Trigger my general lights scene with the come home scene, or have them all configured in the come home scene individually, i get the same result. I can see them turn on in interface, the falls off again. I have built the scene with blocks, but changed it to lua for easy reading. Scene 104 at the end is just my General lighting scene, which works just fine outside this scene. --[[ %% properties 84 value %% weather %% events %% globals --]] local startSource = fibaro:getSourceTrigger(); if ( ( tonumber(fibaro:getValue(84, "value")) > 0 or tonumber(fibaro:getValue(84, "value")) == 0 ) or startSource["type"] == "other" ) then fibaro:call(339, "setThermostatSetpoint", "1", "23"); fibaro:call(348, "setThermostatSetpoint", "1", "25"); fibaro:call(324, "setThermostatSetpoint", "1", "20"); fibaro:call(71, "setThermostatSetpoint", "1", "20"); fibaro:call(79, "setThermostatSetpoint", "1", "24"); fibaro:setGlobal("HjemmeBorte", "Hjemme"); fibaro:startScene(104); end Anybody seen this? Best regards
  19. krossli

    403 access forbidden

    when creating a scene I get the message 403 ACCESS FORBIDDEN. None of mye scenes are working anymore, and I cannot create new ones. I have deleted the old scenes and restarted the Home center lite but does not help. Any solutions anyone??
  20. Hello community! I have a task: Every evening user want to set time for the curtains to open in the morning with the alarm clock. Ideal - the user simply sets the alarm in the phone and the home center gives the command to open the curtains when triggered. But I did not find such option in IFTTT. Another one - set time to open the curtains in mobile app (iOS and Android), without having to enter the web configuration. Does anyone have a solution to this problem? Or maybe any suggestions what I need to use? Thank you!
  21. vanni177

    Hue API in Scenes

    Hi I tried to use a Hue API command in my scene, but it's not working. I copied the LUA code from a working Hue VD and modify a bit, as the original is to switch off a Hue. I'd like to switch "group/0" in Hue-bridge to turn off all hue lights at once. here is how it looks like and is not working. I guess the problem is : Hue = Net.FHttp(hueIP,huePort) response ,status, errorCode = Hue:PUT('/api/'..hueuser..'/groups/0/action', '{"on":'..on..'}') Any help on that is welcome
  22. HI tio all, I would like to run a scene from a widget in my iOS device (iPhone 7 plus), but don't work if I protect the scene wit a PIN... Can someone help me? thanks in advances, Paolino
  23. I sometimes recognize that some scenes are not called as soon as they should be. A couple of my scenes are triggered by a motion sensor to switch on the light for example. Sometimes the light get on as soon as I enter the area of the motion sensor (or by triggering a door sensor). But sometimes it takes about 5 seconds until the lights are getting switched on. There are hardly any other scenes running (about four), there do exist only one VD (sonos), the amount of free RAM is at 73% and the CPU usage is between 3 and 12%. So why is it taking longer some times? Thinking about one second might be fine but more than 3 seconds? Is there any possibility to check out why this is happening? One thing is I will try to compare the event log entry with the time stamp of a debug line in one of my scenes. Would it be a good idea to having one huge scene to cover most other scenes (so this scene stays cached)?
  24. In my toilet i have an AEON LABS Multisensor 6 Aeotec, whereby my light is been triggered by the sensor. You can see the scene below, often the light goes out because there is no movement anymore in the toilet, while the person is still in the toilet! if I increase the reset time, then it takes longer before the light dims (off), but on the other side, I would like to have a scene, when I step outside the toilet the light dims to off, within around 5 seconds. Does somebody has an improved scene from his or her timer from the toilet or any other scene what is equivalent (revised) to this scene? --[[ %% properties 442 value %% globals --]] -- User Settings local debug = false; -- true local toiletSpot = 408; -- ToiletSpot -- function variables local time = 0; local timeReset = 15; -- delay in seconds during which PresentState will not change after last breach local timerStop = 16; local motionSensor = 442; -- Motion Sensor Toilet local Motion = tonumber(fibaro:getValue(motionSensor, "value")); local toiletSpotStatus = tonumber(fibaro:getValue(toiletSpot, "value")); local function log(str) if debug then fibaro:debug(str); end; end -- avoid loop of this scene if tonumber(fibaro:countScenes()) > 1 then fibaro:abort(); end ----------------------------------------------------------------------------- -- Do Not change below this line ----------------------------------------------------------------------------- function toiletFunction() fibaro:call(toiletSpot, "setValue", "75") log("Light Turned ON"); log(timeReset.. " seconds before Light goes OFF starting at " .. os.date()); fibaro:sleep(5000); -- loop start ————————————————————----------------------------------------— repeat if tonumber(fibaro:getValue(motionSensor, "value")) > 0 then time = 0; log("Movement detected from Motion Sensor"); else time = time + 1; log("No Movement " .. time .." of " .. timeReset .. " seconds Detected"); end fibaro:sleep(999); until time >= timeReset -- 16 > 15 fibaro:call(toiletSpot, "turnOff"); log("Timer stopped, Vanity Mirror OFF"); log("-------------------------------------"); end if Motion > 0 then log("Start Timer") toiletFunction() end
  25. robd

    scene or VD main loop

    Sometimes you can do things in a (LUA) scene or in the main loop of a VD. I know that programming differs a little on some items like HTTP but in general you can use the same code. Currently I have a VD that reads a json file from a PI, stores the acquired data in global variables and presents the data in the VD GUI. Next I have a scene that processes the data from the global variables and does some steering of dimmers. Is this from efficiency point of view a good method? the alternative is to put all the calculations and steering which is now done in the scene, in the main loop of the VD. is there a general rule that the processing in a scene is less or more cpu intensive or generates less or more overhead than when done in the main loop of a VD
×