# eWeLink CUBE Version 2.5.2 - nodered/node-red - get-devices node, missing detect.detected **URL:** \ **Category:** eWeLink CUBE\ **Created:** [July 20, 2025, 3:58pm UTC](https://forum.ewelink.cc/t/ewelink-cube-version-2-5-2-nodered-node-red-get-devices-node-missing-detect-detected/194378 "2025-07-20T15:58:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![sven.kelemen](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sven.kelemen](https://forum.ewelink.cc/u/sven.kelemen)\ **Post date:** [July 20, 2025, 3:58pm UTC](https://forum.ewelink.cc/t/ewelink-cube-version-2-5-2-nodered-node-red-get-devices-node-missing-detect-detected/194378/1 "2025-07-20T15:58:30Z")
Hi, this was working before, now the situation is that some contactSensors do not return detect.detected which I query by **msg.payload[0]?.state?.detect?.detected;** with “get-devices” node in Node-RED running on the CUBE/iHost or on the local Raspberry Pi, same situation. But those do return e.g. **payload[0].state.battery.updated\_at**, and the rest. ContactStensor state is visible and correct in eWeLink Web. Device versions that doesn’t return state are e.g. version: “2.5.7”, or version: “2.4.3”, while for example, the ones that return it are e.g. version: “1.4.1”, version: “2.4.5”, if that make any difference. ContactSensors are connected over ZBBridge-P to weLink which is connected/synced over eWeLink Smart Home Docker to eWeLink CUBE Version 2.5.2. I would like to fix this on the CUBE, but also, I’m thinking of asking for a developer https Node-RED connection with eWeLink, as it looks more reliable then on the CUBE/iHost which I’m using thinking that internet is the unreliable part in the chain. Thanks for you comments and help. Kind regards, Sven ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/5/5e3f9bd025cb543fb72485fc96f618a2e33be332.png) Maybe some capabilities/permissions are missing, but why? ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/8/8ef2d919c7fb2b0b90765fdf206ab4c0b6e11aa4.png) ---
**Author:** ![sven.kelemen](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sven.kelemen](https://forum.ewelink.cc/u/sven.kelemen)\ **Post date:** [July 22, 2025, 5:00pm UTC](https://forum.ewelink.cc/t/ewelink-cube-version-2-5-2-nodered-node-red-get-devices-node-missing-detect-detected/194378/2 "2025-07-22T17:00:42Z")
Then I connected it directly to iHost/CUBE and message is different, still missing detected with an additional “SSE connection failed” (this I also sometimes got in the first case): ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/7/7ef774689247533a485e25eb5685583c06cccc1a.png) ---
**Author:** ![sven.kelemen](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sven.kelemen](https://forum.ewelink.cc/u/sven.kelemen)\ **Post date:** [July 22, 2025, 5:29pm UTC](https://forum.ewelink.cc/t/ewelink-cube-version-2-5-2-nodered-node-red-get-devices-node-missing-detect-detected/194378/3 "2025-07-22T17:29:24Z")
Could this be the case: ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/7/7207c0893e7e9585d37aff206243bb19f75cb2e9.png) ## **The Connection:** 1. **Older versions (1.4.1 - 2.4.3)**: All have working detection 2. **Version 2.4.5** : Mixed - some sensors work, others don’t 3. **Newer versions (2.5.6+)**: **Complete loss of detection capability** This suggests either: - **Firmware regression** where newer versions have a bug - **Configuration changes** in newer firmware that requires different setup - **Hardware/capability changes** in newer device revisions - **API compatibility issues** between newer firmware and your home automation system The pattern is too consistent to be coincidental - newer firmware versions appear to have introduced problems with the detection functionality. ---
**Author:** ![sven.kelemen](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sven.kelemen](https://forum.ewelink.cc/u/sven.kelemen)\ **Post date:** [July 22, 2025, 5:56pm UTC](https://forum.ewelink.cc/t/ewelink-cube-version-2-5-2-nodered-node-red-get-devices-node-missing-detect-detected/194378/4 "2025-07-22T17:56:55Z")
New findings in the debug log for Manufacturer coolkit, ZIGBEE\_DOOR\_AND\_WINDOW\_SENSOR: Version: “2.4.5”, returns {“detected”:false} Version: “2.5.7”, returns {“contact”:false} ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/c/caf49e2807c3d9121b8d226d99259d73cc81a0cb.png) But how to get {“contact”:false} as it’s not in the payload… ![image](https://europe1.discourse-cdn.com/flex005/uploads/ewelinkforum/original/2X/b/b7720d18ed2d30fdda0352e9edb36f855dbea386.png) ---
**Author:** ![sven.kelemen](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sven.kelemen](https://forum.ewelink.cc/u/sven.kelemen)\ **Post date:** [July 22, 2025, 6:22pm UTC](https://forum.ewelink.cc/t/ewelink-cube-version-2-5-2-nodered-node-red-get-devices-node-missing-detect-detected/194378/5 "2025-07-22T18:22:16Z")
Found it, I used the wrong one, older, “iHost” instead of “Cube”. ## Key Findings: 1. **node-red-contrib-ihost 1.3.0** is a **fork** of **node-red-contrib-ewelink-cube** that was specifically created to address issues with device support on SONOFF iHost 2. From the search results, I found that node-red-contrib-ihost was “forked from node-red-contrib-ewelink-cube. As that one did not support all devices from SONOFF iHost because of the devices missing the tags property” [node-red-contrib-ihost (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-ihost) 3. **The Original Repository** has been archived: The CoolKit-Technologies repository “was archived by the owner on Jan 23, 2024” and points to the new repository at “[GitHub - eWeLinkCUBE/node-red-contrib-ewelink-cube: Node-RED nodes to control eWeLink Cube.](https://github.com/eWeLinkCUBE/node-red-contrib-ewelink-cube)” Case closed.