Ikea tradfri discovery throws exception about zigpy HOT 12 CLOSED

If I manually update device db:
update endpoints set profile_id = 0x0104, device_type = 0x0102;

I can control the bulb from hass, including brightness and color temperature.
bellows report the device as dimmable though.

Device:
  NWK: 0xcddb
  IEEE: 00:0b:57:ff:fe:30:61:cb
  Endpoints:
    1: profile=0x104, device_type=DeviceType.COLOR_DIMMABLE_LIGHT
      Input Clusters:
        Basic (0)
        Identify (3)
        Groups (4)
        Scenes (5)
        On/Off (6)
        Level control (8)
        Color Control (768)
        Diagnostic (2821)
        LightLink (4096)
      Output Clusters:
        Scenes (5)
        Ota (25)
        Poll Control (32)
        LightLink (4096)

db data prior to update (different device from the above hence the different ieee):
00:0b:57:ff:fe:24:4f:09|1|49246|544|1
after
00:0b:57:ff:fe:24:4f:09|1|260|258|1 (decimal values for above hex)

from zigpy.

I cannot confirm it, I use a tradfri base now instead of ZHA. If you guys think it's fixed, feel free to close it.

from zigpy.

The device joins twice (some devices seem to do that ...). The exception is for the first join, but the initialization succeeds for the device with its second NWK.

Failed ZDO request during device initialization: ('Endpoint request failed: %s', [129, 35764, []])

35764 = 0x8bb4.

Can you provide hass debug logs? Also, since it's in the database (otherwise it wouldn't show in bellows devices, hass should try to set it up on start. What's not working?

from zigpy.

On hass UI, nothing happens
Log during join (I think I've reset the bulb)
join.log
And from that point, each time hass boots:
restart.log

from zigpy.

OK -- I think this is because Tradfri devices need messages sent to them with profile ID 0x0104 (ZHA), and not the profile ID they report (0xc05e, ZLL).

from zigpy.

Is this the same issue as my submission #12213 in the main home-assistant repo?

Sounds similar, but my bulb doesn't report DeviceType.COLOR_TEMPERATURE_LIGHT, only the hex number assigned to that. And then it acts as a switch, not a dimmable/color temperature bulb.

I'm on 0.63.3 now, so maybe i'll try rerunning bellows to see if I get a different output.

from zigpy.

It’s related, but different.... and probably different firmware versions on the bulbs.

@andrasbiro’s bulb reports the ZLL profile ID, but expects messages to be sent to it with the ZHA profile ID.

Your bulb reports the ZHA profile ID, but a device type that is valid for ZLL and not ZHA. On your bulb, hass makes a guess about the device based on what clusters are there, since it doesn’t match a known (profile, device type), but it only knows how to look for individual clusters.

from zigpy.

See also my logs in zigpy/bellows#107

from zigpy.

@perosb's workaround worked for me as well. Thanks!

from zigpy.

@perosb wondering if it is possible to do the device db update with hassio? Currently have a few ikea GU10s that I am having trouble pairing with the same issue...

from zigpy.

I believe this is resolved, I didn't have an issue during my last pairing.

from zigpy.

As a side note, I do see Ikea bulbs showing twice in the pair screen and, very seldom, an exception. But anyway pairing finishes and I can control the bulb.

hass-core 0.105
Ikea GU10 bulbs (10 color temp model and 3 only brightness model)
Ikea controls E1743 and E1810

from zigpy.