Why do you need it? I assure you that you wonât find anything extraordinary in the latest version. Itâs a bit better, but overall itâs the same as version 1.12.0. Maybe something really shocking will be released after Christmas?
There is no need to pay, if you have encountered the same issue and submitted feedback, the operations staff will get back to you and consider your device ID to be placed in a whitelist for targeted push testing.
Hello,
I have the ihost updated to the latest version 1.13.0 and the minir4M switches are not detected. The switches are in the eWeLink application.
My minir4m are displayed in ihost. I have versions ihost 1.13.0 and eWeLink Smart Home 2.0.0
Have you updated the ewelink smart home add-on to the latest version?
YES, I have updated both to the latest version. I have 3 minir4m switches and they are not detected; one was detected at the beginning but later went offline.
do you see minir4m in the ewelink application?
You can use the mDNS Discovery LAN scanning tool to check whether MINIR4 can be found on the LAN. If you can find the minir4, try taking control of the minir4 once to see if the device comes back online.
iHost still cannot be paired with Amazon Alexa with 1.13.0. The Matter Sonoff device is visible in the Alexa app, the pairing process starts and after a few minutes the message âSomething went wrongâ is displayed. The only thing that has changed is that iHost does not disable the pairing mode. BTW, this can hardly be called an âoccasional pairing issueâ because the problem is permanent.
TRVZB is indeed supported, but after the update you have to wait several minutes for the synchronisation in add-on to be possible. For some reason, the âOpen Window Detectionâ option is switched to Off even though it was switched to On before synchronisation.
On the same network, during our cross-pairing tests, we found that Alexa was indeed more difficult to pair when compared to Google Home and Apple Home, and Alexa was a difference in the success rate between the Android and iOS versions (the Alexa App for iOS had a higher success rate)
In the unsuccessful add log, we found that Alexa did not initiate an add request to iHos during the pairing process, this indicates that it did not find the iHost Matter bridge within the LAN (but in cross-pairing tests Google Home and Apple Home did it easily! ), and weâre in the process of feeding back with the relevant Amazon Alexa developers to get them to fix it.
I understand. Iâm keeping my fingers crossed and waiting for the results. Letâs hope it works out in the end!
Beyond any doubt, both Echo devices and iHost are on the same network. According to Amazon, both are compatible with Matter over Wi-Fi.
Since the iHost works as a Matter bridge, for what purpose does one actually need any Echo in the role of a hub? In fact, it is illogical. I donât have a Matter device from Google and iHost pairs seamlessly with that platform. If there is an NSPanel Pro on my network, what could be its role as a Matter hub in conjunction with Alexa?
Hi Songal,
I was on 1.12.4. And during the night, Alexa got all Zigbee devices reset again, without any action from my side. (no further FW update nor reboot)
So I checked and found out that there is a new FW release 1.13.0 available (but I did not update it yet)
What I find weird is that all Zigbee names were reset without any action, apart from a new FW being pushed (made available) to my device.
Do you think this will be a recurring behavior⌠? Coz Iâd like to avoid re-entering names (I have +30) every time a new FW is made available to my deviceâŚ
Explain this as best as I can with what I know about third-party Matter Hubs (Apple HomePod, Google Nest, and Amazon Echo). They act as gateways to receive and send down control messages in Matterâs control link (similar to a Zigbee gateway)ă
The iHost Matter bridge is in the Matter control link, and its job is to convert non-Matter protocols from the iHost device into Matter protocols for reporting to the Hub, or to receive Matter protocols from the Hub and convert them into non-Matter protocols for sending down to the iHost device.
Theoretically, a mobile app can also act as a Matter Hub, except that after the app process is terminated, the gateway ceases to exist and control and upload messages are not persisted.
Currently the NSPanel Pro is just a Zigbee gateway, it doesnât support the Matter protocol and canât exist as a Matter Hub (in the future it might be able to)
V1.13.0, after completely fixing the issue of name loss occurring on devices that have been synchronized after an iHost reboot, the next time you upgrade to a higher version, the issue will no longer occur.
And syncing the device name on the iHost to the third-party app when the Matter bridge is first added,that is exactly what weâre going to do after fix the add and reboot issue.
Yes, the feature is still in development and will be able to add Matter devices.
When this feature goes live, it means youâll be able to add other brands of Matter devices to your ihost - and yes, itâs planned, with an update expected in the first half of 2024 as well.
This is quite interesting. See: How to Add and Control Matter Device by NSPanel Pro - SONOFF Official. One may learn this: âIn version 2.0.0, NSPanel Pro has finally introduced Matter Hub capabilities, allowing you to add Matter devices from different brands to the eWeLink APP.â So is this another manifestation of the marketing departmentâs excessive fantasy?
NSPanel Pro can works as Matter hub of eWeLink cloud and eWeLink app, but it can not works as Matter hub of Local eWeLink CUBE (ihost) - the Matter hub of eWeLink CUBE will be the ihost itslef - Itâs different from the eWeLink cloud/app matter fabricator and network.
In our latest update, we have removed the option to bind eWeLink CUBE to eWeLink account, just to avoid confusion between the two things -eWeLink CUBE is a localized system, and currently it has no connection with eWeLink Cloud.