Sure, Nspanel pro (v2.4.0) is supported as a Matter Hub, and the eWeLink App (v5.3.0) is supported to add a Matter bridge. However, the eWeLink App in v5.3.0 only supports switches, plug, and some categories of light devices, and the others are not supported at this time, so you won’t see some of the iHost’s lights and sensors is normal.
As for whether the Matter bridge device on eWeLink App will go offline after iHost reboot, we will pay attention to its test performance in iHost 1.13.1 and later versions.
1 Like
Has anyone encountered such a problem? maybe I’ll try to recreate it.
In the ewelink application, I changed the order of tiles on the nspanel pro screen.
After changing the order of tiles on the screen the name of the TEMPERATURE screen was automatically changed to LIVING ROOM.
Additionally, all Matter devices and devices added via IHOST MATTER BRIDGE HAVE BEEN OFFLINE.
I restarted nspanel pro and ihost but the devices are still offline.
I noticed that if the Ihost matter bridge is offline in the eWeLink application and on the nspanel pro screen. It is in the ihost (matter bridge) menu that pairing with ewelink is removed.
If I re-pair, it displays error 30003.
Re-pairing can only be performed when we remove the inactive matter bridge from the eWeLink application.
Has anyone already tested the connection of MATTER BRIDGE IHOST with the ewelink application and MATTER HUB NSPANEL PRO?
What do you have on mind? For what purpose would this be done?
IHOST devices are displayed using Hub Matter in the eWeLink application and on the NSpanel Pro screen. Doesn’t anyone know about this?
It already works, but there are synchronization errors
I didn’t know. Thanks for pointing it out 
@songal The description from https://ewelink.cc/whats-new-in-ewelink-app-v5-3/ is vague and mentions nothing about iHost via Matter.
Indeed, it does work, but only with LAN devices. Zigbee are not added. It gets confusing though, because if you use the eWeLink Smart Home add-on, the devices are duplicated in the app (looped). Also, they are listed under enigmatic names like ‘Device000095’. In general, this makes no sense! So I stand by my earlier question: For what purpose would this be done?
Zigbee devices are also added, e.g. Zigbee Mini R2.
Only sensors are not supported yet.
And what names does Alexa add?
There are also strange names.
In my opinion, this is a great alternative for people who want to have remote access to devices managed by ihost.
I wasn’t so lucky, because Zigbee devices were not added. I severed the connection and tried again. This time the connection failed despite several attempts. Instead, the NSPanel Pro screen displayed a message that the LAN devices were on the same network.
The implementation of Matter in eWeLink (CUBE) is disappointingly clumsy.
Let’s forget about Alexa. Let’s focus on eWeLink.
To perform re-pairing, you must first remove the matter bridge in the eWeLink application if it is displayed. I also restarted nspanel pro because it was not detected in the network.
I wonder how long it will take for them to get it working properly
@songal
It appears that the problem with the iHost Matter bridge is in the eWeLink cloud. After an overnight pause, re-pairing with NSPanel Pro was successful. As before, only devices connected via the eWeLink Smart Home add-on are visible in the app. No Zigbee devices despite the fact that, according to the summary in iHost, they are supported. Of course, this makes the whole action taken pointless. Makes me wonder if the lack of Zigbee from iHost is influenced by the fact that I added Matter devices to SNPanel Pro and that it was already acting as a Matter hub. Because why in my case are Zigbee devices from iHost not added to the cloud?
@ociepa.ekotox It also makes me wonder if the ability you discovered to add iHost (bridge) to NSPanel Pro (hub) is an intended option or if the eWeLink stuff didn’t anticipate that possibility.
Sure the idea would be “a great alternative for people who want to have remote access to devices managed by iHost”. So far it’s going poorly for the eWeLink guys.
What type of zigbee device do you have? Currently App version 5.3 only supports switch type devices with iHost Matter bridge added.And the first time you add Matter bridge, the device name on iHost is not synchronized to the app.
I have zigbee devices added to ihost. I have ZBMINIR2, BASICZBR3, 3 gang switch without n (moes ZLS3M). All are displayed.
Are the device names in ihost matter bridge supposed to be synchronized in the application?
The problem repeats itself every time
Thanks for the clarification. That explains the lack of light sources. The description of the app’s new possibilities needs to be corrected then, as it reads: “…you can use the Matter bridge as an intermediary to connect Zigbee, Z-Wave, and Bluetooth plugs, or Matter lights to the Matter Network”. Well, you cannot. At least for now.
Since you can add the iHost Matter bridge to the hub in NSPanel Pro and this is the intended capability, it would be sensible to rethink adding LAN devices to avoid looping. There will be users lost in this, surprised by such a occurrence.
The Matter bridge (iHost)/hub (panel) trick would be of no use to me if Paral-sync worked bi-directionally. Apparently this is not to be done, as such a solution will cause confusion and conflicts. In my judgment no more than the one we are exchanging opinions about.
Good question. Given the struggles of pairing the iHost bridge with Alexa or Google Home, the names should be mapped out. After all, among other things, that was the jostling.