Skip to content

Lattice 2/4: gateway + GE-Cloud producers#4082

Draft
mgazza wants to merge 2 commits into
lattice-pr1-frameworkfrom
lattice-pr2-producers
Draft

Lattice 2/4: gateway + GE-Cloud producers#4082
mgazza wants to merge 2 commits into
lattice-pr1-frameworkfrom
lattice-pr2-producers

Conversation

@mgazza

@mgazza mgazza commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

PR 2/4 of the Lattice merge train. Stacked on #1 (framework).

Commits (story):

  1. gateway producer — fragment, real device-type, control via publish_command + publishes inverter_serial
  2. GE-Cloud producer — read-only/dormant (settings keyed by numeric id; name→id resolution + live verify needed before control)

The local gateway is the GivEnergy control executor; GE-Cloud is the (dormant) fallback. Still flag-gated — no behaviour change.

🤖 Generated with Claude Code

mgazza and others added 2 commits June 18, 2026 09:51
…rial

GatewayMQTT.lattice_fragment (local-Modbus inverters, charge/discharge controllable),
_lattice_device_type (real inverter type from the proto), and lattice_control via publish_command.
automatic_config also publishes inverter_serial so inverter.py can correlate each unit to its node.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
GECloudDirect.lattice_fragment emits the cloud-reachable inverters; control stays read-only
because GE-Cloud settings are keyed by numeric id while the mapping is by name — resolve
name->setting-id + verify live before declaring control. The local gateway is the GE executor.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant