2.9.5

2.9.5 — the settings dialog showed no values

Fixed

• The settings dialog opened with empty fields. Home Assistant only fills the fields of a
  sectioned form when the suggested values are nested under the section name
  (add_suggested_values_to_schema copies a section's schema only if the section key is present).
  The options flow passed the values flat, so no field received the stored value: the dialog showed
  empty boxes and the first entry of the device-type list, and pressing Update wrote those empty
  values back.
  If you submitted that dialog on 2.9.3/2.9.4, check Create diagnostic entities and Enable control
  entities — they may be stored as off, which hides all diagnostic and control entities.
• The dialog now keeps what you typed when it has to be shown again after a validation error.
• Host names are accepted (e.g. pontos.fritz.box), not only IP literals — 2.9.3/2.9.4 rejected
  them with invalid IP address.
• Port, interval and timeout keep their integer values (2.9.4).

Added

• testing/diagnose.py — a dependency-free probe that talks to the device without Home Assistant and
  reports which device type answers, the HTTP status and the first payload keys. Run it when the
  integration reports cannot connect or shows no entities:

  python3 diagnose.py 192.168.1.100
  python3 diagnose.py pontos.fritz.box --make "SYR SafeTech+"
  

Verified

• The options form now receives all 14 stored values, checked against Home Assistant 2026.9.3's own
  add_suggested_values_to_schema; with the previous flat mapping 0 of 14 were filled.
• Every platform creates its entities for all five device types, using the payload of the bundled
  simulator.
• Still no Home Assistant runtime available here (2026.9 needs Python >= 3.14), so this is static and
  offline verification, not an end-to-end test.