It doesn’t seem that many people use them, though I could be wrong.
I also have no idea who I would talk to to get an official look at this issue. I’m guessing it is a home assistant issue as hue plays nicely with the bulbs.
I just bought innr bulbs as a replacement for Hue lights (3 broken bulbs after 3 years with about 10-14k hours use )
Hue app works fine, iConnectHue works fine, manuall curl on the Hue API works fine, HA goes crazy
Alright guys, this is a solution that works for me:
It seems that alerts and effects are not supported by the innr bulbs. So I copied the hue component in custom_components in my config folder and just commented out the lines for alerts and effects support in the light.py.
Just the quick and dirty method but works for me, since I don’t care to loose the alert and effect function in general.
I guess it’s a good starting point to further develop the idea and maybe commit to the HA project
I use them, too and that flash to 100 is really annoying. Daytime ok…but in the evening Ilay in bed, there is ONE light on, I tell HA to turn the lightoff and all lights in the room flash to 100.
Would love if this could get solved. In the meantime I created an “Off” Scene on the bridge again, when using hue_activate_scene I don’t have this effect.
I wonder why there is so few feedback - can’t imagine so few people use them. They are cheap, available as many different models and work excellent (except in HA).
I have two Innr bulbs but I’m not using the Hue hub to control them.
If you’re looking for an alternative solution you can check out the Conbee stick in combination with deconz (see hassio addons). As a side effect this would allow you to add other zigbee devices as well that Hue does not support.
look for the the async_turn_on and async_turn_off method and comment the flash and effect blocks out
async def async_turn_on(self, **kwargs):
"""Turn the specified or all lights on."""
command = {"on": True}
if ATTR_TRANSITION in kwargs:
command["transitiontime"] = int(kwargs[ATTR_TRANSITION] * 1)
if ATTR_HS_COLOR in kwargs:
if self.is_osram:
command["hue"] = int(kwargs[ATTR_HS_COLOR][0] / 360 * 65535)
command["sat"] = int(kwargs[ATTR_HS_COLOR][1] / 100 * 255)
else:
# Philips hue bulb models respond differently to hue/sat
# requests, so we convert to XY first to ensure a consistent
# color.
xy_color = color.color_hs_to_xy(*kwargs[ATTR_HS_COLOR], self.gamut)
command["xy"] = xy_color
elif ATTR_COLOR_TEMP in kwargs:
temp = kwargs[ATTR_COLOR_TEMP]
command["ct"] = max(self.min_mireds, min(temp, self.max_mireds))
if ATTR_BRIGHTNESS in kwargs:
command["bri"] = kwargs[ATTR_BRIGHTNESS]
''' this causes the innr bulbs to flash. ignore the next lines
flash = kwargs.get(ATTR_FLASH)
if flash == FLASH_LONG:
command["alert"] = "lselect"
del command["on"]
elif flash == FLASH_SHORT:
command["alert"] = "select"
del command["on"]
else:
command["alert"] = "none"
if ATTR_EFFECT in kwargs:
effect = kwargs[ATTR_EFFECT]
if effect == EFFECT_COLORLOOP:
command["effect"] = "colorloop"
elif effect == EFFECT_RANDOM:
command["hue"] = random.randrange(0, 65535)
command["sat"] = random.randrange(150, 254)
else:
command["effect"] = "none"
'''
if self.is_group:
await self.light.set_action(**command)
else:
await self.light.set_state(**command)
async def async_turn_off(self, **kwargs):
"""Turn the specified or all lights off."""
command = {"on": False}
''' this causes the innr bulbs to flash. ignore the next lines
if ATTR_TRANSITION in kwargs:
command["transitiontime"] = int(kwargs[ATTR_TRANSITION] * 10)
flash = kwargs.get(ATTR_FLASH)
if flash == FLASH_LONG:
command["alert"] = "lselect"
del command["on"]
elif flash == FLASH_SHORT:
command["alert"] = "select"
del command["on"]
else:
command["alert"] = "none"
'''
if self.is_group:
await self.light.set_action(**command)
else:
await self.light.set_state(**command)
(dont forget to backup the file before you start editing)
I know its dirty but this works for me. I dont even know what the flash effect should looks like. I’ll try to dig a bit deeper. At the moment I’m new to home-assistant. I hope it helps.
The ‘flashing’ has been fixed for Innr bulbs since version 0.104.0 (I think) but only when they are manipulated individually. If the bulb is part of a group then the problem still occurs. A workaround is posted in another thread