[问答]

chip-tool pairing ble-wifi给matter设备配网异常的原因？

问答对人有帮助，内容完整，我也想知道答案 0 在使用chip-tool pairing ble-wifi 0x7283 SSID PASSCODE 20202021 3840给matter 设备配网的时候，出现如下错误，wifi名字和密码已经设置到matter设备的，看着是后面还有些配置没有成功 [1688103497.794157][22124:22126] CHIP:DL: HandlePlatformSpecificBLEEvent 16387 [1688103498.919658][22124:22126] CHIP:DIS: Checking node lookup status after 45001 ms [1688103498.919684][22124:22126] CHIP:DIS: OperationalSessionSetup[1:0000000000007283]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout [1688103498.919689][22124:22126] CHIP:CTL: Device connection failed. Error src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout [1688103498.919700][22124:22126] CHIP:CTL: Error on commissioning step 'FindOperational': 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout' [1688103498.919704][22124:22126] CHIP:CTL: Failed to perform commissioning step 20 [1688103498.919708][22124:22126] CHIP:CTL: Going from commissioning step 'FindOperational' with lastErr = 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout' -> 'Cleanup' [1688103498.919715][22124:22126] CHIP:CTL: Performing next commissioning step 'Cleanup' with completion status = 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout' [1688103498.919719][22124:22126] CHIP:CTL: Successfully finished commissioning step 'Cleanup' [1688103498.919726][22124:22126] CHIP:TOO: Device commissioning Failure: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout [1688103498.920293][22124:22124] CHIP:CTL: Shutting down the commissioner [1688103498.920318][22124:22124] CHIP:CTL: Stopping commissioning discovery over DNS-SD [1688103498.920340][22124:22124] CHIP:DIS: Closing all BLE connections [1688103498.920346][22124:22124] CHIP:IN: Clearing BLE pending packets. [1688103498.921023][22124:22124] CHIP:BLE: Auto-closing end point's BLE connection. [1688103498.921031][22124:22124] CHIP:DL: Closing BLE GATT connection (con 0x7effac0ec930) [1688103498.921135][22124:22125] CHIP:DL: BluezDisconnect peer=D2:87:93:87:CD:A7 [1688103501.596697][22124:22124] CHIP:IN: SecureSession[0x7effa40dd600]: MarkForEviction Type:1 LSID:38471 [1688103501.596760][22124:22124] CHIP:SC: SecureSession[0x7effa40dd600]: Moving from state 'kActive' --> 'kPendingEviction' [1688103501.596805][22124:22124] CHIP:IN: SecureSession[0x7effa40dd600]: Released - Type:1 LSID:38471 [1688103501.596822][22124:22124] CHIP:CTL: Shutting down the controller [1688103501.596833][22124:22124] CHIP:IN: Expiring all sessions for fabric 0x1!! [1688103501.596841][22124:22124] CHIP:FP: Forgetting fabric 0x1 [1688103501.596909][22124:22124] CHIP:TS: Pending Last Known Good Time: 2023-06-21T21:51:50 [1688103501.596990][22124:22124] CHIP:TS: Previous Last Known Good Time: 2023-06-21T21:51:50 [1688103501.597044][22124:22124] CHIP:TS: Reverted Last Known Good Time to previous value [1688103501.597074][22124:22124] CHIP:CTL: Shutting down the commissioner [1688103501.597082][22124:22124] CHIP:CTL: Stopping commissioning discovery over DNS-SD [1688103501.597091][22124:22124] CHIP:CTL: Shutting down the controller [1688103501.597097][22124:22124] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack [1688103501.597174][22124:22124] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet [1688103501.597393][22124:22124] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented. [1688103501.597422][22124:22124] CHIP:FP: Shutting down FabricTable [1688103501.597427][22124:22124] CHIP:TS: Pending Last Known Good Time: 2023-06-21T21:51:50 [1688103501.597446][22124:22124] CHIP:TS: Previous Last Known Good Time: 2023-06-21T21:51:50 [1688103501.597449][22124:22124] CHIP:TS: Reverted Last Known Good Time to previous value [1688103501.597578][22124:22124] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-m3hrN6) [1688103501.597881][22124:22124] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini) [1688103501.597910][22124:22124] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0) [1688103501.597945][22124:22124] CHIP:DL: Inet Layer shutdown [1688103501.597950][22124:22124] CHIP:DL: BLE shutdown [1688103501.609307][22124:22124] CHIP:DL: System Layer shutdown [1688103501.610224][22124:22124] CHIP:TOO: Run command failure: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:114: CHIP Error 0x00000032: Timeout 0 本主题由 Harmony威廉希尔官方网站专家于 2024-6-27 16:28 审核通过
2024-6-27 07:45:20　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × wang21cj 该类别下有 38 个回答。邀请回答 hgimtk 该类别下有 38 个回答。邀请回答新星之火12138 该类别下有 33 个回答。邀请回答 zyh34997 该类别下有 32 个回答。邀请回答就好国dd 该类别下有 32 个回答。邀请回答 chm5 该类别下有 32 个回答。邀请回答 zaichenxi 该类别下有 31 个回答。邀请回答 heks 该类别下有 31 个回答。邀请回答 flowerddd 该类别下有 29 个回答。邀请回答 muwersddg 该类别下有 29 个回答。邀请回答四川赵赵该类别下有 29 个回答。邀请回答星星公交站该类别下有 28 个回答。邀请回答 vinww特烦恼该类别下有 28 个回答。邀请回答 caosurround 该类别下有 28 个回答。邀请回答 gvjhvbc 该类别下有 27 个回答。邀请回答安德森大该类别下有 27 个回答。邀请回答 xwgc888 该类别下有 27 个回答。邀请回答 lkjflksjfsa 该类别下有 27 个回答。邀请回答 h1654155143.8331 该类别下有 27 个回答。邀请回答 723662364d 该类别下有 27 个回答。邀请回答举报张敏相关推荐 • 请问一下ESP32 wifi配网多频合一找不到设备是何原因？ 282 • BLE Mesh的node如何暂时退出配网状态？ 255 • 请问ESP32-WROVER-B用作BLE4.2 + Station + SoftAP这种工作模式是否可以共存? 222 • esp-matter light示例配对过程中出错的原因？ 150 • ESP32-C3是否支持matter协议？可以通过softap方式配网吗？ 301 • 在使用智能配网时如果输入WiFi的密码是错的，为什么会反复尝试连接WiFi？ 459 • wifi模块配网问题 1763 • 请问ESP32-C3是否支持matter协议了？可以通过softap方式配网吗？ 276 • 请问ESP32-C3是否支持matter协议了？可以通过softap方式配网吗？ 250 • ESP8266配网失败如何返回消息给APP？ 219 1个回答

