Log says "pairing established" but any interaction throws "is no known alias"

[cablesandcoffee]

Log says "pairing established" but any interaction throws "is no known alias"

[Jc2k]

Hi, sorry it's a known problem outside of home assistant. Pairing works but the encryption keys aren't saved.

I'd love to make the cli fully functional again but short of time.

Iirc it's a result of the refactoring to add ble and thread support. That added a controller for each protocol, then a meta controller that started all 3 backends. Pairing is I think creating the record in IpController but the "save pairings" code is saving data from the meta controller. (Before there was just one controller object, so it worked fine).

There are a bunch of refactors planned, one of which would have fixed this by replacing how saving and loading pairings work. I wanted to add a PairingStorage abstraction so in HA we could read the keys directly out of HAs config abstraction, and in the CLI we just read them off disk.

Right now HA ignores the aiohomekit saving/loading. When it gets a pairing object from finish_pairing it saves the pairing record itself manually. Then it loads it back into a controller itself as well.

There is probably a temporary fix for the cli controller to have the save function iterate through all the transport controllers maybe. I think it just persists self.pairings. But needs to gather self.pairings from its children?

[cablesandcoffee]

Love the fast and interesting answer! Sounds like I'll just have to be patient and hope that you can use the client on it's own in the future. It would be a great tool for non HA-setups, I've been digging around the internet for days for something that can do what this does and was so happy when I found it. Started with the HomeKit Python which I think you were involved with as well but no luck with pairing there either. Imagine how happy I was when the log said "pairing for "device" was established". :D

Your last sentence: Don't know what you are talking about but it sounds great and super smart! :) I would use it and I would do a Youtube video about it cause people need to here about this awesome software!

But anyways, it clearly stated proceed with caution and that your focus is Home Assistant. Great work and thank you for taking the time to answer!

Oh, just realized one thing. Does this mean I could use an older version of your software where this still worked?

[Jc2k]

In theory, versions < 2 should work as the split to enable multiple backend transports hadn't happened. There might be other problems of course.

[cablesandcoffee]

Okay worth a try for now. I will check it out when I have time. Thank you!