Global TFT display udp and p2p!

[cree]

Hi!
udp data is flowing between 2 modules espeasy "BOJER_00 module" variable A/B:[ALSO_BJ#temperature] C I would like to display this on the TFT display of the espeasy "Display" module!?
How to define the TFT display of the "Display" module A/B: [ALSO_BJ#temperature] value to be printed?
"Display" module" c013 plugin Command unknown ?

All module settings in the video!

https://drive.google.com/file/d/1SYGe0l ... FojUN/view

I don't speak English, just google translator! Tankyou!

[Ath]

Hi, what TFT module are you using? The list of plugins is here

Is that data also sent to the ESP with the Display installed?

[cree]

Hi, what TFT module are you using? The list of plugins is here

Is that data also sent to the ESP with the Display installed?

Just install display firmware version! We can never translate Vscode to Custom.h, which is still a disease!

[Ath]

Hm, that translation is a bit weird.

If you use the ESPEasy P2P network using C013, you can have the data on the ESPEasy Display unit.
Then you can put in the display Lines section [ALSO_BJ#temperature]{D}C and it should show the temperature, and if you set the Interval > 0 it will also update the data automatically.

[cree]

Hm, that translation is a bit weird.

If you use the ESPEasy P2P network using C013, you can have the data on the ESPEasy Display unit.
Then you can put in the display Lines section [ALSO_BJ#temperature]{D}C and it should show the temperature, and if you set the Interval > 0 it will also update the data automatically.

just a celsius symbol tft!
https://i.ibb.co/7X4r9xm/Snap034.jpg

all modul udp Controller Publish:; %sysname%_%tskname%_%valname%=%value%

[TD-er]

I think quite a lot got lost in translation here...

When using ESPEasy p2p you can create a virtual task on another node which will receive the output data of the originating node.

For this you need to follow the steps as described here: https://espeasy.readthedocs.io/en/lates ... mong-nodes

I cannot stress it enough, but make absolutely sure you have set an unique unit ID to each ESPEasy node and those should not be 0 or 255.

So for example you have some task at node A collecting data and a display on node B.
Let's assign node ID 1 to the first one and node ID 2 to the second one.

Now -as described in the link I gave before- you add the p2p controller and enable it on both nodes.
Then you try to share the task on node with ID 1, so you go to the task settings and check to share it with the p2p controller.
N.B. you need to make sure that on the node with ID 2 there is no task on the same task index.

When you have saved this task on the first node, it will magically appear in the task list on the second node, with the same task name and task value names.

Then you can refer to those using the [ALSO_BJ#temperature]{D}C syntax

[cree]

I think quite a lot got lost in translation here...

When using ESPEasy p2p you can create a virtual task on another node which will receive the output data of the originating node.

For this you need to follow the steps as described here: https://espeasy.readthedocs.io/en/lates ... mong-nodes

I cannot stress it enough, but make absolutely sure you have set an unique unit ID to each ESPEasy node and those should not be 0 or 255.

So for example you have some task at node A collecting data and a display on node B.
Let's assign node ID 1 to the first one and node ID 2 to the second one.

Now -as described in the link I gave before- you add the p2p controller and enable it on both nodes.
Then you try to share the task on node with ID 1, so you go to the task settings and check to share it with the p2p controller.
N.B. you need to make sure that on the node with ID 2 there is no task on the same task index.

When you have saved this task on the first node, it will magically appear in the task list on the second node, with the same task name and task value names.

Then you can refer to those using the [ALSO_BJ#temperature]{D}C syntax

Two modul all seting video!
https://drive.google.com/file/d/1SYGe0l ... FojUN/view
problem setting?

[TD-er]

Can you please read my post again?
The Unit number on the "config" tab is set to 0, this is NOT one of the numbers you should use.
You need UNIQUE numbers NOT being 0 or 255 there.

Then you need to have the ESPEasy p2p controller set to ENABLED on both, where you have them DISABLED now.

To share a task between nodes via p2p, you need to use the same task index on both nodes for the shared task.
Thus if you have your task you want to share on the other node at task 2 (your "ALSO_BJ" temperature sensor), you need to make sure it is still a free slot on the other node.

So in short:
Set node named "BOJER_00" to use Unit number "1" (config tab)
Set node named "Display" to use Unit number "2" (config tab)

Enable p2p controller on BOTH nodes (controller tab)

Make sure task index 2 (assuming that's the one you need to share) on the "Display" node is empty.

Enter the config page of task 2 (temperature sensor) on node "BOJER_00" and select to share it with the ESPEasy p2p controller
Save

See the newly created task #2 on the "Display" node.

[cree]

Can you please read my post again?
The Unit number on the "config" tab is set to 0, this is NOT one of the numbers you should use.
You need UNIQUE numbers NOT being 0 or 255 there.

Then you need to have the ESPEasy p2p controller set to ENABLED on both, where you have them DISABLED now.

To share a task between nodes via p2p, you need to use the same task index on both nodes for the shared task.
Thus if you have your task you want to share on the other node at task 2 (your "ALSO_BJ" temperature sensor), you need to make sure it is still a free slot on the other node.

So in short:
Set node named "BOJER_00" to use Unit number "1" (config tab)
Set node named "Display" to use Unit number "2" (config tab)

Enable p2p controller on BOTH nodes (controller tab)

Make sure task index 2 (assuming that's the one you need to share) on the "Display" node is empty.

Enter the config page of task 2 (temperature sensor) on node "BOJER_00" and select to share it with the ESPEasy p2p controller
Save

See the newly created task #2 on the "Display" node.

all setting
https://ibb.co/CPPpZgh
https://ibb.co/F7hnKLN
https://ibb.co/vXL07JJ
https://ibb.co/BN6xJGC
https://ibb.co/4Tw0wmQ

"Enter the config page of task 2 (temperature sensor) on node "BOJER_00" and select to share it with the ESPEasy p2p controller" no index funcion!:(
https://ibb.co/mHQ0gZc

all the settings you suggested!
But still no data tft temperature value!

[Ath]

On BOJER_00 You have the P2P port set to 8080, that should also be set to 8266 (Tools/Advanced), so the P2P Controllers can communicate with each other.
The UDP controller should be disabled (or removed) from both ESP Units, as it will interfere with the P2P network for using the same port.

After a fixing that setting and a reboot of BOJER_00, again save the device task and it should be available also on the Display unit.

NB: Why does BOJER_00 have an old(er) version of ESPEasy? It's best to upgrade all units to the current release (20240822).

[cree]

On BOJER_00 You have the P2P port set to 8080, that should also be set to 8266 (Tools/Advanced), so the P2P Controllers can communicate with each other.
The UDP controller should be disabled (or removed) from both ESP Units, as it will interfere with the P2P network for using the same port.

After a fixing that setting and a reboot of BOJER_00, again save the device task and it should be available also on the Display unit.

NB: Why does BOJER_00 have an old(er) version of ESPEasy? It's best to upgrade all units to the current release (20240822).

Still no data tft lcd i only get a celsius symbol[ALSO_BJ#temperature]{D}C!
https://ibb.co/whS6mr4
https://ibb.co/0nDDY8K
https://ibb.co/dG9FwqL
https://ibb.co/GFnCS1K

[TD-er]

[...]
"Enter the config page of task 2 (temperature sensor) on node "BOJER_00" and select to share it with the ESPEasy p2p controller" no index funcion!:(
https://ibb.co/mHQ0gZc

On the "devices" tab, you see in the 2nd column (under "Task") numbers 1 .. 32
Those are the task index numbers I mentioned.

So the 2nd row on that page is about task index. 2

The IDX value near some controllers (at the bottom of the config page of a task) is only used as some extra parameter.
Not all controllers have or need this extra parameter.
You only need to have a checkbox next to the "p2p" controller, nothing else.

As Ton mentioned and also stated on the page I linked before, you need to check (double check):
- Use unique "Unit Number" (you can set on the "Config" tab, right below "Unit Name")
- Use the same UDP port (Tools->Advanced "ESPEasy p2p UDP port:") and the default is port 8266.
- Reboot ESPEasy after making changes

Ton also noticed you did not run the same build?
If so, please run the latest build.

[Ath]

On the Display unit, check if the P2P created the task for ALSO_BJ with the Temperature value. If that doesn't exist, then go to the BOJER_00 unit and again save the settings for the ALSO_BJ task, so the P2P controller can transfer it to the Display unit.

[cree]

On the Display unit, check if the P2P created the task for ALSO_BJ with the Temperature value. If that doesn't exist, then go to the BOJER_00 unit and again save the settings for the ALSO_BJ task, so the P2P controller can transfer it to the Display unit.

I restart the modules with each setting!
I don't understand what you wrote, I'll create a new version on the display module, but where?!
config!
https://drive.google.com/file/d/1LX1npN ... CYkSo/view

[Ath]

Please re-read this documentation: https://espeasy.readthedocs.io/en/lates ... mong-nodes

[TD-er]

Task 2 on the "Display" unit is not cleared, there is still some task configuration left even though it is disabled.

You need to clear/delete (!!) the task 2 on the "Display" unit.
Then you go to the other unit, go to "edit" task 2 and press "Submit".
This will then send via the p2p controller to the other "Display" unit how task 2 should be configured.

[cree]

Task 2 on the "Display" unit is not cleared, there is still some task configuration left even though it is disabled.

You need to clear/delete (!!) the task 2 on the "Display" unit.
Then you go to the other unit, go to "edit" task 2 and press "Submit".
This will then send via the p2p controller to the other "Display" unit how task 2 should be configured.

Hi!
"display" module TFT only shows 0C, but the temperature of the "BOJER_00" module ALSO_BJ is 23C!

https://ibb.co/vPC6x2S
https://ibb.co/9bzQSjn
https://ibb.co/4FP1Gxr
https://ibb.co/2qDK2JT
https://ibb.co/z7xRwQz

Send to Controller(ESPEasy P2P Networking, enabled) "In module BOJER 00 ALSO_BJ I turn on the setting on the other side Display Send to Controller(ESPEasy P2P Networking, enabled) will be inactive why is this happening because it was enabled before! Endless struggle! What collides with each other?

[TD-er]

You had it working apparently and now you've changed stuff so it is not working anymore.

The task on unit ID 1 which actually is reading the temp sensor is now task index 3?
And it is not sending to the p2p controller?


So maybe you should start over...
You have now task index 1 empty on unit ID 2 ("Display")
Leave it like it is, do not touch this!

Setup the temp sensor as task index 1 on unit id 1 and select to send it to the p2p controller.
N.B. use a different task name as the other one, or remove the temp sensor task from task index 3 before adding this as task 1.
Save

Refresh the "devices" page on unit 2 ("Display")

It should have added a new task on task index 1 and should also be updated.

[cree]

You had it working apparently and now you've changed stuff so it is not working anymore.

The task on unit ID 1 which actually is reading the temp sensor is now task index 3?
And it is not sending to the p2p controller?


So maybe you should start over...
You have now task index 1 empty on unit ID 2 ("Display")
Leave it like it is, do not touch this!

Setup the temp sensor as task index 1 on unit id 1 and select to send it to the p2p controller.
N.B. use a different task name as the other one, or remove the temp sensor task from task index 3 before adding this as task 1.
Save

Refresh the "devices" page on unit 2 ("Display")

It should have added a new task on task index 1 and should also be updated.

Result! Thank you for the many helpers who did this!
https://i.postimg.cc/mDFJW4Qx/IMG-20240826-125706.jpg

[TD-er]

Great!
Have fun with it

[cree]

Great!
Have fun with it

Does anyone know how to reach the sysname path via p2p? Unfortunately, the pin state query does not work %BOJER_00%[Plugin#GPIO#Pinstate#13] tft line does not appear!

BOJER_00 json!

{
"log": "",
"plugin": 1,
"pin": 13,
"mode": "output",
"state": 0
}

global tft display %BOJER_00%[Plugin#GPIO#Pinstate#13] unfortunately nothing appears!!:(

[TD-er]

What should %BOJER_00% represent?

[cree]

What should %BOJER_00% represent?

I need a real-time gpio status check!
espeasy driver1:BOJER_00
espeasy driver2: global tft Display
connection p2p!
I cannot send "BOJER_00" gpio status "global tft Display" line 8 command %BOJER_00%[Plugin#GPIO#Pinstate#13]!

[Plugin#GPIO#Pinstate#13] What is the full path p2p?

https://ibb.co/2nhfGkS

[Ath]

You can not 'pull' data from another unit via P2P, but you can send data to another ESPEasy unit via P2P, lookup the SendTo command:

On the sending node (2):

Code: Select all

on GPIO do // (use an event f.e. after using the monitor command to setup GPIO pin monitoring)
  SendTo,1,"event,sendPinState=%eventpar%,[Plugin#GPIO#Pinstate#%eventpar%]" // Send to remote P2P node 1
endon

On the receiving node (1):

Code: Select all

on sendPinState do // arguments: pin,state
  LogEntry,"State for GPIO %eventvalue1% is: %eventvalue2%"
endon

[cree]

You can not 'pull' data from another unit via P2P, but you can send data to another ESPEasy unit via P2P, lookup the SendTo command:

On the sending node (2):

Code: Select all

on GPIO do // (use an event f.e. after using the monitor command to setup GPIO pin monitoring)
  SendTo,1,"event,sendPinState=%eventpar%,[Plugin#GPIO#Pinstate#%eventpar%]" // Send to remote P2P node 1
endon

On the receiving node (1):

Code: Select all

on sendPinState do // arguments: pin,state
  LogEntry,"State for GPIO %eventvalue1% is: %eventvalue2%"
endon

thankyou!