Skip to content

🚀 Feat(eldom): add sensors for IoT flat boiler device type#45

Open
ptfly wants to merge 2 commits into
qbaware:mainfrom
ptfly:feat/iot-flat-boiler-sensors
Open

🚀 Feat(eldom): add sensors for IoT flat boiler device type#45
ptfly wants to merge 2 commits into
qbaware:mainfrom
ptfly:feat/iot-flat-boiler-sensors

Conversation

@ptfly
Copy link
Copy Markdown

@ptfly ptfly commented Mar 20, 2026

  • Expose heater state, chamber 1/2 temps, and target temp as HA sensors
  • Add chamber-level temperature and mode-aware target temp properties to FlatIoTEldomBoiler

ptfly added 2 commits March 19, 2026 01:03
- Expose heater state, chamber 1/2 temps, and target temp as HA sensors
- Add chamber-level temperature and mode-aware target temp properties
  to FlatIoTEldomBoiler
- Extract _IoTBaseSensor to reduce duplication across IoT sensor classes
- Add sensors: current temp, powerful target temp, eco target temps,
  extra save rate, ready/remain/delayed start/smart end times
- Expose new boiler properties for the added sensors
- Remove redundant async_config_entry_first_refresh calls
- Import FlatBoilerDetails from local iot_models_override
Copy link
Copy Markdown
Member

@danielgospodinow danielgospodinow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! I've left some comments.



@dataclass
class FlatBoilerDetails:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why have the User and flat boiler details in this repo? Those are supposed to be in the pyeldom lib.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This whole file is supposed to be in another repo.

# ─── IoT Flat Boiler Sensors ─────────────────────────────────────────────────


class _IoTBaseSensor(SensorEntity, CoordinatorEntity):
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's avoid having another class and be consistent with how we define other sensors. Even if it means more boilerplate.

self.async_write_ha_state()


# ─── IoT Flat Boiler Sensors ─────────────────────────────────────────────────
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove this comment.


eldom_data: EldomData = hass.data[DOMAIN][entry.entry_id]

await eldom_data.coordinator.async_config_entry_first_refresh()
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did we remove this?



@dataclass
class Device:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This (and the other classes) is a duplicate of what we have already in pyeldom.

martinhrvn added a commit to martinhrvn/homeassistant-eldom that referenced this pull request May 4, 2026
Adds chamber/target temp/heater/ready/remain time properties to
FlatIoTEldomBoiler and corresponding HA sensors. Based on qbaware#45 with reviewer feedback addressed: no override
models module, no section divider comment, async_config_entry_first_refresh kept, naming consistent with existing sensors.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants