Debian 12 (bookworm) image testing (v1.5-dev)

Didn’t manage to review and merge the UI-repo updates on time. They are only optimisations and improvements in the background and not actual UI changes but it may would have helped in taking off some load or the responsiveness of the screen.

Keep it in mind to include this UI copy on next image @hestia_hacker

Testing the v1.5-dev release next…

Here are my comments:

Crowdfunding model was used for all below tests.

  1. Flashed SD, booted, left it unattended for ~1hr - HESTIAPI SSID could not be found. Rebooted by pressing the button. HESTIAPI SSID could not be found at least while the provisioning screen was shown. Reflashed same SD, retried, worked fine straight away. Some short of racing condition?
  2. Touchscreen, same as before, has coordinates/scaling mixed up making it impossible to reach any button
  3. WiFi disconnections. Leaving HestiaPi running overnight ended up being offline in the morning. I will leave a ping running in the background to 1.1.1.1 and see if this changes anything
  4. HVAC: testing thoroughly all functions showed no issues
  5. EU: Hot water and Humidity control (dehumidify mode) relays could not be activated with ON or Boost (while Heating works fine)
    2026-03-03 06:59:08.049 [INFO ] [.eclipse.smarthome.model.script.mode] - Humidity mode changed from OFF to ON
    2026-03-03 06:59:08.069 [INFO ] [.eclipse.smarthome.model.script.mode] - HumidityPrevMode changing from OFF to ON
    2026-03-03 06:59:08.836 [INFO ] [ipse.smarthome.model.script.humidity] - Turning ON the Dehumidify: curr humidity = 50.0 setpoint = 43 mode = ON
    2026-03-03 06:59:09.353 [INFO ] [.eclipse.smarthome.model.script.pins] - Commanding Pin18 to ON for HumidityPin

    2026-03-03 07:00:10.266 [INFO ] [.eclipse.smarthome.model.script.mode] - HotWater mode changed from OFF to ON
    2026-03-03 07:00:10.342 [INFO ] [.eclipse.smarthome.model.script.mode] - HotWaterPrevMode changing from OFF to ON
    2026-03-03 07:00:10.706 [INFO ] [ipse.smarthome.model.script.hotwater] - Turning ON the hot water: mode = ON
    2026-03-03 07:00:11.372 [INFO ] [.eclipse.smarthome.model.script.pins] - Commanding Pin12 to ON for HotWaterPin

Thank you for testing.

  1. I’m unable to reproduce this behavior. Do you have any logs that might help us track this down?
  2. Does the screen work with any Debian 12 image? Have you tested with any other screens of the same make and model? If you replace the screen, do the issues go away? I can’t reproduce this with any of the screens I have, so I’m not really sure how to resolve this one. (e.g. recommend some people shouldn’t get upgrade, or tell them they can replace their screen if they have issues)
  3. I can’t reproduce this issue. If you have any logs that would help us track this down, I can try to help troubleshoot.
  4. Yay. Me too.
  5. I reproduced this issue and fixed it. It was part of the Linux kernel’s move away from using sysfs to control GPIO pins. I updated the Humidity and Hot Water rules to compensate for that.

Updated image with the fix for Humidity & Hot Water: