All I can do, with very little to go on, is guess that your emonTx V3 is using a standard configuration for the radio packet.
You will need to copy this into your emonhub.conf file, and ensure you don’t have another Node 15 in the file. If your emonTx V3 is not Node 15, you will need to change the file to suit.
emonhub.conf node decoder (nodeid is 15 when switch is off, 16 when switch is on)
See: emonhub/configuration.md at emon-pi · openenergymonitor/emonhub · GitHub
copy the following into emonhub.conf:
[[15]]
nodename = emonTx3cm15
[[[rx]]]
names = MSG, Vrms, P1, P2, P3, P4, E1, E2, E3, E4, T1, T2, T3, pulse
datacodes = L,h,h,h,h,h,l,l,l,l,h,h,h,L
scales = 1,0.01,1,1,1,1,1,1,1,1,0.01,0.01,0.01,1
units = n,V,W,W,W,W,Wh,Wh,Wh,Wh,C,C,C,p
If the above doesn’t work, this file is my list of all radio message formats that I know of, arranged in order of message length, up to and including the emonTx V3.4. If you can see the length of the radio message in the log, this will make the search a lot easier. It gives details of the data, from which the emonHub node definition can be constructed.
RF Messages by length.pdf (33.9 KB)