The emonTx v3 doesn’t divulge it’s node id to the emonESP, therefore when using the EmonSerialTx3eInterfacer in emonHub to connect to the emonTx using that output designed solely for the emonESP you will need to tell it what node ID you would like it to use by using the “nodeoffset” setting in emonhub.conf eg if using the default node id of 8.
There is a loose end in the interfacer code that falls back to using the first data value as the node id if the nodeoffset isn’t defined, that should not happen, at worst case it should default to a nodeid of zero or just log an error and go no further. But the real issue lays with the nodeid not being passed from the emonTx, and that is unlikely to change as it would upset existing emonESP connections.