Liborsaf

I don't know yet, where to make a tag? 😅

Same issue (firmware 5.1.2), tried removing and then adding back, still nothing. Debug log seems to show no error at all (file attached). [home-assistant_prusalink_2024-01-15T18-04-13.185Z.log](https://github.com/home-assistant/core/files/13941850/home-assistant_prusalink_2024-01-15T18-04-13.185Z.log)

> 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...

I found out if I manually enable these entities, they starts to work. 🤔 But still don't know, why they are disabled by default 😅 [image](https://nextcloud.liborsafar.cz/s/Qb9Wx4FbtNbi6jr/preview)

> 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. > >...

> 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...

I would also appreciate this 😄

https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/bfb0ffc745ee6546e7efdba618d0e7c0f4c909cd/src/lang/po/cs/Prusa-Firmware-Buddy_cs.po#L2027 https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/bfb0ffc745ee6546e7efdba618d0e7c0f4c909cd/src/lang/po/cs/Prusa-Firmware-Buddy_cs.po#L5063

I would guess that those widths are just too short, but i cannot test that https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/bfb0ffc745ee6546e7efdba618d0e7c0f4c909cd/src/gui/wizard/selftest_frame_hot_end_sock.cpp#L24 https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/bfb0ffc745ee6546e7efdba618d0e7c0f4c909cd/src/gui/dialogs/DialogMoveZ.hpp#L47