core 🚀 - Light component always sending the 'on' attribute, making it impossible to use physical switches together ...

I've also experienced this problem, it is incredibly annoying. Even when turning lights off with, for example, Alexa through HA (via Hue emulation) often many of my lights turn back on.

jawilson on 9 Nov 2016

This is an issue I've discussed in part here and here.

The issue is the light component of HA cares not about the attributes of the light if the light is off. So according to the paradigm of HA if the light it off, it has no brightness, no color, no hue, etc.

Which I guess is true in the sense of what is actually happening in the room, but does not address the issue of what you've described along with many other issues outlined in my links.

You see, if I turn off my lights without letting HA know about it, HA will assume they're still on at least until it polls to see if they're still on, which some light components do not do. In addition the light component sends the "on" attribute anytime you want to change any aspect of the light. So flux sends a brightness change along with the "on" attribute and ultimately the light comes back on.

What this also means is that if the lights are off, there is no way to change the brightness, hue, etc to ensure the light is at those settings next time it is turned on.

I've pleaded for the an additional attribute to be allowed to allow us to set the state of the lights if they're off but @balloob has repeatedly refused.

@balloob, my solution to this problem is to allow the state of the lights to be changed even if they're off, and to only send the "on" command/attribute to the light if the user truly intends to turn on the light. This will ensure things like the flux component will only change the attributes it should such as brightness and hue and leave the state of the light alone unless the user explicitly wants it on or off.

Since 0.27 I have hacked this solution on my own box by passing a "power" attribute to the light component with "on" or "off" if I really want the light to turn on and off. Obviously this breaks the paradigm of the turn_on turn_off service, but it does allow me to change the state of the light even if it is off and ensure that doing so does not inadvertently turn the lights on or off. I know this is a crappy solution but a true fix would require a rework of the entire light component. Ideally a change_state service would need to be added leaving the turn_off, turn_on service mostly unchanged and allowing the user to change the state of the light regardless of if it is "on" or "off"

keatontaylor on 15 Nov 2016

👍1

@balloob would you be in favor of the change_state service discussed here? I wouldn't mind starting on the work myself as this flux thing and other limitations are a giant headache for me.

jawilson on 15 Nov 2016

I'd also be willing to work on this over my winter break.

keatontaylor on 16 Nov 2016

I don't see how we got from Flux turns on lights that are off to we should be able to set brightness on lights that are off. This can be simply fixed inside Flux by adding a check if the light is off before sending the turn_on command. A PR is welcome for this.

@keatontaylor issue is unrelated to this. See his linked issues for my position on it.

balloob on 16 Nov 2016

@balloob, like my position in the mentioned PRs/Issues this could also be solved by allowing the flux component to change the state of the lights while they're off, and only turning them on when the user/automation explicitly says to do so. We've seen a recurring issue of the current implementation providing undesirable results.

Changing brightness, color, hue, temperature, etc should be apathetic to the on/off state of the light.
On/Off of the light should only be changed if the automation explicitly calls for it.

Fixing the flux component by checking if the light is off before sending the turn_on command will not fix the issue described above, since the issue is a result of HA not being aware of the change in state of the light until polling is complete. So even with polling set to a low value, there are still edge cases where HA will believe the light is on when it is not. Again, my solution solves this problem along with many others as described above.

keatontaylor on 16 Nov 2016

👍2

@balloob the Flux component already calls is_on before sending the turn_on command. It's just not working correctly for some reason. I suspect a race condition between the last time the light was polled, the is_on check, and turn_on action.

def set_lights_xy(hass, lights, x_val, y_val, brightness):
    """Set color of array of lights."""
    for light in lights:
        if is_on(hass, light):
            turn_on(hass, light,
                    xy_color=[x_val, y_val],
                    brightness=brightness,
                    transition=30)


