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 # 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 # 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); # local time. Only an admin sets it (manually, from the admin app);
# nothing sets it automatically. The integration itself always uses # nothing sets it automatically. The integration relays the API's
# Home Assistant's ``time_zone`` and ignores this field. # 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" CONF_TIMEZONE = "timezone"
DEFAULT_TIMEZONE = "" DEFAULT_TIMEZONE = ""
custom_components/nestquest/core/materialize.py
+3 -3
View File
@@ -259,8 +259,8 @@ async def materialize(
no-past guard compares against; it is threaded into every no-past guard compares against; it is threaded into every
:meth:`~.dao_instances.QuestInstancesDao.upsert_if_valid` write. When :meth:`~.dao_instances.QuestInstancesDao.upsert_if_valid` write. When
omitted the host clock (``datetime.date.today``) is used, which is the omitted the host clock (``datetime.date.today``) is used, which is the
historical default. A caller that computed the horizon in Home historical default. A caller that computed the horizon in the
Assistant's configured time zone MUST pass that same date here so a household's application time zone MUST pass that same date here so a
time zone behind the host around midnight is not rejected as "past". time zone behind the host around midnight is not rejected as "past".
``start_date`` is clamped up to the resolved "today" (the same ``start_date`` is clamped up to the resolved "today" (the same
@@ -415,7 +415,7 @@ async def regenerate_for_child(
execution-day anchor even when the call is queued across midnight. execution-day anchor even when the call is queued across midnight.
``today`` optionally pins a caller-resolved household-local date, threaded ``today`` optionally pins a caller-resolved household-local date, threaded
into the delete cutoff and the re-materialization for the same into the delete cutoff and the re-materialization for the same
host-vs-HA time-zone consistency. ``horizon_days`` sizes the host-vs-household time-zone consistency. ``horizon_days`` sizes the
re-materialization window; when omitted it falls back to re-materialization window; when omitted it falls back to
:data:`~.const.DEFAULT_HORIZON_DAYS`. A bool, non-int, or sub-1 value :data:`~.const.DEFAULT_HORIZON_DAYS`. A bool, non-int, or sub-1 value
raises ValueError BEFORE any delete. Returns the number of instances raises ValueError BEFORE any delete. Returns the number of instances