Sebastian

:tada: This issue has been resolved in version 9.0.0-develop.1 :tada: The release is available on: - [npm package (@next dist-tag)](https://www.npmjs.com/package/@sebbo2002/node-pyatv/v/9.0.0-develop.1) - [GitHub release](https://github.com/sebbo2002/node-pyatv/releases/tag/v9.0.0-develop.1) - `v9.0.0-develop.1` Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

:tada: This issue has been resolved in version 9.0.0 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/@sebbo2002/node-pyatv/v/9.0.0) - [GitHub release](https://github.com/sebbo2002/node-pyatv/releases/tag/v9.0.0) - `v9.0.0` Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Sounds absolutely feasible, implementing `InputAction` would probably make more sense. Unfortunately I have a lot to do at the moment, but if it's not urgent I would take care of...

I had a quick look at the whole thing. Currently `InputAction` does not seem to be available for `atvscript` (which is used by this library for most key actions), also...

No, manual pairing is required. Can you provide a full example with your code and output? Please also set `debug: true` for proper logging.

You get the error because your device doesn’t support the up button. That has nothing to do with the pairing status for now. For example, use getState instead of up...

I'm not aware of any indicator in atvscript. But please let me know if you find out how to check it wirh atvscript, so I can add it here as...

Of course, it would be theoretically possible, but there are some open questions, which is why this feature is currently not implemented: - Currently, fetching artwork only works via `atvremote`,...

This library just uses `atvscript`, which uses the deprecated method internally (by running `atvscript -s 192.168.255.62 volume_down` in your case). I also checked the docs and this call seems to...

Hey, sorry for the late reply. What attributes are you talking about specifically? What are you missing? I would like to avoid adding generic attributes, as this can very quickly...