Add 929003808901_02

[EinRainerZufall]

Device information

Add Signify Hue GU10 White and Color 400lm. These are the 4 GU10 spotlights that came with my Centris. Unfortunately, I don't know if they're just rebranded GU10s. That's probably why they end in _02 through _05. And on the lamp itself, it says: 9290026665

Home Assistant Device information

929003808901_02
von Signify Netherlands B.V.
Verbunden über Home Assistant Connect ZBT-1
Firmware: 0x01002702
Zigbee: 00:17:88:01:0E:E3:3E:68

Checklist

• I have created a single PR per device. When you have multiple submissions please create separate PR's.
• For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
• For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

[github-actions]

Thank you for submitting light measurements!
Here are some visualizations for the CSV files.

[EinRainerZufall]

@bramstroker and theoretically, shouldn't my latest PR have automatically detected my spots? Or does that take some time?

[bramstroker]

Did you notice the existing centris profiles in the library?

You are controlling the whole centris fixture as one, right? Or can you control the 4 spots and downlight separately as 5 entities in HA?

@bramstroker and theoretically, shouldn't my latest PR have automatically detected my spots? Or does that take some time?

Do you have the link to the PR? Still not detected?

[EinRainerZufall]

No, I haven't seen the Centris profile. And I can control all 5 lights, the 4 GU10 spotlights and the large one in the middle, individually. In Home Assistant, these are 5 entities. However, I integrated my lights directly via Zigbee and not through the Hue Bridge.

@bramstroker and theoretically, shouldn't my latest PR have automatically detected my spots? Or does that take >some time?

Do you have the link to the PR? Still not detected?

And that issue has been resolved; it just took a little while for them to be recognized.

[bramstroker]

We already have this GU10 spot in the library:
https://library.powercalc.nl/profiles/signify/LCG006

It also includes 929003666501 as an alias, which should correspond to your model.

That said, I do have some doubts about the correctness. The measured max power for the LCG006 is 4.91 W, while your bulb is rated at 4.2 W (also indicated on the lamp itself). That’s a fairly significant difference.

It might be better to first review the existing Signify GU10 profiles in the library to see if there’s already a closer match (around ~4.2 W max):
https://library.powercalc.nl/?manufacturer=Signify (filter/search for GU10)

I highly doubt we need to introduce a completely new profile here. A more likely approach would be to add the _02 → _05 variants as aliases to an existing profile that better matches the specs.

Also, your measurements don’t look entirely consistent. That could be related to the dummy load used. You mention using an “E27 25 W light bulb”, can you clarify if that’s:

• an incandescent bulb (which is correct), or
• an LED bulb (which is not suitable as a dummy load)?

Only incandescent bulbs should be used as a dummy load to get reliable measurements.

[EinRainerZufall]

All the Hue GU10 bulbs listed in the library have a wattage higher than the 4.2W of the one I have. However, I found Argenta in the library, and that lamp also only has GU10 spots, which match mine quite well. We could add aliases 929003808901_02 through _05 and possibly change the name to make it clearer that the lamp also uses GU10 spots.

And yes, I use an incandescent bulb, but I've noticed that when it's on for a long time, its power consumption becomes a bit inconsistent. I still need to figure out why that is.

[bramstroker]

Nice find.
Yes the GU10 spot would be similar.
As both the Argenta and Centris are from 2024, and highly likely to be using the exact same color spot.
You can go forward and add the aliases to https://library.powercalc.nl/profiles/signify/929003808201.

I prefer to do that and maintain one profile for the same spot. The existing profile also seem to be a bit more consistent.

We might also rename the profile to:
Hue white and color GU10 4.2W 400lm as it will also be clear it's a profile for a separate GU10 spot which is used in multiple fixtures.

[EinRainerZufall]

Should I also change the author information?

[bramstroker]

Please leave the author information as it is. We only update the author when a profile is remeasured and officially adopted. When adding new aliases, the original author should remain unchanged.

Also, you modified library.json, which is why you're seeing conflicts. You can resolve this by selecting “resolve conflicts” and choosing the upstream version. That should fix the issue. There’s no need to update library.json manually, as it is auto-generated by a GitHub Action.

[EinRainerZufall]

I have to say that I didn't modify library.json. I made the changes in GitHub's online editor; I have no idea if any scripts run automatically there.

Do I have to click on “accept current change” for all 300 of them?

[bramstroker]

I have to say that I didn't modify library.json. I made the changes in GitHub's online editor; I have no idea if any scripts run automatically there.

Ah, good to know. WIll have a look what causes this and how to prevent it for PR's.
I have resolved the conflicts.