Open bobrik opened 1 year ago
I had the same issue with the updated HomeKit Architecture. Above steps to reproduce were representative of the issue I had.
Development Device: MacBook Pro 2020 (Intel) running CLion 2023.1.3
Testing Devices:
I had undertaken the following steps to debug:
tlv.rs
and breakpoint all invokations of the error!
macro.FileStorage
Storage engine. However, this appears to be a generic bug that likely came from the pairing process, so it should affect all storage engines.Find the data/pairings/UUID_HERE.json
and create a copy where the UUID is the one emitted in console with the error. It should begin with: [TIMESTAMP DEBUG hap::transport::http::handler::pair_verify] device pairing UUID:
Location for your debugger: ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hap-0.1.0-pre.15/src/transport/http/handler/pair_verify.rs:226
The HAP accessory is now communicating with my HomeKit setup.
Note (unverified observation): Subsequently the new file I created disappeared and it reverted back to the original UUID.
I have two accessories that stopped working either after I switched the hub from Homepod mini to Apple TV or "upgraded home" with a prompt from Home app:
If I run the lightbulb example:
It can successfully pair, but then it fails with "No Response":
Here's what I see in the logs (from macOS):
I wiped the
data
directory and the result is the same. I'm not seeingNo such file or directory
on Linux, but it doesn't work there either.