USB Zigbee not exposed by matter bridge

Matter gateway, Matter bridge, Matter over Wi-Fi, and Matter over thread development.


Sugar
Posts: 28

fangping.guo 2025年 Dec 8日 11:34

I see the new log. Has the device now appeared as successfully bridged? I haven't yet identified why these two devices couldn't bridge, and I'm continuing to analyze the issue. If it's convenient for you, please try resetting the Tuya Matter gateway first and then attempt the process again.

No, it's not exposed. I restarted the gateway, but I can't unbind and bind these devices again at this moment, I'm at work. Normally added devices are exposed instantly, even without restarting the hub.

All exposed devices:

(these 6 switches are different devices)

That marked temperature sensor is still exposed, but that devices in no longer binded to the hub.

Screenshot_2025-12-08-04-02-36-409_com.lumiunited.aqarahome.play.jpg
Screenshot_2025-12-08-04-02-40-520_com.lumiunited.aqarahome.play-edit.jpg

What I can try later: I will unbind and bind devices again, then I will unbind and bind Moe's hub to the Aqara matter controller again, but I doubt it will change anything.
I can factory reset moes hub and bind all devices again, but I'm not sure if it can help? What do you think?

update: I unbinded and binded them again, it didn't help

new virtual ID for relay: bfa44d76757e30c6fenoas
new virtual ID for usb: bfa5ae4d996a72bf414ei6

Sugar
Posts: 28

Re: USB Zigbee not exposed by matter bridge

fangping.guo 2025年 Dec 8日 11:34

I see the new log. Has the device now appeared as successfully bridged? I haven't yet identified why these two devices couldn't bridge, and I'm continuing to analyse the issue. If it's convenient for you, please try resetting the Tuya Matter gateway first and then attempt the process again.

So I did a factory reset of the moes hub. It didn't help.

New Moes Hub Virtual ID is: bf01ab90188976b3f7xqtl

New Relay Virtual ID is: bfc4612dea4df66c1cdbef

New USB Virtual ID is: bf9aa60649df8b4bb7ra6j

After factory resetting the Moes Hub, it is still exposing that non-existent sensor. I think it's somehow hard-binned to my Tuya account on the server now? Maybe that's why Humidity levels for these 2 existing sensors are sometimes 0 percent in the Aqara app.

Marked one is a non-existing sensor:

photo_2025-12-18_14-55-07.jpg
dupaaa.jpg
photo_2025-12-18_14-58-24.jpg
photo_2025-12-18_14-58-27.jpg

Here are the Virtual IDs of these two existing sensors:

  1. bfa08c9e312e0ac938nrgo
  2. bfcbfe6d04ce50680fdbnd
photo_2025-12-18_15-01-47.jpg

Thanks.

Post Reply