I haven’t, because emonhub receives the data from the emonTx just fine with the wires as they are…
Yes! I also tried it with GPIO7(BCM 4) before modifying the script and results were the same…
So the setup on my SD card is slightly different to that described in the docs, despite following the exact same instructions (and it was already installed as-is anyway when I received the prewritten SD card from the shop - running the script, or doing it manually changed nothing).
I might be misunderstanding how symlinks work so bear with me…
The instructions in the README.md file (in the /opt/openenergymonitor/avrdude-rpi/ folder and on github and elsewhere) imply to me that you should end up with a file named “avrdude-autoreset” in /usr/bin/ and that there should be a symlink to this file in the same folder named “avrdude”, with the actual original avrdude renamed “avrdude-original”.
Running the script doesn’t leave me with a “avrdude-autoreset” file, only an “autoreset” file…?
Why are there two copies of these files, one in /usr/bin/ and another in /opt/openenergymonitor/??? The version in /opt/openenergymonitor/ still has GPIO7 as the reset pin so clearly this is not the version being run when I try it…

Did you stop
emonhub
first?

I’ve also stopped the emonhub service first and checked via cat/dev/ttyAMA0 and the emonTx is still outputting data on the serial port but nothing else appears.