Pairing with other controllers.

[Luligu]

Hi,
here is a place to share the experiences...

[tammeryousef1006]

Many thanks for following up with us and for your great work

i share my experince (on android mobile ) while testing as followed :

• homeassistant matter was success to pair and shown all devices correctly without any issues
• ewelink matter (nspanel pro) was success to pair but shown only zigbee switches and didnt show other devices like motion sensors nor locks
• tuya matter on mobile itself without hub was success to pair but shown only one device non functional
• smartthings hub v3 was success to pair and shown all devices correctly except for the smoke sensor was appeared as door lock
• google home was success to pair but shown the devices in offline status , at the settings tab i was able to share from google to other controllers .

Tested Zigbee devices : LELLKI Zigbee Plug , sonoff motion sensor snzb-03 , tuya smoke sensor TS0601_smoke_4 , sonoff presence sensor snzb-06p , Osram light LIGHTIFY LED Classic A60 clear .

Best Regards

[tammeryousef1006]

i got this error whenever i share from smartthings matter to other platforms

Error 0x1/0x4 while invoking command: (1) No commissioning window is opened that could be revoked

its similiar to the error that @nitaybz had , but pairing direct from bridge wont get errors

[Luligu]

That's super interesting.
Thank you so much for sharing your contribution.

[nitaybz]

Trying to pair with Google (from iPhone) for the first pairing came out with this error:

2024-04-14 10:58:30.121 INFO   PaseServer           Received pairing request from udp://fe80::10c0:5932:100e:9eb4%br0:51599.
2024-04-14 10:58:30.303 INFO   PaseServer           Session 11390 created with udp://fe80::10c0:5932:100e:9eb4%br0:51599.
2024-04-14 10:58:30.463 INFO   SessionManager       End insecure session insecure/15896958080810181872
2024-04-14 10:58:33.451 INFO   MatterDevice         Announce done fabric: 1 fabricIndex: 1
2024-04-14 10:58:33.452 INFO   Operationa~alsServer addNoc success, adminVendorId 4996, caseAdminSubject 3801501750998556451
2024-04-14 10:58:33.459 INFO   UdpMulticastServer   lo: send ENETUNREACH ff02::fb:5353
2024-04-14 10:58:33.711 INFO   CaseServer           Received pairing request from udp://10.0.0.23:65273
2024-04-14 10:58:33.756 INFO   CaseServer           session 11391 created with udp://10.0.0.23:65273 for Fabric 0000000034860452(index 1) and PeerNode 34C1A5B3894B5F23
2024-04-14 10:58:33.793 INFO   MatterDevice         All announcements expired
2024-04-14 10:58:33.795 INFO   SecureSession        Register Session secure/11390 to send a close when exchange is ended.
2024-04-14 10:58:33.797 INFO   GeneralCom~erHandler Commissioning completed on fabric #1 as node #881198162.
2024-04-14 10:58:33.802 INFO   SessionManager       End insecure session insecure/10795832523219058266
2024-04-14 10:58:34.263 INFO   InteractionServer    Error 0x1/0x4 while invoking command: (1) No commissioning window is opened that could be revoked.
2024-04-14 10:58:34.618 INFO   PaseServer           Received pairing request from udp://fe80::10c0:5932:100e:9eb4%br0:64264.
2024-04-14 10:58:34.704 INFO   PaseServer           Session 11392 created with udp://fe80::10c0:5932:100e:9eb4%br0:64264.
2024-04-14 10:58:34.709 INFO   SessionManager       End insecure session insecure/11880928492581573414
2024-04-14 10:58:40.190 INFO   SessionManager       End PASE session secure/11390

Trying to pair while it's already paired with other systems gave me this error:

2024-04-11 15:23:26.393 ERROR  InteractionMessenger RetransmissionLimitReachedError
    at MessageExchange.retransmitMessage (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/MessageExchange.js:274:36)
    at TimerNode.callback (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/MessageExchange.js:294:20)
    at Timeout._onTimeout (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter-node.js/dist/esm/time/TimeNode.js:51:12)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7)
