I've updated the antiburn algorithm by writing randomized pixels as a test in v0.6.3-dev.

So 30 minutes for antiburning seems a good start - even with static color.
If you tun off screen backlight for the night, you could write an automation to clear the screen (display full screen obj on page 0) with a static color for while the background is off, to test.

See last example from this page:
https://www.openhasp.com/0.6/integrations/home-assistant/sampl_autom/#keep-backlight-on-dimmed-during-the-day-and-turn-it-off-during-the-night

Ive now had the device on my desk for a few weeks on, and using the burn in at midnight + turning off backlight when not in use has been fine. No permanent damage yet.

Do you notice any artifacts during the day when using the screen?

Do you have any ghosting issues with the display? Can you share your use experience with this device?

Just tried last night with no screen off for 6+hrs and did not see any ghosting issues mentioned.

@gheesung What color do you have as a background in your pages?

@gheesung What color do you have as a background in your pages?

Black background

@fvanroie Please check your email, Ive taken a few but due to size they are to big to attach here, Ive sent them directly to you.

Thanks! I've updated the gallery. Are you running v0.6.3 on it?

@fvanroie Not the latest, Im running an old 0.6.3 on it. Ill give the latest build a try soon.

I'm a little bit confused about the Wireless-Tag WT32 S3 86 boxes on Ali. They all look the same on picture. Some of them have temperature and humidity, some don't. I won't need it I think because it is not supported yet by OpenHASP. One if found here says it is "update 4" which also includes a speaker/mic chip : https://nl.aliexpress.com/item/1005005529368011.html?spm=a2g0o.cart.0.0.153161d7NYkAZ1&mp=1&gatewayAdapt=glo2nld
That is probably also not supported by OpenHASP.
I would like to buy one that supports OpenHASP, can someone point me a good Ali link version ? It is meant to be attached to the wall. On/in the Wall there is just an empty Niko (I live in Belgium) black box with a standard Niko wall socket plate now covering it.
I don't have 230VAC mains over there, only small wires, so only DC voltage possible. I saw that most of these 86 ESP boxes have a dummy white backpart (no relays or power supply), so this would be great. I read from Francis that it would not fit a EU box ? Looking at pictures the back part is 60x60mm ? Won't that fit the Niko/Belgian black in wall box ? Francis also gave a good tip with the Niko PCB claws. I did not know that it existed. It also seems possible to 3D print a back plate for just the front panel to fit on a Niko claw then ? Could you share that 3D print file please Francis ? bought myself a WT32-SC01 plus panel and it works great with OpenHASP, but I don"t know how to attach is to the wall, I don't have a 3D printer myself, so ready made cases like some of the 86 boxes would be great if they fit. For the WT-32SC01 plus there is more 3D print work to fit this on the wall. The 86 box seems easier since the whole display front has a nice edge case already, only it has to clip on a back plate, maybe Francis or Nicolas 3d plate is enough to just screw it to the wall. Don't know if 5V connection will works on that wall box. Maybe I have to add a 24/12V to 5VDC converter module behind the plate in the wall box to lower current and avoid voltage drop. Pity there is no ready EU box style solution on those ESP32 S3 display control panels (with DC supply).

Hi' @8OND007

First of all, the WT86-32-3ZW1 has been deprecated many months ago. So I don't expect a lot of users will actually read this old thread 😉

AFAIK latest threads regarding 86mm display boxes are:
#435 and
#458

I've never seen the 'new' v4.0 version before (haven't searched for those device types lately).
Hard to tell what's actually 'inside' from the description on the Ali page. A datasheet would be helpful.
Can't tell whether or not this v4.0 type can run openHASP 'out of the box'.

Panlee has made quite a few versions last 12 months. I've seen at least three different versions on Ali - All with openHASP support (display/touch only). These versions are all delivered with 'dummy', chinese sized backplates - without PSU/relays.

AFAIK the T3E is still the only device available with EU sized backplate, PSU and three relays.

The issue was here

static lv_color_t buf[TFT_WIDTH * 10];

it should be

lv_color_t *buf = (lv_color_t)heap_caps_malloc(TFT_WIDTH * 10 * sizeof(lv_color_t), MALLOC_CAP_DMA);

Now the only issue is that the touch is not working, no calls to the handler.
This section from lv_conf.h is changed

#define LV_TICK_CUSTOM 1
#if LV_TICK_CUSTOM
    #define LV_TICK_CUSTOM_INCLUDE "Arduino.h"         /*Header for the system time function*/
    #define LV_TICK_CUSTOM_SYS_TIME_EXPR (millis())    /*Expression evaluating to current system time in ms*/
#endif   /*LV_TICK_CUSTOM*/

After resolving one issue, a new one occurs immediately...)

First of all, I created a repo with the source code: https://github.com/strange-v/WT-86-32-3ZW1_LVGL
Second, I had an incorrect build parameter in platformio.ini (it specifies where lv_conf.h is placed):

-D LV_CONF_INCLUDE_SIMPLE=./include/gui

but according to docs, it should be like this

-D LV_CONF_INCLUDE_SIMPLE
-I ./include/gui

The weird part is that I see a correct picture with the first config, but it just hangs.

With the second config, the screen is live, it sows some animations and reacts to touches... but it looks like this

I played with IRAM_ATTR, the way how lv_color_t buffer is allocated, but the result is the same. Have no more options on what to tweak.

Sorry for the long monolog, but finally, the issue was resolved.
Occasionally, I set incorrect LV_COLOR_DEPTH (8 instead of 16), and it caused such behavior.

Now, the code in the repo is fully functional.

I just love it when they cant even get their own diagrams right (see the reset button is covering the voltage reg in the 2nd pic).
Seems like they are going thru a cost reduction/optimization run.

Do you think these delays could be related to the upcoming NSPanel Pro https://notenoughtech.com/home-automation/first-look-at-sonoff-nspanel-pro/ it also has a 480x480 screen and similar shape of the outside.

Not really, but no one really knows.
More likely due to the fact that China still is heavily hit by the newer Covid variants and new lockdowns.
And also the general global lack of semiconductor components has a big impact everywhere.
The 86mm square shape is what everyone should have come up with from the very beginning, as these fit as standard in some 90% of ALL european household sockets 😉

Until you posted here, I didnt realize the original WT-86 did not fit properly into an european box.
I thought the square box was standard everywhere but north america.

Also noticed that the PCB's wasn't labelled with Wireless-Tag but PanLee. I believe Panlee is related to Wireless-Tag in some way. Perhaps a separate company for such household electronics with the complete software package (apps and cloud based solutions)

Nope, that square box is to big to fit in 'standard' EU boxes. It's an asian variant I guess. Don't know that much about EU wall sockets though, as I'm from Denmark. And we've had sort of a monopolized marked for decades, which LK (Lauritz Knudsen) has made billions of dollars on throughout the last many years. Now standards are common and shared with EU. But still 98% of all danish households has wallsockets and switches installed from one company only - LK !!! 🤑🤑🤑🤑🤑🤑🤑

Forgot to ask. Did you consider using the APDS9930 ambient light sensor capability as well to set an appropriate backlight level upon wakeup ?

I didnt even think of it. Its a good idea - more effort than its worth for me at the moment as I set the brightness to full when on, but for night time I could see it being used to reduce the brightness.
I used the standard library available for the APDS9930 so it should be very possible to add brightness based on ambient light.

Well, I've ordered a handfull of 9930's from Aliexpress. I'll try and replicate your hack on my WT86-32 😆If possible, I'll do the same on my WT32-SC01 devices. The sensor should be able to fit, as there's actually already pads for it on the pcb. But with separate wiring it might be an impossible task. Would you mind sharing your compiled firmware binary and your custom code ? My programming skills sucks, so I'll appreciate all the help I can get 😆

I actually got the idea for trying a sensor because of the WT32-SC01 and the space it has for one.
Sure I can share the code no problem. Ill setup a repo in the next few days for my customized version and you can grab that and work from it - ping me if I forget to put up the code after a week or two.
As for the wiring, hopefully the pic above is all you really need (sda/scl/vcc/gnd). The moving of the sensor off the pcb was a 1:1 wire job from sensor to pcb.

@codewise-nicolas any chance of posting your code to get the proximity sensor working??

Hmm... I asked for a datasheet and all I got was this... 🤦‍♂️ Not really sure they've any idea what's actually INSIDE their own products 🤔
Don't know if the Xtensa LX7 CPU comes in any other SoC's than an ESP32 ? Not really keen on spending some 40usd + 30usd in freight to find out.

Well if this image would be real, it would fit standard EU boxes

Yep. With the four cut out corners, I would actually also expect that it would fit a standard EU wall box

Yep. That bit doesn't sound promising. But as with the Lanbons they could have added a dedicated Tuya chip to support the Zigbee network as well. I've asked for more details about the SoC, display controller and touch controller used. Also asked for a photo of the actual pcb. Let's see if they provide

It's almost an impossible task to get anything usefull from that company 🙄😫 I finally got a picture of the pcb. Crappy resolution, so not much can be identified. The U10 chip might be an ESP32 but could actually be anything. As expected the Tuya ZS3L chip is present. ANT1 connector for an external antenna and J1 might be a header for flashing. Funny naming though - R0 & T0 ?

I'll give it a last go and try and ask the nice lady to answer my questions about the actual components used in the device. Or at least send a highres picture of U10 so it can be properly identified

Progress !! 🎉🎇✨
ESP32-S3 onboard and an external GigaDevice 128mb flash.

I'm tired waiting for WT to finalize their new SKU and willing to take a shot on this and order a couple of sample devices.
Hopyfully both the touch and display controller are known supprted types.
But what about the ESP32-S3. Any known issues that currently should prevent openHASP support ?

that looks really nice. almost as nice as the one i'm making myself. based on the (dutch) Gamma K2 switch panels.

Would be awesome to see OpenHASP on it

Yep. Hopefully we will 🙂I'm confident that @fvanroie will solve the openHASP support for the ESP32-S3. But display driver and touch controller used in the device are also still completely unknown. Getting 'real' technical info / datasheet from the supplier has been quite unfruitful so far. But the worrying part is the network capability, as the pcb is not fully occupied. That could potentially be a real show stopper. Time will tell,as test order is en route now. I'll ship one device to @fvanroie upon arrival to Denmark and hopefully he can do some magic with this device as well 🙏😁

Is this one supported by the 8ms.xyz service?
if so, we can always extract the details of the lcd and touch panel from the compiled files 8ms.xyz generates.

Are you referring to the T3E device or the device in the link ?

Regarding the T3E: No, not to my knowledge. Device is marketed as a Tuya slave device without gateway capabilities and can't really do much on it's own with manufacturers firmware. @fvanroie has dug out some ST7701S code that I'm currently testing and trying to get to work on the device. Not working yet, but hopefully we'll get there. There's a couple of devices on the market which are using this 4" 480x480 res. display. All seems to be rather identical. Also when it comes to the actual pin connections between ESP and the display connector.

I've started a new T3E discussion thread, where I'll gather all information about the device.

Btw. Did you make a repo for the WT86-32 proximity sensor ?
My sensors have arrived, but currently I'm occupied getting the T3E display working, so no rush 😉

I'm moving the GS-T3E to this new discussion topic.

This is my board. Can you help-me?

That is the Panlee ZW3D95CE01s-UR-4848. You can download the firmware file panlee-zw3d95ce01s-ur-4848_16MB from:
https://github.com/HASwitchPlate/openHASP/actions/runs/5487951881

I don't know how compile and upload the firmware for the display and esp32. I'm using on download mode and tried to flash by the 8ms.xyz editor but after flash they start a restart looping. I just wanna show some sensors informations on the display :( can you help-me to make a simple interface and read the sensors?

now the flash by 8ms editor works but the display continue on restart loop

Can't tell if you can flash openHASP fw using the 8ms software.
Please try and flash the openHASP fw using before mentioned methods. These are proven methods and will work for sure.

I would also suggest that you read the openHASP documentation to understand the openHASP concept and how to interface with openHASP.

openHASP for sure can do what you need (and much, much more). But it's not 'plug and play' and requires some knowledge in order to integrate with e.g. Home Assistant / MQTT broker etc.