Can you specify the situation by some pic or video?
With the system log of iHost would be more helpful.
feedback.
219878
The log file cannot be added because it is over 60MB.
send via message
4 posts were split to a new topic: Zigbee Lightbulb issues with eWeLink CUBE 2.3.0
After a power outage. Ihost stopped displaying zigbee maps.
1 Like
A post was split to a new topic: TRVZB Glitches with eWeLink CUBE 2.3.0
After the update, the 3-key switch (_tyzb01_mqel1whf ts0013) stopped working in matter bridge. Re-adding the device to ihost did not fix the problem.
Utterly prepostrous. This is even worse than issues we had with node red and sensors not reporting states properly. Oh, God…
New update has added R5 buttons to Google Home via Matter but with no use or functionality. Please update to remove these or add a function for selective device sync through Matter bridge, similar to the ewelink docker app.
@ward @SuiKa
That’s Google to be blame, it has poor supports for Matter generic switches aka scene buttons; Apple and SmartThings work better with them
Hello iHost Development Team,
First of all, I want to give praise to the development team. I think the iHost system is absolutely fantastic. I’ve had the device running since its release march/2023 and am always excited about new updates. 
The Problem:
After the last update to version 2.3.0, some Zigbee devices no longer work with Alexa with Matter .While they appear in the iHost support list, they cannot be controlled via the Matter protocol with Alexa. Additionally, an extra button has been added to these devices, which doesn’t have any function.
In version 2.2.0, it was still working. I removed the devices and repeated the Matter pairing process entirely, but unfortunately, without success.
Zigbee Devices with erro:
Manufacturer: TZ3000_wfzkj5qh (Avatto)
Model: TS0002
Manufacturer: TZ3000_skoh4qcn
Model: TS0002
Manufacturer: TZ3000_ywubfuvt (Zemismart)
Model: TS0002
I hope this will be corrected in the next update. 
A video guide is coming. thx for the advice
1 Like
Thx for the feedback.
You mentioned that you have removed it - may I ask where did you remove it? Do you mean:
a. removed iHost’s Matter Bridge or the Tuya switch from Alexa or
b. Removed it from iHost and re-paired the switch to iHost via Zigbee.
I understand, Google is at fault. Unfortunately I already have a room with 17 devices in because they can not be hidden.
Is it possible for me to rollback firmware to 2.2.0?
The issue with the R5 and TRVZB not reporting voltage are the first two issues I have come across but I expect there will be more. I’d prefer to rollback and wait for a later update.
Sorry for the inconvenience, but there are no rollback options.
R5 as well as other devices exposed to Matter (not just from us) needs support from Google, And our team is already working on TRVZB issues.
Thank you.
For me, it’s like every other update causes issues. One update will be fine, the next one creates problems, the next one fine, the next one problems.
I thought I’d waited long enough to see all the reported issues on this one before I ran the update.
I guess, at least you guys tend to listen and work with us most of the time. There is no hope of getting any help from Google.
I know that it’s not on your roadmap, but to understand if there is any hope for my R5 issue. Is it possibly possible to add selective device sync with Matter or does the platform/system not allow for that ever to be implemented?
not just for my R5 problem, as this would be useful for the many devices users want in the background but without front end control/operation of.
Hello,
Version B. I tried the following:
- deleted the switches mentioned in iHost and Alexa and then re-integrated them. Without success
- Reset the switches mentioned and then re-integrate them. Without success.
- Matter in the iHost and all devices in the Alexa app deleted and then re-paired everything. Without success
These are Zigbee light switches with and without a socket. These function normally in the iHost and are displayed in the Matter connection at iHost and in the Alexa app. However, the control via the Alexa app/manually or by voice no longer works. As I said, the whole thing still worked perfectly with version 2.2.0.
Since these are only a few devices, as an emergency solution I generated virtual switches using a red node, which can then be controlled via the iHost/Matter via voice control in the Alexa app.
What I also noticed now is that the entire energy history (Energy Overview) of all Zigbee sockets was deleted after the update to 2.3.0 and is no longer displayed.
Manufacturer: eWeLink
Model: CK-BL702-SWP-01(7020).
Many thx for the detailed info. Please send feedback in your iHost with log attached. If the log is too large, you can use google drive or Dropbox and DM the link.
We will look into this ASAP.
1 Like