I confirm. With 1.12.2 problems remain the same. Only some messages from Alexa app are different. Now it sees a new Sonoff device that is Matter compatible. I believe that this is due to eWeLink skill installed and active. Any attempt to pair is unsuccessful, as used to be with 1.12.x. Other problem also remain: eWeLink remote control (pilot) function is unstable and randomly renders subdevices unoperational (you need to reboot iHost). The only feature that seems to be better now are scenes.
So far it looks pretty hopeless, but I still have faith in your skills and hope to see a really fixed version of the software soon. After that, I would suggest some kind of tactical break to rethink the overall strategy, as there is evidently a lack of clear vision in your actions.
Hi Faber_GS
Have you had any help or feedback on this particular issue yet?
I want to use my ihost with Google Home.
I thought it would work out of the box but it didn’t. When I realised the amount of work to get +35 (and growing) devices linked through node red i was ready to bin it. Then with 1.12.0 and matter going live i thought my prayers were answered.
Instead everytime my ihost goes through a power cycle all devices are removed/readded in Google Home.
I’m now ready to bin it again as the ihost is unusable like this. I’m better off just using a ZB-Bridge Pro for a fifth of the price and a fraction of the admin and time wasted.
I’ve got plugin sockets and various relays directly connected to the ihost and switches, plugin sockets, relays and usb micros via the sWelink docker addin.
All devices are subject to the same issue.
I really need help before i take a hammer to the ihost and then chuck it in the bin.
I’ve not seen any staff member address this outside of your query.
…also i have door and temp/hum sensors connected via both ihost and eWelink, they are doing the same too…
Sole destroying!
Not yet, they sent me a patch version (1.12.1) to try it out if the issue was resolved but it remained… I sent another set of logs back with the patched version and they said that they are working on it.
Tuya had the same issue for some users with the Zemismart M1 hub, it took them a couple weeks to figure the issue out and release an update, I’m expecting this will be the same case with iHost.
Thank you for replying!
Well at least it sounds like its something they are trying to fix and that it should be fixable. I was concerned it was a fault just a few of us had and it wouldn’t be fixed.
Hi, we publish an beta version v1.12.4. If you had receive any update notes?
Hmm for me it still in 1.12.3, do I need to enable something to receive beta updates? Or just wait a little?
pls message me your deviceid
I’d also like beta updates please.
ID : 1001e7b07c
Done! Shared via PM
get it !
I’ve updated to the latest version 1.12.4 and the issue is fixed 
The devices are persisted after reboot and their name and configuration are not reseted. Great job!
So much joy with Alexa, Google or something else?
Google Home, HomeKit, Home Assistant and SmartThings… Haven’t tried with Alexa though
Can you control devices or is it just the connection done?
Yes, I can control devices normally
With eWeLink CUBE Version 1.12.4, right? Was Google Home the first platform to pair with?
Correct with 1.12.4 and yes… All the platforms that I mentioned before I tested by pairing from scratch. Removing all services listed in the iHost page and reading the QR Code all over again instead of just sharing the access from other platform
Thanks for info.
I understand that you pair iHost with Google Home. No other device is involved. Devices connected to iHost (Zigbee and Wi-Fi) are mapped through the Matter bridge to Google Home platform.
It sounds silly but I want to make things sure.
Thats correct, the only thing that I need to pair in Google Home (besides the Matter Controller) is iHost, the devices connected thru iHost (Zigbee or Wifi) are made available to Google Home via Matter