(similar to #550 for mqtt)
when reading the "push" code (for #609) , i noticed it has the same problem as mqtt:
it hardcodes a specific protocol into the vzlogger core (a protocol specific to the volkszaehler middleware),
instead of providing it as an api plugin.
(it should really be an option of the volkszaehler api.)
this was added in e1eddf3 .
(similar to #550 for mqtt)
when reading the "push" code (for #609) , i noticed it has the same problem as mqtt:
it hardcodes a specific protocol into the vzlogger core (a protocol specific to the volkszaehler middleware),
instead of providing it as an api plugin.
(it should really be an option of the volkszaehler api.)
this was added in e1eddf3 .