No cheap as in not expensive. They work well 
Great. That is what I'm going for! Super simple design that can be easily used by anybody.
RE that desk stand: it's a pity that they didn't sink the display into the stand instead of putting it on top of it!
That would look a whole lot better IMHO...
what depth?
I imagine that yours has a rear relay anyway... because without a relay I don't think it's possible to fix it.
Maybe this is better:
it's cheaper to buy a 3D printer....
I intend to buy a Bambulab A1 Mini perfect for these purposes and it seems easy to use... I think it is now mandatory for these projects
I dont want to preasure you but any idea when public testing will start 
Hi! I hope to see it soon, but not before July. The project is 85% complete. The project has undergone several changes, both in terms of tools and concept. The project is also being written for four devices at once, and more will be added in the future! Unfortunately, or fortunately, despite the similarities, each device has its own characteristics and limitations. For example, one device has rectangular pixels, which makes it difficult to draw full circles... But overall, the process is moving forward, and issues are being addressed. Landscape and portrait versions will be available for rectangular displays. On the main page, you can choose from various widgets and arrange them in a convenient order. There will also be a dashboard page where you can place widgets (mini-cards) of all the Home Assistant entities you need. Cards can be moved directly on the device, but assigning entities to cards is currently done through the web server (because it's more convenient that way). Mini-cards will be accompanied by beautiful extended cards for some domains (light, climate, media_player, vacuum, etc.). All entities can be replaced dynamically, meaning without changing the code or recompiling. Once you've installed it, you can customize it as you wish. Multilingual support, theme changes, and much more are available. The functionality will be improved and refined after the beta, with new cards, widgets, and other features added.
Hello All.
Special shout out to the developers of this amazing piece of code.
I'm a real newbie to all this. Seems a lot of people are, but I think I've bitten off a bit more than my skillset. Please be kind to me...
I've managed to set up my display and it runs, but doesn't really do much in my situation. I don't have HAVAC, Alarms Curtain etc. The time and weather are good, but I want more. Don't we all?
I have spent many hours trying to add / modify so I can display some Home Assistant entities with live status. I have tried to modify the Light Controls slots 1 and 2. I got it to display the entities for me, but a would really like to have LED instead of light bulbs. Also have to LED colors change to RED and GREEN when they register as ON.
I am very willing to research and learn, but have exhausted what information I can find. My little brain is overwhelmed.
Any assistance will be greatly appreciated. As I said, I am willing to learn, so don't just post some code that I can cut and paste. I'm ready to expand on what I have read so far.
Once again, many thanks and I look forward to any and all replies.
You can use the SDL+Host platform to simulate your display in a computer, it will be a lot easier and faster to visualize you changes on computer instead. Also i recommend joining on ESPHome discord, lots of information about lvgl there.
Hello Darryl,
This topic is about a device, not a specific code. Which one are you using? The one from "agillis" on GitHub is quite intuitive.
This is my screen - the actual individual screens are reactive, so when, for example the turntable is on, the Now Playing screen auto selects and shows the album and track playing on the record player
There is also a screen for the logburner that tells you when to add more wood etc. but obviously that's not in use at this time of year!
You can lock the car and fire up the water heater as well by touching the required icons, which will react and change colour (red unlocked, green locked after car sends response).
Hereās a beta version of my project, though itās only for P4 displays for now. A version for the GUITION ESP32-4848S040 will be released a bit later. Itās still in development, and it has its own challenges and peculiarities: DarkForge UI
Iām testing it and it seems really very interesting. There are many aspects that could be improved. I think itās very functional but I would improve and add two things:
- the display should go into standby by itself
- the font and the writing are really too small (I would prefer larger controls and buttons or at least the ability to resize them. I would like to have other members of the family use it too but they canāt read it)
- On the thermostat page itās not clear where to go back to the homepageā¦ I understand it but itās not very direct
- The project is very customizable in many aspects, but less so in others. The interface is very beautiful and functional for people who are familiar with these thingsā¦ an effort should be made to make the interface easier to use for other people tonuse as well.
What I like:
- ease of installation and configuration.
Hi! Thanks for your feedback
the display should go into standby by itself
What do you mean by this and isnāt that how it works now?
the font and the writing are really too small (I would prefer larger controls and buttons or at least the ability to resize them. I would like to have other members of the family use it too but they canāt read it)
Fonts are easier to see on larger displays. If weāre talking about the Waveshare 86 panel 4-inch device, this matrix has a fairly high DPI, and it would be a shame not to take advantage of it. Dynamic font changes for embedded devices arenāt the best idea. But in some places, like the thermostat, the status bar can be set to a larger font. Thereās a tradeoff here, though, in terms of enlarging the buttons and so onā¦ While you might get better readability, youāll have to compromise on functionality. For those with very poor eyesight, the best option would probably be to simply use larger models, such as 7 or 10 inches.
On the thermostat page itās not clear where to go back to the homepageā¦ I understand it but itās not very direct
How swipes work is described in the Q&A section of the website. Swipes are a standard feature on touchscreens, and after a day of use, you quickly get used to them.
The project is very customizable in many aspects, but less so in others. The interface is very beautiful and functional for people who are familiar with these thingsā¦ an effort should be made to make the interface easier to use for other people tonuse as well.
What specific aspects of usability for uninitiated users are we talking about?
The display stays on all the timeā¦ I have to press the power off symbol to turn it off.
It doesnāt go into standby by itself
It goes over, this is set in the settings
Sorry, I havenāt seen them and theyāre not where the Q&A is. However, I can only get back the link by swiping down from top to bottom on the left side of the screen.
Found the settingā¦ thanks.
In any case, Italian is not available on the display.
Hi everyone! Good news: the new firmware for the S3 version will be free and in a week or two will be available to everyone for beta testing. Why is it free for S3 but not for P4? It all comes down to device resources, primarily the small PSRAM: 8 MB versus 32 MB on P4. Plus other differences ā RGB565 instead of RGB888, and so on.
Because of these limitations, itās not possible to implement everything thatās on P4. The S3 version will have reduced graphics in extended cards, no camera video output, and possibly even no media player cover art (still not certain). There will be no voice assistant, and a few other things may be missing. The web server will remain the same as on P4, and the drag-and-drop mode will also be preserved.
Now about memory, to make it clear why we have to cut features. To keep the interface from turning into a slideshow, on S3 we hold three display framebuffers of 480Ć480 in RGB565 format (16 bits per pixel) in PSRAM ā thatās roughly 1.35 MB. LVGL uses two additional line buffers on top of that. But the main memory hog is the need to copy fonts, arrays, and so on from Flash to PSRAM, otherwise everything will lag. That alone takes about 3 MB. Add weather icons, task stacks (which we are forced to place in PSRAM), fat buffers for the web server, Home Assistant, logs, and more ā and almost nothing is left out of 8 MB. Thatās exactly why I still canāt get even cover art running properly on S3 ā weāve hit the memory wall.
Nevertheless, for a device of this class and its cost, it will still be a very decent option. And for those who want more, thereās the paid firmware for P4.
