Toner colors unavailable after 2022.11b0

[iridris]

The problem

After installing the 2022.11 beta, the toner colors are listed as unavailable.

Printer is a Canon MF8200C Series

What version of Home Assistant Core has the issue?

2022.11.0b0

What was the last working version of Home Assistant Core?

2022.10.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

IPP

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ipp/

Diagnostics information

Integration does not provide diagnostics.

Example YAML snippet

No YAML used

Anything in the logs that might be useful for us?

No logs in home-assistant.log related to IPP.

Additional information

No response

[home-assistant[bot]]

Hey there @ctalkington, mind taking a look at this issue as it has been labeled with an integration (ipp) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ipp can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant unassign ipp Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

ipp documentation ipp source _{^{(message by IssueLinks)}}

[luisleonardo]

Same here.

[ctalkington]

I'm seeing this as well. will dig into it

[pdobrien3]

Not sure if it is relevant or helpful but no one else has mentioned it. The uptime sensor related to this integration is also having issues. It seems to reset every minute or so and sometimes every 5-10 seconds.

[ctalkington]

so I think I have narrowed this down slightly to atleast some change in response from my epson. It seems to now require me to explicitly request all the marker attributes. I'm not sure if this is firmware/spec change (recently upgraded that) or something in pyipp request serializer. timing and multiple people/devices impacted leads me to believe it has to be the pyipp update. It doesn't fail any pyipp tests because that's using mocked responses including all data but devices can behave per spec of requested or slightly off. my epson for example never used to respect requested attributes and gave back the whole kitchen sink

[ctalkington]

should have a fix soon. was issue with fixing a bug in pyipp 0.12 that then exposed not all checked attributes were not being requested properly

[pdobrien3]

0b4 fixed this on my end. Thank you.