Beem Energy Smart-Home-Integration, kostenlos und Open Source
Track your Beem solar kits (BeemBox, Beem On): production, history and savings.
Veröffentlicht von Terdious
- Geräte
- Version 1.2.2
- Erfordert Gladys >=5.1.0
- ★ 0
Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.
Track your Beem solar kits (BeemBox of the 300 W kits, Beem On of the 500 W kits) in Gladys Assistant: live solar power, production of the day, the month, the year and since the start, Wi-Fi signal of each box, savings and payback estimate, and alerts when a box produces less than the others.
The integration reads the Beem cloud, with the account of the Beem application: Beem boxes offer no local access.
Requirements
- A Beem account, with your boxes already installed and visible in the Beem application.
- Gladys Assistant 5.1 or later.
Features
Every box of the account becomes a Gladys device, with:
| Feature | Category / type | Unit |
|---|---|---|
| Solar power | energy-production-sensor / power | W |
| Solar production (index) | energy-production-sensor / index | kWh |
| Production today | energy-production-sensor / daily-production | kWh |
| Wi-Fi signal | signal / integer | % |
- Every box in one request: the Beem cloud answers for all the boxes of the account at once, read every two minutes by default (one minute at least: the cloud refreshes a box about once a minute).
- A box asleep at night (powered by its panels, it switches off at dusk) shows 0 W instead of its last power, as soon as its last report is older than 15 minutes.
- The production index is the feature Gladys' energy monitoring turns into thirty-minute production. The Beem cloud only gives the production of the day and of the month: the integration computes its own index from the month total, and asks for the final total of the previous month on a month change. Nothing is lost at midnight, nor during a container downtime: the next reading catches up the missed production.
- History: at startup, the integration asks the Beem cloud for the production of the past months (24 by default, one request every few seconds, once per month: a past month never changes), then of the past days (hourly history, one week per request; when the cloud is slow to answer, the backfill resumes on its own an hour later, without a restart nor a click). The year, lifetime, savings and payback figures and the browsing of the widgets start there.
- The transport badge reads cloud for a box present in the cloud summary, unreachable for a box missing from it.
Linking the production to the energy monitoring
In Integrations → Energy monitoring, add the Solar production (index) feature of each box: Gladys derives the thirty-minute production and shows it in its energy dashboards, next to your consumption.
Configuration
| Field | Role |
|---|---|
| E-mail, Password | The account of the Beem application (the password is never logged). |
| Refresh interval | Seconds between two reads of the cloud (60 to 3600, 120 by default). |
| Months of history | Months fetched at startup (0 to 120, 24 by default, 0 disables). |
| Feature names language | Language of the feature names of new boxes (English, French). |
| Timezone | Days and months of the Beem cloud, off-peak hours, daily report. |
| Tariff, prices… | The savings estimate (see below). |
| Underperformance threshold | The alerts (see below). |
The Test the connection button signs in to the cloud and lists the boxes found.
Dashboard widgets
The card title is the name of the widget; give a title in its settings to show another one (a box always shows its name).
Four widgets, added from Dashboard → Edit → Add a widget:
- Beem box: one box. Power curve of the day (5-minute averages) next
to the expected curve: what the box would produce at the same yield as the
other boxes (production per kWp), to spot at a glance a box below its
neighbours. Gauge of the power over the peak power, live power, production of
the day and the month, yield of the day (kWh per installed kWp, comparable
between a 300 W and a 500 W kit). Below: time of the last report ("asleep" at
night), Wi-Fi signal (dBm and %), cuts of the day (the moments of 5 minutes
or more the box produced nothing while the others produced, with the time of
the last one: useful for a box that connects and disconnects), yield
against the other boxes (in % of the median, or the underperformance
alert), panels (count, power, orientation in words:
SE -30°= 30° to the east from the south, and tilt∠30°), yesterday, the year, and the total since the first month known. - Solar installation: the whole installation, single-phase (the boxes chosen, or all of them) or three-phase: assign the boxes of each phase (L1, L2, L3) in the widget settings. Periods: 12 hours and day (power curve, one curve per phase in three-phase), week and month (production per day), year (production per month). On the current day: power, day, month, year, share of the peak power, one row per phase (power · production of the day), the phase balance (in warning past the threshold set, 500 W by default), the silent or low-yield boxes. On another period: production, peak power or average per day, best day, yield per kWp and the share of each phase. The assignment mistakes (a box in two phases, or in none) always show.
- Solar savings: savings per month (bars per day), per year (per month) or over all the years; savings and production of the period, payback gauge and date, total since the start, value of one solar kWh, self-consumed and exported shares of the period, CO2 avoided.
- Production history: production per month (bars per day), per year (per month) or over all the years; production, average and best day / month / year of the period, comparison with the same period one year before (same days or months), ranking of the boxes over the period (with their yield per kWp). The Default period setting picks the period shown first.
Changing the period and browsing
Like on the charts of Gladys, the Installation, Savings and History widgets have their buttons:
- Period (the name of the period shown): opens a choice of the periods of the widget. Goes back to the current period.
- Previous / Next: steps back or forward by one period (day, week, month, year…). Previous shows only when there is data before, Next once stepped back.
The period shows in the chart title. It is kept per widget (per settings) while the integration runs: two dashboards showing the same widget with the same settings share their period, and a restart goes back to the default period. On a Gladys older than 5.2, the Period button simply goes to the next period.
Data: the power curves are kept 14 days (5-minute averages). The daily production of the past days is fetched at startup from the hourly history of the Beem application (up to 400 days, one week per request); the Diagnose the boxes action tells how many days each box has. The months come from the monthly history.
Example: 3 phases, 6 boxes
For 3 BeemBox (3 × 300 W kits each) and 3 Beem On (2 × 500 W kits each), one BeemBox and one Beem On per phase: add the Solar installation widget, choose Three-phase, then put in Phase L1 boxes the BeemBox and the Beem On of L1, and so on. Each phase shows 1.9 kWp; the installation 5.7 kWp.
Savings (estimate)
A plug-and-play kit has no grid meter: nothing tells which part of the production the home consumed and which part went to the grid. The estimate therefore rests on your figures:
value of 1 kWh produced = self-consumption rate × solar price
- (1 − rate) × resale price (0 without a resale contract: the surplus of a kit without contract is given to the grid)
- Tariff: Base (one price) or Peak / off-peak (two prices and the
off-peak ranges, e.g.
22:00-06:00or02:00-07:00,13:00-16:00). With peak / off-peak, the solar price is weighted by when the panels produce: the curve measured over the last two days, or a standard daylight curve at first. Off-peak hours at night give a solar price close to the peak price; off-peak hours in the early afternoon lower it. - Self-consumption rate: 100 % by default, realistic for a kit sized on the base load of the home. Lower it if your meter often shows an injection.
- Resale: if you have a contract selling the surplus, tick the box and give the price.
- Cost of the installation: what you paid for the kits (and their installation). The widget then shows the share paid back and the payback date, at the pace of the last 12 complete months.
- CO2 avoided: the carbon intensity of the grid electricity your production replaces (50 g per kWh by default, the order of magnitude of the French mix; 0 hides the figure).
The savings are computed from the energy and the current tariff: a price change applies to the past too. It is an estimate, not an invoice.
Alerts and scenes
Box underperforming
The boxes are compared with each other, size for size (production per installed kWp):
- Silent: a box producing nothing for 30 minutes while the others produce (micro-inverter off, Wi-Fi lost, breaker tripped…).
- Low yield: from 14:00, a box whose yield of the day is below the underperformance threshold (60 % by default) of the median yield of the boxes, on a day bright enough to compare (0.5 kWh/kWp at least). If your boxes have very different orientations, lower the threshold; 0 disables the detection.
The alert shows on the widgets and fires the Box underperforming scene
trigger (filters: the box, the reason), once per box and per day. Variables:
device_name, reason (silent or low_yield), ratio (% of the yield of
the others), today_kwh.
Daily production report
The Daily production report trigger fires once a day, when the solar day is
over (every box at 0 W for 30 minutes after 16:00, or at 22:00 at the latest).
Variables: today_kwh, month_kwh, yield_kwh_per_kwp, savings, co2_kg,
best_box, best_box_kwh. For instance, a message: "☀️ Production today:
{{triggerEvent.data.today_kwh}} kWh, {{triggerEvent.data.savings}} € saved".
Get the solar production
The Get the solar production scene action returns the current figures of a
box, or of the whole installation when no box is chosen: power_w,
today_kwh, month_kwh, year_kwh, load_percent (share of the peak power),
savings_today, savings_month. For instance, a condition "if power_w >
1500" to start the dishwasher when the sun shines.
Updating the integration
Installed from the catalog (the usual case): when a new version is out, the
integration shows an "Update available" badge and its Supervision tab
offers the version, with a link to its notes. Click Update: Gladys pulls the
new image and the new manifest. Your configuration, your devices and the history
(in /data) are kept.
Installed in developer mode (manifest pasted by hand): "Force update" only pulls the image again; paste the up-to-date manifest again to get the new fields.
Troubleshooting
- "The Beem cloud refused the e-mail or the password": use the credentials of the Beem application (not those of the online shop).
- "Beem API rate limit reached": the Beem cloud blocks an account that signs in too often. The integration keeps its token for an hour and, after a refusal, waits 20 minutes before trying again. Avoid connecting the same account to several tools at once (Home Assistant, scripts…), or raise the refresh interval.
- A box is unreachable: it is missing from the cloud summary. Check that it shows in the Beem application.
- No history: run the Reload the history action (for instance after adding a box to the account).
Diagnostic
The Diagnose the boxes action shows, for each box, what the cloud reports right now (power, day, month, signal, last report) and what the integration keeps (index, months of history). Attach it to an issue: it holds no e-mail, no password and no token.
Credits
The Beem cloud has no public API: the addresses and fields used were documented by the community, notably the Home Assistant integration CharlesP44/Beem_Energy (MIT License). The code of this integration is original.
Konfigurationseinstellungen
Diese Einstellungen fragt Beem Energy in seinem Konfigurationsbildschirm in Gladys ab.
| Einstellung | Typ | Pflichtfeld | Beschreibung |
|---|---|---|---|
| Beem account | section | Nein | Sign in with the e-mail and password of the Beem application. The integration reads every solar box of the account through the Beem cloud (no local access exists). |
string | Ja | ||
| Password | secret | Ja | |
| Refresh interval (s) | number | Nein | How often the Beem cloud is read, in seconds (one minute minimum: the cloud refreshes a box about once a minute and limits the accounts that insist). |
| Months of history | number | Nein | Monthly production fetched from the Beem cloud at startup (year, lifetime, savings and payback). 0 disables it. |
| Language of the feature names | select | Nein | Applied to the boxes discovered from now on. |
| Timezone | string | Nein | IANA name: the days and months of the Beem cloud, the off-peak hours and the daily report follow it. |
| Savings estimate | section | Nein | Without a grid meter, the savings are an estimate: the production times the price of the electricity it saves you from buying, plus the resale of the surplus if you have a contract. Leave the mode on None to hide them. |
| Electricity tariff | select | Nein | |
| Base price (per kWh) | number | Nein | |
| Peak price (per kWh) | number | Nein | |
| Off-peak price (per kWh) | number | Nein | |
| Off-peak hours | string | Nein | HH:MM-HH:MM ranges separated by commas, in the timezone above. |
| Self-consumption rate (%) | number | Nein | Share of the production your home consumes at once. A kit sized for the base load is close to 100 %; lower it if the meter often shows an injection. |
| I sell my surplus | boolean | Nein | Off: the surplus is given to the grid (the usual case of a plug-and-play kit). |
| Resale price (per kWh) | number | Nein | |
| Cost of the installation | number | Nein | What you paid for the kits (and their installation): the savings widget shows the payback. |
| CO2 avoided (g per kWh) | number | Nein | Carbon intensity of the grid electricity your production replaces. 0 hides the figure. |
| Alerts | section | Nein | The boxes of the installation are compared with each other (production per kWp installed): a box silent while the others produce, or far below them, is flagged on the dashboard and fires the "Box underperforming" scene trigger. |
| Underperformance threshold (%) | number | Nein | A box is flagged below this share of the median yield of the boxes. 0 disables the detection. |
So installierst du Beem Energy in Gladys
- Öffne in Gladys Integrationen: Beem Energy erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
- Klicke auf Installieren. Gladys lädt das Docker-Image (
ghcr.io/terdious/gladys-beem-energy:1.2.2) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration). - Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
- Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/Terdious/gladys-beem-energy.
Beem Energy benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.
Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.
Über externe Integrationen
Beem Energy ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von Terdious veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.
- Alle Integrationen durchsuchen, native und aus der Community
- Deine eigene externe Integration bauen und veröffentlichen
- Quellcode auf GitHub — Quelle dieser Dokumentation