Unable to pair with Google Home

[mfucci]

Steps to reproduce:

• launch Google Home
• click "+" / "set up device" to add a new device
• Select "New device"
• Select location then click "next"
• Wait until it times out to find a new device
• Click "Matter-enabled device"
• Scan node-matter QR code
• Click "I agree" to accept Google Home role
• "Connecting device to Google Home..." fails after a timeout "Can't find your device"

[mfucci]

From Wireshark, the issue might be that node-matter doesn't support IPv6 yet.
I will add the support for it this week then...

[andyearnshaw]

Have you added the matter device in Google Home Developer Console? I'm not 100% certain, but it is implied that test vendor/product IDs will only show up if you do this.

Any Matter device that has passed CSA Matter certification works in the Google Home ecosystem.

(implies that any device that hasn't passed certification will not work)

Reboot your hub to ensure that it receives the most recent Matter integration project configuration. If you have to change the VID or PID later, you'll also need to reboot after saving the project for the change to take effect.

(implies that Google Home will download the developer console configuration on reboot)

https://developers.home.google.com/codelabs/matter-device-virtual#2

[mfucci]

I did not added up in Google Home Developer Console.

The troubles I have:

1. the "Add a Matter Device" is now gone in Google Home on my main phone. Before it was gone, I was able to pair the CHIP lighting app (but appeared afterward as unreachable) but not node-matter
2. I revived an old Android phone: "Add a Matter Device" is not in Google Home as well but "Matter devices" is in Settings app > Google > Devices & sharing. Pairing the CHIP lighting app fails after a few exchanges, when trying to pair node-matter, Android doesn't even try to connect so something is wrong from the start.
3. Pairing from chip-tool is still working fine
4. I have now added IPv6 support so this is not the issue

@andyearnshaw : if you have some time, can you try compiling CHIP lighting app and pair it with your phone (Android or iOs)?
I would love to know a working configuration...

[JimBuzbee]

Regarding the "Add a Matter Device" going missing. You can get it back by opening the camera app, focusing on the node-matter QR code and then pressing the "Tap to Set Up" button that appears. This will go through the same sequence as usual from Google home. Then the button will also appear as it previously did in the Google Home setup. At least until Google pushes another update. Unfortunately, the setup still fails with a lot of debug messages on screen.

[mfucci]

Thanks for the tip!
Yes, that did the trick: I can now try to pair again from my main phone!
Still not working though, digging through Wireshark logs now

[mfucci]

In the Android logs, there is an error : "Commissioning failed with state Failure obtaining credentials."

I now added the VID and PID in Google Home Developer Console but that didn't fix the issue.

The failure seems to be because of a Timeout rather then test credentials missing, I think...

@andyearnshaw @JimBuzbee : where you able to pair CHIP lightning app or a virtual device?
If yes, which instructions did you follow?

[JimBuzbee]

I'm a novice at this and have only tried to pair with Google Home and with the Android Alexa app. I've not been successful with either. Here's the output when trying to pair with Alexa:

2022-11-4 19:39:17.534 INFO Device [email protected]
2022-11-4 19:39:17.547 INFO Device Listening
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ ██▀▄▀▄█ ▄▄▄▄▄ █
█ █ █ █▄▀▄▀▄█ █ █ █
█ █▄▄▄█ ██ ▀▀▄█ █▄▄▄█ █
█▄▄▄▄▄▄▄█ █ ▀▄█▄▄▄▄▄▄▄█
█ █ ▄▄ ▀ █ ▄▀██ █▀█
█▀ ███▀▄▄▀█ ▀▄▄██▄▀█▀█
████▄██▄▄██▄▀ ▀██▄▀ ▄▀█
█ ▄▄▄▄▄ █ █▄█▄█▄▄█▀██ █
█ █ █ █▄▄██▄ ▄█▀▄▄▀██
█ █▄▄▄█ █ ▀ █▄█ ▀▀ ▀▀ █
█▄▄▄▄▄▄▄█▄█▄█▄████▄▄█▄█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

QR Code URL: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT:-24J0AFN00KA0648G00
Manual pairing code: 34970112332
2022-11-4 19:39:17.549 ERROR MdnsBroadcaster Error: send EMSGSIZE ff02::fb:5353

2022-11-4 19:40:35.763 DEBUG MessageExchange onMessageReceived id:0/39861/53639255 t:0/32 reqAck:true payload: 15300120142ff9b9b17dab4a8cc9ce35d10a0ac6d479a041e74a285d06b92f000849a6d125024d11240300280418
2022-11-4 19:40:35.765 INFO PaseServer Pase server: Received pairing request from udp://192.168.1.44:5541
2022-11-4 19:40:35.768 DEBUG ExchangeManager sending id:0/39861/1875800731 t:0/33 acked:53639255 reqAck:true payload: 15300120142ff9b9b17dab4a8cc9ce35d10a0ac6d479a041e74a285d06b92f000849a6d13002209b7dec9ec007ff6b7ae1d4ed2f1d8aea7e3601ea4e5ad55c5d5547dffad041a325035c5e35042501e803300220d32014b423023625731ae603911844634568839becf37028ef49d4fc55f5d0ba1818
2022-11-4 19:40:35.785 DEBUG MessageExchange onMessageReceived id:0/39861/53639256 t:0/16 acked:1875800731 reqAck:false payload:
2022-11-4 19:40:35.865 DEBUG MessageExchange onMessageReceived id:0/39861/53639257 t:0/34 acked:1875800731 reqAck:true payload: 15300141047d1dd9853006379d1e63f5d603d23915f3aa3d2a41809369f0afb01a67fcbf251343d530153a16efa849e4ba154bc99bf065df5d7078c11eebefa7c508b8c8dc18
2022-11-4 19:40:35.905 DEBUG ExchangeManager sending id:0/39861/1875800732 t:0/35 acked:53639257 reqAck:true payload: 1530014104699d72603dcf1ebbe0a45a3e0f9fea3a09cf9e3dd0c5f11a49bb21f87670c3365c362fc2a519ed3cba3f9a1a996d00960db1784dde01869e0532798fb243eb2f300220e3fe67a01d6e91595c664944862ef56be8c24aa9bf5e43b40ab4b6ecfebbbd7f18
2022-11-4 19:40:35.921 DEBUG MessageExchange onMessageReceived id:0/39861/53639258 t:0/16 acked:1875800732 reqAck:false payload:
2022-11-4 19:40:35.993 DEBUG MessageExchange onMessageReceived id:0/39861/53639259 t:0/36 acked:1875800732 reqAck:true payload: 1530012032f85f36e849481862ca0cae47fbfa2b05c806ac0a315dae6830ecf10e002d5118
2022-11-4 19:40:35.994 DEBUG ExchangeManager sending id:0/39861/1875800733 t:0/64 acked:53639259 reqAck:true payload: 0000000000000000
2022-11-4 19:40:36.016 DEBUG MessageExchange onMessageReceived id:0/39861/53639260 t:0/16 acked:1875800733 reqAck:false payload:
2022-11-4 19:40:36.016 INFO PaseServer Pase server: session 24156 created with udp://192.168.1.44:5541
2022-11-4 19:40:36.115 DEBUG MessageExchange onMessageReceived id:24156/39862/180847106 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-4 19:40:36.117 ERROR InteractionMessenger Error: Unsupported message type 10
at InteractionServerMessenger. (/Users/jimbuzbee/matter/node-matter/build/matter/interaction/InteractionMessenger.js:80:31)
at Generator.next ()
at fulfilled (/Users/jimbuzbee/matter/node-matter/build/matter/interaction/InteractionMessenger.js:5:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2022-11-4 19:40:36.117 DEBUG ExchangeManager sending id:24156/39862/1875800734 t:1/1 acked:180847106 reqAck:true payload: 1524000124ff0118
2022-11-4 19:40:36.172 DEBUG MessageExchange onMessageReceived id:24156/39862/180847107 t:0/16 acked:1875800734 reqAck:false payload:
2022-11-4 19:40:51.464 DEBUG MessageExchange onMessageReceived id:0/39863/53639261 t:0/32 reqAck:true payload: 15300120302f5643efe0bed155112015d7e681f522337c10e8d059c242f20efe822a1c6525024e11240300280418
2022-11-4 19:40:51.464 INFO PaseServer Pase server: Received pairing request from udp://192.168.1.44:5541
2022-11-4 19:40:51.465 DEBUG ExchangeManager sending id:0/39863/1875800735 t:0/33 acked:53639261 reqAck:true payload: 15300120302f5643efe0bed155112015d7e681f522337c10e8d059c242f20efe822a1c653002202e08757adde8ffc6eb03a9677371af84fe7c20b6910e7a4c6dcf236b60ca3d5a25035d5e35042501e803300220d32014b423023625731ae603911844634568839becf37028ef49d4fc55f5d0ba1818
2022-11-4 19:40:51.486 DEBUG MessageExchange onMessageReceived id:0/39863/53639262 t:0/16 acked:1875800735 reqAck:false payload:
2022-11-4 19:40:51.563 DEBUG MessageExchange onMessageReceived id:0/39863/53639263 t:0/34 acked:1875800735 reqAck:true payload: 1530014104e5fb98d7878400d7ff04aacc00182e155e3bc81821804f8e92cacdc44544e733acf0881a6634c5cfb52a70720fb8ce75ce545d7a363d16254202dd62017b87c618
2022-11-4 19:40:51.600 DEBUG ExchangeManager sending id:0/39863/1875800736 t:0/35 acked:53639263 reqAck:true payload: 153001410420babd73930d1bdb9b0a71b83330a2a59dd30be8f99c2019aab2c33c2a5b6c44ab26182b8e8b45aa03a33783e3e0fc7e57b7ff366ff3bce2085f83505f083c5b30022073e49f3f7233208dbeac5f7c661a64a0dc8847a6f07c7cae78951215bc2eaa1418
2022-11-4 19:40:51.616 DEBUG MessageExchange onMessageReceived id:0/39863/53639264 t:0/16 acked:1875800736 reqAck:false payload:
2022-11-4 19:40:51.688 DEBUG MessageExchange onMessageReceived id:0/39863/53639265 t:0/36 acked:1875800736 reqAck:true payload: 15300120d49af0c59e0b15978fa846c6e05154f88fcc67a99689bc7e6e05a0187437f42218
2022-11-4 19:40:51.688 DEBUG ExchangeManager sending id:0/39863/1875800737 t:0/64 acked:53639265 reqAck:true payload: 0000000000000000
2022-11-4 19:40:51.709 DEBUG MessageExchange onMessageReceived id:0/39863/53639266 t:0/16 acked:1875800737 reqAck:false payload:
2022-11-4 19:40:51.709 INFO PaseServer Pase server: session 24157 created with udp://192.168.1.44:5541
2022-11-4 19:40:51.809 DEBUG MessageExchange onMessageReceived id:24157/39864/59025 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-4 19:40:51.809 ERROR InteractionMessenger Error: Unsupported message type 10
at InteractionServerMessenger. (/Users/jimbuzbee/matter/node-matter/build/matter/interaction/InteractionMessenger.js:80:31)
at Generator.next ()
at fulfilled (/Users/jimbuzbee/matter/node-matter/build/matter/interaction/InteractionMessenger.js:5:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2022-11-4 19:40:51.810 DEBUG ExchangeManager sending id:24157/39864/1875800738 t:1/1 acked:59025 reqAck:true payload: 1524000124ff0118
2022-11-4 19:40:51.827 DEBUG MessageExchange onMessageReceived id:24157/39864/59026 t:0/16 acked:1875800738 reqAck:false payload:

[mfucci]

Thanks for testing!
The bug you have above is fixed in a PR not merged yet. Look at the PR saying TimedRequest and sync to that branch.

Were you able to get the config giving by Andy working?
https://developers.home.google.com/codelabs/matter-device-virtual#2

I think I am stuck at the point where Google Home is expecting credentials to be provisioned in the dev console in all my configurations...

[JimBuzbee]

Just cloned main and tried to pair using Android Google home and Android Amazon Alexa. See similar quick failure with Google, but different behavior with Alexa (Log below). Seems to take quite a while and then eventually fails with a message in the app of "Is this device set up for control with another assistant or app?" If I say yes, it asks for the 11 digit setup code, but then fails again. If I say no, it just tries and fails again.

---

2022-11-5 10:41:24.219 INFO Device [email protected]
2022-11-5 10:41:24.235 INFO Device Listening
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█ ▄▄▄▄▄ ██▀▄▀▄█ ▄▄▄▄▄ █
█ █ █ █▄▀▄▀▄█ █ █ █
█ █▄▄▄█ ██ ▀▀▄█ █▄▄▄█ █
█▄▄▄▄▄▄▄█ █ ▀▄█▄▄▄▄▄▄▄█
█ █ ▄▄ ▀ █ ▄▀██ █▀█
█▀ ███▀▄▄▀█ ▀▄▄██▄▀█▀█
████▄██▄▄██▄▀ ▀██▄▀ ▄▀█
█ ▄▄▄▄▄ █ █▄█▄█▄▄█▀██ █
█ █ █ █▄▄██▄ ▄█▀▄▄▀██
█ █▄▄▄█ █ ▀ █▄█ ▀▀ ▀▀ █
█▄▄▄▄▄▄▄█▄█▄█▄████▄▄█▄█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

QR Code URL: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT:-24J0AFN00KA0648G00
Manual pairing code: 34970112332
2022-11-5 10:41:24.237 ERROR MdnsBroadcaster Error: send EMSGSIZE ff02::fb:5353
2022-11-5 10:41:58.580 DEBUG MessageExchange onMessageReceived id:0/39920/53639309 t:0/32 reqAck:true payload: 153001202dd54f86b8bc75605f326e8e742559926a5408d5b547db6523d4520bc62f415525025711240300280418
2022-11-5 10:41:58.581 INFO PaseServer Pase server: Received pairing request from udp://192.168.1.44:5541
2022-11-5 10:41:58.585 DEBUG ExchangeManager sending id:0/39920/1174631612 t:0/33 acked:53639309 reqAck:true payload: 153001202dd54f86b8bc75605f326e8e742559926a5408d5b547db6523d4520bc62f4155300220e7c170d73860bfb0fb88abea38029d2b73c7042e158136a1be3131ed84d6e02d2503158d35042501e80330022035258bc77e50acbb75e138b2c75bb68215699395bf81864df115e8f9811d55671818
2022-11-5 10:41:58.605 DEBUG MessageExchange onMessageReceived id:0/39920/53639310 t:0/16 acked:1174631612 reqAck:false payload:
2022-11-5 10:41:58.662 DEBUG MessageExchange onMessageReceived id:0/39920/53639311 t:0/34 acked:1174631612 reqAck:true payload: 153001410499a931b145dccd7ef48074be8034704a98009ac92165c3501ec5f3dc11186e53fe7417ca1ba8a274deb0c20907ed101a5afa011ede134afb668a0297ac23cf6e18
2022-11-5 10:41:58.700 DEBUG ExchangeManager sending id:0/39920/1174631613 t:0/35 acked:53639311 reqAck:true payload: 1530014104f6d76d2398cd545e47d2f80302218c10cd6d3d0874b5861d97d8aa2127983ad28e8623592ac29f333506731dce65bff5166b13ab89cd28d83cfc693da1b91f7f3002204d7b6ebc6240b9cc1ad2c3d8b19d54836d58bdf7876f5e24b9c13b0abc26f4fd18
2022-11-5 10:41:58.708 DEBUG MessageExchange onMessageReceived id:0/39920/53639312 t:0/16 acked:1174631613 reqAck:false payload:
2022-11-5 10:41:58.772 DEBUG MessageExchange onMessageReceived id:0/39920/53639313 t:0/36 acked:1174631613 reqAck:true payload: 153001209fac8cf9c5804ae5e0c06f93ea57eb2f64bd41b5e39b4965d2a4ded409b9fdbe18
2022-11-5 10:41:58.772 DEBUG ExchangeManager sending id:0/39920/1174631614 t:0/64 acked:53639313 reqAck:true payload: 0000000000000000
2022-11-5 10:41:58.782 DEBUG MessageExchange onMessageReceived id:0/39920/53639314 t:0/16 acked:1174631614 reqAck:false payload:
2022-11-5 10:41:58.782 INFO PaseServer Pase server: session 36117 created with udp://192.168.1.44:5541
2022-11-5 10:41:58.897 DEBUG MessageExchange onMessageReceived id:36117/39921/134330321 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:41:58.899 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:41:58.900 DEBUG ExchangeManager sending id:36117/39921/1174631615 t:1/1 acked:134330321 reqAck:true payload: 1524000024ff0118
2022-11-5 10:41:58.910 DEBUG MessageExchange onMessageReceived id:36117/39921/134330322 t:1/8 acked:1174631615 reqAck:true payload: 1528002901360215370024000024013e24020218350124000118181824ff0118
2022-11-5 10:41:58.911 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/62/2
2022-11-5 10:41:58.913 DEBUG ExchangeManager sending id:36117/39921/1174631616 t:1/9 acked:134330322 reqAck:true payload: 1528003601153500370024000024013e2402031835013100ec01308201e83082018fa0030201020208143c9d1689f498f0300a06082a8648ce3d04030230463118301606035504030c0f4d617474657220546573742050414931143012060a2b0601040182a27c02010c044646463131143012060a2b0601040182a27c02020c04383030303020170d3231303632383134323334335a180f39393939313233313233353935395a304b311d301b06035504030c144d6174746572205465737420444143203030303731143012060a2b0601040182a27c02010c044646463131143012060a2b0601040182a27c02020c04383030303059301306072a8648ce3d020106082a8648ce3d0301070342000462e2b6e1baff8d74a6fd8216c4cb67a3363a31e691492792e61aee610261481396725ef95e142686ba98f339b0ff65bc338bec7b9e8be0bdf3b2774982476220a360305e300c0603551d130101ff04023000300e0603551d0f0101ff040403020780301d0603551d0e04160414ee95ad96983a9ea95bcd2b00dc5e671727690383301f0603551d23041830168014af42b7094debd515ec6ecf33b81115225f325288300a06082a8648ce3d040302034700304402202f51cf53bf7777df7318094b9db595eebf2fa881c8c572847b1e689ece654264022029782708ee6b32c7f08ff63dbe618e9a580bb14c183bc288777adf9e2dcff5e61818181824ff0118
2022-11-5 10:41:58.924 DEBUG MessageExchange onMessageReceived id:36117/39921/134330323 t:0/16 acked:1174631616 reqAck:false payload:
2022-11-5 10:41:59.024 DEBUG MessageExchange onMessageReceived id:36117/39922/134330324 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:41:59.025 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:41:59.025 DEBUG ExchangeManager sending id:36117/39922/1174631617 t:1/1 acked:134330324 reqAck:true payload: 1524000024ff0118
2022-11-5 10:41:59.034 DEBUG MessageExchange onMessageReceived id:36117/39922/134330325 t:1/8 acked:1174631617 reqAck:true payload: 1528002901360215370024000024013e24020218350124000218181824ff0118
2022-11-5 10:41:59.034 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/62/2
2022-11-5 10:41:59.035 DEBUG ExchangeManager sending id:36117/39922/1174631618 t:1/9 acked:134330325 reqAck:true payload: 1528003601153500370024000024013e2402031835013100d801308201d43082017aa00302010202083e6ce6509ad840cd300a06082a8648ce3d04030230303118301606035504030c0f4d617474657220546573742050414131143012060a2b0601040182a27c02010c04464646313020170d3231303632383134323334335a180f39393939313233313233353935395a30463118301606035504030c0f4d617474657220546573742050414931143012060a2b0601040182a27c02010c044646463131143012060a2b0601040182a27c02020c04383030303059301306072a8648ce3d020106082a8648ce3d0301070342000480ddf11b228f3e31f63bcf5798da14623aebbde82ef378eeadbfb18fe1abce31d08ed4b20604b6ccc6d9b5fab64e7de10cb74be017c9ec1516056d70f2cd0b22a366306430120603551d130101ff040830060101ff020100300e0603551d0f0101ff040403020106301d0603551d0e04160414af42b7094debd515ec6ecf33b81115225f325288301f0603551d230418301680146afd22771f511fecbf1641976710dcdc31a1717e300a06082a8648ce3d040302034800304502210096c9c8cf2e01886005d8f5bc72c07b75fd9a57695ac4911131138bea033ce50302202554943be57d53d6c475f7d23ebfcfc2036cd29ba6393ec7efad8714ab7182191818181824ff0118
2022-11-5 10:41:59.046 DEBUG MessageExchange onMessageReceived id:36117/39922/134330326 t:0/16 acked:1174631618 reqAck:false payload:
2022-11-5 10:41:59.147 DEBUG MessageExchange onMessageReceived id:36117/39923/134330327 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:41:59.147 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:41:59.148 DEBUG ExchangeManager sending id:36117/39923/1174631619 t:1/1 acked:134330327 reqAck:true payload: 1524000024ff0118
2022-11-5 10:41:59.162 DEBUG MessageExchange onMessageReceived id:36117/39923/134330328 t:1/8 acked:1174631619 reqAck:true payload: 1528002901360215370024000024013e240200183501300020bbd6965895da6469ea80273b1e435ba2e502d5c1414e8c74c11c74e2f5c108b018181824ff0118
2022-11-5 10:41:59.163 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/62/0
2022-11-5 10:41:59.173 DEBUG ExchangeManager sending id:36117/39923/1174631620 t:1/9 acked:134330328 reqAck:true payload: 1528003601153500370024000024013e240201183501310049021531011d023082021906092a864886f70d010702a082020a30820206020103310d300b06096086480165030402013082017106092a864886f70d010701a08201620482015e152400012501f1ff3602050080050180050280050380050480050580050680050780050880050980050a80050b80050c80050d80050e80050f80051080051180051280051380051480051580051680051780051880051980051a80051b80051c80051d80051e80051f80052080052180052280052380052480052580052680052780052880052980052a80052b80052c80052d80052e80052f80053080053180053280053380053480053580053680053780053880053980053a80053b80053c80053d80053e80053f80054080054180054280054380054480054580054680054780054880054980054a80054b80054c80054d80054e80054f80055080055180055280055380055480055580055680055780055880055980055a80055b80055c80055d80055e80055f80056080056180056280056380182403162c04135a494732303134325a423333303030332d32342405002406002507942624080018317d307b020103801462fa823359acfaa9963e1cfa140addf504f37160300b0609608648016503040201300a06082a8648ce3d04030204473045022024e5d1f47a7d7b0d206a26ef699b7c9757b72d469089de3192e678c745e7f60c022100f8aa2fa711fcb79b97e397ceda667bae464e2bd3ffdfc3cced7aa8ca5f4c1a7c300220bbd6965895da6469ea80273b1e435ba2e502d5c1414e8c74c11c74e2f5c108b024030018300140766eb669615717c5f81c1bae6db4bfefc51f0b50a5defdd76482cf42ed07cbea87c85d674599baf13ef391738adb8301db7d3803d1e8686eb04a27245c7422711818181824ff0118
2022-11-5 10:41:59.186 DEBUG MessageExchange onMessageReceived id:36117/39923/134330329 t:0/16 acked:1174631620 reqAck:false payload:
2022-11-5 10:41:59.707 DEBUG MessageExchange onMessageReceived id:36117/39924/134330330 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:41:59.708 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:41:59.709 DEBUG ExchangeManager sending id:36117/39924/1174631621 t:1/1 acked:134330330 reqAck:true payload: 1524000024ff0118
2022-11-5 10:41:59.717 DEBUG MessageExchange onMessageReceived id:36117/39924/134330331 t:1/8 acked:1174631621 reqAck:true payload: 152800290136021537002400002401302402001835012500840324010118181824ff0118
2022-11-5 10:41:59.717 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/48/0
2022-11-5 10:41:59.719 DEBUG ExchangeManager sending id:36117/39924/1174631622 t:1/9 acked:134330331 reqAck:true payload: 152800360115350037002400002401302402011835012400002c01001818181824ff0118
2022-11-5 10:41:59.732 DEBUG MessageExchange onMessageReceived id:36117/39924/134330332 t:0/16 acked:1174631622 reqAck:false payload:
2022-11-5 10:41:59.830 DEBUG MessageExchange onMessageReceived id:36117/39925/134330333 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:41:59.830 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:41:59.831 DEBUG ExchangeManager sending id:36117/39925/1174631623 t:1/1 acked:134330333 reqAck:true payload: 1524000024ff0118
2022-11-5 10:41:59.846 DEBUG MessageExchange onMessageReceived id:36117/39925/134330334 t:1/8 acked:1174631623 reqAck:true payload: 1528002901360215370024000024013e240204183501300020989e092d786d9662edbd9e0b00f9ade6fb82a73cd033b1924f257445e77cf57f18181824ff0118
2022-11-5 10:41:59.846 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/62/4
2022-11-5 10:41:59.852 DEBUG ExchangeManager sending id:36117/39925/1174631624 t:1/9 acked:134330334 reqAck:true payload: 1528003601153500370024000024013e2402051835013000f4153001cc3081c93070020100300e310c300a060355040a0c034353523059301306072a8648ce3d020106082a8648ce3d03010703420004e3abf4181514d1dc9d1cac2a21299a45613afe87701fd052c1be83bbcf1c81116b0d46145bd333f170f2cd8b6554d35448197833254706b1099f8c8fc15ceee7a000300a06082a8648ce3d0403020349003046022100f0d51bd149b813ca859240fdc2a088f62b570cad26dbeab29b0c9551817727bb0221008ed0e8e0134a5b2043eccde0d9ae46cd8695d3e7695aaf1ac606b286b0407483300220989e092d786d9662edbd9e0b00f9ade6fb82a73cd033b1924f257445e77cf57f18300140df9ec0d87cbf46b1b383ed915fd5c36b4c824ab42b8aa099d15a01ac6d0146c8330c8fdd1d521c0397b295ff4b6c7634d5dad0d12ea1537cf6d26aa4106a18931818181824ff0118
2022-11-5 10:41:59.869 DEBUG MessageExchange onMessageReceived id:36117/39925/134330335 t:0/16 acked:1174631624 reqAck:false payload:
2022-11-5 10:42:3.603 DEBUG MessageExchange onMessageReceived id:36117/39926/134330336 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:42:3.604 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:42:3.604 DEBUG ExchangeManager sending id:36117/39926/1174631625 t:1/1 acked:134330336 reqAck:true payload: 1524000024ff0118
2022-11-5 10:42:3.611 DEBUG MessageExchange onMessageReceived id:36117/39926/134330337 t:1/8 acked:1174631625 reqAck:true payload: 1528002901360215370024000024013e24020b1835013100040115300110449debca2e2e9842e0876f8bfa23e45424020137032714f656b785f4bf3000182604e2dcbc2a260572dbc25937062714f656b785f4bf30001824070124080130094104ac7346eb93c34258f1696365a69fbecb33d482d9dfc73e94615883ba2e3ab2dd19cb8c122e190e902cb8ecb9aaea1000bb60ebe392b92c78bb41fd5cdcc30f46370a35012901183004142b335573c7c9124659e8e5fc50c56876fc93dc0b2402613005142b335573c7c9124659e8e5fc50c56876fc93dc0b18300b40488a6df0a59c3db55a29ebf69aba7ad249b8cce733e3aa45996e343ae3231d3094367733509a289b2542baaf1350dae843b4e1498c610dab24cde21cb25a36d51818181824ff0118
2022-11-5 10:42:3.612 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/62/11
2022-11-5 10:42:3.613 DEBUG ExchangeManager sending id:36117/39926/1174631626 t:1/9 acked:134330337 reqAck:true payload: 1528003601153501370024000024013e24020b1835012400001818181824ff0118
2022-11-5 10:42:3.623 DEBUG MessageExchange onMessageReceived id:36117/39926/134330338 t:0/16 acked:1174631626 reqAck:false payload:
2022-11-5 10:42:3.728 DEBUG MessageExchange onMessageReceived id:36117/39927/134330339 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:42:3.728 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36117
2022-11-5 10:42:3.728 DEBUG ExchangeManager sending id:36117/39927/1174631627 t:1/1 acked:134330339 reqAck:true payload: 1524000024ff0118
2022-11-5 10:42:3.763 DEBUG MessageExchange onMessageReceived id:36117/39927/134330340 t:1/8 acked:1174631627 reqAck:true payload: 1528002901360215370024000024013e2402061835013100150115300110096fa1ee1e4bd6c8d6f37ca36fc3bcf02402013703271328a22bb4d24e311018260458d1412b260568e20d3e37062715624a810d4b509900271140fb7509d9719b001824070124080130094104e3abf4181514d1dc9d1cac2a21299a45613afe87701fd052c1be83bbcf1c81116b0d46145bd333f170f2cd8b6554d35448197833254706b1099f8c8fc15ceee7370a3501280118300514cd74496f1130109c320baf27a5870dab17c209463004140f8eac55658c832b16a3f85b465d32eb2b9fcce62402013603040204011818300b4049e1cc863c96b07c6f8e2ea52357c359f8c1e1df1bfba853dc68de7609c652961df25e857b6aa1784abc8716cc6c38483c508d76a1a55f3b7561b517ad60887618310108011530011100cfde3823a4582e26fdfc65f0576be67024020137032714f656b785f4bf30001826045e13102b2605ee6b47473706271328a22bb4d24e31101824070124080130094104324c7e75275ac82b4d1ee71b75a6292e81c9a7b1df5ae0441cfa0cfcc8079fb69a9868437f414e15973ebd081ce1800ac471c0a70e2de2bbaa2daac2712bbef2370a35012901240200183005142b335573c7c9124659e8e5fc50c56876fc93dc0b300414cd74496f1130109c320baf27a5870dab17c2094624026118300b40af71273b1816c5dcaaa92af3f7a08ea54d40a01cd95b0cf1d571c222311f03316761cf36ded375d19f39d0f3942dc3938b4ff27415adabd6416db20c2a1505a51830021093b9524eb8e97a8e15412bfb3e123e8f27032a001100fdffffff2504f1ff18181824ff0118
2022-11-5 10:42:3.764 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36117: 0/62/6
2022-11-5 10:42:3.773 DEBUG ExchangeManager sending id:36117/39927/1174631628 t:1/9 acked:134330340 reqAck:true payload: 1528003601153500370024000024013e2402081835012400001818181824ff0118
2022-11-5 10:42:3.797 DEBUG MessageExchange onMessageReceived id:36117/39927/134330341 t:0/16 acked:1174631628 reqAck:false payload:
2022-11-5 10:42:4.120 DEBUG MessageExchange onMessageReceived id:0/39928/53639315 t:0/48 reqAck:true payload: 1530012008cfa4addef9cde7444ff3ff4851d64342e57b93514f76ef333fff20ccc9ac1d2502581130032040cbf215307275af79199bfa44cf511ebdf00b0e327e923c76d47e194eb21f54300441047a593180860c4037c83c12749845c8ee1424dd297fadcb895e358255d2c7d2b2a8ca25580f2626fe579062ff1b99ff91c24a0da06fb32b5be20148c9249f565018
2022-11-5 10:42:4.121 INFO CaseServer Case server: Received pairing request from udp://192.168.1.44:5541
2022-11-5 10:42:4.126 DEBUG ExchangeManager sending id:0/39928/1174631629 t:0/49 acked:53639315 reqAck:true payload: 15300120354f79582ee587d40b880b044b24be337f0fc48a98c637b0270c4b64a05a79d62502168d300341047f19bb6bd952ee4a4b25d83ead47764de238357a66b8e3ed7f5750c7de5f37c4175ea5590aaaf39e533cdbb5d5de347e80f0a309a8e00ff9cfbc4f6eac3ca80231048d025232dfc3880c4e6ec61bd62427360011b4d9138ebc08150be0c767ea1c83ab2c3e7cd3666db587b2751100ca589aca9360747ccb2d37b859a1bce077209cd10cd052965d3fd297b358a8bb30d2e9975c3d0836353a566cd4ce5ae9f47bb595da6d192afb280e4b1ec56d643f4d9ed8ad87f0c2666a670439517ca7a96d903bcde2b39eeb92fa1f71b92602005c1e693e8330b17f134dc0c2ed60de7a53dd8ee74907c5ce18b79b2ea319f662678d7b22f8cca2bc47429a7cfd2e657ef8a8d46199df9f6fa723796fc41fea55f7a84182c8295249c40ef2020f1d9d54a20169bdeacdf89f8b324c580238f53d3d03cace7d21e945675d476e05a1151d0d03bac9130a8697719c217dd64e666e0cc4dcd0b7530697a30bd146807b4327283ebf005874e3b682f61843d65051338a99a76585a03d46ccb68ca6272ae2df2de1f015bf633cf1682c903221d8f601795a846ece7cce6dfc7d454093689c6c77b073b0b3dc344123206f18b556936b76455b1c2e1fe325065daa833707e1029cfb6b4283a4446bae6c5ba6319850157aad4811fa1c109b78f6da162e31fb56138c65f186bd8863f8ffa8a679024be86ed2621f409df69cd4aa32161ff2a02677530810312514bd406f8d16e8be201146c51acb13427ff127133dbc11d173521d558737f50ddf55e4bcc869124b468d9ae62aeb1be2c326ea902c95d73cbe268c2e6245c4fe629d5e69d361b58431669f06abd2b611963ec6ae03850074d3dd493b8c4ac838d8f2295dee6c768ce474c14f9d7dc3a3ebb967b7ca97d167caebfc80f4b9cbe586ce829cdf2cd8eb43a374bada902bfff4e11d78bbd728852187fd91c2665d7f16633c11c4e037eba60074c2a977fba9f19c4af8c82e7c5f2de726228cd8c6d522733e0a43efda930a44ac18
2022-11-5 10:42:4.136 DEBUG MessageExchange onMessageReceived id:0/39928/53639316 t:0/16 acked:1174631629 reqAck:false payload:
2022-11-5 10:42:4.271 DEBUG MessageExchange onMessageReceived id:0/39928/53639317 t:0/50 acked:1174631629 reqAck:true payload: 1531018102cbde602d84d14230fe813568786cecab949507dbf1ef09211362852b36317e5870eabdad4420d23ee1d557d25ca9041b3b1d8df0800b54c04736cec77c9b42fc75776adfca9ec3fef4f3af94b573ebb9d743869d28db5ba65ee3c9c8de1707b59a7e20681690daa610805309109be95e455261e3da236b4a494380ccb707fc804da8489b6b74c5e723704350f794453a7df77d53b1bc6c833c16e54fb39bbd0288e61f21fe98e38db966e28bf43ea1e7e015e7016bb6f60dd527e771e0c0bb96f3177a3491ccfc37c443fa86a4976dd5b63191d2aa549905bdee53e32f143857449f0811a16709d12a7a7f1d790779c2e572f0203beec3bb98d5e0ba767ee81328d4bb1769711f161c93cddea87c0fbc23e991fa840119d504f1bceb2df785447423c8c18020b032fde7859cfd752004bca84e2218b6209c13d30ae82531148745497dae3434d99236c0d4dfedfaeec4da81c4a651f7b7f231b57c4b4c8cfe756069b02c7bc9012d97fd64b6c4d28d38a1c3a14adb76e3535034a07fe48f621da07107287425f6712b0d59f1c4f1e271bd8a8a2ac29c718b18aa48532dcc8bf97c188971754e579c2b3df4c0a73cc89e2c18122fa6c72ff8a24eccb38cdd6812f2f267546735a154e4132c7683d7650edf98f0330723740fec21b38853e48fc8e7f95097ddb88b534024ff2caa558fb2c8ce060799c85796490ac7ce1ae784d58b8c8a9ba5bfb3add756b2f05a01b5ef982b74de14816a155bc2634a3d6a662bb078ff248f88ab7e896ec7acf9f06e6d93714ef7d5ae07558386c1d1314d76b252f073c53f89d2b2276b93daf5c59b5d185d329a5925dd1f572b40711309d6269daef2137d2741d4eacbd1b51cb1a03fa515f7808fc3ffecf5ecc1fa4716efe78618
2022-11-5 10:42:4.275 INFO CaseServer Case server: session 36118 created with udp://192.168.1.44:5541
2022-11-5 10:42:4.276 DEBUG ExchangeManager sending id:0/39928/1174631630 t:0/64 acked:53639317 reqAck:true payload: 0000000000000000
2022-11-5 10:42:4.301 DEBUG MessageExchange onMessageReceived id:0/39928/53639318 t:0/16 acked:1174631630 reqAck:false payload:
2022-11-5 10:42:4.398 DEBUG MessageExchange onMessageReceived id:36118/39929/84707528 t:1/2 reqAck:true payload: 1536001724020124031d2404001818290324ff0118
2022-11-5 10:42:4.399 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 1/29/0
2022-11-5 10:42:4.400 DEBUG ExchangeManager sending id:36118/39929/1174631631 t:1/5 acked:84707528 reqAck:true payload: 153601153501240000370124020124031d24040018360215250000012401011818181818290424ff0118
2022-11-5 10:42:4.412 DEBUG MessageExchange onMessageReceived id:36118/39929/84707529 t:0/16 acked:1174631631 reqAck:false payload:
2022-11-5 10:42:4.516 DEBUG MessageExchange onMessageReceived id:36118/39930/84707530 t:1/10 reqAck:true payload: 152500102724ff0118
2022-11-5 10:42:4.517 DEBUG InteractionProtocol Received timed request from udp://192.168.1.44:5541 on session secure/36118
2022-11-5 10:42:4.517 DEBUG ExchangeManager sending id:36118/39930/1174631632 t:1/1 acked:84707530 reqAck:true payload: 1524000024ff0118
2022-11-5 10:42:4.529 DEBUG MessageExchange onMessageReceived id:36118/39930/84707531 t:1/8 acked:1174631632 reqAck:true payload: 1528002901360215370024000024013024020418350118181824ff0118
2022-11-5 10:42:4.529 DEBUG InteractionProtocol Received invoke request from udp://192.168.1.44:5541 on session secure/36118: 0/48/4
2022-11-5 10:42:4.530 INFO GeneralCommissioningClusterHandler Commissioning completed on fabric #43153954716076642 as node #009B71D90975FB40.
2022-11-5 10:42:4.530 DEBUG ExchangeManager sending id:36118/39930/1174631633 t:1/9 acked:84707531 reqAck:true payload: 152800360115350037002400002401302402051835012400002c01001818181824ff0118
2022-11-5 10:42:4.540 DEBUG MessageExchange onMessageReceived id:36118/39930/84707532 t:0/16 acked:1174631633 reqAck:false payload:
2022-11-5 10:42:4.657 DEBUG MessageExchange onMessageReceived id:36118/39931/84707533 t:1/2 reqAck:true payload: 153600172402002403282404051818290324ff0118
2022-11-5 10:42:4.658 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 0/40/5
2022-11-5 10:42:4.658 DEBUG ExchangeManager sending id:36118/39931/1174631634 t:1/5 acked:84707533 reqAck:true payload: 1536011535012400003701240200240328240405182c0200181818290424ff0118
2022-11-5 10:42:4.666 DEBUG MessageExchange onMessageReceived id:36118/39931/84707534 t:0/16 acked:1174631634 reqAck:false payload:
2022-11-5 10:42:4.772 DEBUG MessageExchange onMessageReceived id:36118/39932/84707535 t:1/2 reqAck:true payload: 1536001724020024032824040f1818290324ff0118
2022-11-5 10:42:4.772 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 0/40/15
2022-11-5 10:42:4.773 DEBUG ExchangeManager sending id:36118/39932/1174631635 t:1/5 acked:84707535 reqAck:true payload: 153601153501240000370124020024032824040f182c02126e6f64652d6d61747465722d302e302e3131181818290424ff0118
2022-11-5 10:42:4.787 DEBUG MessageExchange onMessageReceived id:36118/39932/84707536 t:0/16 acked:1174631635 reqAck:false payload:
2022-11-5 10:42:4.886 DEBUG MessageExchange onMessageReceived id:36118/39933/84707537 t:1/2 reqAck:true payload: 153600172402002403282404011818290324ff0118
2022-11-5 10:42:4.887 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 0/40/1
2022-11-5 10:42:4.887 DEBUG ExchangeManager sending id:36118/39933/1174631636 t:1/5 acked:84707537 reqAck:true payload: 1536011535012400003701240200240328240401182c020b6e6f64652d6d6174746572181818290424ff0118
2022-11-5 10:42:4.898 DEBUG MessageExchange onMessageReceived id:36118/39933/84707538 t:0/16 acked:1174631636 reqAck:false payload:
2022-11-5 10:42:4.998 DEBUG MessageExchange onMessageReceived id:36118/39934/84707539 t:1/2 reqAck:true payload: 153600172402002403282404031818290324ff0118
2022-11-5 10:42:4.999 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 0/40/3
2022-11-5 10:42:4.999 DEBUG ExchangeManager sending id:36118/39934/1174631637 t:1/5 acked:84707539 reqAck:true payload: 1536011535012400003701240200240328240403182c02124d6174746572207465737420646576696365181818290424ff0118
2022-11-5 10:42:5.010 DEBUG MessageExchange onMessageReceived id:36118/39934/84707540 t:0/16 acked:1174631637 reqAck:false payload:
2022-11-5 10:42:5.111 DEBUG MessageExchange onMessageReceived id:36118/39935/84707541 t:1/2 reqAck:true payload: 1536001724020124031d2404001818290324ff0118
2022-11-5 10:42:5.112 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 1/29/0
2022-11-5 10:42:5.112 DEBUG ExchangeManager sending id:36118/39935/1174631638 t:1/5 acked:84707541 reqAck:true payload: 153601153501240000370124020124031d24040018360215250000012401011818181818290424ff0118
2022-11-5 10:42:5.121 DEBUG MessageExchange onMessageReceived id:36118/39935/84707542 t:0/16 acked:1174631638 reqAck:false payload:
2022-11-5 10:42:5.223 DEBUG MessageExchange onMessageReceived id:36118/39936/84707543 t:1/2 reqAck:true payload: 153600172402002403312504fcff1818290324ff0118
2022-11-5 10:42:5.223 DEBUG InteractionProtocol Received read request from udp://192.168.1.44:5541 on session secure/36118: 0/49/65532
2022-11-5 10:42:5.224 DEBUG ExchangeManager sending id:36118/39936/1174631639 t:1/5 acked:84707543 reqAck:true payload: 15360118290424ff0118
2022-11-5 10:42:5.232 DEBUG MessageExchange onMessageReceived id:36118/39936/84707544 t:0/16 acked:1174631639 reqAck:false payload:

[mfucci]

Hi Jim,

Looks like you are able to go further in the pairing flow than me!
I am stuck at 0/62/4 command, Google Home says "Something went wrong" after that.

Can you help me reproduce your configuration so I can debug from there?

I will need those info:

• version of Google Home app? I have 2.62.80.2
• version of Home service? I have v224814000 (command "adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.home")
• do you set something in Google Home Dev Console? If yes, which name / vendor ID / product ID
• do you have a Google Matter-compatible device in your house? On my side, I have a Google Nest speaker but I have no clue if it is Matter-compatible

Thanks!

• Marco

[JimBuzbee]

Marco - To be clear, the long debug output is not from my Google Home. It's from the Amazon Alexa app running on Android when I try and add the node-matter "device". I've tried both Google Home and Alexa. I think I get similar behavior to you on Google Home.

[mfucci]

Sorry, I missed that part...

Can you create a new bug "Pairing with Alexa not working" with your logs above so I can work on it in parallel?

Thanks!

• Marco

[andyearnshaw]

Apologies, I'm temporarily without a personal computer so am unable to contribute at present.

[mfucci]

Google just pushed an update (com.google.android.gms.home [v224915000]) so things are working much better.
I am now able to pair the example from the official codebase and node-matter is going a little further in the pairing flow.

I will probably have node-matter pairing with Android by the end of the week.

[mfucci]

Seems like it was easier than I thought. After fixing one bug and adding the implementation for one additional cluster, I am now able to pair node-matter from Google Home: branch add-android-support

It appears as "offline" so I cannot operate it after pairing, but I think this is due to a misconfiguration of my Nest Speaker: I will investigate this tomorrow.

[mfucci]

I can now pair but there is some issues to control it after pairing.
The hub subscribe to //* (all attributes from all clusters from all endpoints) instead of just the one it needs and node-matter incorrectly assumes that it is possible to subscribe to all attributes, which is not the case, which is not the case.

So I need to:

• refactor all cluster definitions to clearly declare which ones can be subscribe to
• add support in the server to pass the subscribe info
• when a client asks to subscribe to //*, filter attributes based on if they can be subscribe to or not.

[Apollon77]

I take csare about first todo today

[Apollon77]

@mfucci Verified for the existing clusters ... only the onoff attrible of onoff is "reportable" for now (BUT the specs do not contain this, but the chip XML file does, so it is already in our code as comment "reportable: true".

Filed it as docs bug project-chip/connectedhomeip#24300

[bzbarsky-apple]

@mfucci @Apollon77 Just to be clear: the "reportable" quality (P) in the spec is Zigbee-only. In Matter, the behavior is as follows:

1. The priming part of subscription setup sends values for all attributes which match the given attribute paths.
2. After that, updates are sent for all attributes except the ones that have the "C" ("Changes Omitted") quality.

It's not sounding to me, based on the comments above, that node-matter is implementing that behavior so far...

[Apollon77]

Ahh ... ok then I think we misunderstood that ... Thank you!

@mfucci I will have a look but I did not discovered "changes omitted" so far in any of our defined-out clusters ...

[mfucci]

@bzbarsky-apple : thanks for clarifying the expected behavior!
That was not my understanding but this actually match the current implementation in node-matter: since "reportable" or "changes omitted" were not implemented, all attributes can be subscribed to and changes will be reported.

However chunking is not implemented either, and reporting all attributes in one message probably goes beyond the max length. I will work on adding this mechanism then. Alexa and Home Assistant only subscribe to onoff attribute so don't trigger this issue.

[mfucci]

Chunking implemented! It was actually easier than I thought: #176

node-matter is now working with Android!!!!!
Closing this issue.

[Apollon77]

btw: do we know if Google home on ios also works? Else I can also test that later