Skip to content

chore(drivers): move the bundled pin to device-drivers@76c968bd #722

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
frahlg merged 1 commit into from
Jul 30, 2026
Merged

chore(drivers): move the bundled pin to device-drivers@76c968bd #722

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .changeset/bundled-pin-sungrow-ems-refusal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
"ftw": patch
---

Move the bundled-driver pin to device-drivers@76c968bd. A gateway booting
offline no longer retries the Sungrow EMS control block on an inverter that
has already refused it — an SG string inverter logged a failed
self-consumption reset once per watchdog tick for the life of the session.
Sungrow is the only bundled driver the move changes (1.5.6 → 1.5.7).
2 changes: 1 addition & 1 deletion drivers/BUNDLED_SOURCE.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
"for coverage. Run scripts/sync-bundled-drivers.sh to update."
],
"repository": "srcfl/device-drivers",
"commit": "a4d0205d5f4439f0994b2b708a4d69a7a0c20023",
"commit": "76c968bd888193cc9362da951ec9bcca7488b256",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Retry safety resets after transport failures

When a controllable hybrid is left in forced EMS mode and three default-mode attempts encounter a temporary TCP outage or reconnect backoff, the pinned 1.5.7 driver counts those errors as refusals and suppresses subsequent reset writes for the rest of the session. host.modbus_write returns transport errors as well as definitive Modbus exceptions, so if connectivity recovers while dispatch remains stopped—for example, because the site meter is still stale—the watchdog cannot return the inverter to autonomous mode until FTW restarts. Only latch the unsupported-block state for a definitive device rejection, or resume attempts after transport recovery.

AGENTS.md reference: AGENTS.md:L31-L32

Useful? React with 👍 / 👎.

"source_dir": "drivers/lua",
"drivers": [
"ambibox_v2x", "ctek", "ctek_hybrid", "ctek_v2", "deye", "easee_cloud",
Expand Down