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

Search the Community

Showing results for tags 'lifx'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL





Found 2 results

  1. 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
  2. Hi gents, quite a bummer that my old account has gone missing but what to do. Back to the point. I intend to create a LiFX virtual device as I have a few LiFX bulbs around my home and I can't really integrate them with Fibaro. I've also checked LiFX community and they said: I tried to connect my Lifx bulbs with the HC2. Now it works! I found a lot of information on the subject of http requests in the pages of this forum. Here you find how I did it: You need to use the new firmware version on Lifx bulbs (version 2.0) - we can do the update in the app on Android. Register on https://cloud.lifx.com , search the "settings" and register a new "token" for the API. You can find all the API information that exists on http://developer.lifx.com/ Create a new scene in HC2 and put for example: Adapt your LUA code. For authorization: Take your lifx cloud token, add a ":" and encrypt it in base64 ( https://www.base64encode.org/ ) That's all, good luck At this point, I'm a bit lost. Any ideas on what he wants to say with adapt your LUA code? local http = net . HTTPClient () http : request ( 'https://api.lifx.com/v1beta1/lights/group%3ASchlafzimmer/power.json?selector=group%3ASchlafzimmer&state=on' , { options = { method = 'PUT' , headers = { [ 'Authorization' ] = 'Basic Y2YxM2FjODJkZDcyYjRmZmZiYTAwOGQ4ZDUxMTE2ZWQ4ZTdlMTE0ZTJjYWU4YWMzZjI5NzUwMTEyMjBmMTk0Nzo =' } }, success = function ( response ) fibaro : debug ( response . data ) end , error = function ( err ) fibaro : debug ( "Error:" .. err ) end }) this bit was missing
  • Create New...