Sure, I just shared via PM. Btw, the testing that I did was not a normal reboot. I tried to simulate a power outage (which happens a lot around here). So the testing was done following the steps below:
I like this, team effort!
Still not working any more, iHost not working any more with Apple Home matter
its says Home Hub Required,
eWeLink CUBE Version 1.13.0
iOS 17.2.1
Do you have a homepod or a appleTV as a home hub - if you want to use the Apple
matter funcion in app home, you need one of these two home hub at home.
Since upgrading to 1.13.0 the Matter behaviour in Alexa has changed for me.
On 1.12.0, at times, all of the Matter devices were re-added to alexa along side the existing ones. So I ended up with multiple devices with the same ID but only the most recently added was âresponsiveâ.
Now, at times, (not just after a reboot), all the Matter devices are removed from Alexa and re-added. This means that everything needs to be renamed again and re added to any rooms or groups, which is a bit tiresome.
As a work around Iâve linked the ihost to the Matter plugin for Home Assistant and Iâm exposing them to Alexa from there. This seems to be stable atm.
I still have the link to Alexa so I can keep an eye on whats happening. Approximately once a day I get >20 messages on the Alexa app saying I have new devices as they are re-added.
It also means any automations set up in Alexa or Google Home will fail.
In late November/early December the team were actively working with forum users to fix it but it seems to have gone quiet for a month now.
I donât think this issue will ever get fixed and its a shame because the ihost is unusable to me in this state.
Hello, weâve been refactoring this part of the code for a while now to solve the problem of initializing the names of synced Matter devices, and weâre still in the testing phase.
There may be some differences between our testing environment and your actual usage scenarios, and weâll be going back to some of the users who are experiencing this issue to test it together, which may take a bit of time, but weâre really working hard to resolve this issue.
So it is being worked on in the background, this is good news. I feared it had been abandoned!!! 
Hello, the issue with device names being initialized has been resolved after a code refactoring of iHostâs Matter bridge feature and has passed preliminary internal testing. However, we still need to recruit some of the users experiencing this issue to confirm with us that it has been completely resolved, so a targeted push of patch version 1.13.1 has been made.
If youâd like to help us out, please visit iHostâs Settings page, wait 5 minutes for a refresh, and youâll be alerted to the push of the patch version, so please upgrade it and help verify that the issue has been resolved.
Thank you in advance for your support and help!
@jam3 @lostathome31 @Damin0u
Version 1.13.1 doesnât show up on my iHost.
Will have a look now⌠thank you @songal
@songal i believe you have got it this time!
Nearly all devices are pulled through to GHA with their correct names, only the temp/hum sensors arenât and these are pulled through as separate devices (which is a good thing). Its doesnât matter if the devices are added to ihost directly or via the eWelink addon.
All devices operate correctly and remain added and keep their assigned rooms after ihost reboot.
Great work devâs, well done!!!
The only erroneous thing is the ihost is pulled through as two devices. Both named smart home hub. One is the ihost and has no actionable function ad expected. The second shows as a light with cool white/warm white temp range. When operated an error message is returned.
This is not an issue for me but thought youd want to know.
Thank you for getting this done, i appreciate the effort you have put it!
Version 1.13.1 doesnât show up on my iHost.
Already pushed to you, Wait 5 minutes after you refresh the settings page
Got it. Thank you.
This isnât a bug, itâs the Matter bridge logo, which allows you to share the Matter bridge to other apps (e.g. Homekit, Alexa) via Fabric from itâs settings page!
Weâve identified the cause of this issue and resolve it for a combined release in the next version, it will not appear again.
Looks good to me, I restarted iHost a bunch of times via the UI and cutting the power and with 1.13.1 it seems that the issue was fixed. 
Hello. I updated Nspanel pro to version (v2.4.0). Using the eWeLink application (v5.3.0) I added the ihost matter bridge to nspanel pro. All devices except sensors have been added. Zigbee devices added to ihost were visible in nspanel pro and could be controlled. I performed a power outage test. After restarting. Ihost bridge and all devices became offline. Has anyone tested this yet.
Can I check if the trial version 1.13.1 can fix this problem?
id: 1001e7b07c
