.36 Flux_led errors

Configuration
1

Just upgraded to .36 and getting errors with flux_led. I am using this in a dedicated yaml file:

 - platform: flux_led
   automatic_add: True

Error:

17-01-16 11:43:16 homeassistant.components.light: Error while setting up platform flux_led
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 151, in _async_setup_platform
    entity_platform.add_entities, discovery_info
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/light/flux_led.py", line 75, in setup_platform
    light = FluxLight(device)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/light/flux_led.py", line 92, in __init__
    self._protocol = device[CONF_PROTOCOL]
KeyError: 'protocol'
2

It does appear to load normally if I directly add the devices in the config.

3

Should be fixed by this: https://github.com/home-assistant/home-assistant/pull/5373

1 Like
4

just as a side question, Can you have automatic_add AND also statically assign lights (in case one changes IP addresses.)?

5

Yes, but not before the bug is fixed

1 Like