Pierre Ståhl
Pierre Ståhl
Wow, this is interesting. I have no idea what is going on. One more test that is interesting now though is if the initial pairing guid works when passing it...
Does it change again if you, let's say restart the device? Maybe they are doing MAC address randomization now?
I can see similar issues, but not quite the same. The MAC address as reported by scan (which is collected from the various zeroconf services) seems to match old behavior....
It's interesting that change of MAC address causes so much problem as there are other identifiers as well. Can you check if all of them change when the MAC changes?
> Is there way to retrieve the serial number? That's something Apple most likely won't randomize due to warranty claims. Maybe with some protocol, but that would require a connection...
deviceId is the same as MAC address i believe that is what i use today) and i have never seen serialNumber in the context of AirPlay, so i suspect that...
I tried to go down the ARP cache road a long time ago (with getmac as an example) and I concluded that it's not a viable way. It's hard to...
We should never expose any raw values from the protocol, but rather come up with a stable API. I assume most of the "now playing" data should be exposed via...
We have a basic implementation for NSKeyedArchiver here: https://github.com/postlund/pyatv/blob/master/pyatv/protocols/companion/keyed_archiver.py It was implemented for keyboard support, but might be useful here too?
`home_hold` and shall not be used and will be replaced by passing a hold delay to `home` instead, one this PR is merged: https://github.com/home-assistant/core/pull/105764