2024-04-11 15:23:26.395 ERROR  ExchangeManager      The previous message has not been acked yet, cannot send a new message.
    at MessageExchange.send (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/MessageExchange.js:182:13)
    at InteractionServerMessenger.send (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/interaction/InteractionMessenger.js:61:26)
    at InteractionServerMessenger.sendStatus (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/interaction/InteractionMessenger.js:64:17)
    at InteractionServerMessenger.handleRequest (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/interaction/InteractionMessenger.js:158:20)
    at async InteractionServer.onNewExchange (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/interaction/InteractionServer.js:72:5)
    at async ExchangeManager.onMessage (file:///usr/lib/node_modules/matterbridge/node_modules/@project-chip/matter.js/dist/esm/protocol/ExchangeManager.js:173:9)

I Was also not able to pair with Tuya/SmartLife, directly as the first pair or after activating pairing from Apple Home, I get an immediate error from their app without a visual error in the logs.

[Ultra-bob]

I have the same issue, did you ever find a solution

[Apollon77]

"Same error" is way too unspecific ... also above

• first log do not show any real error ... the one log that sounds like an error is a normal behavior for google and ok
• second log is mainly showing that the "ther side" was not answering requests ... sooo way more log is needed to see what was send and such to get an idea on what could have happened.
  The most important thing is that the matterbridge host needs to be rechable via UDP from the mobile device used for pairing AND also from the Google hub device ... so make sure not different net segmets or such stuff is there. Rest needs way more log

[Ultra-bob]

Here's my issue with debug logs
#61

[nitaybz]

Success was on these Systems:
Apple Home - All works well
Home Assistant - All works well
Alexa - succeeded pairing and all accessories showed except switches.

[nitaybz]

I got my hand on an Android phone so I get the following as well:

Google Home Success pairing from Android phone as the first pairing device.

SmartLife showed a bit of progress on Android, according to the logs the pairing was a success but the app showed it failed, tried a few times as a first pairing device or after pairing with Google but it fails everytime.
this is what I get in the logs:

2024-04-14 15:37:51.958 INFO   PaseServer           Received pairing request from udp://10.0.0.101:26847.
2024-04-14 15:37:52.173 INFO   PaseServer           Session 11263 created with udp://10.0.0.101:26847.
2024-04-14 15:37:52.191 INFO   SessionManager       End insecure session insecure/8716180572232612365
2024-04-14 15:37:54.478 INFO   MatterDevice         Announce done fabric: 2035326 fabricIndex: 1
2024-04-14 15:37:54.480 INFO   Operationa~alsServer addNoc success, adminVendorId 4701, caseAdminSubject 65536

[nitaybz]

After further investigation and using zigbee2mqtt plugin I see that all devices in Google are shown as Offline

[tammeryousef1006]

i did manage today to pair it with google home without having any offline devices , what i did is i created new home at google home app , then i added one of my nest hub device v1 to it , after that i did reboot for the nest hub and added the matterbridge direct (no other controllers connected) and the devices started to show up at google home and works locally very well .

[Luligu]

With the controllers I know (Apple Home and HA) sometimes is just a question of time... waiting 1 or 2 minutes and everything gets online.
BTW thank you for sharing.

[nitaybz]

Your work is amazing!
Can't wait to make it more stable to work flawlessly with all platforms. Next step would be to
Do an easy migration from Homebridge

[Luligu]

Thank you so much
I published the updates on all packages. Also presence.

[Luligu]

Thanks again for trying with all controllers.
I appreciated so much.
If you feel it, it would be nice to write something on the readme of Matterbridge or Matterbridge zigbee2mqtt about it...

[gary-sargent]

I'm trying to pair with an Aqara M3 Hub and get the error "The device certificate is invalid and cannot be added". Any idea?

[tammeryousef1006]

we face similiar msg with other controllers like google home , alexa , smartthings , ewelink , and there is selection to continue anyway , I didn't test aqara because I don't have it but you can try to see if there is option to continue anyway and skip certificate validation

[gary-sargent]

There doesn't appear to be a way to skip this

[tammeryousef1006]

if you dont mind me asking , are you on android or over iPhone ? can you screenshot at that page of pairing ?

[gary-sargent]

Android.

[tammeryousef1006]

[Apollon77]

So yes this will stay for the next future that way because without being a CSA member and certifying the device (matterbridge in this case) and then getting real per-device-instance certificates (and each step costs money) matterbridge will stay a "test device" without proper certificates. And this generates this message.

And yes controllers need to tell the user that he pairs an (uncertificated and pot unsecure) device and allow him to "Opt out". Why Aquara choose to block it completely I do not know. I would propose to email them to ask for it to be allowed and added :-)) maybe they change their mind