Hello,
I configure my 2 espeasy to communicate via P2P controller.
under : mega-20200410
The data arrives well on the second one, but the name of the value is missing.
The controller is number 3. the device i number 12 on each of course !
the sender :
the receiver :
As u can see, the data is ok ,but the name is failed !
Q1 : Is is a bug ?
Q2 : Does the received data would be transmit to controller 1 ?
it seems not !
Q3 : What does 'age' column mean in the main tab ?
Weirdness in P2P data transfert.
Moderators: grovkillen, Stuntteam, TD-er
Re: Weirdness in P2P data transfert.
Hmm that sounds like a bug, somewhat.
More like an undocumented feature
What happens here, is that the system info plugin has a relatively new feature.
If no name is filled in, it will use the default generated name of the selected output type.
I guess the p2p related code does only look at the stored names and not at the generated ones.
If you set the names yourself, then the name will be sent (you may need to remove the task on the receiving end and pair again)
But it should be fixed in the code for the p2p sharing.
The "age" in the front page is the last time it was seen (in minutes).
It should be 0 or 1. If the node has a bad WiFi connection, or the ARP packets are missed (Enable Send Gratuitous ARP), then the age is reported much higher.
After 10 minutes, the node is "forgotten", so is not listed again in that list until it is seen again.
More like an undocumented feature
What happens here, is that the system info plugin has a relatively new feature.
If no name is filled in, it will use the default generated name of the selected output type.
I guess the p2p related code does only look at the stored names and not at the generated ones.
If you set the names yourself, then the name will be sent (you may need to remove the task on the receiving end and pair again)
But it should be fixed in the code for the p2p sharing.
The "age" in the front page is the last time it was seen (in minutes).
It should be 0 or 1. If the node has a bad WiFi connection, or the ARP packets are missed (Enable Send Gratuitous ARP), then the age is reported much higher.
After 10 minutes, the node is "forgotten", so is not listed again in that list until it is seen again.
Re: Weirdness in P2P data transfert.
Thank you for your answer.
I try several things.
I have "Generic - System Info" on the both espeasy.
When i try to name the values of the appaired one, the name of values of the local one dissapear
I thought it might be because I have the same device in the receiver, but even deleting it doesn't help.
So impossible to send the received data from the other one !
I try several things.
I have "Generic - System Info" on the both espeasy.
When i try to name the values of the appaired one, the name of values of the local one dissapear
I thought it might be because I have the same device in the receiver, but even deleting it doesn't help.
So impossible to send the received data from the other one !
Re: Weirdness in P2P data transfert.
I can try this !
But the documentation mention thats the ports have to be the same, not 65500 .
But the documentation mention thats the ports have to be the same, not 65500 .
from :https://espeasy.readthedocs.io/en/lates ... /C013.htmlMake sure all nodes have an unique unit number and share the same UDP port.
Re: Weirdness in P2P data transfert.
better but still have a snag !
If I try to edit to tick "send to controller" , it all goes away
If I try to edit to tick "send to controller" , it all goes away
Re: Weirdness in P2P data transfert.
Remember, the plugin info is only sent when the sender device is saved and this description is only processed by the receiver when it has an empty task slot at the receiving end. (yeah I know, not really intuitive)
Who is online
Users browsing this forum: Google [Bot] and 59 guests