Automation to set repeater time

[dinki]

I have a couple repeaters running in power save mode. This appears to cause the time to drift. I would like to create an automation that checks HA time versus repeater time and if it is off by a handful of minutes it would issue a command via service call to have the repeater set the time via cli command.

Is this possible? Can someone share the bit about getting the repeater time and compare to HA server time?

[IoTThinks]

@dinki What is your board?
ESP32 based repeaters with power saving drift less than 3.5 minutes/month now.
https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving15

By right, clkreboot + sync will work for your question.

[dinki]

@dinki What is your board? ESP32 based repeaters with power saving drift less than 3.5 minutes/month now. https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving15

By right, clkreboot + sync will work for your question.

Thanks for this. I am already running that firmware.

I am asking how to trigger. I would rather trigger based on need rather than just scheduling. Is the time value available for the repeater status when it polls for sensor data?

[awolden]

Repeater time isn't exposed as a sensor entity today. Only entity-mapped status fields (battery, queue, counts, uptime) become sensors.

Two paths:

• Schedule the sync every few days, much simpler.
• Call meshcore.execute_command with get_status "RepeaterName", parse the response in a template sensor or script, compare against now(), trigger sync when drift exceeds your threshold.

The trigger-on-need flow needs the second path. Worth a feature ask if you want a built-in time-drift sensor.