Planning and setup - ESP32-S3 - 4848S040 - 480*480 IPS touchscreen

Hardware
165

What do you see as it boots then?

166

a text with “openhasp” written then the screen becomes black with “plate” written at the top left

167

Well you’ll have to find it on your network. Start with your access point. Or use fing in android, or this on windows. Wireless Network Watcher - Show who is connected to your wireless network

168

What have you done so far?

169

I installed the firmware on the device, entered the coordinates of my wifi but I do not have access to the ip address, I think that the device does not connect to the wifi I do not know what is the reason

170

Try flashing the firmware again, then pay attention as you set up wifi.

171

Try starting over.
Here are my notes from my notebook:

Flash the Firmware:

  1. Use Chrome Browser and go to the Nightly Build Site: https://nightly.openhasp.com/
  2. Select “Guition ESP32-S3-4848S040” and Install.

Set Up Wifi:

  1. Follow Instructions on the screen

Install HomeAssistant Components
Install The OpenHASP Component from within HACS

If your display is running and reachable, you will see the text “plate” on the top left corner of the screen and a brief popup with the IP-Address.

MQTT Credentials

  1. Go to the device IP-Address with your browser: http://your_ip/config/mqtt and fill in your MQTT credentials.
172

when I enter the coordinates of my wifi and I press the confirm button nothing happens so I tried to connect it to my mobile wifi with the connection sharing option and it worked can I continue with my mobile network or is it absolutely necessary that the device is connected to the home wifi

173

It needs to connect to your mqtt broker. Try turning 5 g mhz off on your router/AP.

At least when connected to your phone you can try to debug via telnet and the web page.

174

The what??

Do you mean that you started a WiFi hotspot on your phone and use the WiFi credentials provided by your phone?

If yes, then I have to question your home WiFi credentials. It should be simple- you have an SSID and a passcode. The passcode is case sensitive, Horse and horse are different.

175

He hasn’t gotten that far. When he enters the correct WiFi credentials and reboots the device, he should get the device IP, and only then can he get into the setup menu.

176

Yes I know. I am saying that connecting to his hotspot, he won’t be able to connect to the mqtt broker. So it’s not going to be much use.

He will be able to access the web server for configuration, and the telnet interface. But it is not going to be much use beyond that.

I suggested turning off 5mhz wifi, in case something funky is going on with the AP.

Edit: can also reset his wifi credentials at that point.

177

Good thought. He can also get the device MAC address then find the IP in the router.

But, I think there is something wrong with his router WiFi credentials. That he can log on to the device over his phone hotspot tells me that the firmware is correctly flashed.

1 Like
178

Salut @edenflamboyant (j’imagine que tu es français vu ton pseudo ? )

J’ai eu le mĂȘme problĂšme que toi avec ma plate et la freebox. Dans l’interface de la freebox je voyais la plate tenter de chopper le dhcp et se dĂ©connecter en boucle. Il a fallut que j’aille dans les rĂ©glages DHCP de la box et que je force une rĂ©servation DHCP. AprĂšs plus de problĂšmes. Si ça peut t’aider


Translation :
I had the same problem as you with my plate and my router (Freebox). In the admin page of the box I was seeing the plate trying to obtain a dhcp lease but it kept disconnecting and re-trying again and again. I had to go to the DHCP settings and force a reservation for the object in my router. No problem since. If it can help


179

Merci beaucoup a vous pour votre aide !

180

But, does it connect now?

1 Like
181

Sorry for late reply, had a busy week.
Actually done both but nothing unusual.
Here’s the telnet logs: (For recap: p1b1 doesn’t work / p1b2 does)

#[23:24:01.444][94196/110804 14][56636/56648  1] MQTT PUB: p1b1 => {"event":"down"}
#[23:24:01.534][94196/112400 16][56628/56648  1] MQTT PUB: p1b1 => {"event":"up"}
#[23:24:02.942][94196/112400 16][56628/56648  1] MQTT PUB: p1b2 => {"event":"down"}
#[23:24:03.076][94196/112400 16][56628/56648  1] MQTT PUB: p1b2 => {"event":"up"}
#[23:24:03.372][94196/112344 16][56628/56756  1] MQTT RCV: p1b2.val = 1
#[23:24:03.384][94196/110748 14][56628/56756  1] ATTR: Unknown property val (15809)
#[23:24:03.520][94196/112344 16][56628/56756  1] MQTT RCV: p1b2.text = 

MQTT Analyzer also show’s same logs for both buttons

182

Looks normal to me.
Have you told Home Assistant what to do with the MQTT?

I use !include in my configuration.yaml a lot- it really simplifies configuration.yaml and compartmentalizes various functions.

openhasp: !include openhasp.yaml

In my openhasp.yaml file I define what I want Home Assistant to do with the MQTT message:

    - obj: "p12b1"  # light-switch toggle button
      properties:
        "val": '{{ 1 if states("switch.officelight") == "on" else 0 }}'
        "text": '{{ "\uE6E8" if is_state("switch.officelight", "on") else "\uE335" | e }}'
      event:
        "up":
          - service: homeassistant.toggle
            entity_id: "switch.officelight"

“val” is either 1 or 0 depending on the state of the entity.
“text” is one of two icons depending on the state of the entity.
event: is what the panel publishes over MQTT: “hasp/plate/state/p1b2”

In this example, if the event is “up”, then a service is called to toggle the light.

(\uE6E8 and \uE335is the code for the MDI Icon “lightbulb on” or “lightbulb off”.

183

I am not sure what your are trying to do here, but what is hold: trying to do? In any event it isn’t showing up in your telnet log, but it is hold: that activates the toggle of light.w2

184

Stupidly enough, even though I read through it all three times late at night I somehow skipped the “hold:” line. There was my mistake. Thanks @nickrout !
And also huge thanks to @stevemann for the great tips!