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!



Smart Home Forum by FIBARO Team

All Activity

This stream auto-updates

  1. Past hour
  2. Yesterday
  3. Hello, I'd like to use a FGD-212 to control a light into a corridor. I'll use a rule (send by my Eedomux box) to set the FGD-212 at 100% during the day and 20% during the night. I want to start the light by connecting to the FGD-212 a motion sensor. I'm thinking of using two Legrand Ecodetecteur 078458 (2 wires sensor) which are already located at both side of the corridor. Is it possible to connect a motion sensor to a FGD-212 (as a toggle swich) ? As the motion sensor need to be connected all the time to the electric source, does the FGD-212 provide some power to the motion sensor at any time ? I'm giving here some drawing of the connections. Thank you for the help
  4. remote control? interessting, newer tried it, give me the name / product link
  5. Exclude, reset fgms (20sec until light yellow and click ones) Include and check Also new battery will help If update then update again After update click 3 times include button fast
  6. Do you have a suggestion ?
  7. any chance to make it work on Home Center 2? I have three GREE (with wifi) units, with static IP, would be great to be able to control them by fibaro.
  8. small optimisationLIFX_Controller (0-11).fqa
  9. Well, starting 100-1000 timers in parallell is not a problem The problem is if you start them faster then they complete so they start to stack up - as it will of course eat memory. However, timers don't eat cpu while they wait to execute, so that is at least good news.
  10. The arrays range from 10s to 100s of cells, so I don't want to have that many timers. I did not know that next existed, thanks.
  11. A bit late, but no. The slider component in the VD could have been useful if one could adjust its scale. This is still not possible in HC3. So, my solution is to have a label followed by two buttons (or 4). Example from HC3, but it applies to HC2. In this example, the buttons increase/decrease the value by 1 for Humidity and 5 for Minutes
  12. I am trying to make things more efficient this time with HC3. On the HC2, on the advice of the installer, I had to suspend a lot of my stuff as the HC was too slow. Including Heatpump controllers that I had purchased. In fact, they were the worst offenders. It was so bad, that I had to disable all scenes before a backup or it would never start up after. I had a scene to disable/enable all other scenes.
  13. function QuickApp:onInit() if not api.get("/devices/"..self.id).enabled then self:warning("Device", fibaro.getName(plugin.mainDeviceId), "is disabled") return end : : end I am not sure. Are you suggesting that it does this already ? If so, I don't see any evidence of it. If its a solution, then thanks, it will work. cleanly.
  14. What I normally do is to have a QuickApp for a particular function. For example Blinds_Controller, Gate_Controller or Bathroom_Controller. Where all the business logic is inside the QA. Then other scenes or users or Alexa just press the buttons in the QA to execute something. A few of the Logic examples in the Blinds Controller Will not open a blind in the Movie Room if someone is watching a movie. Will not close the blinds at night if there is a storm forecast, in case we lose power and cant activate them next morning Will not close blinds on Doors or Windows if they are open/ajar This way, I don't have to replicate the logic everywhere. BTW, there is an override button for the user, so they can bypass the restrictions if so desired. For some of the logic, it would be nice to know if a user pressed the button or a scene. I see this in the logs, but there is nothing there. Can I determine if a user or a scene pressed a button What is the "values":[null] in the event. [2023-06-05] [01:00:05] [TRACE] [QA-GATE]: UIEvent: {"eventType":"onReleased","values":[null],"elementName":"bnt_Lock","deviceId":1757}
  15. I did the update, and it went well. However, the HC3 box always tells me to update?
  16. Witam, jest jakiś sposób aby odczytać log a nie stan? odczytując stan tracę informacje np. o czujkach ruchu, które pomiędzy odczytami zdążyły zmienić swój stan.
  17. It can be your self:process() that crashes. Unfortunately, when called from within a setTimeout it may not show an error in the console. Try this function QuickApp:loop() local stat,res = pcall(function() self:process() end) if not stat then self:error("loop",res) end setTimeout(function() self:loop() end, self.loopInterval) end
  18. Lode

    RIP Fibaro

    I did....🤪
  19. RH_Dreambox

    RIP Fibaro

    Yes, RTSPtoWebRTC fixes the delay. My cameras now display the image in real time. But there's probably no point in telling inveterate Fibaro users how good HA is, because they won't believe what you tell them 🤣
  20. One of the things that was missing for me when I got my HC3 recently was support for LIFX lights. I have some of these lights and wanted to add them to my integrations in HC3. So, I have written a QA to provide this integration. It’s my first QA (and Lua programming) but seems to work OK. The QA is a controller for the LIFX lights in the system. On start-up it discovers the lights on the network and for each light it creates a child device. Discovery is run regularly (based on a number of seconds in a QA Variable) to allow for devices being added. Light capabilities are read from the LIFX repository on GitHub and each child is given a UI according to it’s capabilities (e.g. white temperature, colour, infrared). These are then devices in the dashboard and can be operated from scenes and other QAs like EventRunner4. This is stretching the boundaries of official feature support on the HC3 but it works! Lights are polled on a regular interval (again set by a QA Variable) to get their latest settings. This allows for the fact that other software such as the LIFX official app may also be used to control the lights and keeps them in sync. If a device goes “dark” for a period of time, (it may be turned off at a switch), then the child device is hidden. It is not deleted as it may then be created with a different ID when available again and that would make it difficult to keep consistent in other scenes/QAs. If a device is no longer used or has failed, then there is a button in the controller UI to toggle hidden children and you can then delete it using the dashboard. Light names are read from the devices and used to name the child device. Location is read and can be seen in the log file when the list devices button is used in the UI. The location is not used as you can put the devices in your own sections and rooms in the HC3. I only have white, variable white temperatures and colour lights which I can test with. It should also work with the infrared light as well. Multi-zone products are not supported as I cannot test them, and it is a UI challenge on the HC3. The controller uses the LAN protocol as I didn’t want to be dependent on the LIFX web services being available given the aim is to keep things controlled from the hub. It’s UDP over Wi-Fi so packets can go missing occasionally especially if other software is interacting with the lights as they are not good with concurrent queries and tend to send incomplete packets. This does not happen very often though. You will still need to use the LIFX app to edit names or if there are firmware upgrades available. This is a first version but does most of what I think is needed. If others think this is of any use, then I can add it to the download section. LIFX_Controller (v0-1).fqa
  21. Lode

    RIP Fibaro

    So here it is. It's just a first trial to see how things work but for the moment i'm quite happy whit it..... The Button-card is my favorite. It's so powerfull. I'm still learning all the possibilities. Also the mushroomcards are very nice. Downside is that all camera's have a significant delay. I'm going to try the webrtc integration. That should speed things up.
  22. thanks for the hint, interestingly it works with that initial function for a few days and then it suddenly stops. I now changed it to hub.setTimeout which indeed seems to have a different signature... function QuickApp:loop() self:process() hub.setTimeout(self.loopInterval, function() self:loop() end ) end let's see for a few days if that is stable now.
  23. I think it will not accept the negative value on the Fibaro tariff table. That's what happens on the QA we are using with the Spot electric price (Energy Spot Prices on the Fibaro Marketplace). Don't know what the error is, but it don't accept the value. Note that you can't also input a negative value manually.
  24. Why not use direct association (device settings, tab associations), faster, and works when the controller (HC3) is down. Then you can use parameter 6 (Fibaro Motion Sensor) to turn off the light automatically after x minutes of no motion detected. With parameter 9 you set with which lux level the lights need to turn on.
  25. Hello Guys , I just haveneed some help with some ip wifi device and I have these commands to turn on/off/toggle these commands works if i put them in browser and in other app , can anyone help me to put them in binary switch . i have no idea how this happens and if there is a way to call and update the status will be great , those devcies are actualy speakers with built in lights , so these commands is just for the light in these speaker , so later on i can control them with the room lights on and off . thanks
  26. Last week
  27. Thank you, that's a big help...Straight to the point I'll build on that!
  1. Load more activity
  • Create New...