Thank you for the info, as indicated I’m referring to this guy:
You can think it is why that some devices like IKEA TRADFRI series as you posted it’s not reported follows the standard Zigby protocol, so the zigbee2cube feature is a work around that ensure those can communicate with the iHost.
There should be a prompt when you fail to pair, which lead you to enable the zigbee2cube feature.
@songal would you please post the results of our verification about IKEA products? thank you in advance.
The following are verified devices:
Supported list:
Brand/Vendor: IKEA
Model: LED2005R5
Description: TRADFRI LED bulb GU10 345 lumen, dimmable, white spectrum
iHostType: light
iHostCapability: power+brightness+color_temperature+startup
Brand/Vendor: IKEA
Model: LED2104R3
Description: TRADFRI LED bulb GU10 345 lumen, wireless dimmable white spectrum/chandelier opal white
iHostType: light
iHostCapability: power+brightness+startup
Brand/Vendor: IKEA
Model: E2102
Description: PRAKTLYSING cellular blind
iHostType: curtain
iHostCapability: motor-control+percentage+motor-reverse
Brand/Vendor: IKEA
Model: E1746
Description: TRADFRI Repeater
iHostType: repeater
iHostCapability: rssi
Brand/Vendor: IKEA
Model: ICPSHC24-10EU-IL-2
Description: TRADFRI LED POWER SUPPLY with wireless receiver
iHostType: light
iHostCapability: power+brightness
Brand/Vendor: IKEA
Model: LED1924G9
Description: TRADFRI bulb E27 CWS 806 lumen, dimmable, color, opal white
iHostType: light
iHostCapability: power+brightness+color_temperature+color-rgb+startup
Not supported yet:
Brand/Vendor: IKEA
Model: E1766
Description: TRADFRI Remote,Open/Close remote
iHostType: remote
iHostCapability: detect
Brand/Vendor: IKEA
Model: E2002
Description: STYRBAR Remote control,On/Off/Brightness adjust
iHostType: remote
iHostCapability: detect
Brand/Vendor: Philips
Model: 9290035001
Description: Tap dial switch
iHostType: remote
iHostCapability: remote+brightness
Hi Yitie,Tks for the answer.
FYI, ref to :“There should be a prompt when you fail to pair, which lead you to enable the zigbee2cube feature.” - I didn’t get a prompt , but I enabled it looking around - should/can I do more ?:

and these are the screens I got with my iHost:
So time to time it works ,but very slow & eratic, here is a log:

Can I do anything, or consider the “Tradfri Control Outlet” is not compatible & jump to something else - simply advice.
Tks beforehand.
Chris
Just the zigbee2CUBE feature enabled, and upgrade the iHost to the latest firmware.
The ON/OFF control for TRADFRI control outlet E1603 should be supported, if not, please send the logs via feedback channel in the iHost web portal and let me know, i’ll let our dev-team to have a look.
OK tks.
- zigbee2CUBE feature is enabled and iHost is at the latest firmware , the TRADFRI control outlet E1702 (or 1603 difference is hardware type (french vs. others) doesn’t work ON/OFF (FYI - iHost has identified it as a router


Here are the logs
37843da2-b47e-49ea-bb3e-1401c0e97fa3.zip (919 Bytes)
Not good enough let me know.
Chris
Not sure the logs are what you are looking for, pls guide me through so that I can provide what you need & where to put (not clear to me what is : feedback channel in the iHost web portal…) - yes… I’m a new to this environment ![]()
Hello! I’ve notice a couple of issues with zigbee power outlets after updating iHost to the latest versions (1.11 and 1.12). Those devices worked fine before the update with super fast response time.
Those power outlets are Zigbee2CUBE devices and whenever I try to turn them on, I get a “Failed to Control” message:

I’ve checked the logs and this is the error message that the system is reporting:
[2023-12-01T11:11:22.866] [ERROR] default - Publish 'set' 'toggleState' to '0x60a423fffeeb101f' failed: 'Error: Command 0x60a423fffeeb101f/2 genOnOff.on({}, {"sendWhen":"immediate","timeout":3000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error)
at CUBEAdapter.sendZclFrameToEndpointInternal (/root/aibridge-cube/src/zigbee-herdsman/dist/adapter/cube/adapter/cubeAdapter.js:1:13901)
at async Queue.executeNext (/root/aibridge-cube/src/zigbee-herdsman/dist/utils/queue.js:1:1756)'
The devices are both Tuya power outlets with the model _TZ3000_5f43h46b (1 outlet) and _TZ3000_o005nuxx (5 outlets).
Let me know what other info I can share to help with debuging.
I found my way and send the log as requested…
hello,
WSDCGQ11LM seem not to work despite mentioned as supported,
does someone manage to get temperature from those devices ?
Hi, Add Window Mage10B Motorized Tuya Zigbee Curtain Kit not working. İhost shows as a plug but no button. Is it possible to add ?
No worries, i’ll let forward the .zip file to the dev-team and check the feedback channel with the CS colleagues also, let you know if we address something.
Freitas and Sergio in the forum have verified the device is supported.
Did you pair the WSDCGQ11LM after enable the zigbee2CUBE feature, if issue exists, post with screenshots and logs attached would be issue addressing helpful.
The device with model “Mage10B” is not on the supported list, it maybe supported later but we are now focused on those which are on the list, we noted your request and any screenshots and logs attached would be helpful.
I 'll tried before and after enabling zigebee2cube, I’ve tried several time.
I’ve got the same result …
Ticket ID196756 has been opened and logs are attached to this ticked.
Update report: Aqara T1 switch SSM-U01(with neutral) is know functionnal as Pairing, Repeater and Control.
Missed Energy monitoring … Can’t update Google sheet device supported list.
Thx
Hi @yitie
I have added a Heiman siren in the Ihost, but it seems does not supports its functions.
Please let me know if it is something I can do to enable its functions.
Thank you.
GM
I’ve tried to pair another WSDCGQ11LM.
I’m getting the same result ![]()
From the logs, it seems that capabilities are not seens …
[2023-12-10T19:41:32.509] [INFO] default - onmessage <========== zigbee-adapter/node/information/0x00158d0001fa5941 {“type”:“Zigbee-ZED”,“ieeeAddr”:“0x00158d0001fa5941”,“nwkAddr”:49162,“manufId”:4151,“manufName”:“LUMI”,“powerSource”:“Mains (single phase)”,“modelId”:“lumi.weather”,“appVersion”:31,“stackVersion”:2,“dateCode”:“05-12-2020”,“hwVersion”:1,“zclVersion”:3,“softwareBuildID”:“3000-0001”,“endpoints”:{“1”:{“profId”:260,“epId”:1,“devId”:24321,“inClusterList”:[0,3,65535,1026,1027,1029],“outClusterList”:[0,4,65535]}}} 409
[2023-12-10T19:41:32.514] [INFO] default - this.deviceLookup 0x00158d0001fa5941 true
[2023-12-10T19:41:32.517] [INFO] default - publish ==========> zigbee2cube/device/0x00158d0001fa5941/information {“manufacturer”:“LUMI”,“model”:“lumi.weather”,“firmwareVersion”:“1”,“serialNumber”:“0x00158d0001fa5941”,“zhcSupport”:true,“displayCategory”:“temperatureAndHumiditySensor”,“linkLayerType”:“EndDevice”,“capabilities”:[{“capability”:“battery”,“permission”:“read”}]}
[2023-12-10T19:41:35.243] [INFO] default - this.deviceLookup 0x00158d0001fa5941 true
[2023-12-10T19:41:35.243] [INFO] default - Received Zigbee message from ‘undefined’, type ‘attributeReport’, cluster ‘msTemperatureMeasurement’, data ‘{“measuredValue”:2697}’ from endpoint 10
[2023-12-10T19:41:35.243] [INFO] default - this.deviceLookup 0x00158d0001fa5941 true
[2023-12-10T19:41:35.245] [INFO] default - publish ==========> zigbee2cube/device/0x00158d0001fa5941/availability {“online”:true}
[2023-12-10T19:41:35.345] [INFO] default - this.deviceLookup 0x00158d0001fa5941 true
[2023-12-10T19:41:35.345] [INFO] default - Received Zigbee message from ‘undefined’, type ‘attributeReport’, cluster ‘msRelativeHumidity’, data ‘{“measuredValue”:5635}’ from endpoint 10
[2023-12-10T19:41:35.346] [INFO] default - this.deviceLookup 0x00158d0001fa5941 true
I’ve checked in the google spreedsheat and it is reported as non OK for temp & humidity ![]()



