-
Notifications
You must be signed in to change notification settings - Fork 4
HowTo: Update values in the docker image #5
Comments
it took me some hours too! Here is an example for my meter (I use a different port for the image) { |
I don‘t understand the problem. The VZ api is documented. What particularly needs additional docs? And what has vzlogger configuration to do with it?
Viele Grüße,
Andreas
… Am 13.05.2018 um 13:07 schrieb artcrime ***@***.***>:
it took me some hours too! Here is an example for my meter (I use a different port for the image)
{
"uuid": "7a7b9980-49c8-11e6-a31d-8b29f99xzzy",
"identifier": "1-0:16.7.0",
"api": "volkszaehler",
"middleware": "http://192.168.100.200:8090/",
"type": "device",
"scaler": 1,
"aggmode": "max",
"duplicates": 0
},
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
normaly you configure your vzlogger.conf like that { for the docker container you have to leave out "middleware.php" or you'll get an exeption error. I moved my configuration from an existing installation and didnt understand why I got no data until I found the comment from emeins. Gruß Sascha |
Thanks for raising this topic. For performance reasons the docker image uses That means that according to https://github.com/volkszaehler/docker/blob/master/README.md (and https://github.com/volkszaehler/volkszaehler.org/blob/master/etc/middleware.json#L3) both frontend end middleware will be provided on port |
Maybe it is worth to update the documentation how to put values from outside into the docker container: "http://:/data/$UUID.json?operation=add&ts=&value="
It is only a documentation issue, but it costs me some hours. The container itself runs very well.
The text was updated successfully, but these errors were encountered: