Sebastian Nohn

https://github.com/home-assistant/core/pull/84366 seems to be related.

Hi @solarnz thanks. I've upgraded and keep you posted. Out of curiosity: Have you switched to a different solution or have you abandoned controlling PA with hardware devices?

Apprently downgrading to 2023.10 is possible and doesn't have unwanted side effects. How to identify whatever will be broken by upgrading to 2023.11 before upgrading to 2023.11 and what exactly...

For automations this looks like a feasible solution for those prefering yaml over the GUI: https://community.home-assistant.io/t/2023-11-to-do-add-release-title/634647/239: > Don’t use device triggers. Use State triggers.

> @Campagne8758 please could you verify, if the as "unknown device" alerted devices are really back (_with this exact id_) after the rollback? For me, the device IDs remained unchanged...

> > For me, the device IDs remained unchanged which makes sense, as 2023.11 does not change device IDs, just adds some extra checks for device IDs. > > @nohn...

For me it works fine with 2024.9.4. This obviously doesn't mean that this bug is invalid, it just means that I can't reproduce it, which is very likely caused by...

It is (was) not set. After setting it to 0, white is white. Thanks for the hint. Feedback: * It is counterintuitive to have to care about dithering at all...

According to https://github.com/OpenEPaperLink/Home_Assistant_Integration/blob/main/docs/drawcustom/supported_types.md, dither = 2 is the default:  The source confirms that: https://github.com/OpenEPaperLink/Home_Assistant_Integration/blob/main/custom_components/open_epaper_link/services.py#L27

Displays used are M2 2.9", 296x128, fw:19 0x13 if that matters.