Only logo and TNDisplay in the screen #1
Comments
|
Hi, please open tasmota console type Rule1 hit enter and paste the console output here. |
|
16:35:20.608 CMD: Rule1 |
|
Rule was not added correctly. Open tasmota console and paste following comand then hit enter: after that if you type rule1 the result should be: |
|
Now i get this when i touch the screen. cmnd in my MQTT exploror but still the logo with TNDisplay in my touch screen |
|
17:54:40.033 CMD: Rule1 1 |
|
ok, next step check serial port settings, type Baudrate in the console and hit enter, what result? |
|
{"Baudrate":115200} |
|
Change it to 9600, execute following command: after that try execute command: If the page on the display changes then the settings are correct. Restart tasmota and you should see "WiFi OK", "MQTT OK". |
|
18:09:33.241 MQT: stat/TND/RESULT = {"Baudrate":9600} When i touch |
|
Touch events looks good, after restart display show informations about wifi and mqtt? |
|
00:00:00.001 HDW: ESP8266EX |
|
No wifi or MQTT still the same |
|
TX pin from ESP is correctly connected to the RX pin on display? |
|
18:25:55.145 MQT: tele/TND/RESULT = {"SerialReceived":"70735F636C69636BFFFFFF"} Wherever I touch the screen it gives this output. it cannot be that the flashing of the screen was not done correctly. because I get the same output everywhere. |
|
TX i think its ok |
This output is correct, on the status page there is one large button for the entire screen. Clicking it should send just such a message. Port speed settings are also ok, data received from the display is ok, the problem is only with sending data to the display... try check serial settings by sending this command: result should be 8N1 |
|
18:40:48.925 MQT: stat/TND/RESULT = {"SerialConfig":"8N1"} |
|
And still after sending the command: the screen does not respond? |
|
18:44:48.302 CMD: serialsend5 706167652033ffffff |
|
Can you post some photos of pins connections? Software looks good, lets check hardware... |
|
And one more check, what is output of command: ? |
|
|
|
|
|
19:12:19.732 MQT: stat/TND/RESULT = {"SerialDelimiter":255} |
|
Connections look good, try change delimiter to 254, command: any changes after restart? |
|
No changes |
|
Your module and template settings looking like this? |
|
Yes i think so Only by my is the name tasmota. And i have tasmota 14.1.0 instead of 13.4.0
|
|
We have probably checked all possible settings step by step and you have everything configured correctly, the communication from the display works, the problem is still with sending data to the screen and I have no idea what could be wrong anymore.... do you have the possibility to connect nextion via ttl adapter to PC? There is a debug option in NextionEditor, maybe this way you could check if the problem is only in Tasmota or maybe on the side of the display.. wires? Some people also reported problems with correctly uploading the project to nextion via SD card, I uploaded the project via nextion editor and ttl adapter, maybe try this option? |
|
okay I have a TTL module. I'm going to try this. thank you so much for your project and time. If I get any further I will let you know. |
|
You can also hook up the ttl adapter to esp and see exactly what Tasmota is sending through the serial port. When decoding/encoding the hex strings i recommend this tools: https://codebeautify.org/hex-string-converter Good luck! |
|
I orders another One. Just a different type because i ordered in the netherlands. Now i get this message. Can i adjust this? |
|
So the old display was broken? You can change the display model here: |
|
yes i think is is broken, got no response to the RX. |
|
In nodered, make sure you have properly configured the MQTT connection (MQTT configuration node) and in all MQTT-IN and MQTT-OUT nodes are correctly set MQTT topics (according to what you entered in Tasmota). |
|
where do I find the MQTT configuration node? I have some experience with nodered, but not much |
|
In the upper right corner the gear icon:
And then double click on:
Set your MQTT server IP and port:
If you have enabled Mosquitto Username and Password Authentication then enter it here:
After that make sure you have enabled TNDisplay flow:
Then click on deploy and you should see demo app on the nextion screen. If the demo app doesn't show up, make sure you set a topic and full topic in Tamota like that:
And finally if you want to use other topics in tasmota change the configuration of these nodes:
|
|
Next step. I get a connection and also the buttons on the screen. I tried it this afternoon in the office and when I heard a switch I also went to the switches. At home I have the same buttons, but when I press buttons I stay in the menu screen and do not go to switches. I do get the output below in nodered. FYI I want to use this later for domoticz 8-7-2024 21:55:33node: fe1719b2.b214f8 |
|
When returned value from display is a string, the returned data is 0X70+ASCII code+0xff 0xff 0xff so 70315F636C69636BFFFFFF is a 1_click and it looks good, you make any changes in demo flow? You can also enable debug for display, click here and deploy flow:
As for controlling Domoticz from TNDisplay it can of course be done, TNDisplay can control anything you can do in Node-Red. |
|
It's the same display, same WiFi(SID), just a different MQTT IP. {"RawData":"70315F636C69636B","ReturnCode":"70","RawValue":"315F636C69636B","DataType":"String","Value":"1_click"} ref_stop;PH.pic=15;TH.txt="Switches";P1.pic=49;T1.txt="Switch1";P2.pic=48;T2.txt="Switch2";P3.pic=48;T3.txt="Switch3";P4.pic=48;T4.txt="Switch4";ref_star |
|
It seems to me that you must have accidentally changed something in the demo flow. In my case DemoApp looks like this: |
|
that works the same for me. I now realize it's a demo. so when touching a button i get the same output in the console and mqtt i am right. son no matter what butten the same output. |
|
Great, so we finally got everything up and running. Now you just need to experiment with the demo application to understand how it works and then rework it for your project. It will be nice if you share the final version of your project. |
|
If I understand correctly you made the demo for the screen and logos. and not yet the input for home assistant. is that right? I can now send code when pressing a button. I think I should mainly look at nextion editor if I'm right. If I have something working I will definitely share it. I may have some questions later. There is still a difference between my office and home, but I don't dare to change anything here at the moment. among other things, all my air conditioners and shutters run on my mqtt/nodered at home. |
|
Let's get back to my previous post. I see that you have a YouTube video that shows you switching your lighting. do you have an example of this? the code? |
|
The purpose of the DemoApp is to show how the communication between NodeRed and the display works. In this sample flow you have shown how to control the display and how to respond to touch events sent by the display. On this basis, you can already create any Nextion<->NodeRed integration. As for HomeAssistant, I use this set of nodes for NodeRed<->HA communication: e.g. there is a "CallService" node, with which you can drive any device from HomeAssistant, so just connect the output of the "OnClick" node to the input of the "CallService" node and touching a button on the screen will drive some device. Try experimenting with this. As for the demo of homeassistant integration, there is not really how to do it, because everyone has different devices and entity names and zones.... and creating a demo that would, for example, change the state of all available switches could make a mess. This is what the nodes connections look like in my lights control flow: |
|
I will close this issue as a solved problem, if you still have any questions go ahead and create a new discussion thread or another issue. |
I think I have done all the steps.
it also says update success and then take out the SD card and restart it.
only when I start it I don't see any WiFi ok <-> MQTT ok.
I only see TNDisplay and the logo.
Can you help me on where I should look?
The text was updated successfully, but these errors were encountered: