Calling meshtastic --set-time 1769686798 causes reboot

[dynamodan]

Calling meshtastic --set-time 1769686798 causes my Heltec Lora32 v4 to reboot, which then loses the time, defeating the purpose of setting the time.

My use case is a node that is connected by USB cable for serial connectivity.

It works to call the --set-time switch, then quickly disconnect the USB cable. The time gets set, but being disconnected then prevents the python CLI from calling a reboot function (I assume this is what's happening). This establishes fair certainty that the bug is in the Python CLI and not the firmware itself.

It would be useful to know what the exact comms between the python CLI and the meshtastic firmware is. Is there a way to use PuTTY or some other client to communicate with a serial-connected node?

Thanks in advance.