Zum Hauptinhalt springen

Zendure Smart-Home-Integration, kostenlos und Open Source

Zendure-Integration für Gladys Assistant

Connect your Zendure solar batteries (SolarFlow) to Gladys Assistant through the Zendure cloud.

Auf GitHub ansehenAlle externen Integrationen
Info

Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.

Connect your Zendure SolarFlow / Hyper solar batteries to Gladys Assistant. Gathers read-only telemetry (battery level, charge/discharge power, home output and solar production) from the Zendure cloud, and — optionally — directly from each device's local MQTT broker for LAN-speed, offline-resilient updates with automatic cloud fallback.

Supported models​

SolarFlow 800, SolarFlow 800 Pro, SolarFlow 1600, SolarFlow 2400, SolarFlow 2400 AC, SolarFlow 2400 Pro, and Hyper 2000 (experimental — telemetry mapping to be confirmed by a community tester).

Getting your Zendure cloud key​

The integration authenticates against the Zendure cloud with an authorization key (a base64 token) that you generate once from the Zendure mobile app:

  1. Open the Zendure mobile app and sign in with your account.
  2. Go to the developer / Home Assistant integration section of the app and generate (or copy) your authorization key (also called the "HA key").
  3. Copy that key.

The key is a secret tied to your Zendure account: keep it private. Gladys stores it encrypted and never logs it.

Configuration​

  1. Open the Configuration tab of the integration in Gladys.
  2. Paste your key into Zendure cloud authorization key.
  3. Set the Refresh interval (seconds) — how often the telemetry is refreshed when no real-time update is flowing. The default (30 s) is fine.
  4. (Optional) Enable local MQTT (zenSDK) — see below.
  5. Save. Your batteries appear in the Discovery tab, ready to be added.

When you enable local MQTT in the Zendure app (developer mode), each device publishes its telemetry to a local broker on your network. Turning on Enable local MQTT in Gladys makes the integration read from that broker:

  • Faster: local values update every 1–3 s instead of ~30 s over the cloud.
  • Resilient: telemetry keeps flowing during a Zendure cloud or internet outage.
  • Automatic fallback: if a device goes silent on the local broker, the integration falls back to the cloud on its own, and returns to local as soon as local messages resume — no action needed.

Transport badges​

Each device shows a badge telling you how it is currently reached:

  • Local (green) — served by its local MQTT broker (nominal when local MQTT is enabled).
  • Cloud (blue) — served by the Zendure cloud (nominal when local MQTT is off).
  • Cloud + orange dot (degraded) — the device should be local but is temporarily on the cloud fallback (its local broker went silent). Hover the badge for the reason. This clears by itself when the device resumes locally.
  • Unreachable (red) — the Zendure cloud reports the device offline, or it is silent on every source.

One cloud consumer per Zendure account​

Zendure allows only one cloud consumer per account at a time. If another app uses the same account's cloud connection (Home Assistant, a second Gladys instance…), the two fight over the connection and telemetry becomes intermittent. Prefer the local MQTT path for any second consumer — the local broker has no such limit. The integration warns once in its logs when it detects this take-over pattern.

Troubleshooting​

  • One device shows no values (or is slower than the others) while the rest work. Check its transport badge. If it fell back to Cloud (degraded) while local MQTT is enabled, its firmware may have silently stopped publishing locally. In the Zendure app, toggle that device's MQTT control OFF, save, then ON again — it resumes publishing within a minute. The integration falls back to the cloud in the meantime and returns to local automatically.
  • Too Many Requests in the logs. The integration paces its updates under the Gladys core rate limit and self-throttles when needed; occasional bursts are harmless. Persistent floods usually mean a second integration instance (e.g. a prod and a test container side by side) sharing the same core budget — run only one.
  • Everything is silent right after configuration. Make sure the cloud key is correct: an invalid or expired key shows a "Zendure cloud is unreachable or the cloud key is invalid" status on the Configuration screen.
  • Full detail. Set LOG_LEVEL=debug and read the integration logs from the Gladys UI (or docker logs on the host). Every telemetry-source switch is logged on a telemetry: line.

Konfigurationseinstellungen​

Diese Einstellungen fragt Zendure in seinem Konfigurationsbildschirm in Gladys ab.

EinstellungTypPflichtfeldBeschreibung
Getting startedsectionNeinPaste your Zendure cloud authorization key below (generated from the Zendure mobile app). Your SolarFlow / Hyper batteries then appear in the Discovery tab. Optionally enable local MQTT for LAN-speed, offline-resilient telemetry with automatic cloud fallback. The full step-by-step is in the Documentation link above.
Zendure cloud authorization keysecretJaThe authorization key generated from the Zendure mobile app (base64 token used to reach the Zendure cloud API).
Refresh interval (s)numberNeinHow often device telemetry is polled, in seconds.
Enable local MQTT (zenSDK)booleanNeinRead telemetry from the device's local MQTT broker when available, instead of the Zendure cloud.

So installierst du Zendure in Gladys​

  1. Öffne in Gladys Integrationen: Zendure erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
  2. Klicke auf Installieren. Gladys lädt das Docker-Image (ghcr.io/terdious/gladys-zendure:1.2.0) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration).
  3. Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
  4. Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/Terdious/gladys-zendure.

Zendure benötigt Gladys >=4.62.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​

Zendure 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.

Abonniere den Newsletter von Gladys Assistant

Ein paar E-Mails im Monat zu neuen Releases und Neuigkeiten aus dem Projekt. Verschickt von Pierre-Gilles Leymarie, dem Gründer des Projekts. Jederzeit abbestellbar 🙂
Zuletzt aktualisiert am