Nextion display plugin
Moderators: grovkillen, Stuntteam, TD-er
Re: Nextion display plugin
I am having issues to get sliders running, some how the data looses its first chars.
print "publish .........
and gives result in the debug screen sh......
So somehow it looses publi
Tried alsmost anything i could think of but did not find any answers. Rules just wont do for my setup as there are to many buttons and things going on that 4 pages arent enough for me.
https://github.com/maragelis/NextionMqtt
This firmware does reveals that the nextion sends out more data on the serial than we receive.
Like wakeup on sleep
0x87
0xff
0xff
0xff
Sleep
0x86
0xff
0xff
0xff
thup=1 {To set sleep on for your nextion project ( 0/1))
thsp=xx (Set sleep after xx secs)
I prefer node red and mqtt route, as you could change the status of a button based on incoming msg.
So when the lights are set on thru a rocker, the status on the nextion screen will be updated.
I would prefer to use the espeasy route, but some how i cant get it working further than buttons and updating fields.
print "publish .........
and gives result in the debug screen sh......
So somehow it looses publi
Tried alsmost anything i could think of but did not find any answers. Rules just wont do for my setup as there are to many buttons and things going on that 4 pages arent enough for me.
https://github.com/maragelis/NextionMqtt
This firmware does reveals that the nextion sends out more data on the serial than we receive.
Like wakeup on sleep
0x87
0xff
0xff
0xff
Sleep
0x86
0xff
0xff
0xff
thup=1 {To set sleep on for your nextion project ( 0/1))
thsp=xx (Set sleep after xx secs)
I prefer node red and mqtt route, as you could change the status of a button based on incoming msg.
So when the lights are set on thru a rocker, the status on the nextion screen will be updated.
I would prefer to use the espeasy route, but some how i cant get it working further than buttons and updating fields.
Re: Nextion display plugin
Very well posible. I never tested it and I do not know the difference between the two.dragowasabi wrote: ↑28 Oct 2017, 21:08 This is how you celebrate your first success with this http://support.iteadstudio.com/support/ ... rl_locale= contributor to Dave A "Steve, thanks very much for your help. " etc .. So at least the display works (I thought it was necessary to break it). Perhaps the problem is that your library does not support Nextion Enhanced. Or ...?
On the other hand, the code shows some strange serial port handling. I am not sure what baudrate is used to communicate with the display, but the plugin uses 9600 baud.
Re: Nextion display plugin
Please keep in mind this plugin is highly experimental. I did ask for someone with more programming skills to make it nice.r_255 wrote: ↑29 Oct 2017, 09:56 I am having issues to get sliders running, some how the data looses its first chars.
....
I prefer node red and mqtt route, as you could change the status of a button based on incoming msg.
So when the lights are set on thru a rocker, the status on the nextion screen will be updated.
I would prefer to use the espeasy route, but some how i cant get it working further than buttons and updating fields.
Without using the Nextion drivers, it is not easy to interprete the data coming from the display.
I created a kind of workaroud for sliders. It is a mixture of programming the display and the use of Rules.
I'll see if I can find it.
Regarding MQTT, I have a lot of problems getting it to work reliably.
Re: Nextion display plugin
Hi Bert,
Its much appreciated, all the efforts you put into the plugin.
I got the dimmer running thru the mentioned plugin, but Espeasy gives me more flexebility in other devices.
Your programming, is much better than mine... with a lot of effort i can read some.
I also did see on Jeffs website that there is some one that has things running up and down, not sure as time is a issue at the moment here.
Thanks!
Robin
BIG PS:
The example on jeff's website is domoticz related and works with bash scripts.
The whole reason that i don't want to use rules is because there are not rules enough for what i want ( 4 pages is not enough )
What i want to try is that my toggle buttons get their status get updated thru mqtt. So the intention is to make a button visible based on the on or off status and later on also push dimmer values to a slider.
" { "topic":sendCommand, "payload":{ "command":"click b9,1" } }" Works in the mqtt firmware i mentioned so technical it would be possible to send commands to your nextion screen
and get buttons updated based on a device status.
I am not sure how the decoding in your plugin works, but it could be that some data from the nextion comes thru as it sends more data than only a key press. ( strange data that occurs now and then ) The other firmware works on softserial to, and does not receive any weird chars.
Its much appreciated, all the efforts you put into the plugin.
I got the dimmer running thru the mentioned plugin, but Espeasy gives me more flexebility in other devices.
Your programming, is much better than mine... with a lot of effort i can read some.
I also did see on Jeffs website that there is some one that has things running up and down, not sure as time is a issue at the moment here.
Thanks!
Robin
BIG PS:
The example on jeff's website is domoticz related and works with bash scripts.
The whole reason that i don't want to use rules is because there are not rules enough for what i want ( 4 pages is not enough )
What i want to try is that my toggle buttons get their status get updated thru mqtt. So the intention is to make a button visible based on the on or off status and later on also push dimmer values to a slider.
" { "topic":sendCommand, "payload":{ "command":"click b9,1" } }" Works in the mqtt firmware i mentioned so technical it would be possible to send commands to your nextion screen
and get buttons updated based on a device status.
I am not sure how the decoding in your plugin works, but it could be that some data from the nextion comes thru as it sends more data than only a key press. ( strange data that occurs now and then ) The other firmware works on softserial to, and does not receive any weird chars.
Re: Nextion display plugin
Hi !BertB wrote: ↑22 Jan 2017, 15:34 Under Tough Release Event of down:
va0.val--
if(va0.val<0)
{
va0.val=0
}
cov va0.val,t3.txt,0
print "|u,i230,n,s"
print t3.txt
printh 0a
Under Tough Release Event of b0:
va0.val++
if(va0.val>30)
{
va0.val=30
}
cov va0.val,t3.txt,0
print "|u,i230,n,s"
print t3.txt
printh 0a
This will increase or decrease value of 1, is it possible to make it change (+ or -) of 0,5 ?
Regards,
Re: Nextion display plugin
The variable in Nextion is either a string or an integer. You could try to work it out, by adding or subtracting 5 and dividing the value by 10 in domoticz.dokho wrote: ↑06 Nov 2017, 18:55Hi !BertB wrote: ↑22 Jan 2017, 15:34 Under Tough Release Event of down:
va0.val--
if(va0.val<0)
{
va0.val=0
}
cov va0.val,t3.txt,0
print "|u,i230,n,s"
print t3.txt
printh 0a
Under Tough Release Event of b0:
va0.val++
if(va0.val>30)
{
va0.val=30
}
cov va0.val,t3.txt,0
print "|u,i230,n,s"
print t3.txt
printh 0a
This will increase or decrease value of 1, is it possible to make it change (+ or -) of 0,5 ?
Regards,
Re: Nextion display plugin
First post here so want to thank all contributors, very good thread and just the plugin i needed.
ESP12E bare connected to Nextion 4" and MQTT to Node-red.
Had a hard time compiling ESPEasy v2.0.something but in the end did manage with the v2.0 with plugin included.
Also took some time to understand the espeasy setup, needed to get MQTT publish triggered etc. %systemdate% etc not yet available in this version either so now filling this data via formatted MQTT input from node-red.
All communications sorted now, there is just one thing not clear to me, are actually 2 things.
First, in the ESPEasy => Device tab, the section with the 4 Values, i just don't get what "code" stands for and where the reported codes/values come from.
I've created some of @BertB 's code in the Nextion button. When using:
i get a constant code value of 105.00 but when i use |u instead of |s the code changes all the time and part of the send string "|u,i33,n,s18" is missing.
I suppose "|s |u" is some lua talk? at some point lua and other text came as data, but happened only once.
The other Values are also filled when i send a button press with this code to ESP, but can't figure out where the come from.
And the Rules engine does not pick up on this. I've changed the nextion code to:
giving me this msg in the log:
but the rule does not work.. ? ( neither does : on Nextion#code=105 .. or Nextion#code=105.00 )
[update] Ok sorry, got it, about the 4 value fields anyway, it's the serial read buffers. Code is assuming the deviceid is being sent with the 0xFF's ending.
Had to rack my brain for some 1970's info stored away very deep about serial comms..
I get that the plugin is a bit of a quick and dirty solution but it works so love that, and the print string is an ever quicker and dirtier solution then, but don't see how BertB's rules would work if no device id is being sent. Will give it some more thoughs and tries, maybe try Pete Scargils way of using "get attr" on the Nextion.
[update2] Solved my problem by only using button/deviceid then rule on Nextion#code to send '1' or '-1' ,depending on button, via mqtt to node-red and have node-red return the desired temp. update is fast enough for ux ease-of-use.
leaves me with the sleep/wake-up data refresh issue as all data on nextion comes from node-red in 1 min intervals. the nextion page touch event is not sent when screen is being woken up. so cant tell esp that sceen is tapped to wakeup and needs refreshing data....
setup...
ESP12E bare connected to Nextion 4" and MQTT to Node-red.
Had a hard time compiling ESPEasy v2.0.something but in the end did manage with the v2.0 with plugin included.
Also took some time to understand the espeasy setup, needed to get MQTT publish triggered etc. %systemdate% etc not yet available in this version either so now filling this data via formatted MQTT input from node-red.
All communications sorted now, there is just one thing not clear to me, are actually 2 things.
First, in the ESPEasy => Device tab, the section with the 4 Values, i just don't get what "code" stands for and where the reported codes/values come from.
I've created some of @BertB 's code in the Nextion button. When using:
Code: Select all
if(va0.val=0)
{
print "|s,i13,n,s"
} else
{
print "|s,i33,n,s"
}
print page0.vattempset.txt
printh 0xa
I suppose "|s |u" is some lua talk? at some point lua and other text came as data, but happened only once.
The other Values are also filled when i send a button press with this code to ESP, but can't figure out where the come from.
And the Rules engine does not pick up on this. I've changed the nextion code to:
Code: Select all
print "|s,idx=33,value="
print page0.vattempset.txt
printh 0xa
but the rule does not work.. ? ( neither does : on Nextion#code=105 .. or Nextion#code=105.00 )
[update] Ok sorry, got it, about the 4 value fields anyway, it's the serial read buffers. Code is assuming the deviceid is being sent with the 0xFF's ending.
Had to rack my brain for some 1970's info stored away very deep about serial comms..
I get that the plugin is a bit of a quick and dirty solution but it works so love that, and the print string is an ever quicker and dirtier solution then, but don't see how BertB's rules would work if no device id is being sent. Will give it some more thoughs and tries, maybe try Pete Scargils way of using "get attr" on the Nextion.
[update2] Solved my problem by only using button/deviceid then rule on Nextion#code to send '1' or '-1' ,depending on button, via mqtt to node-red and have node-red return the desired temp. update is fast enough for ux ease-of-use.
leaves me with the sleep/wake-up data refresh issue as all data on nextion comes from node-red in 1 min intervals. the nextion page touch event is not sent when screen is being woken up. so cant tell esp that sceen is tapped to wakeup and needs refreshing data....
setup...
Re: Nextion display plugin
@BertB
First of all: Great Plugin !
I am just beginning with the plugin for the Nextion display. I flased a nodeMCU V 1.0 and I have communication with the display.
I can send Data to the display through a url (http://192.168.178.55/control?cmd=NEXTI ... txt="Hallo" ).
Question:
Do you have more documentation for the Nextion programming
print "|u,i230,n,s" The parameters where do they stand for?
The "1230 thats the Idx value that's simple but the rest?"
Alvast bedankt!
Mvg Ernst
First of all: Great Plugin !
I am just beginning with the plugin for the Nextion display. I flased a nodeMCU V 1.0 and I have communication with the display.
I can send Data to the display through a url (http://192.168.178.55/control?cmd=NEXTI ... txt="Hallo" ).
Question:
Do you have more documentation for the Nextion programming
print "|u,i230,n,s" The parameters where do they stand for?
The "1230 thats the Idx value that's simple but the rest?"
Alvast bedankt!
Mvg Ernst
Re: Nextion display plugin
Hi Ernst,
First of all, the code is not ready, it needs a some more attention, but I do not have much time to do it.
Initially the code simply received the data to the outputs, like this:
output 1 = pagenumber * 256 + itemnumber.
Page = 1 (it starts with 0) and button id is 9, you get 256+9=265
output 2 = button state, 0 is off, 1 is on.
With rules and events you can then make things happen:
Set the time out timer to 20 seconds and background intensity to 80%
on E16Nextion#code do
Nextion,tm0.tim=20000
Nextion,dim=80
endon
You only need to tick the Send Component ID box for that.
If you want more detail, like toggling a light switch via domoticz:
put this code in the Touch Release Event code box of the switch:
page0.vBT0.val=bt0.val /this is to update a variable
if(page0.vBT0.val==1)
{ / if on then send on
print "|s,i7,sOn" /This and (|s is switch identifier, i7 is a chosen id for a button)
printh 0a / this is sent to the ESP code
}else
{ / else send off
print "|s,i7,sOff"
printh 0x0a
}
The ESP code now shows 7 and the value is 1 or 0
In this case idx 7 must be a real switch. Nextion id and idx are not related.
The rules need the folowing code:
on E16Nextion#code=7 do
if [E16Nextion#value]=1
SendToHTTP <ip of domoticz,8080>,/json.htm?type=command¶m=switchlight&idx=7&switchcmd=On
else
SendToHTTP <ip of domoticz,8080>,/json.htm?type=command¶m=switchlight&idx=7&switchcmd=Off
endif
endon
sending the value of a counter after an update, you need to program the display:
va0.val-- /when the down button is touched, the variable decreases
if(va0.val<0) / not less than 0
{
va0.val=0
}
cov va0.val,t3.txt,0 convert a string to integer
print "|u,i230,n,s" |u is identifier for update of a variable, i230 is a choosen id
print t3.txt also print the value of the variable
printh 0a end of string
In the rules you can use:
on E16Nextion#code=230 do
sendtohttp ,domoticz ip,8080>,/json.htm?param=udevice&type=command&idx=79&nvalue=0&svalue=[Nextion#value]
endon
Hope this helps
First of all, the code is not ready, it needs a some more attention, but I do not have much time to do it.
Initially the code simply received the data to the outputs, like this:
output 1 = pagenumber * 256 + itemnumber.
Page = 1 (it starts with 0) and button id is 9, you get 256+9=265
output 2 = button state, 0 is off, 1 is on.
With rules and events you can then make things happen:
Set the time out timer to 20 seconds and background intensity to 80%
on E16Nextion#code do
Nextion,tm0.tim=20000
Nextion,dim=80
endon
You only need to tick the Send Component ID box for that.
If you want more detail, like toggling a light switch via domoticz:
put this code in the Touch Release Event code box of the switch:
page0.vBT0.val=bt0.val /this is to update a variable
if(page0.vBT0.val==1)
{ / if on then send on
print "|s,i7,sOn" /This and (|s is switch identifier, i7 is a chosen id for a button)
printh 0a / this is sent to the ESP code
}else
{ / else send off
print "|s,i7,sOff"
printh 0x0a
}
The ESP code now shows 7 and the value is 1 or 0
In this case idx 7 must be a real switch. Nextion id and idx are not related.
The rules need the folowing code:
on E16Nextion#code=7 do
if [E16Nextion#value]=1
SendToHTTP <ip of domoticz,8080>,/json.htm?type=command¶m=switchlight&idx=7&switchcmd=On
else
SendToHTTP <ip of domoticz,8080>,/json.htm?type=command¶m=switchlight&idx=7&switchcmd=Off
endif
endon
sending the value of a counter after an update, you need to program the display:
va0.val-- /when the down button is touched, the variable decreases
if(va0.val<0) / not less than 0
{
va0.val=0
}
cov va0.val,t3.txt,0 convert a string to integer
print "|u,i230,n,s" |u is identifier for update of a variable, i230 is a choosen id
print t3.txt also print the value of the variable
printh 0a end of string
In the rules you can use:
on E16Nextion#code=230 do
sendtohttp ,domoticz ip,8080>,/json.htm?param=udevice&type=command&idx=79&nvalue=0&svalue=[Nextion#value]
endon
Hope this helps
Re: Nextion display plugin
It can even get better if you only enable Send Component ID in the Touch Release Event of a button.
Let's assume that gives the code of 774 in the ESPEasy and in Domoticz you have a switch with idx 7.
Then with Rule:
on E16Nextion#code=774 do
SendToHTTP <domoticz ip,8080>,/json.htm?type=command¶m=switchlight&idx=7&switchcmd=Toggle
endon
you can toggle the switch.
And if you put:
http://<domoticz ip>/control?cmd=NEXTION,page3.b5.bco=1024 in the switch's On Action and
http://<domoticz ip>/control?cmd=NEXTION,page3.b5.bco=48631 in the off action
With a switch b5 on page3 of the Nextion, obviously, you get a feedback.
The switch is grey when off and green when on. It is important that the switches have a vscope set to global.
If on the Nextion you have the switch on page 0, you send: http://<domoticz ip>/control?cmd=NEXTION,page0.b5.bco=1024
Have fun.
Let's assume that gives the code of 774 in the ESPEasy and in Domoticz you have a switch with idx 7.
Then with Rule:
on E16Nextion#code=774 do
SendToHTTP <domoticz ip,8080>,/json.htm?type=command¶m=switchlight&idx=7&switchcmd=Toggle
endon
you can toggle the switch.
And if you put:
http://<domoticz ip>/control?cmd=NEXTION,page3.b5.bco=1024 in the switch's On Action and
http://<domoticz ip>/control?cmd=NEXTION,page3.b5.bco=48631 in the off action
With a switch b5 on page3 of the Nextion, obviously, you get a feedback.
The switch is grey when off and green when on. It is important that the switches have a vscope set to global.
If on the Nextion you have the switch on page 0, you send: http://<domoticz ip>/control?cmd=NEXTION,page0.b5.bco=1024
Have fun.
-
- New user
- Posts: 2
- Joined: 13 Feb 2018, 09:22
Re: Nextion display plugin
In Domoticz I created a few scripts to update the device through this plugin. Took me a while to figure out how to send a textvalue in quotes.
So for historial purposes and well, maybe it saves someone a lot of time I''ll put a few lua examples here. You can simply update any value this way.
For example button color, button txt, textvalues, text color etc.etc. Basically everything that's "green" in the attribute window (right-down window in Nextion Editor) when selecting a box (Button, text whatever) can be updated this way. It's quite easy if you get the hang of it.
(Lines that start with -- are not code, they are comments and are ignored by Lua)
First is text as is, (no values just text in quotes)
script_device_nextiontextquotes.lua
Next one is sending a value from Domoticz (Temperature or Solar or Energy for example) to Nextion. Nextion cannot handle floats (0.1 or 1.5) so sending the value in a textbox works like a charm but needs some extra lines of code.
script_device_nextion_valuequotes.lua
What I did for example is I created 18 pictures for Solar (cropped, global) which are updated based on the power value.
power =tonumber(powervalueintext) -- If you want to compare numeric values, thats why powervalueintext and powervalueinquotes
( Original background Domoticz picture and GUI is from here https://www.domoticz.com/forum/viewtopi ... 6&start=20
So for historial purposes and well, maybe it saves someone a lot of time I''ll put a few lua examples here. You can simply update any value this way.
For example button color, button txt, textvalues, text color etc.etc. Basically everything that's "green" in the attribute window (right-down window in Nextion Editor) when selecting a box (Button, text whatever) can be updated this way. It's quite easy if you get the hang of it.
(Lines that start with -- are not code, they are comments and are ignored by Lua)
First is text as is, (no values just text in quotes)
script_device_nextiontextquotes.lua
Code: Select all
commandArray = {}
print('Script bin_selector_nextion executed') --This shows up in Domoticz log
print(devicechanged['Afval'])
afval = otherdevices_svalues['Afval'] --Afval is the name of my dummy selector switch in this case.
print(otherdevices_svalues['Afval']) -- svalue returns the value of level (Off, 10, 20, 30, etc)
if (afval == "10") then -- In this case 10 is selector level 10, needs quotes, just for reference
os.execute('curl -s "http://192.168.1.125/control?cmd=NEXTION,default.nAfval2.pic=20" ') -- changing a picture does not requires quotes
os.execute([[curl -s 'http://192.168.1.125/control?cmd=NEXTION,default.nAfval1.txt="Weekend"']]) --changing a text does requires quotes
return commandarray --execute the commands
end -- to close if
script_device_nextion_valuequotes.lua
Code: Select all
-- we need this function to send the quotes around the values
function url_encode(str)
if (str) then
str = string.gsub (str, "\n", "\r\n")
str = string.gsub (str, "([^%w %-%_%.%~])",
function (c) return string.format ("%%%02X", string.byte(c)) end)
str = string.gsub (str, " ", "+")
end
return str
end
powervalueintext = otherdevices_svalues['SolarEnergyLive'] --this values can be for example 88.5 or 1433.2, just like temperature can be 2.3 or -4.4)
powervalueinquotes = '"' ..powervalueintext.. '"' --First part of the magic
commandArray = {}
print('Power = '..powervalueintext) --This shows up in Domoticz log
power =tonumber(powervalueintext) -- If you want to compare numeric values, see example later on
if (devicechanged['SolarEnergyLive'])then --If value changes of device SolarEnergyLive
os.execute('curl -s "http://192.168.1.125/control?cmd=NEXTION,default.tSolar1.txt=' .. url_encode(powervaluesinquotes) .. '"') --sending value to textbox in quotes
print('Sending data to Nextion') --This shows up in Domoticz log
return commandarray --execute the commands
end --To close the If
power =tonumber(powervalueintext) -- If you want to compare numeric values, thats why powervalueintext and powervalueinquotes
Code: Select all
-- If power value (not the quoted onces these are the to a real number ones) is between 80.x and 160.x
-- this can not be compared in Nextion editor because value can be x.x (floats) so lua does that for me
if (power>=80 and power<=160) then
os.execute('curl -s "http://192.168.1.125/control?cmd=NEXTION,default.nSolar2.pic=3" ') ---pictures do not need quotes around the value
os.execute('curl -s "http://192.168.1.125/control?cmd=NEXTION,default.nSolar1.txt=' .. url_encode(powerquotes) .. '"') --textvalue send with quotes
print('Sending data')
- Attachments
-
- Quick demo
- nextion.png (417.42 KiB) Viewed 181713 times
-
- New user
- Posts: 2
- Joined: 13 Feb 2018, 09:22
Re: Nextion display plugin
Quick PHP example (Because I also use a php script (for the bus part) but just to show you how things can be done in PHP or without Domoticz.
For example(a very small part of the actual script) that is a cron job every minute around bus arrival, again not depending on Domoticz.
/* PHP code Not Lua */-- just for reference
For example(a very small part of the actual script) that is a cron job every minute around bus arrival, again not depending on Domoticz.
/* PHP code Not Lua */-- just for reference
Code: Select all
$Trip_Status = "Active"; //Example text
/* Text color changes based on value*/
if ($Trip_Status == "Active")
{
$color2 = 63488; //Color value red because Active is true in this case
}
else if ($Trip_Status == "DroppedOff")
{
$color2 = 65535; //Color White
}
else
{
$color2 = 1024; //Color Green
}
$nex3 = curl_init("http://192.168.1.125/control?cmd=NEXTION,default.nRitstatus2.txt=\"$Trip_Status\""); // text does need quotes while sending so escaped
$nex3c =curl_init("http://192.168.1.125/control?cmd=NEXTION,default.nRitstatus2.pco=$color2"); //color doesn't need quotes while sending so no escapes
$nex3d = curl_init("http://192.168.1.125/control?cmd=NEXTION,page%20default"); //Screen jumps to the page with the name default,space escaped with %20
error_log("Nextion ('$Trip_Status')",0);
closelog();
curl_exec($nex3);
curl_exec($nex3c);
curl_exec($nex3d)
curl_close($nex3);
curl_close($nex3c);
curl_close($nex3d)
Re: Nextion display plugin
It realy looks great, but honestly ... Lua is too much for me
Re: Nextion display plugin
hi, and congratulations for the plugin
I'm using it to interface a nextion display with my domoticz server.
I'm having trouble changing the value of a setpoint.
In t3 I have the value to send
with a send button
If I enable "send compoment id" I can intercept the evendo from the esp but not the value.
Below is the log
s if the value of t3.txt
If I disable "send component id"
I get only
Nextion: send command: s7
10:00
Nextion: send command: s8
10:00
what am I wrong?
I'm using it to interface a nextion display with my domoticz server.
I'm having trouble changing the value of a setpoint.
In t3 I have the value to send
with a send button
Code: Select all
va0.val++
if(va0.val>30)
{
va0.val=30
}
cov va0.val,t0.txt,0
print "|u,i230,n,s"
print t0.txt
printh 0a
Below is the log
Code: Select all
Nextion : code: ,,
EVENT: NEXTION#idx=261.00
ACT : temperatura=
ACT : sendtohttp 192.168.1.80,8080,/json.htm?param=udevice&type=command&idx=245&nvalue=0&svalue=0
HTTP/1.1 200 OK
EVENT: NEXTION#value=0.00
EVENT: NEXTION#=255.00
EVENT: NEXTION#=255.00
Nextion: send command: s7
10:00
If I disable "send component id"
I get only
Nextion: send command: s7
10:00
Nextion: send command: s8
10:00
what am I wrong?
Last edited by fabix68 on 24 Feb 2018, 18:10, edited 1 time in total.
Re: Nextion display plugin
Where did you put the code in the Nextion button?
It has to be in the Touch Release Event.
Your Nextion#idx=261
This is the code in Rules:
xxx is to be replaced by your address.
This is what I get in the log:
It has to be in the Touch Release Event.
Your Nextion#idx=261
This is the code in Rules:
Code: Select all
on Nextion#idx=230 do
sendtohttp xxx.xxx.xxx.xxx,8080,/json.htm?param=udevice&type=command&idx=79&nvalue=0&svalue=[Nextion#value]
endon
This is what I get in the log:
Code: Select all
EVENT: Nextion#idx=230.00
ACT : sendtohttp xxx.xxx.xxx.xxx,8080,/json.htm?param=udevice&type=command&idx=79&nvalue=0&svalue=22
HTTP/1.1 200 OK
EVENT: Processing time:165 milliSeconds
EVENT: Nextion#value=22.00
EVENT: Processing time:107 milliSeconds
HTTP : connecting to xxx.xxx.xxx.xxx:8080
Re: Nextion display plugin
The code in nextion is released in the release event of the page1 id 5 (detected as 261)
these are the rules set in the espeasy
245 if the Setpoint idx in Domoticz
if I do not enable "send component id" it will always expeasy ignore the rule.
these are the rules set in the espeasy
245 if the Setpoint idx in Domoticz
Code: Select all
on NEXTION#idx=261 do
sendtohttp 192.168.1.80,8080,/json.htm?param=udevice&type=command&idx=245&nvalue=0&svalue=[Nextion#value]
endon
Re: Nextion display plugin
I am sorry,choxnox wrote: ↑29 Jan 2018, 08:52 Is this the latest version of the plugin?
https://github.com/letscontrolit/ESPEas ... extion.ino
It is not the latest version. Somehow I cannot get it on the playground.
Just above, there is the newest one.
Re: Nextion display plugin
I have compiled ESPEASY with the new plugin but the result does not change.
Can you send me an HMI file and a working rule in order to understand what I'm wrong with?
Thank you
Can you send me an HMI file and a working rule in order to understand what I'm wrong with?
Thank you
Re: Nextion display plugin
Is this plugin currently mature enough to port to the Mega branch for the "testing" builds?
Re: Nextion display plugin
I am trying to get it to the playground, but I just don't understand this process.
My current attempt seems to end up in all sorts of conflicts.
My current attempt seems to end up in all sorts of conflicts.
Re: Nextion display plugin
If you think it is workable, I can port it to the Mega branch, then more people can test it.
- budman1758
- Normal user
- Posts: 301
- Joined: 15 Apr 2017, 05:13
- Location: Riverside CA USA
Re: Nextion display plugin
Please do that. I have one of these displays coming.
"The glass is twice as big as it needs to be".
-
- New user
- Posts: 2
- Joined: 05 Mar 2018, 22:21
Re: Nextion display plugin
hi
I am trying to upload the plugin but I keep getting an error. when I flash it without the nextion plug in it works fine. when I add the plugin _p117_nextion.ino I get the following error
C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\SoftwareSerial/SoftwareSerial.cpp:38: multiple definition of `sws_isr_0()'
libraries\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:C:\Program Files\Arduino\libraries\ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp:41: first defined here
libraries\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_1()':
C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\SoftwareSerial/SoftwareSerial.cpp:39: multiple definition of `sws_isr_1()'
libraries\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:C:\Program Files\Arduino\libraries\ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp:42: first defined here
libraries\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_2()':
C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\SoftwareSerial/SoftwareSerial.cpp:40: multiple definition of `sws_isr_2()'
libraries\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:C:\Program Files\Arduino\libraries\ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp:43: first defined here
c:/documents and settings/me2/local settings/application data/arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/1.20.0-26-gb404fb9-2/bin/../lib/gcc/xtensa-lx106-elf/4.8.2/../../../../xtensa-lx106-elf/bin/ld.exe: C:\DOCUME~1\me2\LOCALS~1\Temp\arduino_build_87757/ESPEasy.ino.elf section `.text' will not fit in region `iram1_0_seg'
collect2.exe: error: ld returned 1 exit status
Multiple libraries were found for "Servo.h"
Used: C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\Servo
Not used: C:\Program Files\Arduino\libraries\Servo
exit status 1
Error compiling for board NodeMCU 0.9 (ESP-12 Module).
I am at a loss. any help would be great. thank you in advance
I am trying to upload the plugin but I keep getting an error. when I flash it without the nextion plug in it works fine. when I add the plugin _p117_nextion.ino I get the following error
C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\SoftwareSerial/SoftwareSerial.cpp:38: multiple definition of `sws_isr_0()'
libraries\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:C:\Program Files\Arduino\libraries\ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp:41: first defined here
libraries\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_1()':
C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\SoftwareSerial/SoftwareSerial.cpp:39: multiple definition of `sws_isr_1()'
libraries\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:C:\Program Files\Arduino\libraries\ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp:42: first defined here
libraries\SoftwareSerial\SoftwareSerial.cpp.o: In function `sws_isr_2()':
C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\SoftwareSerial/SoftwareSerial.cpp:40: multiple definition of `sws_isr_2()'
libraries\ESPEasySoftwareSerial\ESPeasySoftwareSerial.cpp.o:C:\Program Files\Arduino\libraries\ESPEasySoftwareSerial/ESPeasySoftwareSerial.cpp:43: first defined here
c:/documents and settings/me2/local settings/application data/arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/1.20.0-26-gb404fb9-2/bin/../lib/gcc/xtensa-lx106-elf/4.8.2/../../../../xtensa-lx106-elf/bin/ld.exe: C:\DOCUME~1\me2\LOCALS~1\Temp\arduino_build_87757/ESPEasy.ino.elf section `.text' will not fit in region `iram1_0_seg'
collect2.exe: error: ld returned 1 exit status
Multiple libraries were found for "Servo.h"
Used: C:\Documents and Settings\me2\Local Settings\Application Data\Arduino15\packages\esp8266\hardware\esp8266\2.3.0\libraries\Servo
Not used: C:\Program Files\Arduino\libraries\Servo
exit status 1
Error compiling for board NodeMCU 0.9 (ESP-12 Module).
I am at a loss. any help would be great. thank you in advance
Re: Nextion display plugin
in the plugin rename 3x SoftwareSerial on ESPeasySoftwareSerial
Re: Nextion display plugin
This code should work, but only added it, not tested yet and therefore not made a PR to the Mega branch: https://github.com/TD-er/ESPEasy/blob/f ... extion.ino
-
- New user
- Posts: 2
- Joined: 05 Mar 2018, 22:21
Re: Nextion display plugin
i got it sorted. I found an installer with the plugin on it.
Re: Nextion display plugin
Can you share where you got it?Dennis.prior wrote: ↑08 Mar 2018, 18:50 i got it sorted. I found an installer with the plugin on it.
Re: Nextion display plugin
I have trying for days now to get my nextion working as thermostat control
I'm using the following on for the logic on the nextion for a up / increment button
for the increment down button
this then increments t4 as a decimal xx.x
I then use on touch press event on t4.txt
on the touch release of t4.txt
This then allows me to use the up + down buttons to create a setpoint where the font is red, I then press the t3.txt this then changes the font white, and sends the selected value to the esp
on the log is see :
Does any one know how get this to my mqtt broker
switches work fine by using the following rules
but trying to send a value doesn't seem to be possible?
I'm using the following on for the logic on the nextion for a up / increment button
Code: Select all
va0.val=va0.val+2
if(va0.val>9)
{
va1.val=va1.val+1
va0.val=va0.val-10
}
if(va1.val>25)
{
va1.val=va3.val
va0.val=va4.val
}
cov va0.val,t9.txt,1
cov va1.val,t10.txt,2
t4.txt=t10.txt+"."+t9.txt
Code: Select all
va0.val=va0.val-2
if(va0.val<1)
{
va1.val=va1.val-1
va0.val=va0.val+9
}
if(va1.val<5)
{
va1.val=va5.val
va0.val=va6.val
}
cov va0.val,t9.txt,1
cov va1.val,t10.txt,2
t4.txt=t10.txt+"."+t9.txt
I then use on touch press event on t4.txt
Code: Select all
print "set-temp"
print t4.txt
t4.pco=18242
Code: Select all
t4.pco=65535
on the log is see :
Code: Select all
send command: set-temp19.11
Code: Select all
Nextion : send command: set-temp19.1116
switches work fine by using the following rules
Code: Select all
on nextion2#code=3.00 do
sendtohttp 192.168.0.48,8080,/json.htm?param=switchlight&type=command&idx=91&switchcmd=Toggle
endon
Re: Nextion display plugin
how can i send a slidder value to openhab over mqtt.
i have the plugin working.
but then, with nextion i'm new and need some help.
i have the plugin working.
but then, with nextion i'm new and need some help.
Re: Nextion display plugin
Does someone have a simple example of how the plugin works? Like sending a temperature value to n0...
I can test on my screen.
I can test on my screen.
Re: Nextion display plugin
Do not forget to lower the signal levels of the TX from Nextion to the RX gpio of the ESP.
The Nextion outputs 5V, but the ESP does only accept 3v3.
The Nextion outputs 5V, but the ESP does only accept 3v3.
Re: Nextion display plugin
Are all displays like this? Mine is the enhanced and at least on their website says:
Code: Select all
Interfaces Performance
Test Conditions Min Typical Max Unit
Serial Port Baudrate Standard 2400 9600 115200 bps
Output High Voltage IOH=-1mA 3.0 3.2 V
Output Low Voltage IOL=1mA 0.1 0.2 V
Input High Voltage 2.0 3.3 5.0 V
Input Low Voltage -0.7 0.0 1.3 V
Serial Port Mode TTL
Serial Port 4Pin_2.54mm
USB interface NO
SD card socket Yes (FAT32 format), support maximum 32G Micro SD Card
* microSD card socket is exclusively used to upgrade Nextion firmware /HMI design
Re: Nextion display plugin
Not sure if all have high ( > 3V3) TX lines.
I saw at least one and better safe than sorry.
Judging from that datasheet, I would say that one should be safe to use on an ESP directly.
I saw at least one and better safe than sorry.
Judging from that datasheet, I would say that one should be safe to use on an ESP directly.
Re: Nextion display plugin
I just got my first nextion and i'm already making some progress. I have to say, it's a bit confusing... someone should make a nice noob summary at some point (pointing at me too, don't worry )
This will be great with openhab / mqtt. I don't plan to use a slider yet, but i may at least test so I can help answer arnold's question.
I think I know the answer to this already but I'll ask anyway.
Is there any way to remotely update the Nextion? I'd love to get this pinned to a wall and halfway usable but i also need a way to update it. I know i'll be tinkering with the interface until i get it just right.
I didn't see much in the way of updating it remotely. I hate the thought of actually having to finalize some sort of design before getting it on the wall. that could take months :O
awesome plugin!
also, all the spec sheets i've looked at from the current ones show +3.3v max on the serial line. maybe older ones used 5v?
This will be great with openhab / mqtt. I don't plan to use a slider yet, but i may at least test so I can help answer arnold's question.
I think I know the answer to this already but I'll ask anyway.
Is there any way to remotely update the Nextion? I'd love to get this pinned to a wall and halfway usable but i also need a way to update it. I know i'll be tinkering with the interface until i get it just right.
I didn't see much in the way of updating it remotely. I hate the thought of actually having to finalize some sort of design before getting it on the wall. that could take months :O
awesome plugin!
also, all the spec sheets i've looked at from the current ones show +3.3v max on the serial line. maybe older ones used 5v?
Re: Nextion display plugin
There is some kind of a summary halfway this topic. I agree, it deserves a proper one, but I simply have no time.waspie wrote: ↑21 May 2018, 01:26 I just got my first nextion and i'm already making some progress. I have to say, it's a bit confusing... someone should make a nice noob summary at some point (pointing at me too, don't worry )
This will be great with openhab / mqtt. I don't plan to use a slider yet, but i may at least test so I can help answer arnold's question.
I think I know the answer to this already but I'll ask anyway.
Is there any way to remotely update the Nextion? I'd love to get this pinned to a wall and halfway usable but i also need a way to update it. I know i'll be tinkering with the interface until i get it just right.
I didn't see much in the way of updating it remotely. I hate the thought of actually having to finalize some sort of design before getting it on the wall. that could take months :O
awesome plugin!
also, all the spec sheets i've looked at from the current ones show +3.3v max on the serial line. maybe older ones used 5v?
Remote update would be awsome, but I honestly have no clue how to do it.
I have my displays direcly connected to WeMos boards without any problem. If you interprete the description of the interface, you see it gives an output of max 3.2 volts, but accepts between 3.3 and 5 volt as a logic high at its input.
Re: Nextion display plugin
I started to create a WIKI in the devices list, but it is in its very preprepre stadium.
https://www.letscontrolit.com/wiki/inde ... IONDisplay
https://www.letscontrolit.com/wiki/inde ... IONDisplay
Re: Nextion display plugin
Nice! I may go in there and at least fix grammatical issues.BertB wrote: ↑21 May 2018, 14:18 I started to create a WIKI in the devices list, but it is in its very preprepre stadium.
https://www.letscontrolit.com/wiki/inde ... IONDisplay
on another note, for you or hopefully anyone else that can answer...
How can I get imported text into the nextion?
Code: Select all
on foyerNextion#temp do
nextion,page0.t0.txt="%[foyerNextion#temp]%"
endon
Code: Select all
on foyerNextion#temp do
nextion,page0.t0.txt="[foyerNextion#temp]"
endon
Code: Select all
on foyerNextion#temp do
nextion,page0.t0.txt="%foyerNextion#temp%"
endon
Code: Select all
2009401 : IMPT : [foyerNextion#temp] : 69.13
2009402 : EVENT: foyerNextion#temp=69.13
2009450 : ACT : nextion,page0.t0.txt="%%"
page0.t0.txt="%%"
***EDIT**** it's %eventvalue% duh. trying to remember all the stuff on the rules tutorial page is hard got it!
Re: Nextion display plugin
ever make any progress on this? I think I'm looking to do something similar. I may end up doing the counting in ESP rules but maybe better to do in Nextion? not sure the best route to gohamster wrote: ↑21 Mar 2018, 23:21 I have trying for days now to get my nextion working as thermostat control
I'm using the following on for the logic on the nextion for a up / increment button
for the increment down buttonCode: Select all
va0.val=va0.val+2 if(va0.val>9) { va1.val=va1.val+1 va0.val=va0.val-10 } if(va1.val>25) { va1.val=va3.val va0.val=va4.val } cov va0.val,t9.txt,1 cov va1.val,t10.txt,2 t4.txt=t10.txt+"."+t9.txt
this then increments t4 as a decimal xx.xCode: Select all
va0.val=va0.val-2 if(va0.val<1) { va1.val=va1.val-1 va0.val=va0.val+9 } if(va1.val<5) { va1.val=va5.val va0.val=va6.val } cov va0.val,t9.txt,1 cov va1.val,t10.txt,2 t4.txt=t10.txt+"."+t9.txt
I then use on touch press event on t4.txton the touch release of t4.txtCode: Select all
print "set-temp" print t4.txt t4.pco=18242
This then allows me to use the up + down buttons to create a setpoint where the font is red, I then press the t3.txt this then changes the font white, and sends the selected value to the espCode: Select all
t4.pco=65535
on the log is see :Does any one know how get thisCode: Select all
send command: set-temp19.11
to my mqtt brokerCode: Select all
Nextion : send command: set-temp19.1116
switches work fine by using the following rulesbut trying to send a value doesn't seem to be possible?Code: Select all
on nextion2#code=3.00 do sendtohttp 192.168.0.48,8080,/json.htm?param=switchlight&type=command&idx=91&switchcmd=Toggle endon
and rather than pressing something to "enter" the number why not a timer that waits 5-10? seconds after last press to send the number? not sure if that's an option?
what about in the rules of ESP do something like
on ESPNXT#code=5 (say 5 is up and 6 is down)
if ( dummval#TMP <= 79 )
dummyval#TMP = dummyval#TMP+1
else
dummyval = 65
endif
timerSet,1,10
endon
on ESPNXT#code=6
if ( dummvalTMP >= 66 )
dummyval#TMP = dummyval#TMP+1
else
dummyval = 80
endif
timerSet,1,10
endon
on Rules#Timer=1 do
Publish /%sysname/dummyval#TMP
endon
this is all untested and off the top of my head. I'm not a rules expert so take this as a general IDEA of what you need to do. Would this not be better then? The rules portion of the ESP handles all the incrementing.
When no button has been pressed then after 10 seconds it publishes the value to MQTT. I think that's how it will work? TD-er?
then with an MQTT import you can set the display to show the setpoint AND update the dummyval so it all stays in sync.
Re: Nextion display plugin
is there a way to make a button with a cropped picture change based on a variable without refreshing the page?
say page0.b0 has picc 1 (on) and 2 (off)
and there's a global variable va0 used to storing that state for when pages are changed.
trying to keep espeasy, the button, and openhab (mqtt) involves some rules. many buttons means many rules and running out of rule space
I could cut down a lot of i could just set the variable to the nextion and make the nextion update the picture based on the variable instead of having to set the variable and the picture.
so say on some mqtt#import do
nextion,page0.va0.val=0
then the nextion sees that va0.val changed and changes the b0 picc = 2
is this possible (without sending a page refresh) ?
say page0.b0 has picc 1 (on) and 2 (off)
and there's a global variable va0 used to storing that state for when pages are changed.
trying to keep espeasy, the button, and openhab (mqtt) involves some rules. many buttons means many rules and running out of rule space
I could cut down a lot of i could just set the variable to the nextion and make the nextion update the picture based on the variable instead of having to set the variable and the picture.
so say on some mqtt#import do
nextion,page0.va0.val=0
then the nextion sees that va0.val changed and changes the b0 picc = 2
is this possible (without sending a page refresh) ?
Re: Nextion display plugin
If you need some extra commands to make the rules easier, just ask.
What I need then is:
- Command-name
- Parameters + description
- Description of the call to the Nextion, based on such parameters.
We can add commands to the Nextion plugin, which can be called from rules.
If the discussion about what commands are needed and how to format them is closing to something useful, we can add an issue on Github about it.
What I need then is:
- Command-name
- Parameters + description
- Description of the call to the Nextion, based on such parameters.
We can add commands to the Nextion plugin, which can be called from rules.
If the discussion about what commands are needed and how to format them is closing to something useful, we can add an issue on Github about it.
Re: Nextion display plugin
Ok, let me think about that. A lot of the stuff is pretty repetitive but I don't know how else to do it. I'll get back to you on Monday when I'm at work and have time to tinker
Re: Nextion display plugin
all right, so I haven't had a lot of time to dedicate to this yet. I've been busy at work and when i get home i'm tending to try and wrap up several of my HA things that are in progress. Replacing bedroom switches with nextions that control the light via relay and my vents via openhab. car presence. etc etc.TD-er wrote: ↑10 Jun 2018, 10:29 If you need some extra commands to make the rules easier, just ask.
What I need then is:
- Command-name
- Parameters + description
- Description of the call to the Nextion, based on such parameters.
We can add commands to the Nextion plugin, which can be called from rules.
If the discussion about what commands are needed and how to format them is closing to something useful, we can add an issue on Github about it.
So one way i found to update the nextion display is to create a hotspot on the page, typically named m0 (this was suggested in their forums by one of the two main guys i think). in the m0 on the nextion IDE you put all your commands for that page similar to the page pre-init stuff.
then you "click" the m0 like:
nextion m0,click (IIRC, i'd have to look at my rules on one of the new units i've set up).
So a function like "Check this box to "click" m0 when a variable is sent to the nextion" hah no idea how you'd do that... that's why you get paid the big bucks :O
A rule looks like
on MQTT#import=1 do
nextion,page0.va1.val=1
TaskValueSet,2,1,1
nextion m0,click
endon
I do this stuff to keep the nextion,esp, and openhab all in sync.
I know you can do "nextion,page0" and it refreshes the page but for whatever reason "clicking" the m0 doesn't redraw the page so it looks much smoother.
Try both, you'll see what I mean.
so i suppose maybe the command could just be "nxtupdate" ? and then the parameter would be the hotspot name. m0, m1, m2 etc. that makes sense i think...right?
on whatever do
nextion, stuff
nxtupdate
endon
Re: Nextion display plugin
Just to be clear, I don't get paid anything for ESPeasy.
It only costs me money to let the postmen (and -women) visit my front door very frequently with bags filled with all kind of stuff from Ali or Banggood.
I really have to free some time to get my Nextion display connected so I could play with it a bit.
Then I am sure I would get annoyed enough by missing features and add them. Until then you'll have to formulate your annoyances for me to convert into C++ code.
Who is online
Users browsing this forum: Google [Bot] and 136 guests