4 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5.5	1d28daf8a0	MAINT-10 review: warn when HA did not answer and TZ is UTC; test the 3 s budget ... HA can take minutes to start (2026-10-05, 502 from the proxy). Then TZ holds, which the Supervisor sets from HA's zone, so the hour stays right; only a TZ of UTC there now logs a WARNING asking for a restart. A test pins the 3 s budget on the zone request (a mutant without it survived). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-05 23:24:02 +02:00
glenn schrooyenandClaude Opus 5.5	0b6b34f563	MAINT-10: every pack at N=2, the next DST days, plainer upgrade note ... test_maint10.py part 10: at two inverters both packs get the site zone, the real Controller is identical for 11 UTC and 13 Brussels, and two due packs across 24/25 Oct 2026 and 27/28 Mar 2027 start at the local hour on successive days; a pack freed in the repeated hour does not start there. Part 3 adds 28 Mar 2027. DOCS: an existing install keeps its saved hour, now read as local time; an hour set to make up for UTC goes back to 19. DECISIONS: the SAFETY-83 gate is met; section on two inverters. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-05 21:51:15 +02:00
goodwe-agent	2f5ab1f378	MAINT-10: DECISIONS says where the release note lives ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 23:09:06 +02:00
goodwe-agent	02c0a3dd7b	MAINT-10: maintenance start hour in local time, default 19:00 ... The start hour was compared with the UTC hour, so the shipped 10 started at 12:00 in a Belgian summer. It is now read in Home Assistant's time zone (fallback: the container's TZ, then UTC, one log line says which), and the default moves to 19. DST: a missing hour starts at the first hour after the jump; a repeated hour starts only in its first pass. Stored options are not rewritten: a saved 10 now means 10:00 local (DOCS, CHANGELOG). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 22:52:05 +02:00