spec: Blixt L1 headroom emit keys + inverter as reporting stream - #89
Merged
Conversation
added 3 commits
August 18, 2026 10:18
Blixt L1 battery/hybrid drivers report their AC stage on
host.emit("inverter", ...) and feed available_charge_W /
available_discharge_W (battery) and available_import_W /
available_export_W (inverter) into the arbitrator clamp. L1 reads
those keys by exact name with no lowercase fallback, and the profile
already names Blixt as the emit-key reference — but the four keys were
missing from emit_keys.canonical, and the emit-type tests rejected
"inverter" outright because it is not a DER type.
Add the keys to the profile, document that inverter is a stream (the
device is still declared as ders: [battery]), and let the structure /
manifest-consistency tests accept the stream without listing it in
ders. No driver changes; the emit-fields tests already derive their
allowed set from the profile.
Signed-off-by: David Mozart <david@sourceful-labs.com>
Blixt L1's host.write is FC16 with count=1 (Deye ignores FC06 on some ranges) and exposes host.write_fc06 for true FC06; FTW's is FC06. The two hosts also disagree on how a failed write is reported: FTW returns an error string and never raises, Blixt returns true or raises. The test harness follows FTW, so a Blixt-only driver that trusts pcall's ok reads a mocked refusal as success. Document both, add write_fc06 to the profile's modbus group, and give the portable check. Signed-off-by: David Mozart <david@sourceful-labs.com>
test_signed_manifest_rejects_unsafe_runtime_fields mutated payload.drivers[0] and relied on it being read-only. The catalog is sorted by id, so the first control driver whose id sorts before abb_meter (any id starting with a digit) made the mutations hit a different, earlier check than the one under test. Select a read-only modbus.read-only entry explicitly. Signed-off-by: David Mozart <david@sourceful-labs.com>
This was referenced Aug 18, 2026
konja-261-svk.lua + its manifest were staged by an over-broad git add; they belong to #95, not here. Signed-off-by: David Mozart <david@sourceful-labs.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spec prerequisite for the Blixt L1 driver migrations (#90–#95).
Emit keys
spec/host-api-profile.jsonemit_keys.canonical: addbattery.available_charge_W/available_discharge_Wandinverter.available_import_W/available_export_W. Blixt L1 reads these by exact name (no lowercase fallback) and feeds them into its arbitrator's headroom clamp.inverteras a reporting stream of a battery/hybrid driver (its AC stage), not a DER type. The device staysders: [battery].test_driver_structure.py/test_manifest_consistency.pyaccept the stream inhost.emit()without requiring it inders.Write semantics (
spec/host-api.md+ profile)host.write_fc06(Blixt L1) to the modbus group.host.writeis FC16(count=1) on Blixt L1 (Deye ignores FC06 on some ranges) but FC06 on FTW — the spec previously said FC06 unconditionally.trueor raises. The test harness follows FTW, so a Blixt-only driver that trustspcall'sokreads a mocked refusal as success. Documented with the portable check a dual-target driver must use.Tests
test_signed_manifest_rejects_unsafe_runtime_fieldsmutatedpayload.drivers[0]and relied on it being read-only; select a read-only entry explicitly so a control driver whose id sorts first cannot change which check trips.No driver changes. Full suite green.