hi,
Different platforms have inconsistent adaptation to the Matter standard protocol and device compatibility. Other brands have also had the same problem with Alexa. we are working hard to jointly debug with Alexa.
Hi, not sure if this will be changed but for now Matter allows you to add device to different platforms, but only once per platform, meaning you canât add to 2 accounts of 1 platform. maybe you can just use the share feature between 2 accounts.
Hello, can you reply with your iHost device ID? Weâll let the eWeLink team check it out further!
Hello, can you reply with your iHost device ID?
Weâll let the eWeLink team check it out further!
I have no doubt that you are working hard 
The point is that Matter protocol worked well prior to v. 1.12.0. Does this change have anything to do with inconsistent adaptation? Itâs unlikely that the change happened both on Amazon and Google at the same time. Isnât it logical to assume that the bug was introduced to your software?
Hello
Here it is: 1001ec3697
Thx
Got it. 
1 Like
Hi
Ok clear. So that is by Standard right ? No limitation due to the iHost itself ?
Now I understand that with Matter you can (still) pair to different platforms (letâs say I want to pair it with my Wifeâs Alexa and my Own Google Home), that should be doable then right ?
Thing is, if I want to get the pairing code (for my pairing to Google) I need to get into my Wifeâs Alexa App to generate this QR Code from the iHost device that appears in here peripheral list⊠quite strange to proceed like this. I would have preferred to be able to generate this code directly from the iHost itself but it canât (once it is paired with a first platform, cant generate the QR code directly in the Matter tab of the iHost anymore).
Is that also part of the Matter Standard ?
yes iHost has no limitation.
yes you can pair it with Alexa and Google Home, as well as Apple Homekit, Samsung SmartThings.
Only the first addition requires the QR code or manual code on the device (iHost). The next platform can be paired with the temporary code enabled by the first platform app. it is part of the Matter standard.
1 Like
Hi, the eWeLink team has made an urgent fix for the unpairing issue generated by the Matter Bridge of iHost, and patch version 1.12.1 has been targeted and pushed to your device.
If your device could not be paired in version 1.12.0 (or earlier version), please try updating to the 1.12.1 patch version and retry.
We would like to hear from you whether or not we were successful in resolving your issue,thank you for your continued support of eWeLink!
Hi,
I just updated the FW (see screenshot below).
However Iâm not sure which issue it should address ?
- Pairing is only allowed once per platform, so this issue (for me) wont be fixed as this is per standard
- Loosing Zigbee Switches names (or even, not transmitting the names I assigned in iHost) when pairing to Alexa.
For the info, this is what I see on my Matter Tab
The Alexa adaptation doesnât seem to be our iHost problem, weâre still talking to their developers, If there is any progress, we will announce it to you in time!
What you see on your Matter tab is the remainder of the successful pairing when using 1.11.1. If you unpair, you wonât be able to pair again. So donât, if only Alexa doesnât remove previously recognized devices attached to iHost as a Matter Hub. In my case, all those devices became unresponsive.
How come that with 1.11.1 all went as expected? Unannounced changes introduced quietly in Seattle in between?
How about Google? Looks like somewhat similar problem when pairing with Home.
For now, I had to go back to Alexa Skill and pair Zigbee devices with NSPanel Pro to have voice control. Now itâs a bit schizophrenic as several sensors need to be connected to the iHost via Zigbee2CUBE. Fortunately, these are only the sensors needed for locally executed scenes.
I was so happy that via Matter I could bypass the limitations of iHost as a local server. And hereâs the bummer 
ok.
So far I had all Zigbee devices paired on 1.11.0 and since then I did not unpair (in Alexa). So I did not lose any Voice control over them.
But based on your feedback it seems that if I now do UNPAIR from Alexa (in iHost) I wont be able to pair again ??
However in the meantime, I replaced the Echo Pop by an Echo Studio⊠and bang. All the ZigBe devices re-appeared (in the new Echo Studio) using their original iHost name (a long string of characters). So I had to rename again.
- I would have tought that maybe there is a way (in MAtter Bridge FW) to pass on to Alexa the names we have set inside iHost device instead of the long string device ID.
- Since these Zigbee devices hadnât changed, I would have expected that Alexa would have retained (in the cloud) the association of the ZigBee original name strings (unfriendly) with the names I had entered manually in the Alexa App⊠After all, the name change (on Alexa side) is done inside the App, on the Phone⊠So it should not be tied to a hardware device and the replacement of one by another should be transparent for the user in term of ZigBee namingâŠ
Echo Pop does not support Zigbee and Matter. Echo Studio supports both and has in-build home hub. It is impossible to make out from your description how the devices are connected. I paired the iHost with the Alexa platform via the app, and not with a specific Echo client. Two different things.
Echo Pop does not, but Alexa does, no ?
At least it is working in my house 
Sorry I might have not been clear enough. Indeed I paired everything using the Alexa App, none of the hardware I mentioned.
My Initial Setup:
Zigbee Switch â iHost â Matter Bridge â Alexa â Echo Pop used for Voice Commands
This was working just fine, with the 2 above limitations I described in previous messages
My Current Setup:
Zigbee Switch â iHost â Matter Bridge â Alexa â Echo Studio used for Voice Commands.
This is also working just fine, with the 2 above limitations I described in previous messages
Note that for now Iâm not using the integrated ZigBee Hub within the Echo Studio.
Iâd rather keep the iHost as I can get access to the Web Server to manage configurations, whereas in Alexa itâs a bit more cumbersome (I yet have to look into that later as anyhow my Curtain Zigbee controller is recognized by iHost, but NOT bridged to Alexa so I fear Iâll have to pair it with the Studio integrated hub anywayâŠ)
What happened is that to replace my Pop by my Studio, I powered OFF the Echo Pop, then I powered ON the Echo Studio and configured it using Alexa App.
By doing so, I was thinking that the previous Zigbee configuration I had entered manually (the Zigbee re-names) would have been kept (since done in Alexa App (cloud ?)). But this was NOT the case.
As soon as I finished configuring the Echo Studio, the Alexa App popped up again the message saying it had detected 20 SwitchesâŠwith the weird/long string names (ID String)âŠ
So I had to rename those again inside the Alexa AppâŠ
I hope it is clearer with this description
Now, what I do not know is if there is a possibility from the Matter protocol to âforwardâ any names configured manually inside the iHost, to the Alexa using the Matter bridge implemented in the iHost firmware ?
And also, why Alexa (Cloud App) canât keep the association of the Zigbee original names provided by iHost Matter bridge (ID String) vs the manually entered namesâŠ
1 Like
I believe that it came out because of v. 1.12.0 being installed. I came across the same several hours after the update. On the next day all my devices turned out to be unresponsive in Alexa. The new Echo device has triggered a refresh.
Looks like passing customized names might not be possible on Matter platform yet.
Hola, ¿cómo puedo recibir o forzar las versiones fw que liberan de manera manual? Me encuentro en México, tengo mi casa domotizada con Sonoff, tengo problemas con IHOST en sincronizar Wifi, Zigbee y Alexa. Pronto estaré compartiendo mi experiencia y consejos al usar Node Red y como resuelvo la infinidad de problemas de conectividad entre Wifi, Zigbee y Alexa.
Escribo en español por ser mi idioma nativo,
Gracias
Enrique
Hello. whether integration of matter bridge with the ewelink application is planned