NS Panel (non-pro) use iHost temperatures

eWeLink CUBE
1

I was just going to set the temperature display on the NS Panel (non-pro) to a nearby Zigbee T&H sensor but have noticed none of the locally connected sensors are available to it. Presumably it gets that information from the cloud. Is there any way to make a local Zigbee device connected to an iHost available to it?

2

Sorry, but I donā€™t think itā€™s possible at the moment.

Hereā€™s a list that NSpanel supports for external therometer sources:

  • SNZB-02
  • SNZB-02P
  • TH10/TH16
  • THR3
3

If the Zigbee device (eg. SNZB-02) is connected to an iHost does it still work? I have several TH and they are there but are shared with the cloud already.

Maybe an additional Node Red node to connect to the whatever the NS Panel connects to? That way you could maintain the secure connection, check the data was a reasonable number locally and not updated too frequently without making the server freely available. That would be easier than rewriting the NS Panel firmware to allow access to Local devices and the eWeLink App interface to allow selection. The same node could also allow security alarm status and doors etc. to be communicated from the iHost to the cloud without adjusting much code.

4

Sorr for the misundersanding.

They have to be paired with a eWeLink-supported Zigbee bridge like SONOFF ZBBridge-P/U.

The two product lines (cloud/local) can work together but not all features are exposed to each others at the moment.

5

What did you think of the suggestion of just adding an extra node into the EWeLink Cube Palette for Node Red. It already does HTTP in Node Red. You could encrypt traffic using a Pre-Shared Key of your own. You could limit the maximum polling rate to avoid your servers getting hit. Itā€™d be a bit of a bodge for now but itā€™d work.

6

Hey

Like I said above, the two are separated lines. It could be more possible that the app adds support for Matter sensors as external sources.

Please turn one of your ideas that meet the need best into a feature request. We are collecting ideas for eWeLink CUBE.

many thx

7

I donā€™t really understand the Matter map. My interpretation of the plan is that the iHost bridges Zigbee sensors so they appear as matter devices and then a distinct device connected to the cloud acts as a Matter Border Router, presumably would need to be a newer ESP32 containing device so that it can leverage the built in Matter functions, so the eWeLink app can connect to them? Or would the temperature sensor need to be matter over wifi compatible itself?

My suggestions for additional eWelink Cube Node Red Palette development would be:

  1. add generic ā€œconnect to cloudā€ node in the Node Palette: this would allow multiple functions such as
    A) connect to temperature on NS Panel (non-pro).
    B) synchronise security status and alerts.
    C) add manual data to energy dashboard [for example, I have a basic R2 controlling a ~600w panel heater so no need for a POW.
  2. change Device Control Node so it accepts msg.payload as the setting in addition to fixed values set in the Node, eg. true would become ā€˜onā€™ and 50 would become ā€˜50%ā€™ etc.
  3. alter device control node options so iHost control includes turning on pairing, in addition to the security settings etc. Creating an ugly but functional switch in the Node Red Dashboard is easy and would negate the need to be able to pair via the iHost dashboard on a big screen.
  4. alter virtual device create node so that virtual device types includes TRV and capabilities includes target temperature
1 Like
8

Thereā€™s no border router thing for Wi-Fi and Ethernet Matter Bridges; All you need is the iHost (as Matter Bridge) and Matter Hub to work with each other. However, the external sensor binding feature relies on the eWeLink app and it only supports a specific range of thermometers at the moment.

Thx for the other ideas for Node Red