[SOLVED] (Example) Broken relay in my pre-assembled HestiaPi

[HestiaPi]

Hello @auch1 and welcome to the forum
That does not sound fun at all so lets dig right into it and find whats wrong:

The HTML loader is working in the following way:

1. The HTML is using one DIV to show the graphics, countdown etc and another hidden DIV that is trying to load the HABPanel URL (http://localhost:8080/habpanel/index.html#/view/HestiaPi) every x seconds.
2. Every y seconds its checking if the hidden DIV loaded the HABPanel which means that OpenHAB finally finished loading. This does take a long time in RasPi Zero indeed.
3. If this happens, it redirects to it and once this is done, you should see that on the LCD

We have seen sometimes this to take even longer for the first time, causing Chromium to freeze, so we increased the x and y times. Your 222 sounds like an old value. Can you please update openhabloader.blank.html (very important!), openhabloader.html and openhabloader.sh and try again? This should at least solve the problem that the UI is not loaded at the end of the loading script.

@auch1

the HABPanel portion of the GUI does not work in my browser, but actually I don’t really know if that should be the case or if I am holding it wrong.

What you are missing is that HABPanel by default is looking at your browser cookies to see what it should load and your computer’s browser knows nothing. RasPi’s browser loading the LCD UI knows more
In order to load on your computer the same UI, even though it is not supposed to be used outside the LCD, follow these steps:

1. Visit http://[RasPi_IP]:8080
2. Click on HABPANEL
3. Click on the burger menu (the three dashes) on the top left corner
4. Click on the gear icon bottom left next to the clock
5. Select “Panel configuration: Server Storage”
6. Press OK on the popup
7. Click on the burger menu again on the top left corner
8. Choose HESTIAPI

@auch1

i’ve tried to kill them all and restart chromium via the icon on the lxde desktop, but am not quite able to do that. maybe my smartphone-multitouch-spoiled fingers are just not made for this kind of display

The resistive LCDs are generally less fancy than our SmartPhones’ We have tested in the past capacitive touchscreens which rock indeed but come in much larger sizes and almost double the total cost of BOM so we left it there.
Right now there is even another extra issue with a misscalibration that we haven’t shorted. Your actual pressing point is about 4-5mm further from the point you actually touch in the direction towards the centre of the screen, making small icons at the edges of the screen hard to select, but the way the UI is designed should not cause any trouble with this issue as the buttons are big enough to compensate on the misscalibration until we fix it. You found first Use the cap of a pen or anything pointy but not sharp to double tap on the Chromium icon on the desktop.

@auch1

from ~/scripts/openhabloader.sh I get how to intentionally start chromium … aaand the touch-input i guess. okay. so far so good. but that I should have been doing from the right display … because trying to start it via ssh fails with:

Try that:

DISPLAY=:0.0 sudo -u pi /usr/bin/chromium-browser --disable-restore-session-state --disable-web-security --user-data-dir --noerordialogs --disable-session-crashed-bubble --disable-infobars --kiosk /home/pi/scripts/openhabloader.html &

@auch1

I managed to check the working relay with my multimeter, and that confirmes that the “hot water” one works. “heating” does nothing.

Can you check the voltage on the “good” relay while it is activated and while it deactivated and compare it to the “bad” relay while it is supposed to be activated and while it is supposed to be deactivated.