Niklas Wagner

Hi, 1. Can you [enable and provide debug logs](https://www.home-assistant.io/docs/configuration/troubleshooting/#debug-logs-and-diagnostics) 2. Verify that you can reach the PrusaLink Web UI (Got o Settings -> Devices -> PrusaLink -> You Printer ->...

@home-assistant add-label needs-more-information

Yeah, not much to see in the debug log beside that it successfully connected to your printer. Since I don't have a MK4 (only a XL) I cannot reproduce this...

Thanks. JSON data structure is identically to my Prusa XL. So that's not the issue causing this...

Some are disabled by default, probably to avoid cluttering the UI. They are disabled by default since the very first version of this integration 2 years ago. https://github.com/home-assistant/core/blob/3ff74fe20fc725781edceeec72e983817caa27fc/homeassistant/components/prusalink/sensor.py#L70

Developer documentation states: > Indicate if the entity should be enabled or disabled when first added to the entity registry. This includes fast-changing diagnostic entities or, assumingly less commonly used...

Looks like the Prusa Link for MK3.x will get an update to the new API with the next release: https://github.com/prusa3d/Prusa-Link/commit/02e6a82146607d08c2e4689580a599712f74d364

Additionally, the digest implementation is currently broken (but a PR is open) https://github.com/home-assistant-libs/pyprusalink/issues/77

API key is considered deprecated and the HTTP Digest Auth is the way to move forward. The SL1(s) printer doesn't even have the old API key auth. On Mini/MK4/XL the...

I had the same issue when enabling Server Side apply. You need to enabled Server Side diff in argocd in order to fix this. https://argo-cd.readthedocs.io/en/stable/user-guide/diff-strategies/#server-side-diff