I've just received an IKEA notification implying that inspelning outlets will be back in store (Warrington) within a week. Fingers crossed for this.
Ironically the folks who will buy them will be using the Dirigera hub and won't have any inkling of the true power of home automation vie HE.
I have several (10) IKEA bulbs that is working perfectly, however one of them keeps generating error messages like:
Text version: Sent unexpected Zigbee message: description=read attr - raw: 10240103000A0700217201, dni: 1024, endpoint: 01, cluster: 0300, size: 0A, attrId: 0007, encoding: 21, command: 0A, value: 7201, msg=[raw:10240103000A0700217201, dni:1024, endpoint:01, cluster:0300, size:0A, attrId:0007, encoding:21, command:0A, value:0172, clusterInt:768, attrInt:7, endpointInt:1, commandInt:10]
I tried to run the configure (can also be seen in log entries), and I have veried that it is configured like the other once.
Bulp generating error setup:
Over bulp that is not generating error:
Only difference I see is the Home kit settings, but can that be the cause?
It is working perfectly, but why is it generating error messages? And only that one?
What am I missing?
It looks like that the throwing of exceptions happens reguarly:
Text versions:
Sent unexpected Zigbee message: description=read attr - raw: 10240103000A0700217201, dni: 1024, endpoint: 01, cluster: 0300, size: 0A, attrId: 0007, encoding: 21, command: 0A, value: 7201, msg=[raw:10240103000A0700217201, dni:1024, endpoint:01, cluster:0300, size:0A, attrId:0007, encoding:21, command:0A, value:0172, clusterInt:768, attrInt:7, endpointInt:1, commandInt:10]
Sent unexpected Zigbee message: description=catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 8000000000, msg=[raw:catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 8000000000, profileId:0000, clusterId:0001, clusterInt:1, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E07D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[80, 00, 00, 00, 00], endpointInt:0, commandInt:0]
Sent unexpected Zigbee message: description=read attr - raw: 1024010300140300216B610400217D60, dni: 1024, endpoint: 01, cluster: 0300, size: 14, attrId: 0003, encoding: 21, command: 0A, value: 6B610400217D60, msg=[raw:1024010300140300216B610400217D60, dni:1024, endpoint:01, cluster:0300, size:14, attrId:0003, encoding:21, command:0A, value:616B, clusterInt:768, attrInt:3, additionalAttrs:[[value:607D, encoding:21, attrId:0004, consumedBytes:5, attrInt:4]], endpointInt:1, commandInt:10]
Stue sofa 
Sent unexpected Zigbee message: description=read attr - raw: 10240103000808003002, dni: 1024, endpoint: 01, cluster: 0300, size: 08, attrId: 0008, encoding: 30, command: 0A, value: 02, msg=[raw:10240103000808003002, dni:1024, endpoint:01, cluster:0300, size:08, attrId:0008, encoding:30, command:0A, value:02, clusterInt:768, attrInt:8, endpointInt:1, commandInt:10]
Have og skur lyskæde Sent unexpected Zigbee message: description=catchall: 0104 E001 01 01 0040 00 6AEE 01 00 0000 E1 01 0AFCC3CC3077020000730200006E0200006902000061020000580200004E020000470200003F0200003602000001, msg=[raw:catchall: 0104 E001 01 01 0040 00 6AEE 01 00 0000 E1 01 0AFCC3CC3077020000730200006E0200006902000061020000580200004E020000470200003F0200003602000001, profileId:0104, clusterId:E001, clusterInt:57345, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:6AEE, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:E1, direction:01, data:[0A, FC, C3, CC, 30, 77, 02, 00, 00, 73, 02, 00, 00, 6E, 02, 00, 00, 69, 02, 00, 00, 61, 02, 00, 00, 58, 02, 00, 00, 4E, 02, 00, 00, 47, 02, 00, 00, 3F, 02, 00, 00, 36, 02, 00, 00, 01], endpointInt:1, commandInt:225]
dev:232025-12-11 01:51:24.533
error
Indkørsel lyskæde Sent unexpected Zigbee message: description=catchall: 0104 E001 01 01 0040 00 ABA4 01 00 0000 E1 01 09EEC3CC30E9010000E3010000E3010000E1010000E1010000E1010000E1010000DF010000DC01000000, msg=[raw:catchall: 0104 E001 01 01 0040 00 ABA4 01 00 0000 E1 01 09EEC3CC30E9010000E3010000E3010000E1010000E1010000E1010000E1010000DF010000DC01000000, profileId:0104, clusterId:E001, clusterInt:57345, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:ABA4, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:E1, direction:01, data:[09, EE, C3, CC, 30, E9, 01, 00, 00, E3, 01, 00, 00, E3, 01, 00, 00, E1, 01, 00, 00, E1, 01, 00, 00, E1, 01, 00, 00, E1, 01, 00, 00, DF, 01, 00, 00, DC, 01, 00, 00, 00], endpointInt:1, commandInt:225]
dev:242025-12-11 01:51:18.054
error
Fransk hjørne lyskæde Sent unexpected Zigbee message: description=catchall: 0104 E001 01 01 0040 00 F510 01 00 0000 E1 01 0AE8C3CC30E1020000DC020000D8020000D3020000CF020000CA020000C5020000C1020000BD020000B902000001, msg=[raw:catchall: 0104 E001 01 01 0040 00 F510 01 00 0000 E1 01 0AE8C3CC30E1020000DC020000D8020000D3020000CF020000CA020000C5020000C1020000BD020000B902000001, profileId:0104, clusterId:E001, clusterInt:57345, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F510, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:E1, direction:01, data:[0A, E8, C3, CC, 30, E1, 02, 00, 00, DC, 02, 00, 00, D8, 02, 00, 00, D3, 02, 00, 00, CF, 02, 00, 00, CA, 02, 00, 00, C5, 02, 00, 00, C1, 02, 00, 00, BD, 02, 00, 00, B9, 02, 00, 00, 01], endpointInt:1, commandInt:225]
Could this have anything to do with activation of Hubitat retry functionality?
Change the driver to ''IKEA White Spectrum Light''.
Thanks. Nicely spotted 
I was certain that I had configured them all according to the list (Error 500 -- probably because our servers are overloaded right now.</h3> <p>Please retry either.), but apparently not 
After reviewing and adjusting all my IKEA devices there a few left, that still generates error entries. All three are 30 W LED drivers like this (Type =
ICPSHC2430EUIL2):
According to this page (Error 500 -- probably because our servers are overloaded right now.</h3> <p>Please retry either.), I should use the driver 'Dimmable Light' (as I allready do)
These are some of the entries being logged as error:
dev:1302025-12-16 08:20:21.229
error
Skur strip Sent unexpected Zigbee message: description=catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A900000000, msg=[raw:catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A900000000, profileId:0000, clusterId:0001, clusterInt:1, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E07D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A9, 00, 00, 00, 00], endpointInt:0, commandInt:0]
dev:1302025-12-16 07:40:32.690
error
Skur strip Sent unexpected Zigbee message: description=catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A700000000, msg=[raw:catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A700000000, profileId:0000, clusterId:0001, clusterInt:1, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E07D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A7, 00, 00, 00, 00], endpointInt:0, commandInt:0]
dev:1302025-12-16 07:10:38.890
error
Skur strip Sent unexpected Zigbee message: description=catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A500000000, msg=[raw:catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A500000000, profileId:0000, clusterId:0001, clusterInt:1, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E07D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A5, 00, 00, 00, 00], endpointInt:0, commandInt:0]
dev:1302025-12-15 09:24:16.947
error
Skur strip Sent unexpected Zigbee message: description=catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A300000000, msg=[raw:catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A300000000, profileId:0000, clusterId:0001, clusterInt:1, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E07D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A3, 00, 00, 00, 00], endpointInt:0, commandInt:0]
dev:1302025-12-14 21:07:37.927
error
Skur strip Sent unexpected Zigbee message: description=catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A100000000, msg=[raw:catchall: 0000 0001 00 00 0040 00 E07D 00 00 0000 00 00 A100000000, profileId:0000, clusterId:0001, clusterInt:1, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E07D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A1, 00, 00, 00, 00], endpointInt:0, commandInt:0]
What am I missing this time?
Assuming these LED drivers are working correctly, there is nothing to worry about — these messages can safely be ignored for now.
@dandanache may choose, in a future driver update, to downgrade the logging severity of these unknown ZDO messages to Debug level. They are (should be) handled at the Hubitat platform system level rather than being treated as driver-level errors.
I understood that the new Thread/Matter devices can also do Zigbee, there are already Z2M converters for the Bilresa remote and the Kajplatz bulbs. Anyone tried to pair them directly to Hubitat using Zigbee?
Tomorrow I'll go try to fetch some stuff directly from the stores; I don't have any TBR and don't plan to use Thread anytime soon, so hopefully the rumors are true or I'll get myself some nice paperweights
Yep, I came to the same reddit post this morning, and of course - the first thing was to try pairing the BILRESA double button to HE... It paired to my C-8 Pro, but that's all - the device doesn't like something and leaves the HE Zigbee network immediately ..
Manufacturer: IKEA of Sweden
Endpoint 01 application: 01
Endpoint 01 endpointId: 01
Endpoint 01 idAsInt: 1
Endpoint 01 inClusters: 0000,0001,0003,0020
Endpoint 01 initialized: true
Endpoint 01 manufacturer: IKEA of Sweden
Endpoint 01 model: 09B9
Endpoint 01 outClusters: 0003,0004,0005,0006,0008,1000
Endpoint 01 profileId: 0104
Endpoint 01 stage: 4
fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020", outClusters:"0003,0004,0005,0006,0008,1000", model:"09B9", manufacturer:"IKEA of Sweden", controllerType: "ZGB"
I also tested pairing it to my SmartThings hub, it pairs successfully, but lacks a driver at the moment. I am not sure whether it stays connected to ST or not.
The device leaves the HE C-8 network with a ZDO 0x013 message. I haven't used a sniffer or investigated further.
This dual support is kind of fascinating.
Do you have a C7 hanging around you can test the Zigbee connection on? For me, C7 has always been better w/Zigbee than C8/C8-Pro.
I don't have any of these yet, just haven't had any reason to be near the local IKEA and not worth driving down to it just to pick up a few of these devices...
I tried on my C-7 also, without success - the BILRESA was not even found.
My next tests will be to use the button and a KAJPLATS color bulb paired to ST hub (Matter over Thread). I haven't made any automations in ST for ages ,,, If controlling the bulb works reliably there for several days, we will know better where the problem(s) could be.
The good: I paired the 2-buttons BILRESA to my C-7, it stays connected and even reports battery percentage attribute on it's own. It even accepts bind requests and keeps a binding table:
================================================================================================
Node Descriptor
------------------------------------------------------------------------------------------------
▸ Logical Type = Zigbee End Device (ZED)
▸ Complex Descriptor Available = No
▸ User Descriptor Available = No
▸ Fragmentation Supported (R23) = No
▸ Frequency Band = Reserved
▸ Alternate PAN Coordinator = No
▸ Device Type = Reduced Function Device (RFD)
▸ Mains Power Source = No
▸ Receiver On When Idle = No (conserve power during idle periods)
▸ Security Capability = No
▸ Allocate Address = Yes
▸ Manufacturer Code = 0x117C = IKEA
▸ Maximum Buffer Size = 127 bytes
▸ Maximum Incoming Transfer Size = 242 bytes
▸ Primary Trust Center = No
▸ Backup Trust Center = No
▸ Primary Binding Table Cache = Yes
▸ Backup Binding Table Cache = No
▸ Primary Discovery Cache = Yes
▸ Backup Discovery Cache = Yes
▸ Network Manager = Yes
▸ Maximum Outgoing Transfer Size = 242 bytes
▸ Extended Active Endpoint List Available = No
▸ Extended Simple Descriptor List Available = No
================================================================================================
Power Descriptor
------------------------------------------------------------------------------------------------
▸ Current Power Mode = Same as "Receiver On When Idle" from "Node Descriptor" section above
▸ Available Power Sources = [Constant (mains) power]
▸ Current Power Sources = [Constant (mains) power]
▸ Current Power Source Level = 100%
================================================================================================
Endpoint 0x01
================================================================================================
Out Cluster: 0x0003 (Identify Cluster)
------------------------------------------------------------------------------------------------
▸ No generated commands
================================================================================================
Out Cluster: 0x0004 (Groups Cluster)
------------------------------------------------------------------------------------------------
▸ No generated commands
================================================================================================
Out Cluster: 0x0005 (Scenes Cluster)
------------------------------------------------------------------------------------------------
▸ No generated commands
================================================================================================
Out Cluster: 0x0006 (On/Off Cluster)
------------------------------------------------------------------------------------------------
▸ No generated commands
================================================================================================
Out Cluster: 0x0008 (Level Control Cluster)
------------------------------------------------------------------------------------------------
▸ No generated commands
================================================================================================
Out Cluster: 0x1000 (ZLL/Touchlink Commissioning Cluster)
------------------------------------------------------------------------------------------------
▸ No generated commands
================================================================================================
In Cluster: 0x0000 (Basic Cluster)
------------------------------------------------------------------------------------------------
▸ No attributes
------------------------------------------------------------------------------------------------
▸ No received commands
================================================================================================
In Cluster: 0x0001 (Power Configuration Cluster)
------------------------------------------------------------------------------------------------
▸ No attributes
------------------------------------------------------------------------------------------------
▸ No received commands
================================================================================================
In Cluster: 0x0003 (Identify Cluster)
------------------------------------------------------------------------------------------------
▸ No attributes
------------------------------------------------------------------------------------------------
▸ No received commands
================================================================================================
In Cluster: 0x0020 (Poll Cluster)
------------------------------------------------------------------------------------------------
▸ No attributes
------------------------------------------------------------------------------------------------
▸ No received commands
================================================================================================
Bindings Table
------------------------------------------------------------------------------------------------
▸ Src:10359700001A440E | Endpoint:0x01 | Cluster:0x0006 | Dest:000D6F0017C9A6E9 | Endpoint:0x01
▸ Src:10359700001A440E | Endpoint:0x01 | Cluster:0x0008 | Dest:000D6F0017C9A6E9 | Endpoint:0x01
▸ Src:10359700001A440E | Endpoint:0x01 | Cluster:0x0001 | Dest:000D6F0017C9A6E9 | Endpoint:0x01
================================================================================================
Neighbors Table
------------------------------------------------------------------------------------------------
▸ Addr:0000 | Type:Zigbee Coordinator | RxOnWhenIdle:Yes | Rel:Parent | Permit Joining:Unknown | Depth:255
================================================================================================
Routing Table
------------------------------------------------------------------------------------------------
▸ Could not retrieve data
The bad: Looks like, although it binds to the coordinator, it broadcasts the button commands, and HE filters these broadcast messages. See Wireshark capture:
The message broadcast does not make any sense since these remotes should bind to individual old Tradfri Zigbee lights.
Yep, it is the same issue with using the Tuya buttons/dimmers in HE ... : (
I'm using your driver for Aqara Dual Relay Module T2 (DCM-K01). Works great, thank you! For my purposes, I don't need any reports of power, energy, or temperature - and in fact it is hogging a lot of zigbee messaging bandwidth. Would it be possible for you to make the power, energy, and temperator individually configurable in terms of whether and/or how often reports are sent?
Here is a post of pure success: Your IKEA Drivers package did all of the following:
A great big thank you!
Hi, I'm new to Hubitat, moving from ST. I found this great thread, installed drivers for Ikea E14 bulbs which work perfectly, also installed drivers for the Tradfri remote E1810 and Tradfri on/off switch E1743, also updated the firmware on the E1810.
Problem, I can't get the remote or on/off switch to work.
All of the devices seem to be paired and there are events from them in the logs, but when I create a Basic Rule e.g. when button 1 pressed, turn on bulb 1, pressing the button does nothing.
Please tell me I'm missing something basic?
Thanks in advance!
Welcome to the community!
Please join the owners group.
Then go to your devices:
And post screenshots of your devices:
And post a screenshot of what your devices events look like.
Edit: It sometimes helps to re-pair more than once. 
And sometimes Step 9 gets overlooked.
I think you need to update the firmware to the latest version (24.4.6). Old version is still using inbound group messages.
