[BUG] THR316D mapping issue in native integration (CUBE 2.12.0) - Regression from Docker Add-on!

eWeLink CUBE
,
1

Hi eWeLink Team,

I am reporting a critical bug in the scene engine logic (CUBE OS) regarding the THR316D (Firmware 1.3.0) on the iHost (CUBE Version 2.12.0).

The issue appears after migrating from the deprecated “eWeLink Smart Home” Docker add-on to the new native device synchronization method (“Add eWeLink-linked Devices”). The new native method completely breaks the logic for TH devices by introducing incorrect capability mapping.

Here are the two critical bugs we are currently facing:

BUG 1: “OFF” state blocks temperature reading in conditions (UI Bug)
In the native scene creator, when trying to set up a complex condition (IF) for the THR316D:

  • If I set the relay state to ON, the system allows me to add a second condition from the same device (e.g., Temperature < 20°C).
  • If I set the relay state to OFF, the iHost UI incorrectly assumes the entire device is inactive/powered down and blocks/hides the ability to add a temperature condition.
    This is an absurd UI logic flaw. The most basic heating automation is: “IF the heater is OFF AND the temperature drops below X → TURN ON”. Currently, this is impossible to set up natively. In the old Docker add-on, this worked flawlessly.

BUG 2: Missing promised exception for TH devices (IF / THEN block)
It has been stated multiple times on this forum (e.g., by admin songal) that TH (Temperature & Humidity) devices would be an exception to the rule and could be used simultaneously as a trigger (IF) and an action (THEN) in the same scene.
Unfortunately, in the new native integration, this exception does not work. If I use the THR316D in the IF section (e.g., temperature drop), the device completely disappears from the list of available devices in the THEN section. Again – there was no such issue in the old Docker add-on because the relay and the sensor were treated independently.

Summary:
This is not a “Feature Request”. It is a clear regression and a bug in the CUBE OS code, which misinterprets multi-capability devices added via the new method. Users are being forced to abandon a perfectly working Docker add-on in favor of a native system that makes it impossible to build a basic thermostat.

Please forward this directly to the development team to fix the TH device mapping and UI logic in CUBE OS.

4

Hello @JMZ,

Thank you for your feedback. We sincerely apologize for any inconvenience this may have caused.
We have urgently identified the root cause of this issue and completed verification of the fix. This fix will be officially included in the upcoming 2.13.0 release in August.
To help resolve your current problem sooner, we are offering an early firmware version 2.12.1 with the fix already applied. Could you please provide the device ID of your iHost so that we can push this version to your device? Once the push is completed, we will update you in this thread and provide instructions on how to install the firmware package.
After the official 2.13.0 release, you will still be able to obtain the formal version through the regular update feature.
We appreciate your cooperation.

5

I sent DM with IDs