--set-time improvements and documentation

[roberthadow]

--set-time [TIMESTAMP] is included in the CLI error message, but not in the online documentation. If this is a supported feature, it should be documented.

The command would be more useful if it used the general Meshtastic syntax --set preference PREFERENCE and had the matching -- get avaible. That way it could be used as an admin command.

By POSIX definition, TIMESTAMP should be the integer number of seconds that have elapsed since January 1, 1970, at 00:00:00 Coordinated Universal Time (UTC)

This command sequence works for me in CLI:

MDATE=$(date +%s)
...
    --set device.tzdef 'EST5EDT,M3.2.0,M11.1.0' \
    --set position.time $MDATE \

I do notice that my Heltec v3.2 with firmware 2.6.11 displays New York time as requested.
My Heltec V4 with firmware 2.7.12 prefers to display Zulu time (UTC)

[ianmcorvidae]

The documentation needs updating, but the existing --set-time both accepts seconds since the epoch and works over remote admin. I don't know where you got --set position.time from; that's not anything as far as I'm aware.

The --help output will always be the most updated documentation, in any case, compared to the online docs

[roberthadow]

@ianmcorvidae Hello Ian --

The online doccumentation makes two general assertions:

(1) The default syntax for all preferences is --set preference PREFERENCE

(2) remote admin works only with commands in the form --set preference PREFERENCE or --get preference

Because of (1), I tried --set position.time POSIX. It works.

Yes, remote admin --set-time works.