答案对人有帮助，有参考价值 0 在这种情况下，我们需要逐步分析可能导致配网异常的原因。以下是一些可能的原因和相应的解决方案： 1. 设备兼容性问题：确保你的matter设备和chip-tool都支持BLE-WiFi配网。如果设备或工具不支持，可能导致配网失败。 2. SSID和密码格式问题：检查SSID和密码是否符合要求。例如，SSID不能包含特殊字符，密码长度和复杂性也需要满足要求。 3. 配网命令格式问题：确保你使用的配网命令格式正确。根据你提供的信息，命令格式应该是：`chip-tool pairing ble-wifi < discriminator>`。请检查命令中的参数是否正确。 4. 设备距离问题：确保你的matter设备和chip-tool之间的距离足够近，以便BLE信号可以正常传输。 5. 设备电源问题：检查matter设备是否有足够的电量进行配网操作。 6. 网络环境问题：确保你的WiFi网络环境稳定，没有其他干扰因素。 7. Matter设备固件问题：检查matter设备的固件是否为最新版本，如果不是，请更新固件。 8. chip-tool版本问题：确保你使用的chip-tool是最新版本，如果不是，请更新到最新版本。 9. 日志信息分析：根据你提供的日志信息，可以看到"operational discovery failed"，这可能意味着在配网过程中，设备之间的通信出现了问题。需要进一步检查设备之间的通信是否正常。 10. 尝试重新配网：如果以上步骤都无法解决问题，可以尝试重新执行配网操作，有时候问题可能是暂时性的。通过以上步骤，你可以逐步排查并解决配网异常的问题。如果问题仍然存在，建议联系设备制造商或chip-tool的开发者寻求威廉希尔官方网站支持。

2024-6-27 17:04:13 评论举报 h1654155272.9717