Homey Community Forum

Lifx (lan)

LIFX (LAN)

Adds support for controlling LIFX devices using your local network.
large
App Store: LIFX (LAN)
Frequently Asked Questions & Troubleshooting
Change Log

Supported Languages

:uk: English
:de: German

Supported Devices

All LIFX Devices (theoretically, I don’t own all models)
Note: You cannot add a LIFX device which is paired to any other possible LIFX app.

Permissions

From v0.8.0 on this app requires the homey:manager:api permission to access the Zones info of Homey for additional zone specific actions cards.

Available Flowcard Actions

  • All default light parameters with optional transition duration
  • Set infrared max (can also be set from the Homey app as additional dim value)
  • Set Multizone Advanced and Simple (for LIFX BEAM, LIFX Z, … - see details below)
  • Set random led colors (for LIFX BEAM, LIFX Z, …)
  • Show Progress (for LIFX BEAM, LIFX Z, …)
  • Play effects per device (see details below)
  • Special card which takes an RGB Hex Code for setting the color (useful if you have such codes in tags)

Scene Flowcard Actions

Requires you to set your LIFX cloud access token in the app settings.

  • Set scene stored in LIFX cloud
  • Set color of lights in a scene
  • Set brightness of lights in a scene
  • Turn lights of a scene on
  • Turn lights of a scene off

Zone Flowcard Actions (v0.8.0+)

Requires homey:manager:api permission for access to the zones data.
The zone cards respect hierarchy. When selecting a zone the action is applied to all child zones as well.

  • Zone On/Off with duration
  • Set Zone Color
  • Set a random color in a zone
  • Set a random color in a zone (advanced)
  • Set Zone Color by RGB Hex Code
  • Set Zone Dim Level
  • Set Zone Relative Dim Level
  • Set Zone Temperature
  • Play Effect in Zone: Glow
  • Play Effect in Zone: Saw
  • Play Effect in Zone: Pulse

Available Flowcard Triggers

  • All default light triggers
  • Ambient Light Level changed event (in flux)
  • Device gone offline/online event (generic and per device)

Available Flowcard Conditions

  • Light is On|Off

Set Multizone Action Card

The Set Multizone action card is enabled to set every single zone. To get this job done we need to use a Zone Code.

The Zone Code

The Zone Code consists of a light description, containing the color, saturation, brightness and kelvin, or a RGB hex code.

You can address as many zones as you like by adding more such data sets separated by ‘;’.

Syntax

Variant A: hue[0-360],saturation[0-100],brightness[0-100],kelvin[2500-9000];…
Variant B: #ff0000;#00ff00;…

Note:

  • Both syntax variants can be mixed.
  • Do not add a trailing ‘;’ to the end of the code.

Examples

Of course these examples could be better but this is just to demonstrate how it works afterall :wink:

  • 0, 50, 50, 2500;50, 50, 50, 2500;150, 50, 50, 2500;200, 50, 50, 2500;250, 50, 50, 2500
  • #fff;#ff0;#f00;#f0f;#00f;#0ff
  • 0, 50, 50, 2500;50, 50, 50, 2500;#f423a0;#0a34d2

Zone Start Index

This is a zero based index, which defines where to start setting the LEDs based on the Zone Code.
For example, you can split up your zone settings into multiple cards and set the zones in groups of 10 LEDs.
Setting a zone which does not exist will have no effect. By definition there cannot be more than 256 zones.

Apply Settings

If you split up your zone settings into multiple cards it might make sense to only apply the settings after sending your last zone configuration to the device. This way all zones will update simultaniously.

Not Working?

Then you have a syntax error in your configuration string. Check and try again.

Effects

Effects are supported for devices with color support only.

  • Glow: Sine & Triangle (First number is the repetitions, second number duration of one impulse)
  • Saw: Saw & Half-Sine
  • Pulse

Firmware Effects for Multizone Devices (LIFX BEAM, LIFX Z, Z2, …)

  • Move Transition (infinite) & Stop
    The move transition actually moves the zones along the line. It does not shift the values from zone to zone. This means you can change the pattern easily whilst it just keeps moving.

Firmware Effects for Chain Devices (LIFX Tile, Candle, …)

This requires you to set your LIFX cloud access token in the app settings.

  • Flames Effect (infinite)
  • Color Morph Effect (infinite)

Power Consumption Data for Homey Energy

This app preconfigures the power consumption data for energy usage approximation.
Note: If you set the values manually, this app will not update them anymore, even after the data was added to the app. If the data is missing for one of your lights, please raise an issue.

Device Settings

The device settings are just showing details about the device. There is nothing to configure there.

Power consumption values are provided by the app automatically. If you have a light which is missing those values please contact me and include the Product Name and Version shown in the Devices Overview of the App Settings menu.

