Closed FutronicsMP closed 1 year ago
Hello Yes I experience the same issue while using a Matter Bridge commissioned by Google Home app. Bridge is displayed but underlying devices are offline.
Hi @FutronicsMP. Thanks for raising the issue. We've identified a relevant cloud flag that hasn't fully rolled out yet that's preventing control. We will work on expediting it.
@rochaferraz Thank you very much for your kind answer! I was trying to get help regarding that from Silicon Labs and Nordic and for at least 2 days trying to make it work. You save my next day :) Do you know when it's planned to release of an improved version?
Same for me with the Nordic Semiconductor Matter-Template extended with thermostat cluster.
@rochaferraz Is your finding a GHA bug or a bug in the Matter/connectedhomeip repository? Thanks for your great support.
@FutronicsMP please try to factory reset the nest hub, remove the devices from the Google home app and link the nest once again with Google Home app, and proceed the commissioning (after commissioning Google Home App may need some time - couple seconds to have fully operational device). I tested that with Nordic, and I saw that after update of Nest Hub firmware I needed to factory reset the Hub.
@doublemis1 I did it once again today:
Both phone and Nest Hub Gen.2 are connected to the same EERO WiFi router. Google account- the same e-mail address for both phone and Nest Hub Gen.2 Below is my google integration config.
@rochaferraz mention that some cloud flags are not set correctly. I would like to learn more about it - I will be appreciated for sending me the issue link if there is created.
Just now installed fresh Nordic SDK v2.2.0-rc1. Still, the device is offline after successful commissioning. Looks like the flags mentioned by @rochaferraz are still not fixed. Does anybody know where I can find information on how I can fix device's offline problem?
Nest Hub 2 software version is: 47.9.4.447810048
Chromecast firmware version: 1.56.324896
Google Home App Versoin: 2.60.1.22
Nordic Light Example from SDK 2.1.2
nRF5340 Board Matter 1.0 Light_Bulb example.
`
[1;32muart:~$ [mI: nRF5 802154 radio initialized
I: 4 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
Booting Zephyr OS build v3.2.99-ncs1-rc1
I: Init CHIP stack
I: 493 [DL]BLE address: DB:98:BC:80:56:3E
I: 515 [DL]OpenThread started: OK
I: 518 [DL]Setting OpenThread device type to ROUTER
I: 523 [SVR]Server initializing...
D: 526 [FP]Initializing FabricTable from persistent storage
I: 532 [TS]Last Known Good Time: [unknown]
I: 536 [TS]Setting Last Known Good Time to firmware build time 2022-11-28T22:24:32
I: 544 [DMG]AccessControl: initializing
I: 547 [DMG]Examples::AccessControlDelegate::Init
I: 552 [DMG]AccessControl: setting
I: 555 [DMG]DefaultAclStorage: initializing
I: 559 [DMG]DefaultAclStorage: 0 entries loaded
D: 563 [IN]UDP::Init bind&listen port=5540
E: 567 [IN]SO_REUSEPORT failed: 109
D: 571 [IN]UDP::Init bound to port=5540
D: 574 [IN]BLEBase::Init - setting/overriding transport
D: 579 [IN]TransportMgr initialized
D: 585 [DL]Using Thread extended MAC for hostname.
I: 591 [ZCL]Using ZAP configuration...
D: 595 [DMG]Failed to read stored attribute (0, 0x0000_0028, 0x0000_0005: a0
D: 603 [DMG]Failed to read stored attribute (1, 0x0000_0006, 0x0000_0000: a0
D: 610 [DMG]Failed to read stored attribute (1, 0x0000_0006, 0x0000_4003: a0
D: 617 [DMG]Failed to read stored attribute (1, 0x0000_0008, 0x0000_0000: a0
D: 624 [DMG]Failed to read stored attribute (1, 0x0000_0008, 0x0000_4000: a0
I: 631 [DMG]AccessControlCluster: initializing
D: 635 [DMG]Endpoint 0, Cluster 0x0000_0030 update version to e0685672
D: 641 [DL]Boot reason: 1
D: 644 [ZCL]GeneralDiagnostics: OnDeviceReboot
D: 648 [DMG]Endpoint 0, Cluster 0x0000_0033 update version to 268fd0e8
D: 655 [EVL]LogEvent event number: 0x0000000000000000 priority: 2, endpoint id: 0x0 cluster id: 0x0000_0033 event id: 0x3 Sys timestamp: 0x000000000000028E
I: 668 [ZCL]Initiating Admin Commissioning cluster.
D: 673 [DMG]Endpoint 1, Cluster 0x0000_0003 update version to 626c8919
D: 680 [DMG]Endpoint 1, Cluster 0x0000_0004 update version to 1f51a49
D: 686 [DMG]Endpoint 1, Cluster 0x0000_0004 update version to 1f51a4a
I: 692 [ZCL]On/Off set value: 1 0
I: 695 [ZCL]On/off already set to new value
D: 700 [DMG]Endpoint 1, Cluster 0x0000_0008 update version to fd42720
I: 706 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 1
D: 712 [ZCL]LED is off. Try to use move-to-level-with-on-off instead of move-to-level
D: 721 [IN]SecureSession[0x20004430]: Allocated Type:1 LSID:23688
D: 727 [SC]Assigned local session key ID 23688
D: 731 [SC]Waiting for PBKDF param request
D: 735 [DL]CHIPoBLE advertising set to on
I: 739 [DIS]Updating services using commissioning mode 1
D: 744 [DL]Using Thread extended MAC for hostname.
D: 749 [DL]Using Thread extended MAC for hostname.
I: 754 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
E: 763 [DIS]Failed to advertise commissionable node: 3
E: 768 [DIS]Failed to finalize service update: 1c
I: 772 [DIS]Updating services using commissioning mode 1
D: 777 [DL]Using Thread extended MAC for hostname.
D: 782 [DL]Using Thread extended MAC for hostname.
I: 787 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
E: 796 [DIS]Failed to advertise commissionable node: 3
E: 801 [DIS]Failed to finalize service update: 1c
I: 806 [DIS]Delaying proxy of operational discovery: missing delegate
I: 812 [IN]CASE Server enabling CASE session setups
D: 817 [IN]SecureSession[0x200044e8]: Allocated Type:2 LSID:23689
D: 823 [SC]Allocated SecureSession (0x200044e8) - waiting for Sigma1 msg
I: 829 [SVR]Joining Multicast groups
D: 833 [ZCL]Emitting StartUp event
D: 836 [EVL]LogEvent event number: 0x0000000000000001 priority: 2, endpoint id: 0x0 cluster id: 0x0000_0028 event id: 0x0 Sys timestamp: 0x0000000000000344
I: 850 [SVR]Server Listening...
I: 853 [DL]Device Configuration:
I: 856 [DL] Serial Number: 11223344556677889900
I: 860 [DL] Vendor Id: 65521 (0xFFF1)
I: 864 [DL] Product Id: 32773 (0x8005)
I: 868 [DL] Hardware Version: 0
I: 871 [DL] Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
I: 876 [DL] Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
I: 883 [DL] Manufacturing Date: (not set)
I: 887 [DL] Device Type: 65535 (0xFFFF)
I: 891 [SVR]SetupQRCode: [MT:6FCJ142C00KA0648G00]
I: 895 [SVR]Copy/paste the below URL in a browser to see the QR Code:
I: 901 [SVR]https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A6FCJ142C00KA0648G00
I: 910 [SVR]Manual pairing code: [34970112332]
I: 915 [DL]CHIP task running
I: 922 [DL]CHIPoBLE advertising started
D: 926 [DMG]Endpoint 1, Cluster 0x0000_0006 update version to a3dbcb10
I: 933 [ZCL]Cluster OnOff: attribute OnOff set to 0
D: 938 [DMG]Endpoint 1, Cluster 0x0000_0008 update version to fd42721
I: 944 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 254
D: 950 [ZCL]LED is off. Try to use move-to-level-with-on-off instead of move-to-level
I: 958 [DL]NFC Tag emulation started
I: 30925 [DL]CHIPoBLE advertising mode changed to slow
I: 100168 [DL]BLE connection established (ConnId: 0x00)
I: 100174 [DL]Current number of connections: 1/2
I: 100178 [DL]CHIPoBLE advertising stopped
I: 100182 [DL]NFC Tag emulation stopped
I: 100624 [DL]BLE GAP connection terminated (reason 0x2a)
I: 100630 [DL]Current number of connections: 0/2
I: 100637 [DL]CHIPoBLE advertising started
I: 100641 [DL]NFC Tag emulation started
I: 130641 [DL]CHIPoBLE advertising mode changed to slow
I: 178981 [DL]BLE connection established (ConnId: 0x00)
I: 178986 [DL]Current number of connections: 1/2
I: 178991 [DL]CHIPoBLE advertising stopped
I: 178995 [DL]NFC Tag emulation stopped
I: 179428 [DL]BLE GAP connection terminated (reason 0x2a)
I: 179433 [DL]Current number of connections: 0/2
I: 179441 [DL]CHIPoBLE advertising started
I: 179445 [DL]NFC Tag emulation started
I: 209444 [DL]CHIPoBLE advertising mode changed to slow
I: 390034 [DL]BLE connection established (ConnId: 0x00)
I: 390039 [DL]Current number of connections: 1/2
I: 390044 [DL]CHIPoBLE advertising stopped
I: 390048 [DL]NFC Tag emulation stopped
I: 390499 [DL]BLE GAP connection terminated (reason 0x2a)
I: 390504 [DL]Current number of connections: 0/2
I: 390512 [DL]CHIPoBLE advertising started
I: 390516 [DL]NFC Tag emulation started
I: 420516 [DL]CHIPoBLE advertising mode changed to slow
I: 537740 [DL]BLE connection established (ConnId: 0x00)
I: 537746 [DL]Current number of connections: 1/2
I: 537750 [DL]CHIPoBLE advertising stopped
I: 537754 [DL]NFC Tag emulation stopped
I: 541107 [DL]BLE GAP connection terminated (reason 0x13)
I: 541112 [DL]Current number of connections: 0/2
I: 541119 [DL]CHIPoBLE advertising started
I: 541124 [DL]NFC Tag emulation started
I: 541577 [DL]BLE connection established (ConnId: 0x00)
I: 541583 [DL]Current number of connections: 1/2
I: 541587 [DL]CHIPoBLE advertising stopped
I: 541591 [DL]NFC Tag emulation stopped
I: 544957 [DL]BLE GAP connection terminated (reason 0x13)
I: 544962 [DL]Current number of connections: 0/2
I: 544969 [DL]CHIPoBLE advertising started
I: 544974 [DL]NFC Tag emulation started
I: 557881 [DL]BLE connection established (ConnId: 0x00)
I: 557886 [DL]Current number of connections: 1/2
I: 557891 [DL]CHIPoBLE advertising stopped
I: 557895 [DL]NFC Tag emulation stopped
I: 561215 [DL]BLE GAP connection terminated (reason 0x13)
I: 561220 [DL]Current number of connections: 0/2
I: 561227 [DL]CHIPoBLE advertising started
I: 561231 [DL]NFC Tag emulation started
I: 561517 [DL]BLE connection established (ConnId: 0x00)
I: 561523 [DL]Current number of connections: 1/2
I: 561527 [DL]CHIPoBLE advertising stopped
I: 561531 [DL]NFC Tag emulation stopped
I: 564872 [DL]BLE GAP connection terminated (reason 0x13)
I: 564877 [DL]Current number of connections: 0/2
I: 564885 [DL]CHIPoBLE advertising started
I: 564889 [DL]NFC Tag emulation started
I: 565912 [DL]BLE connection established (ConnId: 0x00)
I: 565918 [DL]Current number of connections: 1/2
I: 565922 [DL]CHIPoBLE advertising stopped
I: 565926 [DL]NFC Tag emulation stopped
I: 569247 [DL]BLE GAP connection terminated (reason 0x13)
I: 569252 [DL]Current number of connections: 0/2
I: 569260 [DL]CHIPoBLE advertising started
I: 569264 [DL]NFC Tag emulation started
I: 599264 [DL]CHIPoBLE advertising mode changed to slow
I: 601294 [DL]BLE connection established (ConnId: 0x00)
I: 601299 [DL]Current number of connections: 1/2
I: 601303 [DL]CHIPoBLE advertising stopped
I: 601307 [DL]NFC Tag emulation stopped
I: 601728 [DL]BLE GAP connection terminated (reason 0x2a)
I: 601733 [DL]Current number of connections: 0/2
I: 601741 [DL]CHIPoBLE advertising started
I: 601745 [DL]NFC Tag emulation started
I: 631744 [DL]CHIPoBLE advertising mode changed to slow
I: 900720 [SVR]Closing pairing window
D: 900724 [IN]SecureSession[0x20004430]: Released - Type:1 LSID:23688
I: 900730 [DIS]Updating services using commissioning mode 0
D: 900735 [DL]Using Thread extended MAC for hostname.
D: 900740 [DL]Using Thread extended MAC for hostname.
I: 900746 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
E: 900755 [DIS]Failed to advertise extended commissionable node: 3
D: 900761 [DIS]Scheduling extended discovery timeout in 900s
E: 900766 [DIS]Failed to finalize service update: 1c
D: 900771 [DL]CHIPoBLE advertising set to off
I: 900776 [DL]CHIPoBLE advertising stopped
I: 900780 [DL]NFC Tag emulation stopped
I: Software update is disabled
D: 948716 [IN]SecureSession[0x20004430]: Allocated Type:1 LSID:23690
D: 948722 [SC]Assigned local session key ID 23690
D: 948727 [SC]Waiting for PBKDF param request
D: 948731 [DL]CHIPoBLE advertising set to on
I: 948735 [DIS]Updating services using commissioning mode 1
D: 948740 [DL]Using Thread extended MAC for hostname.
D: 948746 [DL]Using Thread extended MAC for hostname.
I: 948751 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
E: 948760 [DIS]Failed to advertise commissionable node: 3
E: 948765 [DIS]Failed to finalize service update: 1c
I: 948773 [DL]CHIPoBLE advertising started
I: 948778 [DL]NFC Tag emulation started
I: 949216 [DL]BLE connection established (ConnId: 0x00)
I: 949221 [DL]Current number of connections: 1/2
I: 949226 [DL]CHIPoBLE advertising stopped
I: 949230 [DL]NFC Tag emulation stopped
I: 949669 [DL]BLE GAP connection terminated (reason 0x2a)
I: 949674 [DL]Current number of connections: 0/2
I: 949682 [DL]CHIPoBLE advertising started
I: 949686 [DL]NFC Tag emulation started
I: 979685 [DL]CHIPoBLE advertising mode changed to slow
I: 994467 [DL]BLE connection established (ConnId: 0x00)
I: 994473 [DL]Current number of connections: 1/2
I: 994477 [DL]CHIPoBLE advertising stopped
I: 994481 [DL]NFC Tag emulation stopped
D: 995537 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 995545 [BLE]local and remote recv window sizes = 5
I: 995550 [BLE]selected BTP version 4
I: 995553 [BLE]using BTP fragment sizes rx 128 / tx 128.
D: 995572 [DL]ConnId: 0x00, New CCCD value: 0x0002
D: 995577 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 995585 [IN]BLE EndPoint 0x2000b0e8 Connection Complete
I: 995590 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 131)
D: 995677 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 995748 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 995755 [EM]>>> [E:14522r M:132793805] (U) Msg RX from 0:8C1C731D09AF00B0 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
D: 995767 [EM]Handling via exchange: 14522r, Delegate: 0x20006614
D: 995773 [SC]Received PBKDF param request
D: 995777 [SC]Peer assigned session ID 49619
D: 995781 [SC]Found MRP parameters in the message
D: 995786 [SC]Including MRP parameters in PBKDF param response
I: 995792 [EM]<<< [E:14522r M:260362351] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I: 995804 IN Sending msg 260362351 to IP address 'BLE'
D: 995809 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 995817 [SC]Sent PBKDF param response
D: 995887 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 995895 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 14)
D: 995957 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 995966 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 995973 [EM]>>> [E:14522r M:132793806] (U) Msg RX from 0:8C1C731D09AF00B0 [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
D: 995984 [EM]Found matching exchange: 14522r, Delegate: 0x20006614
D: 995990 [SC]Received spake2p msg1
I: 997547 [EM]<<< [E:14522r M:260362352] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I: 997558 IN Sending msg 260362352 to IP address 'BLE'
D: 997564 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 128)
D: 997572 [SC]Sent spake2p msg2
E: 997574 [DL]Long dispatch time: 1609 ms, for event type 16388
D: 997637 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 997645 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 997707 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 997716 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 997723 [EM]>>> [E:14522r M:132793807] (U) Msg RX from 0:8C1C731D09AF00B0 [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
D: 997734 [EM]Found matching exchange: 14522r, Delegate: 0x20006614
D: 997740 [SC]Received spake2p msg3
D: 997744 [SC]Sending status report. Protocol code 0, exchange 14522
I: 997750 [EM]<<< [E:14522r M:260362353] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I: 997762 IN Sending msg 260362353 to IP address 'BLE'
D: 997767 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 35)
I: 997775 [SC]SecureSession[0x20004430]: Moving from state 'kEstablishing' --> 'kActive'
D: 997784 [IN]SecureSession[0x20004430]: Activated - Type:1 LSID:23690
D: 997790 [IN]New secure session activated for device <FFFFFFFB00000000, 0>, LSID:23690 PSID:49619!
I: 997799 [SVR]Commissioning completed session establishment step
I: 997805 [DIS]Updating services using commissioning mode 0
D: 997810 [DL]Using Thread extended MAC for hostname.
D: 997816 [DL]Using Thread extended MAC for hostname.
I: 997822 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
E: 997831 [DIS]Failed to advertise extended commissionable node: 3
D: 997837 [DIS]Scheduling extended discovery timeout in 900s
E: 997842 [DIS]Failed to finalize service update: 1c
D: 997847 [DL]CHIPoBLE advertising set to off
I: 997851 [SVR]Device completed Rendezvous process
E: 997856 [DL]Long dispatch time: 141 ms, for event type 16388
D: 997861 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 997869 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 997877 [EM]>>> [E:14523r M:90317629] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D: 997888 [EM]Handling via exchange: 14523r, Delegate: 0x20008ab4
D: 997893 [IM]Received Read request
D: 997897 [DMG]IM RH moving to [GeneratingReports]
D: 997902 [DMG]Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
D: 997911 [DMG]
@FutronicsMP could you tell me how to update Nest Hub 2 to version 1.56.324896. Because my Nest Hub 2 version still stays on 1.56.309385.
Hi @FutronicsMP, @benjaminnestler the cloud flag change is published, but it takes several days to take effect on the whole device population, sorry for the temporary down time.
@resghst the hub updates are automatic. The gradual rollout is also true for Nest Hub 2nd gen updates, but please note that only those specific devices of users enrolled in Matter Public Preview will be affected before launch.
@FutronicsMP could you tell me how to update Nest Hub 2 to version 1.56.324896. Because my Nest Hub 2 version still stays on 1.56.309385.
@resghst In Google Home App choose Nest Hub 2 and choose automatic updates. I also checked the testing update program (In English it might be named differently - I'm trying to translate what I see in Google Home App in polish)
@FutronicsMP, @benjaminnestler the rollout should have reached 100%. Please try again the commissioning-control on your setups. Thanks!
@rochaferraz Thank you for the information, I will do some tests and let you know. So far I tested nRF 2.2.0 SDK with Apple Home pod mini and everything working perfectly fine :)
@FutronicsMP, @benjaminnestler the rollout should have reached 100%. Please try again the commissioning-control on your setups. Thanks!
hi. I also have Google Nest Hub Gen2 and switched development program (testing update program) ON. But it's still on 1.56.309385 chromecast firmware version (47.9.4.447810048 software version).
Is there anything wrong I'm doing?
@AlexeyYukhin I think we have to wait until the update reached our devices :-(
So, now it works for me. Here's what I've done:
I don't know if every step is really needed, but it's doing the job.
[Edit]
My Matter device is a nRF52840DK with the light_bulb
sample, using nRF Connect v2.1.2
It also works with jakubdybczak/esp32-arduino-matter 0.0.1-alpha.1
@FutronicsMP, @benjaminnestler the rollout should have reached 100%. Please try again the commissioning-control on your setups. Thanks!
I've been waiting for 5 or 6 days for the preview update but my Nest 2 still shows firmware 1.56.309385 :(
I tried to factory reset and reboot the device several times and nothing.
I can provision a Matter device but will still appear offline. I'm using nRF 2.1.2.
Is there something else I need to do besides enrolling in the Preview Program for the Nest 2 to be updated to 1.56.32? I'm baffled.
Thanks,
at
The upgrade 1.56.32 hit today before dawn and now it works without having to register the Matter Integration in the Google Developper Console.
Hi @alfonsotames, same behavior for me and my Google Nest Hub. The firmware update was received in the night. Now the Chromecast firmware version shows 1.56.324896 and my devices (Light bulb example on nrf5340DK and a custom thermostat based on nrf52840 dongle) are shown as online devices and the control of these devices works.
@FutronicsMP, I think we can close this issue ;-) It seems to be solved.
The device still show offline in my environment, but work fine in the Apple Home app. Is there any suggestions?
Nest Hub 2 software version is: 47.9.4.447810048 Chromecast firmware version: 1.56.324896 Google Home App Versoin: 2.60.1.22 Nordic Light Example from SDK 2.1.2 Nordic 52840DK Board
For me it has worked for a few days after the Nest Hub 2 update to 1.56.324896. But after removing the Matter device and recommissioning it the problem is back. Commissioning works fine but the device is shown offline and cannot be controlled using the Google Home App or the Nest Hub. Controlling it via an iPhone and Homepod works without problems and I am also able to control it using the google sample app for matter (https://github.com/google-home/sample-app-for-matter-android).
Try rebooting your devices. I also have encountered strange behavior when removing and adding devices again. They appear offline but after some reboots and waiting they appear again online.
I'm using nrf 2.1.2 and nest 2nd gen on preview 1.56.324896.
all the best,
at
On Fri, Dec 9, 2022 at 4:31 AM Bert @.***> wrote:
For me it has worked for a few days after the Nest Hub 2 update to 1.56.324896. But after removing the Matter device and recommissioning it the problem is back. Commissioning works fine but the device is shown offline and cannot be controlled using the Google Home App or the Nest Hub. Controlling it via an iPhone and Homepod works without problems and I am also able to control it using the google sample app for matter ( https://github.com/google-home/sample-app-for-matter-android).
— Reply to this email directly, view it on GitHub https://github.com/project-chip/connectedhomeip/issues/23761#issuecomment-1344130573, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAK75QXBDFEFMF64C2RG2ULWMMDAFANCNFSM6AAAAAASLI256A . You are receiving this because you were mentioned.Message ID: @.***>
hi
After Google Nest hub 2th generation new firmware release on 12/13, Nethub 2th firmware was updated. (https://support.google.com/googlenest/answer/7365257?hl=en#zippy=%2Ccurrent-preview-program-firmware-version)
And I checked the release notes on 12/15 and configured the environment for the Matter 1.0 test. (https://developers.home.google.com/matter/release-notes)
But it doesn't pair with the thread module. My thread module is a Light bulb sample model. Prior to the Matter 1.0 update, it paired normally.
Issue step
1-1 Thread module Power on (nordic nrf52840 <- Supports Matter 1.0 (use to sdk 2.2.0) 1-2 Enter Google Home (Nest hub 2th registered) 1-3 add and manage 1-4 Set up devcie 1-5 New device 1-6 found matter device 1-7 Scan Matter QR code 1-8 Connecting device to google home.. 1-9 pairing failed
The above issue is 100% reproducible.
My Developer Console https://drive.google.com/file/d/1njXeuUD9bBvl7k8SI6NhQSHJsPNH9H4z/view?usp=sharing
reproduce video https://drive.google.com/file/d/1TRbETcwY6YJobEYTo2NUoVxXFOSL9_ca/view?usp=sharing
Google Nest hub 2th fw version https://drive.google.com/file/d/1YNPXQSOzReG6HJFs2ZRZV0O943MyQVhk/view?usp=sharing
issue log https://drive.google.com/file/d/1sX0YCvFKEOkW_n-Tl7-wImFNqq0gTxwF/view?usp=share_link
Please advise on this matter.
@cw-20021349 I checked the phone app logs you've shared. This is a known regression from Google side in their latest update. We have already reported it to them. I will post when there is a fix available.
@dhrishi
According to the community's answer above, there are multiple projects in the Google Developer Console? is said to occur.
I actually tested by deleting all the projects and recreating just one project, but it still doesn't pair.
Do you think the project issues in the developer console are correct?
@cw-20021349 The issue has been fixed now. We can get the commissioning using Google Home functional
@dhrishi hi Commissioning was successful last Friday. thank you
Is it me or it's again broken?
Is it me or it's again broken?
I have had a similar problem. I was using the default ProductID(0xfff1) and VendorID(0x8005) for my nRF52840 device. I had a different vendorid(0xfff4) and productid(0xBEEF) on DeveloperConsole
I was unable to commission my device after removing it.
After I added the correct productid and vendorid to the developerconsole I was able to add my devices again.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This stale issue has been automatically closed. Thank you for your contributions.
Reproduction steps
Nest Hub 2 software version is: 47.9.4.447810048
Chromecast firmware version: 1.56.324896
Google Home App Versoin: 2.60.1.22
Nordic Light Example from SDK 2.1.2
Silicon Labs BRD2601B with Matter 1.0 Light example.
After commissioning my device is seen in Google Home App but I cannot control them as device is seen offline (not active in similar way like not powered up). Device is 30cm away from Border Router. Both Phone and Nest Hub 2 are on the same WiFi network. Phone and Nest Hub 2 are using the same google account (e-mail).
I configured aswell google project as described here: https://developers.home.google.com/matter/project/create
and configured matter integration: LigtBulb Light 0xfff1 0x8005
Does anybody have similar Issue? What might be wrong?
Problem exists for both Nordic and Silicon Labs Matter Light Examples. Enclosed please find log file from Matter Device.
Bug prevalence
Every time after successful commissioning
GitHub hash of the SDK that was being used
Nordik SDK 2.1.2 supporting Matter 1.0
Platform
efr32
Platform Version(s)
1.0
Type
Test Improvement
Anything else?
log matter (1).txt