Develop

[xirixiz]

BREAKING

• Restructured and datalogger modes. STANDALONE is untouched, but API_SERVER and API_CLIENT have been introduced.
• Receiver and sender datalogger modes have been removed/replaced.

NON BREAKING

• Only for STANDALONE - SERIAL a device validation is still in place. This removes errors with other setups like API_SERVER or API_CLIENT.
• Other modes than STANDALONE are now functioning properly. Exactly like the examples provided in the DSMR Reader docs.
• Dcocumentation has been updated and provides better information .

[RubenDijk]

Na update start hij niet meer:

[ INFO ] Checking for CLIENT CERTIFICATE AUTHENTICATION configuration... [ INFO ] ENABLE_CLIENTCERT_AUTH is disabled, nothing to see here. Continuing... [ INFO ] Checking for NGINX SSL configuration... [ INFO ] ENABLE_NGINX_SSL is disabled, nothing to see here. Continuing... [ INFO ] Checking for HTTP AUTHENTICATION configuration... [ INFO ] ENABLE_HTTP_AUTH is disabled, nothing to see here. Continuing... [ INFO ] Configuring DSMR Reader to run all processes in a single container with a serial or ipv4 datalogger... [ INFO ] Using a serial connection for the DSMR Reader remote datalogger... [ INFO ] Fixing /dev/ttyUSB0 security... [ FAIL ] Device /dev/ttyUSB0 not found. Exiting...

[xirixiz]

Klopt. Voor jouw setup moet je in api_server mode draaien. Zie readme.md

Tenminste. Uit de vorige ticket heb ik dat opgemaakt :). Je hebt een remote datalogger die data richting DSMR stuurt via de API (push).

Het doel is de volgende keer een release te maken met ook release notes, zodat breaking changes beter zichtbaar zijn.