Ikea Tradfri bulbs brightness issue

I successfully added 2 Ikea Tradfri bulbs to hub by 6 times on/off magic… (Without using Ikea hub)

But after adding them to Smartthings, their physical brightness lowers. In the app it is 100% but actually they are not.
They were much brighter when I first turned them on before adding them to hub.

To try, I uninstalled them and turned them on manually - they are bright. Add them to hub, a lot less bright…

Anyone has any idea?

What DTH are you using?

1 Like

Sorry, but what is DTH? :slight_smile:

DTH is the Device Type Handler. When you login to IDE at https://account.smartthings.com/ go to the Devices page, then select one of your Ikea bulbs and see what it says under “Type”.

2 Likes

Type -> ZLL RGB Bulb

Are you saying, if you turn the bulbs physically off at the wall switch and back on, their brightness is different from when you change brightness in the app down and back up to 100%?

Physically switching puts them back to default.

No, if I delete the bulb from smartthings hub and use it like a “not smart bulb”, it is bright.

When I smartize the bulb and add it to the hub, then it is not as bright as before. - Even it seems 100% bright in the app

The public code for that DTH is on github:

Near the bottom, it looks like some code to fiquire out the safe color range. Considering there is some rounding involved it is very possible the bulb is dimmer either by design or maybe a rounding error or firmware bug when attached to Smartthings.

You can try this DTH to see if the bulb performs as expected

This should get you rocking

1 Like

@Emre, does it change color as well? To something more warmer?

Hi @sidjohn1

I’m using the code you posted from Pedro Garcia,
I’ve got an issue whereby I’ve got a scene that turns on and sets the brightness of a Ikea bulb.

The issue is that I think the animation of the brightness (when powering on) is negating the brightness set in the scene.

Setting the brightness manually and/or in (webCoRe) pistons works absolutely fine - it’s only happening when both brightness and ‘on’ are set at the same time.

I guess as a work-around, I could use a piston to set all the bulbs instead of scenes, that way I can simply issue the ‘brightness’ setting only, which will result in the light turning on anyway.
Currently I think what happens is that the ‘scene’ turns the bulb on - which starts an animation over x milliseconds to get the bulb to the brightness it was when switched off. the scene is then sending the ‘go to brightness x%’ whilst that animation is still running, and therefore has no affect.

I’m not sure it’s possible to alter the DH to either:

  • allow the brightness command to interrupt the switch on animation;
  • or the ‘switch on’ operation to wait a split second to see if a brightness command is also sent.
    If either could be added it will fix this.

Also, if ST altered the scenes to only issue the brightness command without also issuing an ‘on’ command that would fix this too, but I don’t expect that will happen.

Anyway, I’m not sure there is a fix here - but in case others have the same issue, I thought it was worth mentioning my work-around.