You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I figured, that the "uptime sensor" uses uptime -s but later adds "Z" (=Zulu =CET) to the timestamp value before sending via mqtt.
According to my testing this leads to wrong values as uptime -s is always local (sorry can't find a man entry to prove that. This is according to some blog posts I found and is confirmed by my own tests)
I changed the script like that - maybe this could be considered for further releases?
I figured, that the "uptime sensor" uses uptime -s but later adds "Z" (=Zulu =CET) to the timestamp value before sending via mqtt.
According to my testing this leads to wrong values as uptime -s is always local (sorry can't find a man entry to prove that. This is according to some blog posts I found and is confirmed by my own tests)
I changed the script like that - maybe this could be considered for further releases?
Basically, I use
data +%z
to get the time zone offset of the current installation to send the correct timestamp
The text was updated successfully, but these errors were encountered: