ThinkNode M5 firmware name mismatch

[MSketcher]

After flashing the M5 companion USB firmware, it returns ThinkNode M2 as the device, instead of ThinkNode M5.

Also, Latest Companion Firmware added ThinkNode M5 support, but I don't see it on the https://flasher.meshcore.co.uk/ device list??

[bertjan]

I've observed the same on my ThinkNode M5:

The latest nightly build also reports a ThinkNode M2, by the way:

I was able to flash the firmware by manually downloading the firmware from https://github.com/meshcore-dev/MeshCore/releases and use the Meshtastic (!) web flasher to flash to the device.

I wasn't able to flash the ThinkNode M5 firmware using the Meshcore flasher.

I'm on an M1 mac, have installed a couple of ESP32 usb drivers (before I installed those, the Meshtastic flasher also didn't work).

Upon trying again, I now was able to flash custom firmware via the Meshcore web flasher. I chose "custom firmware" and flashed https://github.com/meshcore-dev/MeshCore/releases/download/companion-v1.11.0/ThinkNode_M5_companion_radio_ble-v1.11.0-6d32193-merged.bin

The Meshcore serial console connection doesn't seem to work (it connects, but then doesn't respond to any commands). Using the Meshtastic flasher, I am able to connect to the serial console and retrieve some data.
Tried the latest nightly build as well (from https://files.brazio.org/meshcore/nightly/companion/ThinkNode_M5_companion_radio_ble-nightly-09005fa.bin) - the serial console doesn't seem to work in that build as well.
Although I'm not sure the serial console should even work for a BT companion node. For my T1000E, the serial console does work in room server / repeater role, but not in bluetooth companion role.

[IoTThinks]

Yes, it is a bug.
In the source code of the main branch, it says M2 for M5 board.

https://github.com/meshcore-dev/MeshCore/blob/main/variants/thinknode_m5/ThinknodeM5Board.cpp#L46

[IoTThinks]

There is a typo for sensors too.