Integration is reporting wrong active preset. - Githubissues

dahlb / ha_carrier

Carrier Infinity Integration for Home Assistant

MIT License

42 stars 3 forks source link

Integration is reporting wrong active preset. #57

Closed myevit closed 1 year ago

myevit commented 1 year ago

System Health details

System Information

version	core-2023.9.2
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	5.15.107+truenas
arch	x86_64
timezone	America/Edmonton
config_dir	/config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4993 Installed Version | 1.33.0 Stage | running Available Repositories | 1294 Downloaded Repositories | 15

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Dashboards

dashboards | 2 -- | -- resources | 6 views | 5 mode | storage

Recorder

oldest_recorder_run | 18 September 2023 at 19:55 -- | -- current_recorder_run | 26 September 2023 at 14:30 estimated_db_size | 271.63 MiB database_engine | sqlite database_version | 3.41.2

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue

it feels like Integration doesn't take into account timezone. sleep schedule should start at 20:00, but HASS showing it two hours ahead

Reproduction steps

1. 2. 3. ...

Debug logs

n/a

Diagnostics dump

No response

dahlb commented 1 year ago

none of the carrier api properly handles timezones, the data is the api pretends utc is the current tz; that shouldn't really matter and to simplify matters even more I updated in https://github.com/dahlb/ha_carrier/commit/99177f83f2ca03b10818b83b552eaec53707275b to have the integration no longer even try to determine the current activity and instead just allow the api's status to provide what it is.