def set_lights_temp(hass, lights, mired, brightness):
    """Set color of array of lights."""
    for light in lights:
        if is_on(hass, light):
            turn_on(hass, light,
                    color_temp=int(mired),
                    brightness=brightness,
                    transition=30)

https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/switch/flux.py#L61-L78

jawilson on 16 Nov 2016

👍1

I'm running into this problem as well (using the flux switch). Whenever I turn the lights off without letting HA know about it, there's a big chance that flux will turn them back on.

Perhaps this could be changed by only sending on command in the hue component if the internal known state is not on? This would follow the instructions of the hue API (only send an on once). The polling of the hue component would then eventually put the internal state to off, which would also stop the flux switch.

I can only think of one situation where this would not be desirable: lights are on, lights are put off using Hue app, HA doesn't know lights are off, user changes color of light in HA, nothing happens (because the internal state is still on). But somehow this feels more desirable than the other way around. What do you think?

timmipetit on 10 Jan 2017

Plus one for @keatontaylor
The current attempt will IMHO never work well when combing lights with motion detectors. Now I will get a bright light at night until flux component correct brightness and color. I don't see how this could work in a perfect manner with the is_on command.

knowhy on 4 Feb 2017

It seems like this may have been fixed in 0.40.1 I haven't exhaustively tested it, however, I no longer seem to end up in cyclical conversations with Alexa asking her to turn the lights off.

alorman on 17 Mar 2017

I can't confirm that. I'm running 0.41.0. When the fluxer switch is turned on all lights get turned on as soon as I turn on one light.

knowhy on 5 Apr 2017

I tried the same thing. I rigged mine to automatically follow the state of the lights. No joy.
It seems to be some sort of bug in the outbid that runs flux.
Have you tried changing the update interval of flux?

Sent from my iPad

On Jun 3, 2017, at 7:49 PM, chimpy <[email protected]notifications@github.com> wrote:

This is bugging me too.

I had the idea to use light.toggle followed by a flux update hoping that when it was toggled on, flux would update it accordingly, and when it toggled off, flux would do nothing.

