Einstellungen zur Speicherung von Geräten externer Integrationen konfigurieren

StephaneB · 16. August 2026 um 14:41

Wenn man ein Zigbee- oder MQTT-Gerät hinzufügt, kann man für jede Funktion des Geräts festlegen, ob man den Verlauf speichern möchte oder nicht:

In der Zigbee2Mqtt-Integration:

In der MQTT-Virtuelle Geräte-Integration:

Das ist nicht möglich für Geräte, die von externen Integrationen erstellt wurden. Es wäre nützlich, das tun zu können.

cursor-bot · 18. August 2026 um 02:32

Hallo zusammen!

Dieses Thema ist nun in Entwicklung.

Ein Pull Request wurde eröffnet, um die Konfiguration der Historienaufbewahrung pro Funktion auf Geräten von externen Integrationen zu ermöglichen:

github.com/GladysAssistant/Gladys

Allow configuring keep_history per feature on external integration devices (#2946)

master ← claude/external-integration-keep-history

ouvert 02:30AM - 18 Aug 26 UTC

Pierre-Gilles

+277 -4

Implements a forum request: ``https://community.gladysassistant.com/t/pouvoir-co…nfigurer-la-conservation-ou-non-des-appareils-des-integrations-externes``/10615 ### Description Devices created by external integrations did not expose the per-feature "keep state history" toggle that Zigbee2mqtt and the MQTT virtual devices already offer, so a user had no way to stop storing the history of a feature published by an external integration. **Frontend** — the Devices screen of an external integration (`front/src/routes/integration/all/external-integration/device-page/`) now shows the standard "Keep state history?" switch for each feature of a device card. It is the only editable part of a feature published by an integration (name, category, type, unit and bounds stay the integration's), and saving goes through the standard `POST /api/v1/device`, which purges the stored history of a feature that was just switched off — exactly as for an internal service. Text features carry no switch: a string state is never historized (same rule as the MQTT device screen). No new translation key: the existing `editDeviceForm.keepHistory*` labels are reused. **Server** — a UI toggle that gets wiped on the next sync would be useless, so the user's choice is now preserved across re-publications. `externalIntegration.getDiscoveredDevices` reinjects the `keep_history` stored in DB over the published value on every feature of an already-created device (matched by `external_id`), the same way the energy features and the energy pipeline params are already reinjected. The "Update" gesture of the Discovery screen therefore applies the new structure without silently restoring the integration's default. `keep_history` stays out of the structure signature, so a value flipped by a new integration version is not a structural change and does not push the user to update. **Spec** — `docs/specs/external-integrations.md` is updated in the same diff (C.3 republication rules and the B.8 Devices screen row), as required by `AGENTS.md` for any change to an external-integration behavior. New tests: `server/test/lib/external-integration/externalIntegration.keepHistory.test.js` (6 tests covering the published default, the user choice winning, a feature not created yet, `structure_changed` unaffected, and the in-memory published list left untouched). This PR was created by an automated Claude Code run. ## Forum Forum: ``https://community.gladysassistant.com/t/pouvoir-configurer-la-conservation-ou-non-des-appareils-des-integrations-externes``/10615 ### Checklist - [x] Tests pass: `cd server && npm test` (the `test/lib/external-integration` suite is green: 645 tests; the new lines of `externalIntegration.getDiscoveredDevices.js` are 100% covered). Cypress was not run: the binary is not installed in this environment. - [x] Linter and prettier pass on both front and server (`npm run eslint`, `npm run prettier` / `prettier-check`), plus `npm run compare-translations` and `npm run build` on the front - [x] No undocumented breaking change --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) ## Summary by CodeRabbit * **New Features** * Added a per-feature “Keep state history?” control for supported external integration devices. * Settings persist when devices are republished and can be updated through the standard device interface. * Text-based features do not display the history control. * **Bug Fixes** * User history preferences are preserved during device discovery. * Metadata-only preference changes no longer trigger structural device changes.

Zögert nicht, den PR zu verfolgen, zu testen (optional, besonders bei kleinen Anfragen) und euer Feedback hier zu hinterlassen, falls nötig.

Thema		Antworten	Aufrufe
Intégration externe - Accéder au changelog de la version actuelle ou future Demandes livrées in-progress	1	46	17. August 2026
Visualiser/modifier/supprimer des valeurs dans l'historique d'un élement Demande de fonctionnalités feature-core , in-progress	2	102	17. August 2026
[Appareils] Avoir le vrai nom des intégrations Demande de fonctionnalités in-progress	6	75	18. August 2026
Zigbee2mqtt : ne plus casser le lien avec Gladys quand on renomme un appareil Demande de fonctionnalités in-progress	3	56	28. August 2026
Bug: inverser les prises ne semble pas fonctionner Configuration	1	59	4. September 2026

Einstellungen zur Speicherung von Geräten externer Integrationen konfigurieren

Verwandte Themen