Added null api for not pushing readings to any consumer.

[r00t-]

i like this.
but we should leave the volkszaehler api as default (with a warning maybe),
and accept the old "vz" value,
to not break people's configurations.

[andig]

but we should leave the volkszaehler api as default (with a warning maybe), and accept the old "vz" value.

Fixed. Any unknown value defaults to the vz api. Console message now clearly mentions this.

[r00t-]

pointless details, fix them if you care, else i'd just merge it:
@file Null.hpp * Header file for volkszaehler.org API calls
@file Null.cpp * Header file for null API calls
the config has one channel with api "volkszaehler" and the others with "vz"
maybe name it NullApi instead of just "Null" to make it less confusing
(even if theoretically the namespace and directory are enough)
whitespace changes in Volkszaehler.hpp

[r00t-]

oh, and no need to warn if the api "vz" (or "volkszaehler") is explicitly set ;)

[andig]

Breaking change: renamed channel->protocol to channel->api for sake of distinction. Should not hurt unless you're a mysmartgrid user.

[andig]

@file Null.hpp * Header file for volkszaehler.org API calls

Fixed. Would not change the Null file name due to api namespace as you've mentioned.

[andig]

TODO: add documentation section following http://wiki.volkszaehler.org/software/controller/vzlogger#meters_protocols once commit is done

[r00t-]

if you're getting tired of it, just merge it...

but i'm still unhappy with how the defaulting is handled...
an explicitly set value should not be ignored when it's unknown.

Meter_Options does:
if (apiProtocol_str == NULL) { apiProtocol_str = strdup("volkszaehler");
(which i missed because it was not even part of your changes.
i was assuming you had changed the name from"vz" to 'volkszaehler"
due to your changes in the config)
and then MeterMap does not actually handle that value explicitly.
if the defaulting when the api is not explicltly specified is done in the config parser already,
metermap could (and should) throw an error on unknown values.

maybe i'll just make a new fork with my changes ;)

[r00t-]

i would probably remove the handling of the NULL in Meter_Options,
pass the NULL to MeterMap,
and handle it there.

[andig]

but i'm still unhappy with how the defaulting is handled...

Understood. I'd be happy if you could fork and take it from there- enough fiddling for one day...

Merry Christmas!