Example: LIFX Tile 1-55-768

Note: If you set the energy settings manually the app will not update them automatically.

App Settings

  • Polling Interval (for light status requests - change this only if really needed)
  • Developer Token (required for LIFX Cloud Access)
  • Default light transition duration
  • List of all devices
  • Logic Behavior: This controls how the app handles on/off and dim level relationships (v0.10+)

Logic Behaviors

  • Athom (default): If dimmed to 0% and the light is on it will be turned off. If the light is off and dimmed up from 0% it is turned on.
    If the device’s dim level is 0% when turned on it automatically dims to 1%.
  • LIFX: Mimics the behavior of the original LIFX apps. You cannot dim below 1%.
    If the device’s dim level is 0% when turned on it automatically dims to 1%.
  • Original: No restrictions or relationships are applied. Logic behaves like LIFX (LAN) v0.9.4 and earlier.

Limitations

  • Firmware effects for LIFX Tile can only be controlled through cloud access.
  • LIFX Tiles cannot be controlled individually.
  • Power consumption for LIFX Tile, BEAM, Z, Z2 and Filament are not implemented, yet.
  • Ambient light flux is showing for all devices, but I don’t know if all devices support that. This feature is not officially supported by LIFX and might be removed in future versions.
  • No fixed listed IPs for lights supported. Discovery broadcast packages must be allowed to find the devices.

Unlikely, but just in case should you need to report an app crash

In case the app crashes, please submit a diagnostics report for the app before restarting the app.

NOTE: Please add your email contact in the crash report if you want me to get back to you about it. At the moment, crash reports are submitted anonymously by Homey.

On a another note

The never released memory feature is now available as a separate app, called ‘Zone Memory’.
Zone Memory works brand independent: Forum Page

3 Likes

Frequently Asked Questions

Q: Why is this app not v1.0.0 at least? Should I be concerned?
A: No. The app is fully functional. I did not bump the major version to 1, yet, because there are still a few things I want to get in before calling it complete. The following points are open still:

  • LIFX Tile support is available in the LAN protocol
  • Power consumption estimation for effect lights: Tile, BEAM, Z, Z2…

Q: Why does “Set random led colors” not respond timely?
A:: All multizone devices are limited to how many transitions they can process simultaniously. If you send too many updates those updates will be queued up to certain extend. Try tuning your settings, delays and transition times to improve the behavior.

Q: Why do you require the homey:manager:api permission?
A:: This permission is required to access the WebAPI, which currently is the only way to access information about the zones (rooms) you have configured in Homey. The zones data is used to provide action flow cards for controlling all lights in a zone (and their subzones) instead of addressing the devices individually.

Q: When I rename a light in Homey it is renamed in the LIFX app as well but when I rename it in the LIFX app Homey still shows the old name?
A: This is by design. Currently Homey does not support renaming devices from the app code. I will support updating light names in a future release, if I find a solution or workaround for this.


Troubleshooting

Problem: “Set Random Color” action card does not seem to set a color.

Reason: The card is autogenerated by Homey and sets a new hue value only.
Solution: Add a "Set Saturation" card in addition to make the color visible.

Problem: I renamed a light in Homey but in LIFX the name got cut short.

Reason: The name of the lights is stored within the physical device and it may be 32 characters long only.
Solution: Use a shorter name please.

Problem: No lights showing up for pairing.

Reason 1: The LIFX device is already paired using a different app.
Solution 1: Remove the LIFX device from the other app first.
Reason 2: Broadcast packages are blocked on your network.
Solution 2: Allow Homey and LIFX devices to send broadcast messages over your network.
Also check your wifi router settings.
It needs to allow devices to see each other.
Also configure your VLAN accordingly if you have such set up.

Change Log

v0.12.4

  • Fixed: Set color by rgb hex code card not working with flow tokens

v0.12.3

  • Fixed: Zone action set temperature not switching to temperature mode

v0.12.2

  • Updated: athom-api to v3.2.7

v0.12.1

  • Updated: athom-api to v3.2.3
  • Updated: lodash to v4.17.15
  • Updated: uft8-binary-cutter to v0.9.2

v0.12.0

  • Added: Additional Show Progress action card for multizone devices, taking a custom scale as input

v0.11.1

  • Maintenance only. No functional changes.

v0.11.0

  • Added: Zone flowcard for advanced random colors
  • Added: Set random led color for mulitzone devices (BEAM, LIFX Z, …)
  • Added: Show Progress card to use multizone devices (BEAM, LIFX Z, …) as progress bar
  • Fixed: UI typos

v0.10.5

  • Minor UI improvement for zone selectors

v0.10.4

  • Maintenance only, no functional changes

