a6d3c3e1c2
Le canal testing sert powersync-plugin-openmeteo 1.15.2+etm1 (publié le 2026-09-08 à 09:49, avant le Contrat A). Cette version envoie les coordonnées du site sans arrondi ; l'arrondi à deux décimales n'existe que depuis etm2, et etm2 à etm16 ne sont dans aucun canal. La fiche OpenMeteo, la page Prévision PV et la FAQ (trois langues) disaient « arrondies à environ 1 km » sans condition. Elles le qualifient maintenant par version, et la fiche porte un avertissement en tête : version décrite à partir de 1.15.2+etm2. PORTING_STATUS reste `testing` : c'est exact. TODO : retirer ces avertissements quand etm16 ou suivant entre dans testing. Vérifié comme en CI : génération, --check et mkdocs build --strict passent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
42 lines
2.1 KiB
Markdown
42 lines
2.1 KiB
Markdown
# FAQ
|
|
|
|
> Stub — frequently asked questions.
|
|
|
|
## Does ETM PowerSync send my data to the cloud?
|
|
|
|
No. Control runs locally, on the box, and keeps working without internet. The only
|
|
component that connects to the internet on its own is the OpenMeteo weather plugin: it
|
|
sends only the site's coordinates (rounded to about 1 km from plugin version `1.15.2+etm2`; version `etm1` in the testing channel sends them unrounded), its altitude and the
|
|
orientation of the panels. Measurements, consumption and the tariff stay with you.
|
|
Remote access is disabled by default; it opens only if you enable it yourself in the
|
|
app. That is an architectural decision, not an option.
|
|
|
|
## Is the project open source?
|
|
|
|
The foundation (`powersync-core`) and the plugins are under GPL-3.0. So is the optimiser
|
|
client built into the energy engine — everything linked against nymea is. The
|
|
optimisation **business logic**, however (tariff arbitration, forecasts learned from
|
|
your installation), is proprietary: it runs in a separate process, reached through an
|
|
open, documented interface. Optimisation runs at your place, on the box or on a machine
|
|
in your local network.
|
|
That IPC boundary is the heart of the Open Core model — the plugin stays free, the
|
|
business logic stays proprietary.
|
|
|
|
## What is the difference between Community and Pro?
|
|
|
|
Two editions, not three — the prediction layer has not been sold separately since
|
|
2026-10-14; it is part of Pro.
|
|
|
|
- **Community** — the GPL-3.0 foundation, self-hostable: deterministic rule-based
|
|
control, solar surplus, load shedding, [PV production forecast](fonctionnalites/prevision-pv.md)
|
|
from physical models (beta, displayed, not used to decide), REST/MQTT API. No
|
|
subscription.
|
|
- **Pro** — installed by ETM-Schurig: adds tariff arbitration and the prediction layer
|
|
(production and consumption forecasts learned from your installation, heat-pump
|
|
thermal inertia). **No
|
|
subscription either**, and everything stays local.
|
|
|
|
Tariff arbitration and prediction are on the **roadmap**: the Open Core boundary already
|
|
exists, the functions it separates are not all shipped. See
|
|
[etm-powersync.fr](https://etm-powersync.fr/en/hems.html).
|