<div dir="ltr">PS.:<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 19, 2014 at 12:36 PM, Andreas Goetz <span dir="ltr"><<a href="mailto:cpuidle@gmail.com" target="_blank">cpuidle@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Ralf,<br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Fri, Dec 19, 2014 at 10:55 AM, Ralf G. R. Bergs <span dir="ltr"><<a href="mailto:Ralf+VolksZaehler@bergs.biz" target="_blank">Ralf+VolksZaehler@bergs.biz</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Andreas.<span><br>
<br>
On 2014-12-18 21:42 , Andreas Götz wrote:<br>
</span></div>
<blockquote type="cite">
<div><span><br>
<blockquote type="cite">vzlogger would <i>always</i> throw an
error, either<br>
<blockquote type="cite">CURL: Couldn't resolve host name</blockquote>
or<br>
<blockquote type="cite">CURL: URL using bad/illegal format or
missing URL</blockquote>
It would not quit, though, so in the end it did what I wanted
(not push the readings to the middleware), but it's not a
clean solution.<br>
</blockquote></span>
You need to change the api, not the middleware. Middleware is a
feature of the vz api. Never tried though.<br>
<br>
</div>
</blockquote>
Sorry, I don't get your point, maybe I'm slow? Why change the API or
the middleware? Would that not simply be a change in vzlogger
behavior independent on how the API or the middleware looks
like/works?<br></div></blockquote><div><br></div></span><div>check etc/vzlogger.conf and search for 'protocol'. vzlogger supports other protocols than volkszahler/middleware, that is e.g. mysmartgrid. You probably need to check the source code if there is an "null" protocol. If you need one feel free to open an issue in github.<br></div><div>Note: these are different from <a href="http://wiki.volkszaehler.org/software/controller/vzlogger#meters_protocols" target="_blank">http://wiki.volkszaehler.org/software/controller/vzlogger#meters_protocols</a> which are on the reading, not the writing side. Unfortunately the config file syntax is confusing in that regard.<br></div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
My idea was to tell the vzlogger daemon <i>not</i> to send the
meter readings anywhere, just to collect them. I would then query
vzlogger via the internal microhttpd for the current readings...<br></div></blockquote><div><br></div></span><div>Exactly. My approach would be logging to a "null" protocol for that purpose.<br></div></div></div></div></blockquote><div><br><a href="https://github.com/volkszaehler/vzlogger/blob/master/src/MeterMap.cpp#L125">https://github.com/volkszaehler/vzlogger/blob/master/src/MeterMap.cpp#L125</a> should be a good place to start, then also <a href="https://github.com/volkszaehler/vzlogger/blob/master/src/api/Volkszaehler.cpp">https://github.com/volkszaehler/vzlogger/blob/master/src/api/Volkszaehler.cpp</a><br><br></div><div>Should be easy to add an additional <null> protocol ;)<br><br>Viele Grüße,<br>Andreas<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<br>
KR,<br>
<br>
Ralf<br></div></blockquote><div><br></div><div>Freundliche Grüße/ Kind regards<span class=""><font color="#888888"><br>Andreas Götz<br> <br></font></span></div></div></div></div>
</blockquote></div></div></div>