noticed the same behavior with mine, but thought it is just a short loss of connectivity 
Well, iāve been struggling to find a solution for this for weeks now. I use a modified version of the HASP (I changed some texts, ommited a few Fields from the web server page, etc).
I thought that these modifications I made was the cause of these reconections. Good to know someone eles is experiencig this.
For what I found out so far: itās not rebooting. It looses conection with the mqtt then quicly conects again.
In my experience itās WiFi dropping out of signal long enough that it loses connection. There is code in the firmware which looks to address these short losses of connectivity, which is what you are seeing. Itās annoying to troubleshoot because it almost never happens while out on the bench (meaning, not inside a metal box and thus has great signal).
Might be better if I do some work to make it less visible on the display itself.
Hi All,
Setup one first HASP last night - booted it up and the LCD wasnt getting power. i put a multimeter on each pad and wasnt getting a connection between the GND on the lcd pins and the D1 mini. if i connecting the LCD GND wire to the side headers on the PCB the LCD powers up and everthing works fineā¦ tested with USB and AC power, same issue.
am i missing something?
That bears the hallmark of a bridged connection on the transistor pads. If you have solder wick you might be able to clean those pads up a bit. They are very close together and itās easy to bridge.
Whatās happening here is that the LCD firmware process, while mostly reliable, can sometimes fail and when that happens you need to power cycle the panel as there is no in-band recovery process. To deal with this, I added a transistor to act as a low-side switch for the display. When D6 is brought high, the āswitchā is closed and the display powers up. If the transistor pads have been bridged at all this process doesnāt work, resulting in the behavior you describe.
If you donāt think youāre going to be flashing the LCD a lot, you can skip this whole part of the circuit. Most people wonāt need this, and you can always flip the circuit breaker to reset if you do wind up getting stuck in an update. To do this, cut the resistor R1 off of the board (MAKE SURE TO DO THIS FIRST), and then you can simply bridge all the pads of the transistor together with a lump of solder.
With this āfixā, youāll be connecting LCD ground to the normal ground directly with no switch in the circuit and things should work as normal.
Hereās the schematic that shows how this is connected:
1 Like
Thanks Luma - iāll look at this when i get home today.
on a side note - eg, can you change B1 and B3 to be arrows and cycle through pages? currently have only the 3 pages to select from?
yes but just need to write the logic automation to do it.
eg i added this when volumio is play
I want hasp screen to display what playing
- alias: hasp_plate01_p8_Media_Playing
initial_state: true
trigger:
- platform: state
entity_id: media_player.volumio
to: "playing"
action:
- data:
entity_id: input_number.hasp_plate01_activepage
value: '8'
service: input_number.set_value
and then when I pause it
- alias: hasp_plate01_p8_Media_paused
initial_state: true
trigger:
- platform: state
entity_id: media_player.volumio
to: "paused"
action:
- data:
entity_id: input_number.hasp_plate01_activepage
value: '1'
service: input_number.set_value
Been messing around with the switchplate, and i love it.
Beeing im kinda new to this i just cant seem to find the way on how to change the code for the alarm panelā¦
Can anyone help me out here.
I have a enhanced version 3.5 and am having a heck of a time getting it to work. I run the serial monitor and can see the communication with mqtt and hmi but no Interactions with the screen. Anyone have an idea as to what changes need to be made on the HMI file or the bin file for the esp to get this working?
I used the provided HMI file, changed the board in the nextion editor and load on the sd. I get the initializing page but the QR code doesnāt show.
Did you set the active screen in HA to 1
If you could post the serial log to https://hastebin.com/ or similar we might be able to help you out.
Thanks Luma,
Of course i get a email that the switches are in stock now!! haha. Iām going to run through everything again and then ill send the serial log. thank you
ok, here is a log from the APP_DATA plink
after this i basically get a txt= with the current time every minute
also, i kept the plate name as plate01
https://hastebin.com/poliyakesu.makefile
First - have you flashed an HMI to the LCD? If you donāt have the required 2.4" display, it will need to be modified in the Nextion editor for whatever size you have. This isnāt an altogether simple process, every single UI element will need to be resized and moved around to make it look right. If you havenāt done this yetā¦ youāre really going to be best off with the correct display.
If you have done this, then the display should be set to 115kbps for serial comms already. From this log it appears you are receiving no serial traffic from the Nextion back to the ESP8266. Check your solder job and wiring on the displayās TX pin back to the ESP8266.
I have flashed the HMI provided in the github. I opened the HMI in Nextion Editor and changed the board configuration to NX4832K035_011 and did a tft output to the sd card. It loads onto the screen. I just ran it in the Nextion Serial and the simulator returns 24 ff ff ff on every change i make in the states ui when toggling a button. So its sending the data but nextion isnt working properly. I planned on buying your 2.4" setup but was out of stock so iām trying to get the 3.5" i have to work. i noticed you have a enhanced TFT file but its not the same size as my board so it wont load. Do you know what changes needed to be made from non enhanced to enhanced?
Looks Like 24 ff ff ff is serial Buffer overflow. Iāll start looking into that. Thanks for your help.
OK great - if youāre using the HMI (converted using the editor for your panel size), then that should include the command on page 0 which tells the Nextion to set the serial rate to 115200bps, which is an important step and could cause the log weāre seeing. If thatās the case, that leaves TX from the Nextion back to your display as the culprit. If you have a multimeter, check to confirm that the āTXā pin on your Nextion has continuity to D7 on the Wemos D1. Also confirm that you donāt have continuity to GND or +5V on the panel itself.
here are my resistance readings
also, I havenāt modified this board. Still has factory connector.
with d7 pinned to TX at the nextion i get the below readingsā¦
d7 to tx - 0 ohm
d7 to rx - 421 ohm
d7 to ground - 413 ohm
d7 removed and nextion board alone
tx to rx - 423 ohm
tx to ground - 415ohm
rx to ground - 10ohm
Checking here on a board I have on the bench:
TX to GND: 4.8 MĪ©
TX to +5V: Open
Something for sure isnāt right on your board. Any chance you bridged a pin while soldering?
Thatās strange. I had to double check my readings and verified its correct.
So it look like its a conflict with the arduino sketch. I added buttons to the nextion and assigned them to the next page and when i hit the button it changed page and the page slider in hassio reflects that. when i hit the button to page 2 the 3 lines are sent.
[22:46:39][+642.303s] HMI IN: 0x66 0x2 0xff 0xff 0xff
[22:46:39][+642.308s] HMI IN: [sendme Page] ā2ā
[22:46:39][+642.312s] MQTT OUT: āhasp/plate01/state/pageā : ā2ā
when the change is made in hassio only the 2 lines are sent
[22:47:51][+714.654s] MQTT IN: āhasp/plate01/command/pageā : ā3ā
[22:47:51][+714.660s] HMI OUT: page 3
so looks like i need to mess with the arduino code to get the HMI OUT to nextion code.