# Semaine ultra intensive sur Gladys **URL:** \ **Category:** Actualités\ **Created:** [Juillet 23, 2026, 11:43 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374 "2026-07-23T11:43:50Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 23, 2026, 11:43 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/1 "2026-07-23T11:43:50Z")
Hello tout le monde 😃 La semaine prochaine, ma compagne n’est pas là, et j’ai décidé d’en faire la semaine la plus intensive de l’histoire de Gladys. Pourquoi maintenant ? Parce qu’avec Claude Fable 5, ma productivité est en train d’exploser. C’est clairement le bon moment pour mettre un gros coup d’accélérateur. Je viens de passer au plan Claude Code maximal à 216€/mois, histoire de ne jamais être bloqué par une limite au milieu d’une session 😃 **🎯 Objectif n°1 : sortir les intégrations externes.** C’est LE chantier qui va changer la dimension de Gladys, et je veux le livrer au plus vite. 🤝 Et surtout : cette semaine, je serais dispo en permanence. Si vous voulez développer une intégration externe, c’est LE moment de vous lancer. Je veux le maximum d’intégrations disponibles dès le lancement, et je serai là du matin au soir pour échanger, répondre à vos questions et vous faire des retours en direct. N’hésitez vraiment pas, même si vous n’êtes pas sûr de vous ou que vous débutez : vous ne me dérangerez jamais. Plus on est nombreux à pousser cette semaine, plus le lancement sera gros. Et vous, qu’est-ce que vous voulez voir ? • Une fonctionnalité que vous jugez capitale ? • Un live YouTube pendant la semaine ? • Du contenu, des coulisses, un format particulier ? Dites-moi tout, aucun tabou, tout peut être fait ! 📅 Mon programme minute par minute : ![_Users_pierre-gilles_Downloads_semaine_gladys.html](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/c/1/c145c1d4debb6c1f2619c3060bb820e5acab3431.jpeg) Il va falloir rester solide pour tenir, mais je n’ai sacrifié ni le sommeil (8h par nuit, non négociable) ni le sport (tous les jours). Par contre, vie sociale = 0 😃 On se retrouve très vite pour les premiers résultats ! ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [Juillet 23, 2026, 12:45 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/2 "2026-07-23T12:45:08Z")
Cool et merci pour tout 🙂 Comme ça se passe pour le developpement d’une intégration externe ? Je voudrais bien lancer un dev pour Daikin Cloud dans un 1er temps 🙂 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 23, 2026, 12:51 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/3 "2026-07-23T12:51:42Z")
Pour développer une intégration externe, je te conseille vivement de prendre un plan Claude, et de lui donner les informations suivantes 😃 La documentation en français : > **[Créer une intégration externe | Gladys Assistant](https://claude-external-integrations.v4-website.pages.dev/fr/docs/dev/external-integrations/)** > > La façon la plus simple de créer et publier une intégration Gladys Assistant. Sans pull request, sans review de code, sans attente : empaquetez votre intégration dans un conteneur Docker, publiez-la sur GitHub, et n'importe quel utilisateur peut... En anglais: > **[Building an external integration | Gladys Assistant](https://claude-external-integrations.v4-website.pages.dev/docs/dev/external-integrations/)** > > The simplest way to build and publish a Gladys Assistant integration. No pull request, no code review, no waiting: package your integration as a Docker container, publish it on GitHub, and any user can install it in one click. Il y a un template d’intégration : [GitHub - GladysAssistant/integration-template-js: Gladys Assistant Integration template for a JS external integration · GitHub](https://github.com/GladysAssistant/integration-template-js) Ce template est basé sur le SDK JS : [GitHub - GladysAssistant/integration-sdk-js: Gladys Assistant SDK for JS external integration · GitHub](https://github.com/GladysAssistant/integration-sdk-js) Ensuite, pour tester pour l’instant c’est sur une image Docker : ```auto ghcr.io/gladysassistant/gladys-preview:claude-magical-turing-qhh7q2 ``` Ou directement en lançant en local cette PR : [https://github.com/GladysAssistant/Gladys/pull/2665](https://github.com/GladysAssistant/Gladys/pull/2665) ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [Juillet 23, 2026, 1:17 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/4 "2026-07-23T13:17:20Z")
Ok merci 🙂 Je pensais que cela allais utilise ton plan claude code comme pour la factory matterbridge 😉 Je vais essayer de trouver du temps pour voir tout cela ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 23, 2026, 7:23 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/5 "2026-07-23T19:23:08Z")
7 messages ont été scindés en un nouveau sujet : [Apprendre à développer avec Claude Code](https://community.gladysassistant.com/t/apprendre-a-developper-avec-claude-code/10376) ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 23, 2026, 7:23 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/10 "2026-07-23T19:23:33Z")
Un message a été fusionné à un sujet existant : [Apprendre à développer avec Claude Code](https://community.gladysassistant.com/t/apprendre-a-developper-avec-claude-code/10376/8) ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 23, 2026, 7:50 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/11 "2026-07-23T19:50:47Z")
Un message a été fusionné à un sujet existant : [Apprendre à développer avec Claude Code](https://community.gladysassistant.com/t/apprendre-a-developper-avec-claude-code/10376/9) ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [Juillet 27, 2026, 8:08 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/12 "2026-07-27T08:08:58Z")
Bonne semaine Gladys 🚀 Prends aussi soin de toi. Je peux développer l’intégration externe **Philips Hue** mais je n’ai plus de pont pour tester 😕 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 27, 2026, 9:19 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/13 "2026-07-27T09:19:25Z")
Hello tout le monde !! La semaine ultra intensive commence 🔥 Hâte de mettre en production les intégrations externes 😃 ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [Juillet 27, 2026, 9:42 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/14 "2026-07-27T09:42:56Z")
Bon courage et hâte de voir ce que ça donne ! ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [Juillet 27, 2026, 11:27 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/15 "2026-07-27T11:27:41Z")
Si ce n’a pas déjà été fait, une vidéo ou un live sur comment tu utilises les agents cloud avec Anthropic m’intéresserait ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 27, 2026, 12:21 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/16 "2026-07-27T12:21:24Z")
J’avais fait cette vidéo où je montre à la fois Cursor iOS et Claude Cloud : [https://www.youtube.com/watch?v=YAvLE5CnBlQ](https://www.youtube.com/watch?v=YAvLE5CnBlQ) Est-ce qu’il y a quelque chose de spécifique que tu voudrais que je couvre ? 🙂 ---
**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\ **Post date:** [Juillet 27, 2026, 4:53 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/17 "2026-07-27T16:53:08Z")
Purée !! Elle tombe bien cette semaine intensive !! Tu as vu 😅🤔🫣 : Claude Opus 5 est arrivé ^^ ![26858](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/f/d/fdd6ff68ec02ecc129795fbf2d6eec0ba46b1536.jpeg) ![26860](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/4/84c1e41dc209db503513314854776a3687300aee.jpeg) ![26862](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/a/0/a0c50de5e8465d015f933464b415eb7596f3d3b9.jpeg) Et dire que je n’avais pas vu que mon VSCode s’etait mis à jour tout seul dessus 🤦🤣 Je comprend mieux pourquoi il gère tant 😍🥰 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 27, 2026, 5:28 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/18 "2026-07-27T17:28:04Z")
Oui, j’ai vu ! Après, j’ai vu des avis mitigés quand on compare à Fable 5. Je pense que Fable 5 reste meilleur sur les tâches de planning/spec lorsque ça touche à du data model, ou des changements profonds. Mais j’utilise Opus 5 pour tous les bugfix et les développements faciles 😊 ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [Juillet 27, 2026, 6:24 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/19 "2026-07-27T18:24:51Z")
> [@pierre-gilles](#): > > Est-ce qu’il y a quelque chose de spécifique que tu voudrais que je couvre ? 🙂 Je teste ce soir, merci ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 27, 2026, 6:49 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/20 "2026-07-27T18:49:23Z")
J’ai demandé à Grok de compiler les retours sur X par rapport à Claude Opus 5 😃 **Ce que disent les retours sur X (Twitter) en ce moment** Le modèle est ultra-récent, donc les retours sont encore en train de se former, mais voici la tendance claire des posts récents : **Les points très positifs (majoritaires sur le rapport qualité/prix et le coding) :** - « Fable-level intelligence at half the price » → beaucoup de monde reprend ce slogan d’Anthropic et le valide en usage réel. - Excellent pour le coding agentique, les multi-fichiers, les refactors, les agents qui bouclent. Plusieurs disent que c’est un « coding monster » et que le coût journalier a purement divisé par deux (exemple concret : de 54 $ à 27 $ par jour en Claude Code). - Plus efficace en tokens, plus rapide que Fable sur beaucoup de tâches, très bon à suivre les instructions (ce qui était un point faible classique de Claude). - Certains le trouvent même meilleur que Fable sur des tâches précises (physique 3D, certains jeux one-shot, coordination d’agents). - « Super smart, super capable, super creative, rivals Fable 5, doesn’t drain usage at all » → un utilisateur très enthousiaste qui dit qu’Anthropic a enfin tout livré ce qu’on attendait de Claude. **Les points négatifs / mitigés (ils existent et sont récurrents) :** - Comportement parfois « adversatif » : il s’oppose, invente des excuses pour ne pas suivre une consigne simple, ou est trop littéral. - Réponses parfois trop longues, « slopifiées », boucles, oublis d’instructions, erreurs triviales ou mensonges confidents sur des détails. - Sur des tâches très complexes / créatives / long-horizon (ex. tuning d’algo ultra-spécifique, design artistique poussé, planification fine), Fable 5 reste devant pour certains. Un utilisateur a dû repasser sur Fable après que Opus 5 n’y arrivait pas. - Vibe checks et retours type « brilliant in flashes, frustrating in practice » : génial par moments, mais pas toujours fluide au quotidien. ---
**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\ **Post date:** [Juillet 30, 2026, 5:13 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/21 "2026-07-30T05:13:48Z")
Hey @pierre-gilles, Tout roule ? Tu tiens le coup j’espère ? Pourras-tu regarder les PR suivantes pendant ta semaine intensive pour avancer sur intégrations externes ? > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items: > > \- \[\] If your changes affect the code, did you write the tests? > \- \[\] Are server tests passing with coverage? (\`cd server && npm run coverage\`) — Codecov requires \*\*100% coverage on lines changed in this PR\*\* > \- \[\] Did Cypress E2E tests pass? (\`npm run cypress:run\` from repo root, if UI changed) > \- \[\] Is the linter passing? (\`npm run eslint\` on both front/server) > \- \[\] Did you run prettier? (\`npm run prettier\` on both front/server) > \- \[\] If you are adding a new feature/service, did you run the integration comparator? (\`npm run compare-translations\` on front) > \- \[\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[forum\](https://community.gladysassistant.com/)) for testing before merging. > \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code) > \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com). > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com). > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > New device feature category for plug-in battery storage systems (e.g. Zendure SolarFlow, Anker Solix, EcoFlow PowerStream): > > \- server: battery-storage category with battery-level, charge-power, discharge-power, charge-index, discharge-index and battery-energy-remaining types, allowed units (watt, kilowatt-hour, percent) > \- front: category icons and en/fr/de translations > > Needed by external integrations reporting battery storage telemetry, starting with the Zendure integration (Terdious/gladys-zendure). Also to be mirrored in the integration-sdk-js device constants. > > Update: following the index-vs-energy question, the two cumulative counters were renamed \`charge-index\` / \`discharge-index\` to match the core's meter-index vocabulary (energy-sensor.index & the energy-monitoring allowlist). > > The remaining energy-flow telemetry is handled by the companion PR #2693: it adds the missing instantaneous \`power\` type on \`energy-production-sensor\` and introduces two dedicated read-only categories — \`grid-sensor\` (grid exchange: \`input-power\`, \`output-power\`, signed \`power\`, \`input-index\`, \`output-index\`) and \`home-output-sensor\` (power delivered to the home: \`power\`, \`index\`, \`off-grid-power\`, \`off-grid-index\`) — so each subsystem stays distinguishable for automations and future auto-dashboards. This PR keeps its scope to the single new \`battery-storage\` category. > > Claude-Session: https://claude.ai/code/session\_012157sX3FKhVYmndWLJdhfo > > > \## Summary by CodeRabbit > > \* \*\*New Features\*\* > \* Added support for the new \`battery-storage\` device feature category. > \* Included battery metrics such as state-of-charge, charge/discharge power, charged/discharged energy, and remaining stored energy. > \* Added matching units, default ranges, and preview values for battery-storage features. > \* Updated UI icons and provided German, English, and French translations for the new category. > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items: > > \- \[\] If your changes affect the code, did you write the tests? > \- \[\] Are server tests passing with coverage? (\`cd server && npm run coverage\`) — Codecov requires \*\*100% coverage on lines changed in this PR\*\* > \- \[\] Did Cypress E2E tests pass? (\`npm run cypress:run\` from repo root, if UI changed) > \- \[\] Is the linter passing? (\`npm run eslint\` on both front/server) > \- \[\] Did you run prettier? (\`npm run prettier\` on both front/server) > \- \[\] If you are adding a new feature/service, did you run the integration comparator? (\`npm run compare-translations\` on front) > \- \[\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[forum\](https://community.gladysassistant.com/)) for testing before merging. > \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code) > \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com). > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com). > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > Companion of #2682 (battery-storage): this PR adds ALL the non-battery energy-flow telemetry in one place, so the taxonomy lands in two reviewable halves (battery / flows). > > \*\*1. \`energy-production-sensor.power\`\*\* — instantaneous production power (watt, \>= 0) that solar inverters and hybrid storage systems report. Also adds the category's missing \`DEVICE\_FEATURE\_UNITS\_BY\_CATEGORY\` entry (its absence hid the unit selector entirely in the device edit form). > > \*\*2. \`grid-sensor\`\*\* (new category) — a device's own grid exchange: \`input-power\`, \`output-power\`, \`power\` (signed: import +, export −, min \< 0), \`input-index\`, \`output-index\`. > > \*\*3. \`home-output-sensor\`\*\* (new category) — power delivered to the home/loads: \`power\`, \`index\`, \`off-grid-power\`, \`off-grid-index\` (backup port). > > Conventions: \`-power\` = instantaneous watts, \`-index\` = cumulative kWh meter reading (aligned with \`energy-sensor.index\` / energy-monitoring vocabulary); the \`-sensor\` suffix auto-classifies both new categories as read-only. Per-type default units, proper min/max (incl. signed grid power) and en/fr/de labels included. > > Implementation note: the per-category blocks in \`getFeatureDefaultValues\` / \`getFeaturePreviewValue\` are placed before the pre-existing type-only checks (\`type === 'power'\` for light), which would otherwise capture these types. Existing category behavior is unchanged. > > Distinct category/type per flow keeps automations and future auto-dashboards able to tell flows apart — same per-subsystem decomposition as the electric-vehicle categories. Open to renaming. > > Claude-Session: https://claude.ai/code/session\_012157sX3FKhVYmndWLJdhfo > > > \## Summary by CodeRabbit > > \## Release Notes > > \* \*\*New Features\*\* > \* Added “Production power” support on device pages, with correct unit handling (W/kW), sensible default ranges, and updated preview values. > \* Implemented category-specific handling for grid and home output sensors, including power/index preview behavior. > > \* \*\*Improvements\*\* > \* Added missing localized labels for production power in English, French, and German. > \* Updated the corresponding category icon for production power. > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items: > > \- \[\] If your changes affect the code, did you write the tests? > \- \[\] Are server tests passing with coverage? (\`cd server && npm run coverage\`) — Codecov requires \*\*100% coverage on lines changed in this PR\*\* > \- \[\] Did Cypress E2E tests pass? (\`npm run cypress:run\` from repo root, if UI changed) > \- \[\] Is the linter passing? (\`npm run eslint\` on both front/server) > \- \[\] Did you run prettier? (\`npm run prettier\` on both front/server) > \- \[\] If you are adding a new feature/service, did you run the integration comparator? (\`npm run compare-translations\` on front) > \- \[\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[forum\](https://community.gladysassistant.com/)) for testing before merging. An AMD64 preview image is built automatically for non-draft PRs; for ARM64, comment \`/build-arm64\` on the PR. > \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code) > \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com). > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com). > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > Extend the air-conditioning device category with three feature types so integrations can expose the full control surface of an AC unit: > > \- FAN\_SPEED ('fan-speed') with the AC\_FAN\_SPEED values (auto/low/low-mid/mid/mid-high/high/mute/turbo); > \- SWING\_HORIZONTAL ('swing-horizontal') with AC\_SWING\_HORIZONTAL (off/same/opposite); > \- SWING\_VERTICAL ('swing-vertical') with AC\_SWING\_VERTICAL (off/swing/position 1-5). > > Front: dashboard dropdown widgets for the three new types (device-in-room), icons, EN/FR/DE labels, and the air-conditioning mode widget now offers the drying and fan modes and honours the feature supported\_options (#2567) so a device only shows the modes it actually supports (cold-only units, no mute/turbo...). Features without supported\_options keep the full list. > > Extracted from the Tuya air-conditioner work (#2591) so the feature types can be reused by any integration (external integrations included) independently of the Tuya service. > > > \## Summary by CodeRabbit > > \- \*\*New Features\*\* > - Added new air-conditioning controls for \*\*fan speed\*\* and \*\*horizontal/vertical swing\*\*. > - Expanded air-conditioning mode support to include \*\*heating, drying, and fan\*\*. > \- \*\*Improvements\*\* > - Air-conditioning mode selection is now a \*\*dropdown\*\* showing only options supported by the device. > - Fan speed and swing selectors likewise show \*\*only supported choices\*\*. > - Updated \*\*English, German, and French\*\* labels for the new controls, and added matching icons. > > > \### Pull Request check-list > > \- \[x\] If your changes affect the code, did you wr…ite the tests? (30 new/updated tests, mirroring the consumption-from-index suites) > \- \[x\] Are server tests passing with coverage? — 100% coverage (stmts/branch/funcs/lines) on every file changed by this PR > \- \[x\] Did Cypress E2E tests pass? (no UI change — only i18n job labels) > \- \[x\] Is the linter passing? (0 errors) > \- \[x\] Did you run prettier? (front + server) > \- \[x\] compare-translations: the two new job-label keys are added to en/fr/de > \- \[\] Real-life test: will be exercised by gladys-zendure once the battery/energy-flow taxonomy PRs land (15 real devices available for testing) > \- \[x\] API documentation: apidoc comments added for the new endpoint > \- \[\] User documentation: to be added once the whole energy-production story (taxonomy + this pipeline) is merged > > \### Description of change > > Today \`energy-monitoring\` turns cumulative \*\*consumption\*\* meter indexes into > \`thirty-minutes-consumption\` states (then cost). Production meters had no > equivalent: \`energy-production-sensor\` already defines \`index\` and > \`thirty-minutes-production\` types, but nothing computed them. > > This PR mirrors the consumption pipeline for production: > > \- New \`PRODUCTION\_INDEX\_FEATURE\_TYPES\` allowlist (\`energy-production-sensor.index\`). > Production is deliberately NOT added to \`ENERGY\_INDEX\_FEATURE\_TYPES\` — that > would pair a solar index with a \`thirty-minutes-consumption\` feature and count > production as consumption. > \- \`calculateProductionFromIndex\`: 30-minute index deltas → \`thirty-minutes-production\` > states (paired via \`energy\_parent\_id\`), with unit conversion and counter-reset > handling. Uses a production-specific \`ENERGY\_PRODUCTION\_INDEX\_LAST\_PROCESSED\` > device param so a device carrying both consumption and production indexes never > corrupts either cursor. > \- Scheduled in the existing 30-minute job (consumption → production → cost). > \- \`calculateProductionFromIndexFromBeginning\` + new authenticated endpoint > \`POST /api/v1/service/energy-monitoring/calculate-production-from-index-from-beginning\` > to rebuild history after adding a device. > \- Two new \`JOB\_TYPES\` + front i18n job labels (en/fr/de). > > Follow-up (separate PR, needs a semantic decision): deriving > \`thirty-minutes-production-revenue\` / solar savings from these production states — > self-consumption × contract price vs export at a feed-in tariff. > > 🤖 Generated with \[Claude Code\](https://claude.com/claude-code) > > https://claude.ai/code/session\_012157sX3FKhVYmndWLJdhfo > > > \## Summary by CodeRabbit > > \* \*\*New Features\*\* > \* Added scheduled 30-minute energy production calculations derived from meter index data. > \* Added an option to recalculate energy production history from the beginning of available data. > \* Added a secured API endpoint to trigger full historical recalculation. > \* Added job type labels for energy production from index in English, French, and German. > \* \*\*Bug Fixes\*\* > \* Improved production computation for counter resets, missing/invalid linked features, and unit conversion. > \* \*\*Tests\*\* > \* Expanded coverage for the new scheduled flow, historical recalculation, API endpoint, and edge cases. > > > \## Description > > When \`CAMERA\_URL\` points to an HLS manifest (\`.m3u8\`) instead of… an RTSP URL — e.g. Netatmo cameras exposing \`/live/files/{quality}/index.m3u8\` — ffmpeg's HLS demuxer starts reading \*\*3 segments behind the live edge\*\* (\`live\_start\_index\` default = \`-3\`). With Netatmo's 2-second segments this adds ~4–6 s of fixed glass-to-glass latency on top of the re-encoding pipeline. > > This PR passes \`-live\_start\_index -1\` as an \*\*input option\*\* (before \`-i\`), \*\*only when the URL contains \`.m3u8\`\*\*, so: > \- HLS cameras start ~2 segments closer to the live edge (measured ~10–15 s → ~6–8 s end-to-end on a Netatmo NACamera); > \- RTSP cameras are untouched (the option is never added for them). > > \## Tests > > \- Added two unit tests in \`rtspCamera.streaming.test.js\` asserting the ffmpeg args: \`-live\_start\_index -1\` is placed before \`-i\` for an \`.m3u8\` URL, and absent for a non-HLS URL. > \- \`npx mocha ./test/bootstrap.test.js ./test/services/rtsp-camera/rtspCamera.streaming.test.js\`: 20 passing, 0 failing. > \- Validated on a real bench (Gladys + Netatmo NACamera streamed over the LAN through the external gladys-netatmo integration). > > 🤖 Generated with \[Claude Code\](https://claude.com/claude-code) > > https://claude.ai/code/session\_016vS9MKCHbLnYJEhqnnX34K > > \--- > \_Generated by \[Claude Code\](https://claude.ai/code/session\_016vS9MKCHbLnYJEhqnnX34K)\_ ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [Juillet 30, 2026, 5:51 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/22 "2026-07-30T05:51:27Z")
Hello ! Tout roule, je déroule le programme comme prévu 😄 Là, je pars au sport ! 💪 Merci pour tes PRs ! Est-ce qu’elles sont bloquantes ou nécessaires pour la release de ce soir ? Comme c’est déjà une grosse release, je suis en mode _merge freeze_ jusqu’à la publication, sauf s’il y a un vrai bug à corriger. Sinon, je mergerai tout ça juste après le tag de la version ce soir 😊 ---
**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\ **Post date:** [Juillet 30, 2026, 6:47 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/23 "2026-07-30T06:47:23Z")
Boudiou il me tarde de rentrer chez moi ce soir 😍😁 ---
**Author:** ![Terdious](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/terdious/32/6316_2.png) [@Terdious](https://community.gladysassistant.com/u/Terdious)\ **Post date:** [Juillet 30, 2026, 1:33 UTC](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374/24 "2026-07-30T13:33:26Z")
Rien de bloquant pour la sortie, juste permettent d’ameliorer ^^ Visuel et fonctionnalités [Page suivante](https://community.gladysassistant.com/t/semaine-ultra-intensive-sur-gladys/10374.md?page=2)