Maniacs_Mansion/NestQuest
11
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct remaining Home Assistant-derived timezone comments (task e9aa78f3)

Browse Source 
The CONF_TIMEZONE comment claimed the integration always uses Home
Assistant's time_zone and ignores the field; it actually relays the
API's effective application timezone. Also reword two materialize.py
docstrings that described the household date as HA-derived.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dev_agent
2026-09-30 10:54:27 -04:00
co-authored by Claude Opus 5.5
parent 47966af6aa
commit c84f26d979
2 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
custom_components/nestquest/core/const.py
+6 -2
View File
@@ -115,8 +115,12 @@ DEFAULT_AUTOMATION_ENABLED = True
# The household's IANA time zone (e.g. ``America/New_York``) the API
# service reads its clock in. The empty string is the API host's own
# local time. Only an admin sets it (manually, from the admin app);
# nothing sets it automatically. The integration itself always uses
# Home Assistant's ``time_zone`` and ignores this field.
# nothing sets it automatically. The integration relays the API's
# effective application timezone (the coordinator carries it and the
# household sensor publishes it for the panel cards) and never derives
# the application clock from Home Assistant's configuration; the Home
# Assistant / browser zone applies only when the API publishes no zone
# (e.g. an older API).
CONF_TIMEZONE = "timezone"
DEFAULT_TIMEZONE = ""