-
Notifications
You must be signed in to change notification settings - Fork 51
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
Timezone not respected when using mlforecaster #128
Comments
Same here, i use mpc but all optimizations are one hour off. |
I'm going to assume my problem is related too? It started from yesterday morning... If I turn
|
If you are using docker, have you mounted this volume? - '/etc/localtime:/etc/localtime:ro' |
I’m using the HA Addon. So that’s not configurable. |
This is all related to #126. |
No, even after running fit, tune and predict ( in that order) the predict output is 1h behind in my case and prints UTC instead of the local time in the web ui (2023-11-01 08:00:00+00:00 instead of 9am). Just to mention again, MPC shows the right time values in the web ui. So I'm not sure if this is the same issue. |
Hi is this still a current issue? There were some changes in time zone handling of the latest versions. Hopefully this was solved. |
I am closing this as the latest changes on handling TZ should improve this. |
Describe the bug
After changing DST in Europe (CEST->CST) the output of the
mlforecaster
is in the wrong timezone (UTC instead local TZ).To Reproduce
Predict a ML model
Expected behavior
Predict values in the right timezone
Screenshots
![image](https://private-user-images.githubusercontent.com/18382402/278857056-dd7e3e1e-c8a0-4e34-8303-7b8f25aed91b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEwMzg3MTksIm5iZiI6MTcyMTAzODQxOSwicGF0aCI6Ii8xODM4MjQwMi8yNzg4NTcwNTYtZGQ3ZTNlMWUtYzhhMC00ZTM0LTgzMDMtN2I4ZjI1YWVkOTFiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE1VDEwMTMzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWMxYjIyYmQwZTQwNzVlOWQyY2MwOWQ5MmRjZGI3NjE4ZTUwYzJiNDZhN2FhZDAzZjQxNWQ5ZjRiYjNkMDM4NjgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.gps9rx2SWh5W2NvDwnR-Ho65nQRf8q3H1R4q32qL5oo)
Home Assistant installation type
Your hardware
EMHASS installation type
Additional context
![image](https://private-user-images.githubusercontent.com/18382402/278857015-131798db-1470-4fa2-a461-2f2175321f7d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEwMzg3MTksIm5iZiI6MTcyMTAzODQxOSwicGF0aCI6Ii8xODM4MjQwMi8yNzg4NTcwMTUtMTMxNzk4ZGItMTQ3MC00ZmEyLWE0NjEtMmYyMTc1MzIxZjdkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE1VDEwMTMzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM1NGYzNzJmZGIyYzU0Yzk0ZGYwNzc5ZThlNTdhODFlMDMyNjczYmQyNzhjYzJiMjYxNDQwZWRjZDk2NmE4Y2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.0zgkCrS3UCNs1Vvp4EQvJLJLFsdtTRVr0pQ84JPthFQ)
Works using MPC:
The text was updated successfully, but these errors were encountered: