0954f66725
Takes the slave ID as an argument instead of reading it from the thing, and takes whether it is the primary connection of that thing. Only the primary one follows the network monitor, writes the connected state of the thing and lands in m_sunSpecConnections; a secondary one lands in a hash of its own. Child things are updated per connection rather than per parent, resolved from the model each child is bound to. With a single connection that is every child of the parent, so nothing changes here yet. No caller creates a secondary connection at this point: behaviour is unchanged for all three vendors. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
SunSpec
Connect nymea to SunSpec devices over Modbus TCP
Supported Things
- SunSpec Inverter
- Model ID 101 & 111 Single phase inverter
- Model ID 102 & 112 Split phase inverter
- Model ID 103 & 113 Three phase inverter
- SunSpec Meter
- Model ID 201 & 211 Single phase meter
- Model ID 202 & 212 Split phase meter
- Model ID 203 & 213 Three phase meter
- SunSpec Storage
- Model ID 124
Tested connections
- SolarEdge (with custom battery)
Requirements
- The package 'nymea-plugin-sunspec' must be installed.
- The SunSpec device must support SunSpec over modbus TCP