Patrick Schurig 9e0cd44af0 sunspec: add a device suite for the two connection behaviour
The two most certain defects of the multi unit ID work are invisible to
the offline suites, because they only appear once a discovery has
actually run: the orphan sweep deleting the children of the other
connection, and the aggregation of the connected state.

This suite mounts the plugin behind a real ThingManager against a real
device. It is deliberately not a testcase, so "make check" never runs
it, but it is still built so it cannot rot unnoticed. Without
SUNSPEC_TEST_HOST every test skips, and no address is written into the
repository: the address of a real installation is customer data.

NOT YET RUN against hardware. It needs the address of a GEN24 and, given
the polling rate guidance, a deliberate decision to point it at a
customer inverter.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-02 09:07:06 +02:00

21 lines
830 B
Prolog

TEMPLATE = subdirs
# logic : logique pure du plugin, sans nymea. Ne demande que libnymea-sunspec.
# plugin : instancie reellement IntegrationPluginSunSpec derriere un
# ThingManager et un HardwareManager doubles. Demande en plus
# libnymea1-dev et libnymea-core (pkg-config nymea, nymea-core).
# multiunit : meme montage que plugin, mais pour un thing froniusConnection
# portant deux SunSpecConnection (F3). Binaire distinct pour ne pas
# fausser les compteurs d'appels globaux verifies par plugin.
# integration : le plugin face a un vrai appareil. Construite mais JAMAIS lancee
# par "make check" : elle exige un onduleur joignable, passe par
# SUNSPEC_TEST_HOST. Voir integration/integration.pro.
SUBDIRS += \
logic \
plugin \
multiunit \
integration