I’ve tested with both the Pi Zero and the Zero 2.
I didn’t look at the load averages, but the UI was responsive and the relays kicked on as expected.
Is the screen calibration issue the same one you had previously? Has anyone else been able to reproduce that issue? Does it happen with a new screen of the exact same make and model, or is it just that one device that’s having calibration issues?
I did have to make some changes to the rules to accommodate the inability to control GPIO via /sys. I don’t think I removed any existing lines of code, but I supplemented the code required to turn the relays on/off on the new version of Debian. The old code won’t work on the new O/S but it’s needed if for the old, and the new code won’t do anything on the old O/Ses but is needed for the new. (Note: I didn’t try testing the new rules on the v1.4-dev image. I figured we could test that after we know the basics work in v1.5).
Here are the differences:
I manually decoded the first change and confirmed it’s just adding code that run events.sendCommand() to turn the relays on and off.
How did you trigger the heating and cooling at the same time? Were you able to adjust the setpoints so they crossed, or were you turning on the heat and then boosting the cooling, or was it something else? I’d like to try to replicate this issue. I’ll also play around with the unit I have on my bench that’s hooked up to LEDs so I can confirm when the relays are really on or off.