How is it different from the previous version? Might the ghosting be fixed?

Chinese endplate means what exactly? Will it fit in a N. American duplex box? I should start an auction for all the frigging displays I've bought in the past couple months... 🥵

Well, hard to tell really, as I haven't recieved the device yet 😉
But my best guess is that the device housing is somewhat or completely identical to the original SKU.
If that's the case, then the actual part which goes into the wall box is appx. 68 x 68 x 25 mm. I've no idea about the N.A. wall box dimensions. I'm from Denmark 😆

The actual pcb and display will most likely be identical with the 4" Panlee device referenced above.
Both specs for the display, driver chip, onboard RS485 and audio codec chip all match and is a strong indication that devices are identical. Meaning that display issues will be long gone, as the 480x480 res. IPS panel is far superior to the original SKU crappy display.
But time will tell...

RS485 isn't supported by openHASP firmware...

Like you say, hard to tell with the generic descriptions. The photo shown as the USB connector, so in theory should be the UR version. Which would be fine by me as I have no interest in audio, as for which one would actually show up of course is anybodies guess as the photo could easily be a stock one and they might just randomly send whatever they have.

I have ordered one to put in my pile of 'that looks interesting, hopefully I'll get some time to play with it soon'. So I'll let you know which version actually does arrive.

It looks like that's the UR version, which is fine and supported. Just pick the right bin file and you're good.

The LCD data line reference (8 bit 8080 mcu) in the AliExpress link seems strange ?
Guess it's just one more crappy Ali sales link with completely 'random' text, pictures and description 🙄

If you like the 4" square design, I would argue that the GS-T3E might be a better choice.
With the T3E you'll get a device with EU sized backplate, PSU and three relays.

The T3E has two (for openHASP unused) GPIO pins easily available at pads near the Tuya chip (U2)
Just desolder the Tuya chip or cut the power trace on the pcb.

The four relay GPIO pins are also easily accessible via the backplate connector (U13)

Hi Ben - any luck getting one of these units sent over to you from AliEx? I'm also a UK buyer, I placed 3x orders on AE each with three units. One order automatically cancelled after a week, two of them were shipped, and one of those shipped orders magically unshipped itself (shipping status was "canceled") - didn't get refunds for either and had to contact AE on chat to request this, which itself is not so easy. Admittedly I bought the 86V versions with the plastic enclosed backbox as opposed to the one with metal frame that you referred to here. I think there are stock issues hence sellers just cancelling stuff. My aim is to end up with about 20 working models but I know just getting that far is going to be a bit of a difficulty given my experience so far. Interested to hear your experience. Thanks

Yes it arrived the other day, its the UR version. No PSU or relays etc that you might get with other versions but that is no issue to me. I have not had any time to play with it except to plug it in and see it power up and run a test app thats installed on it.

@fvanroie
Should we add the TR environment now build options has been confirmed working ?

yes sure, it's a valid SKU now

OK. I'm afraid that I don't know what else is needed besides the build environment to do a PR.
Did you notice my comment on hsync/vsync settings. An initial typo or... ?

I know about the T & TR variants.
As openHASP doesn't natively support the temp. sensor (at least not at the moment) both variants can share identical build env.

Don't really understand your note regarding the two/four variants. Internal pcb antenna / external IPEX connector antenna or... ?

EDIT: OK, found the IPEX versions mentioned in the datasheet. External IPEX connector version possible for batch orders.

I wrote these notes just to remind others, cuz I confused -R and -AR/-UR at the beginning.

I didn't test other hsync/vsync settings, just use the values as-is.

You first click on the top Actions menu. Then select and click on whatever workflow run you want to download (usually the top one) and after that the Artifacts are shown.
Find Panlee and click on it. Then you'll download a zip file containing full and ota binaries for Panlee AR, UR and TR versions

Thanks so much :)

When doing serial flash you need to use the full binary version!!
The ota files are for WiFi 'Over The Air' updates. These can be used after the initial openHASP fw serial flash has been done.

Don't expect a reseller to know anything about the device pcb revision.
There is the problem - I have asked that question but no response ;-)
Never used Alibaba as they tend to have large min order qty and unknown shipping costs.
I might see if I can specify version with order then I can always send it back as not matching description ?

I've ordered T3E devices three times from Golden Security. No issues at all. You can order low quantities as well (even 1 pcs. as test sample)
Just ask Maggie at the chat to ensure you get the pcb 2.3 version
Shouldn't be an issue since the old pcb v1.x has been deprecated for many months now.

Just to chime in, I have also ordered from this Alibaba seller and had no issues either.

I am UK like you @smcgann99

Aliexpress would be preferable as already has taxes/vat included in the price so shipping is less cumbersome.

Alibaba also provides the shipping cost and tax (if you don't have a VAT number) at check out.
But I agree that it's easier to compare prices from Aliexpress as prices shown are including tax/vat

Nope. You'll have to do your own Custom Code for the SHT20

Thanks for sharing, I will give it a try.
Based on your experience it seems like it's not very accurate then ;-)
Also shouldn't the value be in the existing sensor topic, and use the Tele Period set in debug ?

Hi, regarding "Also shouldn't the value be in the existing sensor topic, and use the Tele Period set in debug ?" - I don't know how to do this, but I am open to learn if you give me a hint. Compiling this custom build was my first ever such experience and first time using Visual Studio Code as I am not a developer, just a IoT passionate 😊

You are at least 1 step ahead of me then ;-)

Perhaps someone else can assist you ?

Hello, great work. I have had the panel working for the last few days and been experimenting with different layouts. I have just uploaded your latest build and I can see the temperature and humidity values showing in the MQTT Explorer. As a relative newbie I have tried to incorporate these values into my mqtt.yaml but not having any luck reading the values.
# Panlee Temperature

• name: "Panlee Temperature"
  unique_id: "panlee_temperature"
  state_topic: "hasp/plate01/state/sht20"
  value_template: '{{ value_json.value|float(0)|round(1) }}'
  unit_of_measurement: "°C"

maybe you could help?

worked it out with this and works
# Panlee Temperature

• name: "Panlee Temperature"
  unique_id: "panlee_temperature"
  state_topic: "hasp/plate01/state/sht20"
  value_template: '{{ value_json.Temperature|float(0)|round(1) }}'
  unit_of_measurement: "°C"

  Panlee Humidity

• name: "Panlee Humidity"
  unique_id: "panlee_humidity"
  state_topic: "hasp/plate01/state/sht20"
  value_template: '{{ value_json.Humidity|float(0)|round(1) }}'
  unit_of_measurement: "%"

I have purchased a second panel, identical, from the same provider and the offset adjustment of the temperature and humidity values are different for this second screen. It seems like you need to adjust the offset individually for each particular screen.

Humm, seems the sensors are not much use then.