Read again what I wrote above. The ESP8266 sends the data to ONE specific address, which appears to be emoncms.org. As far as I’m aware there is no mechanism in the ESP8266 software to send it to both the emoncms.org URL AND the emonPi’s URL. So the fact that both are on the same LAN is not relevant as you have it set up at present.
So I believe you are wrong, the emonPi is receiving its data via the radio link. The log shows that there is some received signal at -85 dBm, but the example you’ve picked looks to me more like random noise. If you download the log to your computer and look at the times where data is arriving successfully, you should see messages every 10 s (roughly) that look like this:
NEW FRAME : OK 15 11 0 0 0 38 0 22 0 22 0 0 0 0 0 157 6 0 0 171 6 0 0 151 6 0 0 0 0 0 0 48 117 48 117 48 117 1 0 0 0 (-75)
“OK 15” identifies the data as coming from the emonTx, “(-75)” on the end is the signal strength. -75 is rather low but OK, anything below -80 is marginal and would explain the drop-outs. “unreliable content” means the checksum on the data has failed, so that message is discarded.
I suggest you look at improving the radio link. One cheap and simple way is to provide the antenna with a “ground plane” - there’s a Topic here to read: Improving RF signal strength emonTH emonTX
You can have a ground plane at both ends of the link if you need to.
If that is impractical, then we need some help from a networking expert to advise on how to either get the ESP8266 to send the data to two destinations, or how to get your local emonCMS to forward the data to emoncms.org
It’s easy to send data received via emonHub onwards to emoncms.org, but the data sent by the ESP8266 doesn’t come by that route, it bypasses emonHub completely.