So I’ve completed deployment of a Meshtower v2 (higher power, 30 dBm) version. I have flashed the device with the Heltec-provided Mechcore v1.16 firmware for the repeater configuration:
https://resource.heltec.cn/download/MeshTower-V2/firmware/meshcore
However, the node appears to be auto-rebooting every X minutes (about 5-10?), which resets the onboard clock.
For example, using the remote management meshcore CLI. I can retrieve the firmware version (which matches the heltec download), get the current clock value (note the 2024 year value). Set the click using the time command and the UNIX epoc value (seconds). Then immediately fetch the clock value again to retrieve the correct time:
> ver
v1.16.0-fe59589 (Build: 13-Jun-2026)
> clock
10:54 - 15/5/2024 UTC
> time 1783810804
OK - clock set: 23:00 - 11/7/2026 UTC
> clock
23:00 - 11/7/2026 UTC
However, if I wait several minutes and again use the command line to retrieve the current time, you see that it has reverted to 2024 - the gab between these two commands was about 5 minutes.
> time 1783810804
OK - clock set: 23:00 - 11/7/2026 UTC
> clock
23:00 - 11/7/2026 UTC
> clock
10:53 - 15/5/2024 UTC
I have been periodically resetting the clock, only to see it revert back to the 2024 value throughout the day. When retrieving overall device status, I will typically see uptime values below 10 minutes:
Battery
100% / 4.21v
Clock • At Login
15/May/2024 3:59AM
Uptime
0 days Oh 6m 45s
Total Airtime
TX: 0 days Oh Om 5s
RX: 0 days Oh Om 5s
Last RSSI
-48
Last SNR
10.8
Noise Floor
-119dB
Packets Sent
Total: 6, Flood: 5, Direct: 1
Packets Received
Total: 8, Flood: 5, Direct: 3
Duplicate Packets Seen
Flood: 1, Direct: 0
Has anyone else experienced similar problems using the meshcore firmware on this hardware configuration?