Phase 5: Number & select entities in HA (writable parameters)

[liudger]

Phase 5: Number & Select Entities in Home Assistant

Priority: 🟡 Medium
Scope: HA integration
Depends on: Phases 1-3 (#1373, #1374, #1375)
Parent: #1371

Goal

Expose writable parameters as proper HA number and select entities, allowing users to adjust settings directly from the HA UI without needing service calls.

Background

Currently, the HA BSB-LAN integration primarily uses:

• climate entities (temperature setpoint + HVAC mode)
• water_heater entity (DHW temperature + mode)
• sensor entities (read-only values)
• button entities (one-shot actions)

Many BSB-LAN parameters are writable but have no corresponding HA entity. Users must use service calls or the BSB-LAN web interface to change them.

Proposed Number Entities

Parameter	Name	Range	Unit	Description
710	comfort_setpoint	8-30	°C	Comfort mode setpoint
712	reduced_setpoint	8-20	°C	Reduced (night) mode setpoint
730	dhw_setpoint	30-65	°C	DHW nominal setpoint
740	legionella_setpoint	55-70	°C	Legionella protection setpoint
741	legionella_periodicity	1-14	days	Legionella cycle frequency
3266	sg_boost_offset	0-10	K	Smart grid boost temp offset

Proposed Select Entities

Parameter	Name	Options	Description
700	operating_mode	Protection / Automatic / Reduced / Comfort	HC operating mode
1600	dhw_operating_mode	Off / On / Eco / ...	DHW operating mode
1642	legionella_day	Mon-Sun / Daily	Legionella function day
3264	smart_grid_mode	Block / Normal / Boost / Max Boost	SG-Ready mode

Tasks

HA Integration

• Create number.py platform
  • BSBLANNumber entity class
  • Per-parameter min/max/step from device static values
  • Write support via set_native_value() → library set_*() methods
• Create select.py platform
  • BSBLANSelect entity class
  • Enum mapping from BSB-LAN integer values to human-readable options
  • Write support via select_option() → library set_*() methods
• Update __init__.py with new platforms
• Entity naming: use suggested_object_id from parameter name
• Respect multi-circuit: one set of entities per active circuit where applicable
• Add tests for both platforms
• Translation strings for entity names and select options

Library (python-bsblan) — if needed

• Add set_heating() method for HC setpoints (may already exist via thermostat())
• Expose parameter min/max ranges in model metadata
• Expose enum options for select-type parameters

Acceptance Criteria

• Users can adjust setpoints directly from HA dashboard (number entities)
• Users can change operating modes from HA dashboard (select entities)
• All writable entities properly update their state after writes
• Multi-circuit: separate entities per circuit where applicable
• Enum labels are translated and human-readable
• Graceful handling of read-only or unavailable parameters

Design Decisions Needed

• Should number entities use NumberMode.BOX (text input) or NumberMode.SLIDER?
• Should we group entities under device or use entity categories (config, diagnostic)?
• How to handle parameters that exist on some devices but not others? (Already solved by lazy validation)

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!