API Time Zone is different to Mealie Time Zone set in ENV, posting wrong meal of the day on API request.

mopedy commented 6 days ago

First Check

[X] This is not a feature request.
[X] I added a very descriptive title to this issue (title field is above this).
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the Mealie documentation, with the integrated search.
[X] I already read the docs and didn't find an answer.
[ ] This issue can be replicated on the demo site (https://demo.mealie.io/).

What is the issue you are experiencing?

Setting the TZ in the docker env to Australia/Adelaide does not change the timezone for API requests. This causes the Meal of the day request via API rest request to change @UTC time instead of the set Timezone.

Steps to Reproduce

Meal Plan

Homeassistant Rest Sensor

Docker Container Time

Please provide relevant logs

_mealie_logs (3).txt

Mealie Version

Details Version: v1.12.0 Build: 0d06494bbfc62fc8a1771a85fd308190891d6167 Application Mode: Production Demo Status: Not Demo API Port: 9000 API Docs: Enabled Database Type: sqlite Recipe Scraper Version: 15.0.0

Checks Secure Site: No Server Side Base URL: Yes LDAP Ready: No OIDC Ready: No OpenAI Ready: No Email Configured: No

docker.io/ghcr.io/mealie-recipes/mealie:v1.12.0

Deployment

Docker (Synology)

Additional Deployment Details

No response

boc-the-git commented 6 days ago

How is the HA sensor being created?

mopedy commented 5 days ago

I create it as sensor entity in config.

Not sure if it helps but it has the correct meal in the calender in HA, just the picture in camera entity that is created with the generic camera does not match until 09:30am

http://192.168.1.116:9925/api/media/recipes/{{states('sensor.mealie_todays_meal_id')}}/images/min-original.webp

It seems Mealie integration and Mealie use the set TZ of ACST which is UTC +9:30 but the API uses UTC.

Thanks for looking into this.

mealie-recipes / mealie