Wrong time zone for estimated charge end, TZ environment variable set correctly about teslamate HOT 9 CLOSED

For reference this is the code:

https://github.com/NirKli/teslamate/blob/f18e12a12c0f28dff7244928cbec0d1afa77861b/lib/teslamate_web/live/car_live/summary.html.heex#L153-L157

current_time = Timex.now()
finish_time = Timex.add(current_time, Timex.Duration.from_hours(@summary.time_to_full_charge))
local_timezone = Timex.Timezone.local()
local_finish_time = Timex.Timezone.convert(finish_time, local_timezone)
formatted_finish_time = Timex.format!(local_finish_time, "%Y-%m-%d %H:%M:%S", :strftime)

The documentation for Timex.Timezone.Local says it will use the TZ variable by default.

I believe that Timex.Timezone.local() is just a wrapper for Timex.Timezone.Local.

https://github.com/bitwalker/timex/blob/main/lib/timezone/timezone.ex#L44-L60

All of these explains why it should work. It doesn't explain why it isn't working.

It could be that there is a bug in the Timex.Timezone.Local.localtz(:osx) implementation. But it looks OK to me.

https://github.com/bitwalker/timex/blob/main/lib/timezone/local.ex#L74-L109

from teslamate.

All car trips etc are correct times, too.

That's a different story as grafana uses your browser's timezone.

from teslamate.

Yep that was it. I didn't know I had to run:

docker compose up -d

Thanks for all the help. Solved now!

from teslamate.

I'm not really sure what's going on. I'm getting help over on TMC as well, and it's a very bizarre thing. Still not any closer to figuring out why it's being finicky for me!

from teslamate.

Just to double-check: Your system time is correct?

from teslamate.

Yes, it's correct. All car trips etc are correct times, too.

from teslamate.

I see. Well, either way, correct system time. One thing that's peculiar that I can't figure out. I renamed the yml file and rebooted Docker, and TeslaMate still works. That would indicate that the yml I'm using is not the "right" one, yes? Well,

NAME STATUS CONFIG FILES
teslamate running(4) /Users/username/Documents/TeslaMate/docker-compose.yml

That's the only one I have, so.. I just don't get it. :(

from teslamate.

I renamed the yml file and rebooted Docker, and TeslaMate still works. That would indicate that the yml I'm using is not the "right" one, yes?

No, as soon as you deployed the docker compose stack you can potentially delete the yml file. Only when you want to change something, restart the containers etc. you need your compose specification.

from teslamate.

I renamed the yml file and rebooted Docker, and TeslaMate still works. That would indicate that the yml I'm using is not the "right" one, yes?

No, as soon as you deployed the docker compose stack you can potentially delete the yml file. Only when you want to change something, restart the containers etc. you need your compose specification.

I see. So is that why the TZ line change isn't doing anything? I added the line and restarted Docker, but that's apparently not enough.

from teslamate.