Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .github/INITIAL_PR.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
Adds an experimental ESPHome configuration for local Home Assistant control of a Eurom Mon Soleil DSP 400 WiFi heater through its Tuya MCU. The maintainer is still testing; the 650/770 W and Swiss-plug variants are explicitly unverified candidates.

Includes the sanitized configuration, two approved device photographs, setup and datapoint documentation, a hardware test checklist, contribution/AI instructions and dummy-secret validation CI. Public preparation removes the literal fallback AP password, private device address, placeholder area and unrelated Home Assistant helper while preserving the original heater mappings.

Factory backup/restoration, initial flashing and the internal four-pin connector pinout remain TODO. The manufacturer manual and private original configuration are not included. The README documents M/P behavior, unknown timer persistence and the DP101 write interaction in the climate component.

Validation: ESPHome 2026.10.1 configuration validation and C++ generation results are recorded in TESTING.md. Full firmware/toolchain compilation and hardware testing of this public example are not claimed; see that record for any environment limitation. The workflow has not run on GitHub before publication.

Created with assistance from ChatGPT & Codex (OpenAI). Maintainer review and supervised hardware verification remain necessary.
19 changes: 19 additions & 0 deletions .github/ISSUE_TEMPLATE/compatibility-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
name: Device compatibility / behavior report
about: Report a tested model or reproducible behavior with redacted evidence
title: "[Eurom DSP] "
labels: ""
assignees: ""
---

Model and article number:
Module / PCB revision (or unknown):
ESPHome and Home Assistant versions:
Configuration commit:

Initial mode, ECO and timer state:
Steps / expected behavior:
Observed behavior and redacted datapoint changes:
What was not tested:

Do not upload credentials, private logs, flash dumps or the manufacturer manual. Never create hazardous physical conditions to reproduce an issue.
16 changes: 16 additions & 0 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
## Problem and resulting behavior

Describe what changes and why. Identify the device/model and relevant datapoints.

## Validation

- Software checks and exact ESPHome version:
- Hardware tested (model/article number/revision), or explicitly not tested:
- Expected and observed behavior / remaining unknowns:
- AI assistance used and human review performed:

## Publication review

- [ ] No credentials, private addresses, identifying device logs, firmware dumps or manufacturer manual included.
- [ ] Experimental status and untested model limitations remain accurate.
- [ ] Relevant documentation/test record updated; physical claims are backed by evidence.
25 changes: 25 additions & 0 deletions .github/workflows/validate-esphome.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
name: Validate ESPHome

on:
push:
pull_request:
workflow_dispatch:

permissions:
contents: read

jobs:
validate:
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v5
- uses: actions/setup-python@v6
with:
python-version: '3.12'
cache: pip
cache-dependency-path: requirements-dev.txt
- name: Install pinned ESPHome
run: python -m pip install -r requirements-dev.txt
- name: Validate YAML and generate C++ with temporary dummy secrets
run: python scripts/validate-esphome.py --generate
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ firmware/
*.pdf

# Local tooling
/PUBLISHING.md
.venv/
venv/
__pycache__/
Expand Down
30 changes: 30 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Instructions for coding assistants

## Scope

This repository contains public Home Assistant and ESPHome examples. Read the relevant project README, datapoint notes, test record and TODO before changing a device configuration. Keep changes small and reviewable. Explain behavior changes and preserve existing entity names and secret names unless a migration is documented.

## Privacy and publication

- Never commit actual credentials, API keys, private addresses, household details, private logs, firmware images or flash backups. Use `!secret` and explicit example values.
- Only the supplied public configuration and two approved device photographs may be published from the initial source material. Do not add the manufacturer PDF or extracted manual pages. Link to the manufacturer instead.
- Never assume `.gitignore` removes already tracked secrets. Inspect the staged diff and filenames before a commit.
- Do not embed a remote GitHub package dependency, telemetry or a cloud service into a working local configuration without an explicit request.

## Hardware evidence and heater behavior

- Distinguish maintainer observations, manufacturer descriptions and new contributor measurements. Never fabricate logs or mark untested variants as supported.
- Preserve the existing datapoint IDs, enum values, board and UART pins unless a proposed change includes evidence for that hardware revision.
- Do not invent connector pinouts, electrical isolation, voltage levels, module identities or flashing/backup procedures. GPIO assignments in YAML do not establish connector order.
- M mode is manual heat control; setting a target temperature does not make M mode thermostatic. Do not describe it otherwise.
- DP101 is shared by the climate component and a writable select. Account for the climate component writing it on Heat commands. Document and test changes to this interaction.
- Do not add automatic heating on boot, reconnect or time synchronization. Do not bypass safety mechanisms or create artificial fault conditions to test protections.
- Keep factory-backup, initial-flash and four-pin-connector instructions as TODO until verified evidence is provided. A qualified contributor may submit a PR with measurements, orientation photos and revision details.

## Validation and reporting

- Use the pinned ESPHome version in `requirements-dev.txt`. Run `python3 scripts/validate-esphome.py --generate` after configuration changes; use dummy credentials only.
- Validation and C++ generation are not firmware compilation, hardware verification or a safety assessment. Report exactly which checks ran.
- Hardware test records must state model/article number, module/PCB revision if known, ESPHome version, steps, expected result, observed result and date. Explicitly identify tests that were not run.
- Keep experimental status until the maintainer has evidence to change it. Update README, test notes and changelog when behavior changes.
- Describe AI assistance in the PR and preserve human authorship. Never claim the assistant physically tested a heater.
20 changes: 20 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Contributing

Small, focused pull requests are welcome, including documentation and compatibility reports.

1. Read the project's README and TODO. Open an issue first for a substantial behavior or hardware change.
2. Work on a branch. Keep private device YAML, credentials, firmware and backups outside tracked files.
3. Describe the problem, resulting behavior and evidence. For a new model, include the article number, module/PCB revision if known and a redacted datapoint report. A similar enclosure or wattage is insufficient evidence.
4. Install `requirements-dev.txt` in a virtual environment and run `python3 scripts/validate-esphome.py --generate`.
5. For behavior changes, record relevant supervised device tests using the project test checklist. State clearly when hardware testing was not possible.
6. Review `git diff --cached` and `git diff --cached --name-only` before committing. Do not attach the manufacturer manual or raw device logs.

Never intentionally obstruct, tip, overheat or fault a heater to test this project. Follow the manufacturer's operating instructions. Hardware work belongs with a competent, qualified person; no verified internal wiring guide is currently provided here.

## AI-assisted contributions

AI assistance is allowed. Contributors remain responsible for correctness, permission to contribute material, privacy and safety. Briefly disclose the tools used and what was checked in the PR. Follow [AGENTS.md](AGENTS.md); do not substitute plausible AI-generated mappings or pinouts for measurements.

## License

By contributing original material, you agree to provide it under the repository's MIT License. Only submit photographs and other material you have permission to redistribute. Do not upload manufacturer firmware or manuals.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Community configurations and notes for Home Assistant and ESPHome, developed and

Each project documents its own requirements, observations and limitations. Device compatibility is only claimed when supported by hardware evidence.

See [CONTRIBUTING.md](CONTRIBUTING.md) for contributions, [AGENTS.md](AGENTS.md) for AI-assisted work and [PUBLISHING.md](PUBLISHING.md) for the initial GitHub setup.
See [CONTRIBUTING.md](CONTRIBUTING.md) for contributions and [AGENTS.md](AGENTS.md) for AI-assisted work.

## Credits and license

Expand Down
11 changes: 11 additions & 0 deletions esphome/eurom-mon-soleil-dsp/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Changelog

## Unreleased - public starter prepared 2026-10-29

- Added the experimental Eurom Mon Soleil DSP project, attributed datapoint observations and the two maintainer-supplied photographs.
- Preserved the original board, UART, DP mappings, entity names and encrypted OTA configuration. No heater-control logic change was intentionally introduced.
- Replaced the literal fallback AP password with a `!secret` reference. Wi-Fi and API credentials remain secret references; example values contain no working credentials.
- Removed the private `wifi.use_address`, placeholder area and unrelated Home Assistant helper text sensor. No heater behavior depended on that helper in the supplied YAML.
- Added an ESPHome minimum version of 2026.9.0 for encrypted OTA syntax and a 2026.10.1 validation baseline.
- Added setup notes, raw DP12 limitations, M/P distinctions, DP101 write-path caveat, testing checklist and evidence requirements.
- Left manufacturer backup/restoration, initial flashing, module identification and connector pinout as explicit TODOs. The manual is excluded from the public project.
34 changes: 34 additions & 0 deletions esphome/eurom-mon-soleil-dsp/DATAPOINTS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# Datapoints and evidence

## Provenance

The maintainer's supplied YAML says the following observations were confirmed with logs and button tests on **2026-10-28** on a 400 W unit. Raw logs were not included with the public starter, so these are attributed maintainer observations, not independently repeated measurements. The Tuya product ID in the source is `wv9d5ocs76u6maqj`; it is a product identifier, not a per-device credential or compatibility guarantee.

| DP | Reported type | Meaning/value | Evidence and limits |
| --- | --- | --- | --- |
| 1 | Boolean | Power / standby | Maintainer reports confirmed on/off |
| 2 | Integer | Target 0-37 °C; ECO selects 16 °C | Maintainer reports confirmed; thermostat requires P mode |
| 3 | Integer | Room temperature, °C | Maintainer reports confirmed; ambient accuracy and external probe unverified |
| 4 | Enum | 0 = Manual (M), 1 = Thermostat/program (P) | Maintainer reports confirmed with MODE button |
| 101 | Enum | 0 = heating/sun, 3 = off | Maintainer reports confirmed; bars button in M, thermostat in P; writable through both select and climate Heat path |
| 102 | Boolean | ECO fixed 16 °C / EC display | Maintainer reports confirmed; transition behavior still needs a test record |
| 12 | Bitmask | Raw fault indication; 0 observed/described as no fault | Listed in source; nonzero values and individual bit meanings not verified |

No changed datapoint was observed when testing the remote's open-window control. Do not assign a guessed DP to it or invent a corresponding entity.

## UART assumptions

| Setting | Value in supplied YAML |
| --- | --- |
| ESPHome platform | ESP8266 |
| Board profile | `esp01_1m` |
| ESP RX | GPIO13 |
| ESP TX | GPIO15 |
| Baud rate | 9600 |
| Serial logger | Disabled (`baud_rate: 0`) |

These values describe firmware settings for the test installation. They do not identify the exact module, confirm flash size, specify connector pin order or prove safe voltage levels/isolation. GPIO15 is an ESP8266 boot strap pin; the existing hardware must maintain correct boot conditions. Do not rewire based only on this table.

## Evidence needed for changes

For a mapping change or new device, provide model/article number, revision, ESPHome version and a redacted sequence showing initial state, one physical/HA action, changed DP value/type and resulting display/heat indication. Include conflicting observations and unknown enum values. Keep private identifiers out of logs, and never intentionally trigger dangerous physical fault conditions.
Loading
Loading