v0.10.2

  • Changed: Changing the dim level of a single light by flow card does no longer cause the light to turn on. Except if it is matter to the logic behavior rules (see App Settings for details)
  • Added: Ability to manually choose the desired dim level logic (see App Settings for details)
  • Fixed: A potential crash problem if using whites only lights

v0.9.4

  • Fixed: Light mode change not detected if done by 3rd party app

v0.9.3

  • Just minor corrections for the app store

v0.9.2

  • Changed: Simplified app store info and replaced GitHub Links with Athom Community topic link

v0.9.1

  • Fixed: Wrong or no name during device pairing

v0.9.0

  • Added: App settings now shows a product version code for all devices
  • Added: Zone Card for setting random colors
  • Added: Energy Consumption data for all devices except LIFX Z, Z2, BEAM & Tile (These require some special handling)
  • Added: Device advanced settings dialog now includes energy consumption data as known by the driver app in addition to what was actually set
  • Changed: Now using icons for wifi strength to save space in app settings dialog

v0.8.1

  • Fixed: Reduced memory footprint by removing deprecated network queries
  • Fixed: Homey firmware required is now >=3.0.0
  • Fixed: Trigger device online/offline is now using the Homey device name instead of the LIFX device name

v0.8.0

  • Added: Action cards to control lights based on Homey Zones hierarchy (requires new permission)

v0.7.0

  • Initial Version using SDKv2

Thanks for this app @Shakesbeard works brilliant and fast!

1 Like

You’re welcome. Hope you will enjoy the upcoming version as much :smiley:

1 Like

Did you know?
You can create quite some fancy effects with the MOVE animation of multizone devices, as the zone index is actually being shifted along the device. Means you can basically change the pixels whilst they are moving along the strip.

Sounds cool! I dont use the lamps in multizones though.

The next update is no in certification for rollout.
As Athom wants all light apps behave the same in aspects of onOff and dim behavior, this is now the default behavior as soon as the app is updated to v0.10.0+. In the rare case this, if this causes problems for your existing flows, you can change back to the original behavior through the app settings.
However, use of the Athom logic is encouraged.
If you are used to how the LIFX apps handle this and do not have other lights paired with Homey, you might as well choose the LIFX logic, which will mimic the original LIFX App behavior.

Great work @Shakesbeard! Athom told me it couldn’t be done! :blush:
It’s very stabile and quick for me.

What is the best way to use it with motion sensors?

For example: in the night, I use soft red light if I walk around. In the day, it’s bright white.
If the last motion was detected in the day, it’s hard to get it to soft red light without first going through bright white.
It would be nice to be able to set the temperature/color and dim all at once.

What is your recommendation for this?

hehe, I think nothing is impossible. I do have to admit that you might run into issues if you have a huge amount of lights. Like 30+ maybe. But I had no user with so many lights reporting issues yet. The network communications eats a good amount of RAM :smiley:

well, actually the logic is debounced. So if you just set all the values with flowcards in one go it will cause the LIFX api to execute it as a single command. But I also noticed that the transition behaviour might not be what you expect. This is in the hardware though and cannot be altered.

I have a similiar setup. When homey says am sleeping, my lights are reconfigured to a low dim value. And dimmed back up bright when it registers me being awake.

What I do, am actually using the zone command to reconfigure all lights. The lights do not need to be “on” for the change to be applied.

If you still suffer the flashing bright light. Try setting the dim value first and change the other settings with a little delay. 1s is enough to skip the debounce behavior. Let me know if it helps.

Also, just crossed my mind. If you change the color and dim. You should maybe try using the hue value instead of setting it by RGB with the color picker. That might help with the transition issue as the RGB color from the color picker sets a dim value too, if am not totally mistaken.

I Saw this app today and direct installed.
Worked out of The box.
Finally goodbye The default lifx app with cloud.
Thanks for The app.

2 Likes

Just wanna chime in regarding RAM, I have about 10 lamps, 2 of them multi zone. RAM usage has been around 10-12Mb. It’s one of my more resource effective apps on my Homey.

I’ve just briefly tried to get the sensor-lights perfect, no go so far. Witch method do you use for the app?

What exactly do you mean by “sensor-lights”?

And yes. With the new firmware update the RAM consumption dropped massively ^^ I’m very happy about that myself :smiley:

I just mean the lifx lights that I control by PIR sensors.

I see. Well I actually use Fibaro sensors to capture the light values per room. And then store it in a Homey variable per sensor. I update that variable only if the light in that room is not turned on. Basically to prevent “false” readings of the actual light value when the lights are on.
Then have the motion sensors assigned to Homey Zones. And if a Zone becomes active I check the light value variable for that zone to decide whether to turn the lights on or not.
And then I simple use the ‘Zone inactive for x minutes’ card to turn it off again. Works like a charm.