mega 0805 is ok after that version change > no p2p anymore ?

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

mega 0805 is ok after that version change > no p2p anymore ?

#1 Post by pwassink » 18 Sep 2019, 12:15

Hello,

Today i've spent some time in getting p2p data > other Esp working again, had to downgrade both esp's to the mega 0805 version
Possible that the changes TD'er made in the code in the next version (release note entry : [ESPeasy p2p] Show remote node as port description on device page are causing this issue ?

In my setup i have several DS18B20 sensors attached toe a Esp8266-12* which record outside temperature at different heights, those were not sent after that update, an on the receiving end there were no Event : node/value name: value messages in the debug visible anymore.

Please investigate / anyone having same troubles ?

User avatar
grovkillen
Core team member
Posts: 3284
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#2 Post by grovkillen » 18 Sep 2019, 13:13

What port number are you using and have you made a power reset after saving the port and controller?
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#3 Post by pwassink » 18 Sep 2019, 14:20

Hi,

Udp-port i do use here is 10466 and all units with that problem had several reboots on both sides

P2p based sensor data displayed and used on several other esp-nodes was working fine for many months but stopped working after mega version 0805,
after downgrading to 0805 they were working again, then i found that there was a change in version mega-20190809 in the p2p code, that is why i hinted on that one . release notes of that version state: [ESPeasy p2p] Show remote node as port description on device page in the "Gijs" part ..

Hope it is more clear now

TD-er
Core team member
Posts: 1656
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#4 Post by TD-er » 18 Sep 2019, 14:54

One of the things that were changed with that update/bugfix is that it now is keeping track of the sender.
Can you remove the plugin on the receiving end and add it again?

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#5 Post by pwassink » 24 Sep 2019, 21:55

I thought i did that by removing the devices on the receiving side,
did not reappear in the mega 0903 version on the receiver after that

Sender is nunning the older version mentioned in the stratpost, is that the reason that it did not re-appear ?

TD-er
Core team member
Posts: 1656
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#6 Post by TD-er » 25 Sep 2019, 00:09

I have to look into the code to make sure, but I thought it was only a breaking change on the receiving end.

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#7 Post by pwassink » 10 Oct 2019, 22:31

sorry,

have been quite busy with other things last week(s).

Found this development document at github explaining teh way to go, sounds like, looks like it, that this is my issue more or less:
https://espeasy.readthedocs.io/en/lates ... hlight=p2p

Will investigate this and try to get it working on the bas of this document with the latest versions tomorrow or the weekend.

will mention the results .

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#8 Post by pwassink » 11 Oct 2019, 21:55

Well,

I spent some time tweaking with 2 nodes trying to figure out why the p2p messages from the remote did not appear .
i mean messages like this in the logging on the receiving end : 2159611: EVENT: graspriethoogte-schuur#Temperature=14.56

I've read the documentation, this did not work as described there, afer i removed controller 2 espeasy P@P Neworking on the sending node and disable / enable the device on the sending node which was sending the messages properly , they were seen at the also on OLD mega 0805 version running esp the also re-appeared on the one running the last Mega version mega-20191003. reappear in the logging, and after a refresh also listed in the devices on the receiver.

Will try to get it working with the new version too, and the IP# and port fields are not usable in teh config of the sending node now, i thought the p2p was mentioned to be a broadcast type networking, and do use it like this to get temperature measurements from the garden and displayit on other ESP's and use them in the house further

update:

The sender is now also running at mega-20191003 and on the ESP testreceiver running same version i can see the event messages as they should

that was in the test environment, when i did an update on the livingroom ESP to 1003 version the data disappeared, and also was missing in the logging, disabling and re-enabling that on the sending node does not solve anything this time, i am confused now ..


Reload 0805 there and Leave it, will look into it tomorrow ..

TD-er
Core team member
Posts: 1656
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#9 Post by TD-er » 12 Oct 2019, 00:34

Can you also test with a version before 20191003?
Just to make sure it has nothing to do with the recent changes I made in parsing numbers.

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#10 Post by pwassink » 12 Oct 2019, 22:25

To be clear,

Tested with the receiving end running on version ESP_Easy_mega-2019****_normal_ESP8266_4M1M / result
Sender is running mega-20191003 normal 4mb , after each reboot of receiver with other sw version it has been running for approximate half an hour
and the sending device has been disabled / enabled for controller 2 which is the p2p comm, what usually solves the comm problem.

20191003 / No P2P data
20190928 / No P2P data
20190926 / No P2P data
20190925 / No P2P data (other naming convention, took the mega core 241 normal version from here on )
20190903 / No P2P data (other naming convention, took the mega core 241 normal version from here on )

20190805 / Works ( other naming convention, took the mega core 241 normal version from here on )


Hope this gives some more info ?

TD-er
Core team member
Posts: 1656
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#11 Post by TD-er » 13 Oct 2019, 20:36

Just to be sure, you did clear (delete) and re-add the receiving task using one of the more recent builds?
It is now checking which unit is sending the value and it will only accept values from that one.
I still need to add this 'source' unit as a changeable setting, so you can see and correct the value.
But have not had time to do it.

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#12 Post by pwassink » 15 Oct 2019, 13:31

Ok,
tried this on a receiving node running at 1003 version, freshly restarted after update from a p2p working 0805 version

Then deleted all "remote" devices, what youve asked for, waited a while (>15 minutes ? )
no go / no devices came up and no remote Event messages in the web-logscreen

in this test both esp's were running on 1003 version, as well the sending as the receiving Esp with P2P

When i "downgraded" the receiving Esp back to the 0805 version (so still with the remote devices removed !)
after a while the did not come back, had to reload the config.dat to resolve that and then it started working again.

TD-er
Core team member
Posts: 1656
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#13 Post by TD-er » 15 Oct 2019, 15:26

OK, I will try to add the "receiver" selector.
Not sure if the device will be added also if the sender was already sending it for a while or maybe you have to 'disconnect' it from the p2p controller and add it again so it will send out its config only the first time.

But I think we already concluded the 'pairing' of the p2p controller could use some redesign.

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#14 Post by pwassink » 15 Oct 2019, 16:10

Yes it could be improved a bit .. :-)

i just tried to disable the sending controller, reboot, enabling it again, reboot, no changes visible at the receiver (device list for the remotes still empty)

TD-er
Core team member
Posts: 1656
Joined: 01 Sep 2017, 22:13
Location: the Netherlands
Contact:

Re: mega 0805 is ok after that version change > no p2p anymore ?

#15 Post by TD-er » 15 Oct 2019, 16:33

I'm just thinking about it...
I now have the filtering on the receiving side, but doesn't it make more sense to have it on the sending side?
We do have the IDX value which can also be used to address a unit number (currently not used for p2p controller).
Not sure if it will break existing setups where people try to have several receivers for a single sender. (like MQTT broker also allows)

Or we could have it on both sides, so then the IDX value should be considered similar to a MQTT topic.

pwassink
Normal user
Posts: 38
Joined: 31 Oct 2016, 08:33
Location: Vorden NL

Re: mega 0805 is ok after that version change > no p2p anymore ?

#16 Post by pwassink » 15 Oct 2019, 19:27

Probably you should leave one sender > multiple receivers intact, use it as a broadcast style protocol.

In my setup i do use this, have a esp which registers outside temp and other weather-sensors at several heigts
those values are sent to domoticz but also broadcasted by p2p to the living quarters ESP's which serve 2 functions,
act as room-sensor-node for Domoticz but also display the outside temp and other params on en local connected lcd / oled in that room.

One sender, many receivers for one dataset

Post Reply

Who is online

Users browsing this forum: No registered users and 23 guests