-
-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Time Zone is different to Mealie Time Zone set in ENV, posting wrong meal of the day on API request. #4263
Comments
How is the HA sensor being created? |
Can confirm same happening to me. I'm on EST time, have a similar sensor configured in HA:
My sensor changes to the next meal around 8pm EST time: |
Happening here as well for AEDT (+11 GMT). I am running on V2.04.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still present on 2.2.0 |
from what I can tell, the api endpoint is hardcoded to use UTC timezone as todays date mealie/mealie/repos/repository_meals.py Line 16 in aceed2a
|
First Check
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: 0d06494
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
The text was updated successfully, but these errors were encountered: