<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>You need to change the api, not the middleware. Middleware is a feature of the vz api. Never tried though.<br><br>Viele Grüße, Andreas </div><div><br>Am 18.12.2014 um 21:06 schrieb Ralf G. R. Bergs <<a href="mailto:Ralf+VolksZaehler@bergs.biz">Ralf+VolksZaehler@bergs.biz</a>>:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">On 2014-12-18 16:45 , Andreas Götz
wrote:<br>
</div>
<blockquote cite="mid:B86965FB-BFEB-4266-AC6E-CA77173410FC@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div><br>
<blockquote type="cite">How can I reconfigure vzlogger so that
it does <i>not</i> automatically push the meter readings
towards the middleware?</blockquote>
I think we have an api setting per channel. Vz is the default
for that. See if there is a 'none' setting for that.</div>
</blockquote>
I couldn't "cleanly" do that. Regardless of whether I used something
like<br>
<blockquote type="cite">"middleware" : none,<br>
</blockquote>
or<br>
<blockquote type="cite">"middleware" : null,<br>
</blockquote>
or<br>
<blockquote type="cite">"middleware" : "",<br>
</blockquote>
or<br>
<blockquote type="cite">"middleware" : "none",<br>
</blockquote>
or<br>
<blockquote type="cite">"middleware" : "null",<br>
</blockquote>
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>
<br>
Kind regards,<br>
<br>
Ralf<br>
<br>
</div></blockquote></body></html>