The data comes in first to the “emon” part of the emonPi. This either generates (in the case of the c.t. and voltage) the numbers, or receives the data packet by radio (I assume you mean the emonTH when you write “wireless”) and passes it via a serial link into the Pi, where it’s first handled by emonHub. EmonHub then passes it to the Inputs page and only after the input processing does it appear on the Feeds page. You’re actually looking for it at almost the final stage.
The data was certainly getting as far as emonHub, and being forwarded to emoncms.org.
These lines in emonhub.log show that happening:
The “emon” part:
2021-10-07 13:33:21,304 DEBUG RFM2Pi 522093 NEW FRAME : OK 5 0 0 31 3 31 3 158 90 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
The emonTH (I can only find one)
2021-10-07 13:33:23,235 DEBUG RFM2Pi 522094 NEW FRAME : OK 23 247 0 240 0 168 1 24 0 1 0 0 0 (-86)
and sending to emoncms.org:
2021-10-07 13:34:22,075 INFO emoncmsorg sending: https://emoncms.org/input/bulk.json? data=[[1633610036.320914,5,0,773,773,232.79,0,0,0,0,0,0,0],[1633610041.3597727,5,0,723,723,232.95000000000002,0,0,0,0,0,0,0],[1633610046.2913313,5,0,728,728,232.94,0,0,0,0,0,0,0],[1633610051.3249702,5,0,776,776,232.88,0,0,0,0,0,0,0],[1633610056.3679194,5,0,724,724,232.97,0,0,0,0,0,0,0]]&sentat=1633610062&apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y
2021-10-07 13:34:22,221 DEBUG emoncmsorg acknowledged receipt with 'ok' from https://emoncms.org
But then, it stopped until 9:16 am the next day, when it couldn’t open the serial port to receive the data from the front end:
2021-10-08 09:16:17,713 DEBUG MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2021-10-08 09:16:19,716 WARNING MainThread Device communication error - check settings
So my immediate reaction is - the baud rate setting in emonhub.conf is wrong, or something else is hogging the port. The baud rate has been 38400 for a long time, so it’s not likely to be that (but you could try all the baud rates - 9600, 115200 or 57600 have been used at various times).
I don’t understand Github nor MQTT, so @TrystanLea will have to look at that aspect.