Hey Tim,
let me dig into your post and reply one item at a time.
To be honest we haven’t thought about multiple HestiaPis boot at the same time for the first time. What happened is that you got 2 networks with the same SSID (HESTIAPI) and you couldn’t tell which was which. Of course one solution would be to power up one at a time. The other solution, and probably what you did, was to setup blindly whichever you connected to and see which restarts. Once they are connected to your actual home network they will get unique IPs which will also be displayed on the loading screen to help you identify.
We are changing the case design to minimise these situations. It needs indeed some extra care to align everything.
You are absolutely right. Well spotted. Replacing the download with a new image. Thank you!
Hmmm… never seen this. There may be a bug on Chromium. Try this suggested solution
rm -rf ~/.config/chromium/Singleton*
The switches change the item “TempSetpoint”. Then rules are used to control when to turn the heating on and off to reach these setpoints. So if you renamed the setpoints for each HestiaPi you will need to apply the same change in the rules file.
The setpoint entry in the sitemap file (/etc/openhab2/sitemaps/default.sitemap) is this:
Setpoint item=TempSetpoint minValue=0 maxValue=40 step=0.5 icon="temperature"
The “step” parameter shows the increment step. You then need to keep the bidirectional MQTT (read and write) for the item and it should work.
See the HABPanel section of my answer below and follow steps 1-8.
Then click the edit icon at the top, next to the title and you are in edit mode where you can move, remove and resize everything. I think HestiaPi’s screen only changes on reboot so once your screen looks ok on your laptop, reboot HestiaPi for the changes to take effect. Please keep in mind that you laptop’s resolution and aspect ratio may be different from the LCD so make sure you compensate accordingly.
Well done!!!