IPP integration forgets ink data

[jkufner]

trafficstars

The problem

The IPP integration shows correctly the information how much ink is remaining in the cartriges of my printer; however, when the printer is offline of several days, it forgets the data, including history. It would be really nice to see how much ink was there last time the printer was online, even if it is a week old information, so that I don't have to turn the printer on to check. The data are loaded correctly once the printer is online again, but the historical data are still missing.

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

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 Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign ipp Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[NateEaton]

I ran into this issue quite a while back and set up entities based on MQTT persistent messages to avoid the issue but that really shouldn't be necessary.

I don't know whether it is related but I came here checking for a possible explanation for why my ink sensors keep dropping out to -2 and sometimes stay that way even if the printer had been on.

[jman311]

For integrations like this that have sensors that go unavailable when the device is not reachable or offline, I suggest creating a Helper variable in HA for each sensor that you want to maintain the "last known good" value for. Then create an automation to update the value of the Helper variable to equal the value of the sensor, but only when the sensor is NOT unavailable.

I do this for each of my printer ink levels and I always have the last known value regardless of the status of the integration and related sensors.

[JackboyPlay]

Yeah, I am having the same problem. Maybe an option for the sensors to remember the last ink percentage instead of dropping to -2% would be nice.

[GSzabados]

I love the comments about how to hack around the integration to get some useful data of it, but lets be honest, HA is a HOME automation system. People do not keep printers on all the time, because they generally consume power. Even business level printers go to sleep or shut down to do not consume power. People at home do not print ever day, or every week, but it worth to have the data kept according the last seen value, without any hacky solution.

[jman311]

It would be nice if HA entities could remember last known good values across the board. This can be an issue for any device that reports "unavailable" or "unknown" when off or unreachable.

I have to use the helper "hack" I mentioned earlier for thermostats, pool/spa sensors, vehicle data, device battery levels, etc.

[raindropworks]

It would be nice if HA entities could remember last known good values across the board. This can be an issue for any device that reports "unavailable" or "unknown" when off or unreachable.

I have to use the helper "hack" I mentioned earlier for thermostats, pool/spa sensors, vehicle data, device battery levels, etc.

Absolutely +1 on this. Pulling my printer's ink tank status in was a nice surprise when I set up HA Container, but to make it relatively useless because it reads 'unavailable' 90% of the time just makes it a pain in the neck. I'd rather see a '10%' with a last update of 'two weeks ago' than an 'unknown' with a last update of 'an hour ago'

One gives me useful information, the other gives me junk on my cards.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jhemak]

Still unresolved

[TorbjornMohn]

Any chance to have this "problem" resolved?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[TorbjornMohn]

Still not working.... sad bu true :-(

[IoSonoAndreaZ]

same here

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[IoSonoAndreaZ]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

the issue is still present so there is no reason, my dear bot, to close it.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[IoSonoAndreaZ]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

the issue is still present