Correctly calculating power when bulb is off?

[jblsd]

I have many Philips Hue bulbs that are also connected to physical switches. When the physical switch is off, the bulb is powered off but the state is stale. Is there a way with powercalc to find these situations and to ignore these states?

[bramstroker]

Could you post the exact attributes (using Developer tools) when the physical switch is off? Your use case is pretty common, so maybe I can introduce some configuration option to facilitate this.

[jblsd]

Unfortunately, the state remains "on" after power is removed from the bulb and the attributes don't change either. I'm using the normal Philips Hue integration.

There must be a way to force that status to be refreshed somehow... Maybe there is an alternate integration that can provide this update.

[bramstroker]

hmm as nothing changes for the entity in Home Assistant here is no logic I can apply in the component. I will do some testing myself by removing power from a bulb and see if I can figure out anything.

[bramstroker]

Just switched the power off on one of my Hue lights, and the light becomes quickly unavailable in Home Assistant. Took like 1 minute to get from on to unavailable.
Using the Hue bridge V2 and default Hue integration.
You are sure your light does stay on on and does not go to unavailable state?

[jblsd]

I am also using bridge v2 and the default Philips Hue integration and I am not seeing the change. I do have the “Allow unreachable bulbs to report their state correctly” option set. Are you using this setting? This may be why I’m not seeing “unreachable”.

…

On Sep 8, 2021 at 12:48:48 PM, Bram Gerritsen ***@***.***> wrote: Just switched the power off on one of my Hue lights, and the light becomes quickly unavailable in Home Assistant. Took like 1 minute to get from on to unavailable. Using the Hue bridge V2 and default Hue integration. You are sure your light does stay on on and does not go to unavailable state? [image: Screenshot 2021-09-08 at 21 44 52] <https://user-images.githubusercontent.com/2345875/132575300-c5917d70-95b9-4896-b243-f124a33b7e0b.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#183 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALS3EW3RWH6ALRXDWM53AHLUA642BANCNFSM5DRD37FQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jblsd]

Just unchecked that option and tested it and now I see "unavailable" as the state.

[jblsd]

With the change to disabling "Allow unreachable bulbs...", individual bulbs seem to (mostly) have their status right. However, I was trying to run powercalc on a light GROUP which doesn't seem to reflect the status of the individual bulbs correctly. It may be that some bulbs in the group have their status stuck at 'on' and, therefore, the group remains on. Probably wasn't the best plan of mine to tie this to a light group.

[bramstroker]

Yes I also have "Allow unreachable bulbs" switched off.
In home assistant a light groups is considered "on" when any of the bulbs is "on" as far as I know. So when you not always switch your group as a whole than you could better add a power sensor for each individual light.
When you want to know the the total power of several lights you can later group these with a template sensor. See #58 (comment) for examples