May I suggest this thread. Will probably do some testing on 8.1 during the weekend on a V3.9.
But I’ve found weird readings when the MOSFETs are shared, even on different datalines. But I want to test again for that case. Again, in that thread used an ECO V2, which prevents any good BladeID, and then a V3 in V4 configuration with a V2.2 with a 33k resistor between Data 1 and 3.3V. So now I would like to test on a V3.9 because it has two pins jumped, and thus I don’t know how accurate it is.
On a totally different note, love your new 69 pixel plugs. As soon as I solve some issues with work I will contact to acquire a couple.
Like NoSloppy pointed out, use “scanid” instead of “id”.
Output is normally directed to the terminal that issued the command, so if you run “scanid” in SerialMonitor, you should see the ID there. If you run it from a serial connection, the output should come out there.
Asynchronous output, like the battery monitor is normally printed to the USB Serial monitor, and not printed to the serial port. You can change which terminal receives the async messages with the “make_default_console” command.
There is currently no command to turn off the battery level that is printed out by the battery monitor every 20 (other than modifying the code of course).