-
Notifications
You must be signed in to change notification settings - Fork 110
Gateway Timezone Configuration
What the "Unconfigured timezone on MyHOME gateway" repair issue means, why it happens, how to resolve it across different gateway models, and how Home Assistant automatically clears it.
TL;DR — When an OpenWebNet gateway has never had its timezone explicitly configured (or was reset), it reports a placeholder sentinel value
999in its WHO=13 time telemetry frames. Home Assistant flags this via a Repair issue (unconfigured_timezone). Once you configure the correct timezone in the gateway's web UI or MyHOME_Suite, the gateway emits a valid offset and Home Assistant automatically dismisses the repair issue.
OpenWebNet gateways manage an internal real-time clock (RTC). The Home Assistant MyHOME integration reads or monitors this clock via WHO=13 (Gateway Management):
-
Dimension 0: Time and Date (
*#13**0##) -
Dimension 22: Time, Date and Timezone (
*#13**22##)
When a gateway's timezone has not been configured in its configuration software or web interface, firmware defaults to emitting a sentinel placeholder value 999 in the timezone parameter:
- Dimension 0 frame:
*#13**0*<HH>*<MM>*<SS>*999## - Dimension 22 frame:
*#13**22*<HH>*<MM>*<SS>*999*<DAY>*<MONTH>*<YEAR>##
- Clock & Timestamp Drift: Without a configured timezone, scheduled scenario triggers and time broadcasts on the SCS bus may diverge from your local daylight saving time or Home Assistant's clock.
-
Diagnostic Reliability: Underlying protocol parsers expect a standard UTC offset format (such as
+01:00or numeric minute offsets). While the integration handles999gracefully without crashing or disconnecting, leaving it unconfigured prevents proper clock synchronization.
Depending on your gateway model, the timezone is configured through its web administration interface or via Legrand / BTicino configuration software.
- Open a web browser and navigate to the IP address of your gateway (e.g.,
http://192.168.1.xxx). - Log in using your installer credentials (default username/password is typically
admin/adminor as configured during commissioning). - Navigate to System Configuration → Date & Time (or Device Settings → Clock).
- Select your geographic region or local timezone (e.g.
Europe/Rome,Europe/Paris,Europe/Amsterdam, or appropriate UTC offset). -
(Recommended) Enable NTP Synchronization (Network Time Protocol) and configure an NTP server (such as
pool.ntp.orgor your local router gateway). - Click Save / Apply and allow the gateway to restart its network services if prompted.
- Launch MyHOME_Suite or TiMyHome on your PC.
- Connect to your gateway via Ethernet (IP) or USB.
- Receive or open the gateway's project configuration.
- Navigate to Gateway Settings / General Parameters → Date & Time.
- Set the correct local time zone and check Automatic Daylight Saving Time (DST) if supported.
- Send the configuration to the gateway and perform a reboot.
You do not need to manually dismiss the repair issue in Home Assistant:
- When the gateway completes its reboot or applies the new clock settings, it broadcasts an updated WHO=13 frame carrying a valid timezone offset.
- Home Assistant listens for this telemetry:
- When a valid offset is received (e.g.
+01:00,+02:00, or standard minute offsets), the integration automatically removes theunconfigured_timezoneissue from Settings → System → Repairs.
- When a valid offset is received (e.g.
- You can also trigger an immediate time verification using Developer Tools:
- Navigate to Developer Tools → Actions (or Services) and call
myhome.sync_timefor your gateway. - Alternatively, open the Lovelace Bus Monitor Card and click Sweep Bus to query WHO=13 status.
- Navigate to Developer Tools → Actions (or Services) and call
- Gateway Identification — Model resolution precedence (SSDP, manual, WHO=13) and model mismatch repairs.
- v2.0 Beta Documentation Hub — Architecture overview, active changes, and beta guides.
- Gateways & Connection Setup ↗ — Hardware profiles, connection resilience, and socket tuning.