MeshSense directly connects to your Meshtastic node via Bluetooth or WiFi and continuously provides information to assess the health of your mesh network.
This is just a request for a minor cosmetic change, to show unknown nodes with their hexadecimal ID instead of their integer ID in the Nodes list, map, and packet log. The first-party Meshtastic clients are moving towards showing/using the hex IDs and this would make it easier to integrate with them when doing things like jumping between monitoring with MeshSense and issuing commands with the Meshtastic CLI client when interacting with remote nodes.
For example: Instead of showing the raw integer ID "123456789" in the Nodes list, map, and packet log, it would be useful to show the node's hexadecimal-encoded ID starting with an exclamation point, like "!075bcd15".
This is just a request for a minor cosmetic change, to show unknown nodes with their hexadecimal ID instead of their integer ID in the Nodes list, map, and packet log. The first-party Meshtastic clients are moving towards showing/using the hex IDs and this would make it easier to integrate with them when doing things like jumping between monitoring with MeshSense and issuing commands with the Meshtastic CLI client when interacting with remote nodes.
For example: Instead of showing the raw integer ID "123456789" in the Nodes list, map, and packet log, it would be useful to show the node's hexadecimal-encoded ID starting with an exclamation point, like "!075bcd15".