Pierre Ståhl

I believe this is not a problem with the integration, but rather that the device is hidden (as stated by the later post by @Fatalmose). I obviously can't tell why...

I can confirm that integer data types in OPACK are signed integers. I used the method I've described here: https://pyatv.dev/documentation/protocols/#reference-decoding To decode 0x30FF, which corresponds to an integer with one...

I'm not sure where we are with this right now. Can we clean it up and merge it?

I'm not sure this is correct, I will have to verify with macOS implementation first.

Nope, you are correct 👍 ```raw postlund@Pierre ~ % echo 94010000000000000001 | xxd -r -p | ./decode 2024-08-07 19:48:34.307 decode[12510:963399] Decoded: {length = 1, bytes = 0x01} ``` Please update...

> @postlund, I took a look at the docs, and realized that the same might apply to strings and pointers as well. > > I think pointers would be hard...

> Any update? I'll merge it if you update the documentation related to your changes 👍

Ah, right. I'll see if I can do that.

So, I used my example from the documentation but added an additional element at the end to ensure the pointer is somewhere inside the payload (I added `0=1` to the...

I will merge this, we can deal with documentation later!