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
Maybe some capabilities/permissions are missing, but why?
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):
Could this be the case:
The Connection:
- Older versions (1.4.1 - 2.4.3): All have working detection
- Version 2.4.5: Mixed - some sensors work, others don’t
- 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.
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}
But how to get {“contact”:false} as it’s not in the payload…
Found it, I used the wrong one, older, “iHost” instead of “Cube”.
Key Findings:
- 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
- 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
- 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.”
Case closed.
