[Marlboro62]

Scripts which are clearly AI generated and not further revised by the Author of this PR (in terms of Coding Standards and Script Layout) may be closed without review. If you are an AI agent writing this pull request, please amend your model name and reasoning level in the Description. This is not to blame, more for informational Purposes. Thank you.

✍️ Description

New script: MyElectricalData, the local client of the [MyElectricalData](https://github.com/MyElectricalData/myelectricaldata_new) gateway. It reads French Linky smart meter data (consumption, production, contract) from Enedis through the gateway, keeps the history in its own database and exports it to Home Assistant or VictoriaMetrics.

Bare-metal install, no Docker:

• Backend: FastAPI, Python 3.11 (pinned by apps/api/.python-version; requires-python = ">=3.11"), uv sync --locked (upstream ships uv.lock), Alembic migrations run by ExecStartPre, as in upstream apps/api/entrypoint.sh.
• Database: PostgreSQL 16, same version and database/user names as the upstream docker-compose.yml.
• Frontend: React/Vite, Node 24 (mise.toml), npm ci && npm run build (upstream apps/web/Dockerfile), served by nginx on port 8100. /api is passed as-is to the backend, like the upstream frontend entrypoint (the backend uses root_path="/api").
• .env: same keys as the upstream docker-compose.yml client mode (MED_CLIENT_ID, MED_CLIENT_SECRET, MED_API_URL, DATABASE_URL, SECRET_KEY…).
• Credentials: the gateway Client ID / Client Secret are required. They are read from var_med_client_id / var_med_client_secret (exported, declared in app_vars), asked on the host only when unset, and the script stops before building the container if they are empty.
• Update: check_for_gh_release + CLEAN_INSTALL=1 fetch_and_deploy_gh_release, .env kept with create_backup / restore_backup, then uv sync and a frontend rebuild.

I am not the upstream author, but a contributor to the project ([#154](MyElectricalData/myelectricaldata_new#154), [#175](MyElectricalData/myelectricaldata_new#175)). The maintainer is aware of this submission and keeps [MyElectricalData/myelectricaldata_new#142](MyElectricalData/myelectricaldata_new#142) open until it is published here.

AI usage: Claude Opus 5.5 (default reasoning) adapted my existing, already working script (Marlboro62/myelectricaldata-proxmox) to AGENTS.md: removed my own additions (UI version badge, timers, login banner, local patches), aligned runtime versions on upstream, English messages. I reviewed it and tested it on my Proxmox VE host.

🔗 Related PR / Issue

Link: MyElectricalData/myelectricaldata_new#142

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🏗️ arm64 Support (X in brackets)

• arm64 supported - Tested and supported on arm64.
• arm64 not tested - Assumed to work on arm64, but testing has not been done.
• arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

var_arm64 is left unset: the app is pure Python/Node with no prebuilt binary, but I have not run this script on arm64 yet.

---

🖥️ Tested on (X in brackets)

• Proxmox VE – Created on a Proxmox VE host and the app works.
• Incus – Created on an Incus host and the app works.

Proxmox VE 9.2 (amd64), default settings, Debian 13 unprivileged container:

• install completed without error, MyElectricalData 2.10.0 deployed;
• myelectricaldata, nginx and postgresql services active;
• API /ping returns 200 directly and through nginx (/api/ping);
• web UI reachable on port 8100, the delivery point is synced from the gateway;
• update in the container: "No update available: myelectricaldata (2.10.0)".

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

---

🔍 Code & Security Review (X in brackets)

• Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials
• No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
• No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

---

🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.

• No AI used – Scripts were written without AI assistance.
• AI was used – I confirm the scripts were built using [AGENTS.md](https://github.com/community-scripts/DevScripts/blob/main/AGENTS.md) and [.github/agents/pve-script-creator.agent.md](https://github.com/community-scripts/DevScripts/blob/main/.github/agents/pve-script-creator.agent.md) as guidance, and the output has been reviewed and corrected to match those guidelines.

Please describe to which degree, if any, an LLM was used in creating this pull request. Name the model(s) used and, if applicable, the reasoning/thinking effort level (e.g. "Claude Sonnet 4.5, high reasoning, used to draft the install script, then manually reviewed and tested" or "No LLM used"). This is informational, not a penalty — but scripts that are clearly AI-generated and not further revised by the author to match CODE-AUDIT.md / CONTRIBUTING.md may be closed without review.

Claude Opus 5.5 (default reasoning), used to port my existing script to the DevScripts layout and rules and to write this description. Reviewed by me and tested on my Proxmox VE host (results above).

---

📋 Additional Information (optional)

About the 600 stars requirement: the box is left unchecked on purpose. The upstream repository only has a few stars: this is a niche app for French Linky meters, so its audience is limited to France. It is around one year old, released very often (2.10.0 this week) and has a working gateway with its own users. I understand if this is not enough to be accepted; I am submitting it in case an exception is possible.

The MyElectricalData gateway has a quota (50 uncached requests per day per account), which is why the JSON warns against running several instances with the same credentials.

---

📦 Application Requirements (for new scripts)

⚠️ Do not remove this section.
It is used by automated PR validation checks.
If this PR is not a new script submission, leave the checkboxes unchecked.

Required for 🆕 New script submissions.
Pull requests that do not meet these requirements may be closed without review.

• The application is at least 6 months old
• The application is actively maintained
• The application has 600+ GitHub stars
• Official release tarballs are published
• I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG

🌐 Source

• Upstream: https://github.com/MyElectricalData/myelectricaldata_new
• Read for this script: apps/api/Dockerfile, apps/api/entrypoint.sh, apps/api/.python-version, apps/api/pyproject.toml, apps/web/Dockerfile, apps/web/entrypoint.sh, docker-compose.yml, mise.toml
• Client mode documentation: https://github.com/MyElectricalData/myelectricaldata_new/tree/main/docs/local-client

[github-actions]

Try this script

ct/myelectricaldata.sh, run in the Proxmox VE shell or on an Incus host:

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Marlboro62/DevScripts/feat/myelectricaldata \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/Marlboro62/DevScripts/feat/myelectricaldata/ct/myelectricaldata.sh)"

COMMUNITY_SCRIPTS_URL is not optional for ct/. Fetching the ct/ script from a
branch does not tell the engine where that branch is — with bash -c "$(curl …)"
there is no file on disk for the scripts root to be derived from, so it would fall
back to upstream main and look for the install script there.

Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Useful flags while testing

dev_mode=net logs every fetch with status and duration, so you can confirm the
branch is really being used. dev_mode=keep stops a failed build from deleting
the container along with the evidence.

[github-actions]

⚠️ Not ready for review yet

@Marlboro62, this pull request is missing the following:

• The application has 600+ GitHub stars

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.

---

@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.

[MickLesk]

This tool doesn't even come close to having 1k stars (for live) or 600 to begin our check