core: Error fetching ipp data: Invalid response from API - error log every 1 min
The problem
If printer is switched off, this keeps returning below error each minute. Printers being off should be guarded better, not spamming the log each minute My printer : Epson XP 305
What version of Home Assistant Core has the issue?
core-2021.12.10
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
IPP
Link to integration documentation on our website
https://www.home-assistant.io/integrations/ipp/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.components.ipp.coordinator
Source: helpers/update_coordinator.py:219
Integration: Internet Printing Protocol (IPP) (documentation, issues)
First occurred: January 19, 2022, 11:39:42 AM (235 occurrences)
Last logged: 11:35:15 AM
Error fetching ipp data: Invalid response from API: Timeout occurred while connecting to IPP server.
Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.
Additional information
Old issue from another user closed by robot : #43472
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 8
- Comments: 29 (7 by maintainers)
Also getting the same on a HP printer.
For context, my printer is not always switched on (as I print rarely) and in fact I use an automation for when my printer goes into ‘idle’ it turns off the power socket.
I would also love to see it handle the state better when the printer is offline. For example, instead of it showing as ‘unavailable’ it should show as ‘offline’ or something similar, like this custom component handles it https://github.com/elad-bar/ha-hpprinter. And maybe retain the last know value of the inks
same on lexmark
I am convinced that the sensor could show
Unavailable, but the toner level should be the last known, notUnavailable@ctalkington could you take a look at this issue?
the disable polling should work as we don’t change or override that however, it it’s retrying setup that could be why it’s still doing requests.
given the issues up to 2023.06 fixes, I’m closing this with the note that I do hear everyone’s feedback and desire to improve offline handling.
long term solution on my radar is to implement state restoration and not fail device setup.
This does not solve the problem, it only shows a workaround.
p.s. there is a simpler workaround: https://github.com/snarky-snark/home-assistant-variables#updating-using-tracked-entities
Is anyone maintaining this? My configuration goes unavailable as described above at least once a day. The only fix is to delete then wait for re-discovery, over and over and over again…
I was able to get this working again (somehow) by removing the integration, re-adding it, and making sure I did NOT check “Uses an SSL certificate”
yes sadly my bandwidth is limited lately and maintaining a few other integrations. likely this integration should restore its state and retain some data during connection issues but it needs a bit of reworking for such.
same here for a hp printer