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

  • 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. I am progressively excluding my HC2 devices and migrating them to HC3, but I have a bunch that seem to not be responding to triple clicks...this was for exclusion initially, but then on re-inclusion after I managed to exclude after the 20th try for one dimmer. I think there are/could be multiple causes here: Dodgy switch wiring (there was one light that was finicky even on a directly wired setup and it took ages to even unpair) Devices not where I think they are - behind switchplate - I've already found a few by moving the HC3 closer to the ceiling or pulling a downlight out and seeing a Fibaro device come trailing behind it Connected to S2 instead of S1 by lazy sparkies (possible, unverified) Devices behind brick external walls/internal insulation, and now part of a much populated HC2 network I plan to wait for a dry/cooler day (aussie summer) to trapse my HC3 around the house to likely candidate points, but it would be easier if I could rely on extenders, a secondary controller (Aeotec Gen 7 with Silicon Labs PC controller*), or even just find the devices myself withmy Aeotec Gen 5 stick, running as a sniffer might be a better approach. My questions are: Would a sniffer on a USB stick (small, internal antenna) be of any use to try to triangulate the device's location? (I was thinking to monitor the RSSI or something) If so, does an excluded/factory fresh device send any z wave signals when interacted with via S1 switches? (I have at least one that is now excluded but still in an unknown location with an unresponsive triple click) Do exclusions get passed and processed network wide? Or only in direct range of controller? The 'remove' function lacks an NWI flag. I have added some extenders in the general areas I am having issues, without much change. Can exclusions and inclusions get passedand processed by a secondary controller? If so, do you need to run the process on the secondary (in my case through Silicon labs PC Controller),or start the exclusion on the HC3 and trust the secondary will mediate? Would powering down my HC2, Zniffer, Secondary controller make it easier for the HC3 to find devices through a normal include? *Not sure if relevant, but: All of these 'can't exclude' devices are functioning fine on the HC2 network, though I know each one I exclude changes and limits the mess on that network. I am running Engine v 3 on the HC3. None of the diminishing HC2 networking are security connected, but pretty much all of the HC3 network has been included as S0 or S1. The 700 series controller is behaving a bit odd as a secondary for the HC3 compared to the HC2. It's definitely getting included, finding devices etc, but any mapping and node tracing functions seem to get null results or error out. (the standard APIs also get nulls when tracing last route on the HC3 - I need to use the new engine API to get those details....but I didn't think the silicon labs devices would know/care about that?
  2. Hi all, I 've just bought my new HC3 but before I do the migration I have one issue: After the migration the z-wave devices will network anymore ->ok But I have some VDs only HC2 where I do not have an idea on how to migrate them to HC3, somy Idea was to keep those on HC2 and leave them running, if that is possible at all? e.G. I have one VD that is doing call handling (sending messages on Calls) with my router (fritzbox). This one is actually quite stand-alone, and does not need other devices. Would that work in general, or are all VDs not communicating anymore? cheers joystick
  3. Hi, I have multiple HomeCenters (2x HC3 and one HC2) in 3 different homes. Two of these homes are mine, but are in different geographical locations. I've created two seperate amazon accounts, both of which use alexa. The problem I'm facing is that when setting up the Yubii integration on Alexa, I don't have the opportunity to chose which HomeCenter I wish to use. This results in the devices of my main home being all added to my 2nd home (as these devices were previously added to the Alexa over there) and no way at all to ad the new HC3 and al of it's connected devices. This is particularly annoying as Fibaro (or Yubii now, idk) give you acces to multiple HomeCenters from home.fibaro.com/... . But I have no way to select any of these devices when setting up alexa with Yubii. Is there any way to specify WHICH home center to use when connecting Yubii to Alexa with the skill? Thanks for any help.
  4. I use a managed laptop from my work to manage and program my hc2. Some time I can't log in on my hc2. I get the login screen an can fill in my credentials. But pressing enter or clicking on login does not give any reaction. I tried with Microsoft edge and with Google chrome. On my very old en very slow Mac Mini I tried to login with Safari and with Google chrome and both work! I think my company has set some security settings in my browsers on mij laptop. What browser settings are necessary to use the hc2 interface? My be I can set de settings my self or i can ask my company's it to set it for me. Thanks in advance for any tips!
  5. Hi, I have Alexa connected to HC2 (4.630). Everything was fine for a long time. But now I have problem with Danfoss thermostat. Alexa is funding thermostat as: "Connected Via: Danfoss Description: Thermostat connected by FIBARO Type: thermostat Enabled When I try to change temperature, I have information: "server unresponsive" Do you have similar problem? Some time ago everything was fine.
  6. Version 1.0.3

    1,557 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.
  7. This is a Quickapp script for HC3. I am trying to get this to work in a VD on HC2. Is it possible, or do I have to do it together with a scene to make it work? Can anyone help? function QuickApp:onInit() self:updateProperty("unit", "kr/kWh") self.refresh = 60 -- in seconds local function loop() self:webrequest(); setTimeout(loop,self.refresh * 1000) end if self.username ~= "changeme" then loop() end end function QuickApp:webrequest() local tid = os.date("%R") local minutt = os.date("%M") --OPPDATERER STRØMPRIS OG SNITT HVER TIME if (minutt == "00") then self:OppdaterPris(); self:OppdaterSnitt(); end end function QuickApp:OppdaterPris() --Opprette lokale variable local GammelStrompris = fibaro.get(126,"value") local NyStrompris --Definerer http local http = net.HTTPClient(); --Definerer strengen Payload til å være kommando til tibber local payload = '{"query": "{viewer {homes {currentSubscription{priceInfo{current{total}}}}}}", "variables": null, "operationName": null}'; --API.POST til Tibber-- http : request('https://api.tibber.com/v1-beta/gql', { options = { method = "POST", headers = { ['Authorization'] = '.........', --Min Tibber ID her. ['Content-Type'] = 'application/json' }, data = payload -- Query. }, success = function(response) --fibaro.debug (response.data) --Verifiser at en har fått response.data. Dette er data som en har fått fra Tibber local data = json.decode(response.data); --fjernet local under??? NyStrompris = json.encode(data.data.viewer.homes[1].currentSubscription.priceInfo.current.total); self:updateProperty("value", tonumber(NyStrompris)) --print("OK") end, error = function(err) fibaro.debug ("Error:" .. err) end }); end function QuickApp:OppdaterSnitt() --Definerer http local http = net.HTTPClient(); --Definerer strengen average til å være kommando til tibber local average = '{"query": "{viewer {homes {currentSubscription{priceRating{daily{entries{total}}}}}}}", "variables": null, "operationName": null}'; --API.POST Til Tibber http : request ('https://api.tibber.com/v1-beta/gql', { options = { method = "POST", headers = { ['Authorization'] = '...............', --Min Tibber ID her. ['Content-Type'] = 'application/json' }, data = average -- Query }, success = function(response) --fibaro.debug(response.data) --Verifiser at en har fått response.data. Dette er data som en har fått fra Tibber local data = json.decode(response.data); local Nypris = tostring(json.encode(data.data.viewer.homes[1].currentSubscription.priceRating.daily.entries[31].total)); self:updateProperty("log", tostring(Nypris)) end, } ) end
  8. Witam wszystkich. Może temat już był, ale jestem nowy i nic nie udało mi się wyszukać. Mam 8 sztuk FGR 223 w wersji 5.1 i te działają normalnie. Podnoszą i opuszczają rolety. Mam jedną od znajomego używaną i moje HC2 widzi sterownik jako wersje 3.1 i że jest to sterownik od oświetlenia. Czy da się to uruchomić by na HC2 sterowało roletą czy to już śmieć. Reset poprzez przytrzymanie włącznika do żółtego i klik nic nie dają. Podczas ponownego parowania cały czas nie widzi jako sterowonika rolet. Proszę o pomoc!
  9. I am writing a scene which needs to set the setpoint temperature of my Z-TRM2 thermostats using a LUA command in HC2. I plan to address each thermostat individually, not through heating panels. The current value is succesfully retrieved by this command: fibaro:getValue(id, "value") where id is the id for the setpoint sub-device of the thermostat. This works as expected. However, when I try to change the setpoint through this command: fibaro:call(id, "setValue", "18") nothing happens, as shown by a subsequent getValue call. There is no error message, but the setpoint remains unchanged. I have tried to use the numeral 18 in stead of a string, and I have also tried with a variable name.What am I doing wrong in my fibaro:call command? The syntax is taken from the LUA API documentation, where this example is given: -- 'setValue' action call with one additional parameter fibaro:call(12, 'setValue', '23'); Is the required command for the Z-TRM2 module different?
  10. I am currently using HC2 and will be migrating to HC3 which I have and is live with 2 devices. I need to rewrite my scenes and VDs etc. Question - will there be any interference between the devices owned by HC2 and the ones owned by HC3 ? The reason I am asking is that the whole stuff is so flaky. Devices used to go dead all the time. After literally 5 years of contacting suppliers, installers, support and engineers, I finally figured out the main problem in my network. My conclusion/assumption is. It turns out that 2 devices had removed themselves from the "control panel" as the support call it. I had not realized this as we never tried controlling them from the app or scenes. And devices around these were using them for hopping messages, which the HC rejected. Once I re-enrolled these two (after searching for them all over the house), everything has been running sweet, for the first time in 5 years. I would call this extremely flaky thinking, process and code !!!! And I am beginning to think that I might be up for more pain from similar stupidity happening between the two HCs.
  11. All, randomly I see some of my devices bahving strange. First TZ75 roller shutter occasionally, w/o any pattern would either open or close the blinds without any scene or other user interaction. Then recently my garden gate would open (Nice engine with IBT4ZWAVE module) though not requested through script or any other user action. Worst so far, my irrigation, managed with an FGS2x3 (Fibaro device) would just switch on, not even sending a proper signal back to the HC2, so it seemed switched off although it was actually switched on. Some additonal information - IBT4ZWAVE - I can see the action in the HC2 log, but it's certain that no scene or user request was triggering the action (remotes were at home, we were on vacation, no scene related to gate was active) - TZ75 - Most of the times there is a log entry with multiple values added e.g. open 70% or close 100%. Funny thing is that I don't have a scene requesting to open by only 70% - FGS2x3 - The most scary one as neither in the log file nor in the Yubii application would state that the switch is off, although it's running Happy for any advice. Let me know what else you need to know. Setup: HC2 ver 4.620
  12. I purchased some downlights that work with Hue. I added them to hue and ensured they work. then I added them to fibaro using the plugin with no issues. I set the color to what I want in the app (in this case I want bright white). I run a scene to figure out the value, brightness and saturation. I then put it in a VD as a saved color. once I press the saved color in fibaro the light changes to an off blue color instead of bright white. I can get the light back to a bright white by going to the hue app and adjusting the color so I know its not the light itself. Does anyone know if Hue changed a setting that does not allow the light to change to the correct color? in the app they have 2 different selections for colors and White not sure if this makes a difference on fibaro now. HC2 latest OS @T.Konopka
  13. I just tried updating my HC2 to the latest release firmware. After an hour, I realized it was looping from verifying image, writing image and back again. I tried the recovery procedure. The recovery and power leds are on. But it is still doing loop the loop. I tried this 3 times. Is there anything I can do to recover ?
  14. We have a strange situation with several RGBW (2) controllers. Customer has around 10 of those modules. Most are RGBW controller, on the latest firmware, and parameter to disable associations is on. 3 of them are RGBW2 controllers. Now, client has several scenes to change the color of the RGBW modules. This works sometimes, but on other moments when the scene is started, the LED get a completely different colour. We had this behavior when client was on HC2, we migrated to HC3 and the same thing happens So, what options do we have?
  15. Hello everyone, I am preparing to deploy the design for a Villa with an area of about 8,000m2 expected to have to connect 8 HC2s together on 1 same interface. please tell me if there is a problem connecting so many HC2s? and other zwave devices with the number of 5,000 to 7,000 devices connected together in 1 Villa, is it stable? Anyone with experience please share with me. I've only ever connected 2 hc2's together with about 500 zwave devices in the past.
  16. I have a connection to Tibber for getting energy prices. But I would also like to get data from Tibber Pulse. Prices is collected with REST-API and POST request. Pulse data is collected with web socket and streams. Anyone done this before. Here is a example form python that works: from python_graphql_client import GraphqlClient import asyncio def print_handle(data): print(data["data"]["liveMeasurement"]["timestamp"]+" "+str(data["data"]["liveMeasurement"]["power"])) client = GraphqlClient(endpoint="wss://api.tibber.com/v1-beta/gql/subscriptions") query = """ subscription{ liveMeasurement(homeId:"c70dcbe5-4485-4821-933d-a8a86452737b"){ timestamp power } } """ asyncio.run(client.subscribe(query=query, headers={'Authorization': "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4"}, handle=print_handle)) Any helpe appreciated
  17. Hi everyone, Can someone help me, I am trying to enter my HC2 without success; I need help. The HC2 is connected, the blue lights stop telling me on and connected to my network but the Fibaro Finder cannot find it. Just in case I have also used an "Advanced IP Scanner" program to find it but nothing. I have rebooted, forced to delete all content hoping that something would happen but nothing ... I don't know what else to do since it won't let me in. Anyone who has any idea what I can try ???
  18. Hi! The HeatIt Z-Smoke is a combined Smoke/Motion/Temperature detecor. I have just realised that the support for Z-Smoke in HC2 is faulty. Here is what happens: The Z-Smoke motion detector will NOT trigger the Motion Detector device in HC2, but will trigger the Smoke detector device (!): The motion detector device will stay "Unbreached". I have made contact with HeatIt customer support, who has confirmed that this is a known bug and states clearly that this is a Fibaro problem. My previous experience with Fibaro indicates that getting this fixed will be a walk in the desert. Customer support also states that the problem is fixed in HC3. But I am NOT buying a new hub to fix this stupid error. Therefore: Has anyone a LUA workaround for HC2 for this potentially very useful detector?
  19. Hi! I have a electric meter Aeotec but it shows incorrect data. I consume about 1500kWh a day, but the values that I see are much lower. I put these parameters (2picture) on what I think is a total clamp, but nothing has changed. I tried to make associations for all the clamps, but I can't understand what exactly needs to be noted (3picture).Or should I have set these parameters to all 4 clamps? I will be grateful for all the advice. Thank you!
  20. I have a in wall toggle switch that i connected to my HC2 (latest version). it has been working great until now. The device will be working and then becomes "dead" "communication problem". if i awake the dead node and press turn off/on it says "transfer OK" and turns on/off the light. it stays this way for a while then goes dead again. Distance should not be an issue as it is about 10 feet from HC2. all other devices and scenes are working. I do not understand why this device keeps going dead even though it can still receive a command. Can someone help me understand what is happening and/or have a solution?
  21. Hello All, I am looking for some help to create a virtual device for a epson projector that utilizes the PJLink protocol. that way it could be used for a lot of different projectors. I am a newbie and have little experience with coding, Any help would be gtreatly appreciated.
  22. Hi I have to understand the Quick app HC2 code to make the same app to HC3. This Quick App control Multiroom AMCP MR4.50-XT - 4 Zones with Itach RS232 Serial Interface. I do not understand where in the LUA Code call function like above: local ID_VD = fibaro:getSelfId() fibaro:call(ID_VD, "pressButton", "6") fibaro:sleep(600) fibaro:call(ID_VD, "pressButton", "16") fibaro:sleep(600) fibaro:call(ID_VD, "pressButton", "26") fibaro:sleep(600) fibaro:call(ID_VD, "pressButton", "36") fibaro:sleep(300) Where I need to looking for some information about this code? MULTIROOM.vfib
  23. I am looking to by a z-wave siren which is fully implemented in HC2, with templates for the parameters. Any suggestions? I was initially thinking of the Aeotec Siren 6, but other threads seem to indicate that it is not supported in HC2 (and only for some FW-versions in HC3). What about other sirens? Any good experience to be shared?
  24. Version 1.0.0

    64 downloads

    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)
  25. Version 1.0.0

    13 downloads

    v 1.1 22/05/2021 This scene polls if a Shelly Vintage bulb is online and sets its state. The default state is "opposite" which is converted to legal values "on" or "off". When state is a numeric value it is interpreted as brightness setting. Also, this scene can be called from another scene as fibaro:startScene(number_of_this_scene,{ip_number,a_state_as_described_above}); Things are complicated by the asynchronous character of the http call. With many thanks to jgab for the solution to this challenge. There is now also a VD based on this lua.
×
×
  • Create New...