I was only answering what I thought was your question.
If the sketch is always sending both the radio message and the serial message - in whatever format, this has been the cause of complaints from users of the serial output, because they can and do get multiple copies of the data if the radio is not disabled.
I’ve finally tracked down a V3.4, and the change note says that the difference from V3.3 is in the temperature sensor timing, so I think this will be very close. This only saves the RF Band, group and NodeID in EEPROM, so that’s removed from the list of possibilities.
The principal output is by radio. The DEBUG print does not begin: “MSG: …” and there is no other serial print output of power/current values.
I suggest István either updates his emonTx sketch to the latest CM version (EmonTxV3CM/src at master · openenergymonitor/EmonTxV3CM · GitHub), or you (@borpin) tell him which is the correct Interfacer to use with the plain serial output. He should not use the “RFM69 Native” sketch, because the radio message is only compatible with the emonPiCM
If the Git version is used, it would be prudent to change the final print before the end of the file into a println.
Or, István, if you want a challenge, you can change the print statements in your sketch so that sends the values in the correct format, for example:
MSG:1,ct1:25.6,ct2:36.7, ...(etc)...,vrms:230.1,pulse:0
and continue to use the EmonHubTx3eInterfacer.