Unfortunately, when the light toggles off, flux simply turns it back on again. Disappointing as I now have to create another specific automation, or a template condition perhaps :(

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/4005#issuecomment-306008278, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMTryooVolURQAl-fHPUlKW6wfgSTmwrks5sAfD1gaJpZM4KeKcr.

alorman on 4 Jun 2017

In the end I deleted my comment as I realised it was my fault.
I had a group of two lights (bedside_lights) and whenever I toggled one of the pair, I would flux_update the group:

action:
  - service: light.toggle
    entity_id: light.bedside_1
  - service: switch.bedside_group_flux_update

If both lights were on, it was impossible to turn one of them off as flux addressed the group and as long as one of the pair was on, the group would be on, so flux would update both (which would insta-turn-back-on the light I just toggled).
The fix was to create separate flux updates for each light. Essentially, each light or group that is toggled at once must be linked to its own flux update switch.

On 4 Jun 2017, at 18:34, alorman notifications@github.com wrote:

I tried the same thing. I rigged mine to automatically follow the state of the lights. No joy.
It seems to be some sort of bug in the outbid that runs flux.
Have you tried changing the update interval of flux?

Sent from my iPad

On Jun 3, 2017, at 7:49 PM, chimpy <[email protected]notifications@github.com> wrote:

This is bugging me too.

I had the idea to use light.toggle followed by a flux update hoping that when it was toggled on, flux would update it accordingly, and when it toggled off, flux would do nothing.

Unfortunately, when the light toggles off, flux simply turns it back on again. Disappointing as I now have to create another specific automation, or a template condition perhaps :(

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/4005#issuecomment-306008278, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMTryooVolURQAl-fHPUlKW6wfgSTmwrks5sAfD1gaJpZM4KeKcr.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/4005#issuecomment-306051011, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXOodVCyXGjlX251imAOVyLyBpj0zF7ks5sAtyggaJpZM4KeKcr.

chimpy on 4 Jun 2017

👍1

Interesting! This may have some bearing on my problem! All of my flux bulbs are actually groups of lights within fixtures, so perhaps it's some residual command not being propagated.

I'll have to try separating my lights out into individual bulbs and seeing what I get.

Thanks!

From: chimpy notifications@github.com
Sent: Sunday, June 4, 2017 3:27 PM
To: home-assistant/home-assistant
Cc: alorman; Comment
Subject: Re: [home-assistant/home-assistant] Light component always sending the 'on' attribute, making it impossible to use physical switches together with HA. (#4005)

In the end I deleted my comment as I realised it was my fault.
I had a group of two lights (bedside_lights) and whenever I toggled one of the pair, I would flux_update the group:

action:

service: light.toggle
entity_id: light.bedside_1
service: switch.bedside_group_flux_update

If both lights were on, it was impossible to turn one of them off as flux addressed the group and as long as one of the pair was on, the group would be on, so flux would update both (which would insta-turn-back-on the light I just toggled).
The fix was to create separate flux updates for each light. Essentially, each light or group that is toggled at once must be linked to its own flux update switch.

On 4 Jun 2017, at 18:34, alorman notifications@github.com wrote:

I tried the same thing. I rigged mine to automatically follow the state of the lights. No joy.
It seems to be some sort of bug in the outbid that runs flux.
Have you tried changing the update interval of flux?

Sent from my iPad

On Jun 3, 2017, at 7:49 PM, chimpy <[email protected]notifications@github.com> wrote:

This is bugging me too.

I had the idea to use light.toggle followed by a flux update hoping that when it was toggled on, flux would update it accordingly, and when it toggled off, flux would do nothing.

Unfortunately, when the light toggles off, flux simply turns it back on again. Disappointing as I now have to create another specific automation, or a template condition perhaps :(

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/4005#issuecomment-306008278, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMTryooVolURQAl-fHPUlKW6wfgSTmwrks5sAfD1gaJpZM4KeKcr.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/4005#issuecomment-306051011, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXOodVCyXGjlX251imAOVyLyBpj0zF7ks5sAtyggaJpZM4KeKcr.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/4005#issuecomment-306061421, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMTryhuXtLsiN7H6_0EqqdFhhhA6Le4nks5sAwU3gaJpZM4KeKcr.

alorman on 4 Jun 2017

I have the same problem with my hue lights. I have a fluxer component which is turned on by default. If I press the physical hue switch the lights go off. But after a few seconds they light up again. If I press multiple times after a while the lights stay off.

My assumption is that the hue bridge is polled every X seconds. And fluxer runs every Y seconds. Even if fluxer checks if the lights are off there is a high chance that between the last bridge call the lights got switched off. In order to have a higher chance fluxer should run as soon as the status got polled and do nothing until the next status got polled.

If the hue polling would add a last update attribute to each light and a last update attribute to the fluxer switch we could just build a automation rule which calls fluxer based on these attributes.
"If last fluxer update was more than 60s ago and light update changed right now... run fluxer now"

runningman84 on 26 Jul 2017

Added a last_update attribute to the hue light components shows that each status is only updated every 30 seconds.

What do you think about my proposed solution?

runningman84 on 27 Jul 2017

Unfortunately, your solution will only work for some types of bulbs. It will _not_ work correctly for Z-Wave as those are local push, not local polling.

jawilson on 27 Jul 2017

I suppose that this problem would not occur for local polling because, status updates are instant there... maybe it would occur if the transition is handled by fluxer in an interval of 1 second. But if you update the lights with fluxer only every 60 seconds there is a max chance of 1/60 to have it turned on again after you switched.

I have added my proposed attributes in my hue dev branch:
https://github.com/runningman84/home-assistant/tree/hue

This is the corresponding configuration:

sensor:
  - platform: template
    sensors:
      time_between_fluxer_and_hue_update:
        value_template: '{{
as_timestamp(states.light.hue_lightstrip_monitor.attributes.last_update) | int
-
as_timestamp(states.switch.fluxer_office.attributes.last_update) | int
        }}'
        friendly_name: 'Time between fluxer and hue light update'
        unit_of_measurement: 'seconds'

light:
  - platform: hue
    host: XXX
    filename: phue1.conf
    allow_unreachable: true
    allow_hue_groups: true

switch:
- platform: flux
  lights:
    - light.hue_fido
    - light.hue_lightstrip_monitor
  name: fluxer_office
  stop_time: '23:00'
  start_colortemp: 4000
  sunset_colortemp: 3000
  stop_colortemp: 1900
  brightness: 200
  disable_brightness_adjust: false
  mode: xy

automation:
- id:                   start_fluxer_in_sync
  alias:                Turn on fluxer after hue light update
  trigger:
    - platform:         numeric_state
      entity_id:        sensor.time_between_fluxer_and_hue_update
      above:            60
  condition:
    condition:          and
    conditions:
      - condition:      state
        entity_id:      light.hue_fido
        state:          'on'
  action:
    service:            switch.fluxer_office_update
    entity_id:
      - switch.fluxer_office

I could not reproduce the error with this configuration. I can switch off the lights at any time and they are not switched on again by fluxer. If the lights are on fluxer changes the status immediately after hue api is polled and the last fluxer update was more than 60 seconds ago.

The only problem is that if you switch off the light and turn it on and the template senor is already above 60 it is not triggered anymore. I do not know if we could run this at any value above 60. One solution would be multiple triggers with values like 60,600,3600,..

runningman84 on 27 Jul 2017

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

balloobbot on 20 Oct 2017

I can verify that this issue still occurs on the newest version of Home Assistant.

tdickman on 22 Oct 2017

This is an issue for me as well. I have made sure HA is the only service interacting with my Hue lights, but the issue still occurs for example during transitions.

When you turn_off on a light with a transition, you would want HA to immediately register the light as OFF. It actually does, but within the next polling interval, HA will receive information from the Hue Bridge that this light is actually on, albeit with a reduced brightness. HA registers the light as ON again. The Flux component will then call the turn_on service with a new color temperature set-point. In the end, the Hue light respects the transitions and power commands, and therefor stays on at the minimum brightness level.

I completely agree with the suggestion to allow attribute changes of an object without changing it's power state. You should be able to adjust a light's brightness and color irrespective of it's power. I think it is the most sensible solution for a lot of use cases. The component could let HA know which attributes can be adjusted when it is off, depending on whether it can pass the attributes to the device.

IceEyz on 22 Oct 2017

👍1

I built a fix for this back in January, but a set_state function has to be added to every light, so it currently only support Hue lights. I haven't had the time to maintain it unfortunately, so it doesn't work with the newest version of Home Assistant.

Basically I added a 'set_state' function to lights that is able to adjust light parameters without explicitly turning them on. Every light type would have to be updated to support this new function, or we'd have to come up with a fallback option. I used this for about 6 months until I stopped maintaining it, but it was flawless during that time period.

https://github.com/tdickman/home-assistant/commit/a1a532fb185c8ecfc297c62382e58c1487f67be8

tdickman on 22 Oct 2017

+1 on addressing this issue. I had to put automations in place to turn off the flux light adjustment at certain times of the day so my girlfriend is able to turn off the lights using the Hue app.

fanaticDavid on 23 Oct 2017

I have installed motion sensors in front of my switches. Motion disables the fluxer service. This is a quite expensive workaround

runningman84 on 23 Oct 2017

@tdickman Why not submit a PR with your changes so we can look at including the functionality in HASS? You wouldn't have to add it to all components.

tschmidty69 on 6 Feb 2018

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

balloobbot on 29 May 2018

The issue exists in the latest version of Home Assistant.

jawilson on 30 May 2018

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

balloobbot on 26 Oct 2018

This issue still exists.

I've currently settled with fast or no transitions, or automations that stop the flux component before requesting a slow light transition.

A service that would allow changing an entity's attributes without changing it's power would fix this. Checking a light's current state doesn't cut it, since the current state is not telling you whether the light may be in a transition towards on or off.

IceEyz on 28 Oct 2018

Hey man,

Have you tried disabling flux from periodically updating? Do that, then simply call the fluxer switch « manually » in the action after the light.turn_on (with a delay 0.5s) after each motion event or switch toggle.

My switches all call flux update 0.5s after every toggle.
My motion sensors all call flux update after every turn_on (during the evening only).

The only shortcoming for this method is if you turn on lights during the daytime with a switch (not with motion sensors). This means they will flux update once when you toggle the switch, and that’s it.

On 28 Oct 2018, at 16:27, IceEyz notifications@github.com wrote:

This issue still exists.

I've currently settled with fast or no transitions, or automations that stop the flux component before requesting a slow light transition.

A service that would allow changing an entity's attributes without changing it's power would fix this. Checking a light's current state doesn't cut it, since the current state is not telling you whether the light may be in a transition towards on or off.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

chimpy on 28 Oct 2018

Confirmed. I did this, same residual effect of sometimes coming on in the wrong flux state then updating over the next minute or so.
Still kind of hack-y.

From: chimpy notifications@github.com
Sent: Sunday, October 28, 2018 3:45 PM
To: home-assistant/home-assistant
Cc: alorman; Comment
Subject: Re: [home-assistant/home-assistant] Light component always sending the 'on' attribute, making it impossible to use physical switches together with HA. (#4005)

Hey man,

Have you tried disabling flux from periodically updating? Do that, then simply call the fluxer switch « manually » in the action after the light.turn_on (with a delay 0.5s) after each motion event or switch toggle.

My switches all call flux update 0.5s after every toggle.
My motion sensors all call flux update after every turn_on (during the evening only).

The only shortcoming for this method is if you turn on lights during the daytime with a switch (not with motion sensors). This means they will flux update once when you toggle the switch, and that’s it.

On 28 Oct 2018, at 16:27, IceEyz notifications@github.com wrote:

This issue still exists.

I've currently settled with fast or no transitions, or automations that stop the flux component before requesting a slow light transition.

A service that would allow changing an entity's attributes without changing it's power would fix this. Checking a light's current state doesn't cut it, since the current state is not telling you whether the light may be in a transition towards on or off.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/4005#issuecomment-433735318, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMTrymQvV-TSz9x4ubtA_sntO46Mi__8ks5upglXgaJpZM4KeKcr.

alorman on 28 Oct 2018

True. I guess what we really want is a kind of lifx_set_state to be used across all lights for the fluxer.

On 28 Oct 2018, at 20:49, alorman notifications@github.com wrote:

Confirmed. I did this, same residual effect of sometimes coming on in the wrong flux state then updating over the next minute or so.
Still kind of hack-y.

From: chimpy notifications@github.com
Sent: Sunday, October 28, 2018 3:45 PM
To: home-assistant/home-assistant
Cc: alorman; Comment
Subject: Re: [home-assistant/home-assistant] Light component always sending the 'on' attribute, making it impossible to use physical switches together with HA. (#4005)

Hey man,

Have you tried disabling flux from periodically updating? Do that, then simply call the fluxer switch « manually » in the action after the light.turn_on (with a delay 0.5s) after each motion event or switch toggle.

My switches all call flux update 0.5s after every toggle.
My motion sensors all call flux update after every turn_on (during the evening only).

The only shortcoming for this method is if you turn on lights during the daytime with a switch (not with motion sensors). This means they will flux update once when you toggle the switch, and that’s it.

On 28 Oct 2018, at 16:27, IceEyz notifications@github.com wrote:

This issue still exists.

I've currently settled with fast or no transitions, or automations that stop the flux component before requesting a slow light transition.

A service that would allow changing an entity's attributes without changing it's power would fix this. Checking a light's current state doesn't cut it, since the current state is not telling you whether the light may be in a transition towards on or off.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/4005#issuecomment-433735318, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMTrymQvV-TSz9x4ubtA_sntO46Mi__8ks5upglXgaJpZM4KeKcr.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/4005#issuecomment-433735606, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXOocrOCjnuVezT6S6zrUQFOaKJSwYzks5upgpagaJpZM4KeKcr.

chimpy on 28 Oct 2018

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

balloobbot on 7 Mar 2019

I would still like the light component to support changing the attributes of a light without turning it on.
This should be taken care of by the state machine, so that when the 'on' attribute is sent, the correct (last) values could be sent alongside.

ricmik on 12 Mar 2019

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

iamelk on 22 Mar 2019

Yes this is still a feature that's required to solve problems with transitioning lights.

IceEyz on 22 Mar 2019

Slightly different behaviour with IKEA Tradfri:

Turn on a light
Turn on the Fluxer switch
Turn off the light via remote
Light doesn't turn off
Change colour or brightness on a remote
Switch off
Lights go off

agilob on 10 May 2019

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 8 Aug 2019

I really wish there were some way to deal with this, but it still exists.

jawilson on 8 Aug 2019

👍1

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 6 Nov 2019

Still an issue on tradfri

This bot is really annoying. This is still an issue, fluxer is completely broken and in current state could be as well removed.

agilob on 7 Nov 2019

This is still an ongoing issue with 0.103.6 and Trådfri lights. Clearly related to HA having stale status information from the gateway. I've tried various workarounds including decreasing transition time, increasing update interval, moving the interval to an automation, automating power-cycling of the Trådfri gateway overnight. Each measure reduces the incidence of the problem, but it is not completely eliminated. Another factor may be the number of devices, I have some large groups with 6 lights in each and a total of 30+ lights. It seems that the Trådfri gateway can become slow to poll/update status and so when switching many lights at once maybe some events are dropped. Despite this I still value the Flux component for the needed ability to change colour temperature during the day - it was a primary use case for implementing smart lighting and HA in the first instance. I am still hoping for a real solution to this problem.

lakofsth on 7 Jan 2020

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 7 Apr 2020

👎1

eh this bot again... just because issue doesnt have activity doesn't mean it's ok to close it. When I see already open ticket for a bug I dont think "let's comment here to send more notifications to random people" but "cool, someone already opened it, let's wait for reaction".

agilob on 7 Apr 2020

👍1

I read through all the conversation here and it seems that the only possible solution is to support set color/brightness without changing power states. However, it will require the devices to support. Many light bulbs only support changing color/brightness when turning on, which is the same behavior as HA. There is no easy fix for this problem without hardware support. And I think that is why this issue has been here for such a long time.

shenxn on 11 May 2020

👍1

I believe home-assistant needs a component to represent the configuration of sensors and hardware switches and their related configuration.

At least for Philips Hue the configuration defining what the system will do when a for example a PIR sensor is triggered is accessible via the API. I don't own a hardware switch, but I think that the configuration for switches is the same as sensors for Hue. I don't think that the light component can cover that. In case of hue it is covered by different endpoints.

With hue you can make a POST request to /api/<username>/rules

with

{ "name":"Wall Switch Rule", "conditions":[ {"address":"/sensors/2/state/buttonevent","operator":"eq","value":"16"} ], "actions":[ {"address":"/groups/0/action","method":"PUT", "body":{"scene":"S3"}} ]}

in the body which translates to “If sensor 2 has created an event with number 16 then activate scene S3. https://developers.meethue.com/develop/hue-api/6-rules-api/

knowhy on 11 May 2020

👍1

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 9 Aug 2020

👎1

Core: Light component always sending the 'on' attribute, making it impossible to use physical switches together with HA.

Most helpful comment

All 47 comments

Related issues