GUITION 4" 480x480 ESP32-S3-4848S040 Smart Display with LVGL

Take a look where it is now in the ‘more buttons’ file. It goes there!

So it’s very odd.

I have managed to add another button that pulls the state of a light perfectly well.
But when I press the button nothing happens.

kroonen could you share code on github

I wonder…does anyone of you guys have any problem with random screen wake-ups here? I currently have openhasp on my lcd (it’s easier to learn), but these wake-ups are a problem there, so before i dig into esphome and lvgl i’d like to know if i’ll hit the same problem here?

I remember a thread, perhaps on openhasp GitHub about a similar problem. I honestly can’t remember how or if it was resolved. Perhaps try the main openhasp thread.

Yes, i found that thread, they are trying to solve it with some kind of noise filtering - i’m trying that custom fw right now, too, but results are mixed - some guys doesn’t have any problems, some still do…

That’t why i’m considering to “take a bite” and switch to esphome, but only if lcd runs perfectly here. I don’t want to learn lvgl from scratch only to see that i have the same problem (if you know what i mean). I didn’t find any complaints regarding this phenomenon for esphome, that’s why i ask you guys who already use it…

I guess that here the difference between 70€ nspanel and 30€ lvgl display is clearly seen…

I’ve seen some wake-ups which I was surprised of, but haven’t paid attention to it that much, because I’m still just discovering this screens and lvgl. I remember I saw one screen waking up when I programmed another one laying next to it. Will keep an eye on it and respond when getting more information.

1 Like

Thanks. Please also observe if any buttons were triggered/pressed when screen wakes up if you can. Experiences of other guys show that usually button top - left or top - right is activated - in fact, that’s why screen wakes up, because controller wrongly thinks that button is pressed.

my cover closed when lcd woke up by itself :grimacing:

Sorted.

It seems there’s a switch inside ha when adding espstuff to it to allow the esp to control entities.

nice your work but is it possible to gather several pages in a single page to save space on the screen, I know if it should be said like this

Could you share your code on file?

I placed it on github

2 Likes

No, I know that an issue with openhasp but that is not an issue with esphome

Really? It only takes two lines of code to add a button and get it working in ESPHome and you don’t have to make any changes in HomeAssistant. I think esphome is easier, more reliable, and you can do a lot more with it.

Take a look at my guition-esp32-s3-4848s040-display_modular.yaml build it for your screen and see what you think!

2 Likes

Hey just a crazy idea… (I always get them while I’m working out, just had to post in case I forgot)

Anyone thought of how to do haptic feedback on a button press yet?

I have 2 of these guition devices. I have openhasp on one. I may put esp32 on the other one and test your theory.

1 Like

Yeah, well… openhasp is easier at first glance…you just write one line of code and you get a button (but non-working in HA, of course☺️).
But, as it happened back then when i was in tasmota: you quickly hit an obstacle which openhasp can’t solve…
I did have a test yaml on my lcd, but on first look it seems so complicated…a bunch of display settings, theme settings,font settings, a bunch of unknown stuff…. But now i’m sick and i’m reading a bit this esphome lvgl stuff and i see that many of those settings are “custom”… lvgl has most of basic settings already buitl-in, if i understand correctly (including basic font), right? So, for basic work i can leave out many of those…
Now i ordered a second lcd to play with, since i already installed first one on my wall, so testing will have to wait until i get one, which should be inside a week or so…
So, i think that at the end i will be ending on esphome. It’s nice to know however that it doesn’t have wake-up problems like openhasp.
Thanks for clarification!

Lvgl via Openhasp preceded lvgl on esphome by some 3 years. It supports many devices. It is pretty easy to set up.

There are pros and cons to each. It’s late here and I am not wanting to start a pissing match. I am looking forward to comparing.

1 Like

The biggest problem with openhasp is their version of LVGL is very old so it doesn’t have all the features of the ESPhome. I ran into that limitation very quickly.

As far as how easy it is to use openhasp is just an image you install so you don’t have to compile any code. But compiling code for ESPhome is very easy so I’m not sure that’s a limitation.

I guess if you have a been using openhasp for 3 year and really like it stick with it. But if your looking for a lot more functionality and devices not supported by openHASP go with ESPhome.

1 Like

I am interested in a couple of things that you touch on

  1. I guess with esphome you have to recompile to make even the slightest change to the UI, e.g. to move a button by a couple of pixels (in openhasp you can just change the pages layout and restart the panel)

  2. What are practical implications of the lvgl version improvements? I have seen this stated before, but am unable to find on a practical sense, what you can do in lvgl y what you can’t do in lvgl x?

Regarding 1 : yes, that bothers me a bit, too, from beginning of esphome use - for each even so small change re-compile and re-flash is needed. That part is quite quicker in openhasp ( just save and reload page), since i guess it stores pages into separate memory, while “pages” are part of esphome firmware. But, that’s esphome’s way, and we can’t do much about it, right?