Is anyone else able to keep the ZBBridge-U online in Google Home via Matter?
Whenever I pair it, the connection is successful, but the bridge and its devices immediately show as “Offline” in the Google Home app. I have other Matter bridges (both certified and uncertified) that work fine, so it doesn’t seem to be a network or certification issue.
Any tips or known fixes?
No offense, but I’ll comment on what you’re saying like this: I want to ride a bike, but I’ll buy an SUV because it has a bike rack.
I’ve been waiting for 5 months for them to fix it, so far unsuccessfully. The problem with iHost is that the gateway does the same thing.
Just at google home has this issue , pairing other controllers is totally fine
It doesn’t work yet if you want to bridge directly with ewelink.
Sorry for keeping you waiting. I have been testing the scenario you described, but I haven’t been able to reproduce the issue where the -U device goes offline immediately on Google Home. I am currently running a continuous stability test on this device as well.
To help us investigate the problem you are encountering, could you please provide the device logs?
Thank you for your support and understanding!
1774361690611.tar.gz (3.8 MB)
also regarding covers from home assistant to matterbridge via zbbridge-u
Problem: Commands work, but status reporting is reversed. When the cover is physically closed, the controllers show “Fully Opened.” When physically opened, the controllers show “Fully Closed.”
Requested Action:
Please update the ZBBridge-U firmware to correctly map the open/closed attributes so that the controllers reflect the true physical state of the cover
any update ?
Hello, thank you for your feedback. Here is the progress update:
Regarding the issue where the device immediately shows as offline after bridging to Google Home via the ZBBridge-U Matter bridge, our technical team is currently investigating the problem based on the logs.
Regarding the issue where the curtain status is displayed in reverse, our testers successfully reproduced the problem today, and it has been submitted to the technical team for investigation and resolution.
We will handle this as soon as possible and release a version update to fix the issues. I will definitely contact you proactively if there are any new developments! Thank you for your support and understanding！
