VZLogger as Addon

Hi,
first of all, sorry for my bad English, it is unfortunately not my native language.
several times ago I switched from Container based Home-Assistant to Home-Assistant OS and forgot to read the deficits of Home-Assistant OS, I have no normal Linux anymore.
Anyway I needed an VZLogger without setup another RPI, so I looked for an HASS Addon of VZLogger, and found one with an fork.
I forked the fork :sweat_smile::see_no_evil: and finished an first working Version
homeassistant-addon-vzlogger
I added my own Example vzlogger.conf file and used to Read the Values
following Tutorial
https://go-seven.de/2021/10/easymeter-stromzaehler-in-home-assistant-einbinden/

I get so much Support from the Community and want to give back anything, it’s only a first version and sure not perfect, but maybe a first draft.

Greetings

p.s.
If I have to write more details for integrations will will modify my Post.:see_no_evil:

1 Like

Hi Helming, please excuse my lack of knowledge since I am a beginner in HA and vzlogger.

  1. I use the vzlogger fork from the link you posted above (manual added using repository in pic “vzlogger_add_repository”). Thank you!!

  2. After the installation and start of vzlogger I got this protokol:
    [Aug 04 10:32:08] Failed to parse configuration due to: Cannot open configfile.
    [10:32:09] INFO: ==============================================================================
    [10:32:09] INFO: ==============================================================================
    [10:32:09] INFO:
    [10:32:09] INFO: ==============================================================================
    [10:32:09] INFO: Starting vzlogger
    [Aug 04 10:32:09][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:09] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:09] Failed to parse configuration due to: Cannot open configfile.
    [10:32:10] INFO: ==============================================================================
    [10:32:10] INFO: ==============================================================================
    [10:32:10] INFO:
    [10:32:10] INFO: ==============================================================================
    [10:32:10] INFO: Starting vzlogger
    [Aug 04 10:32:10][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:10] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:10] Failed to parse configuration due to: Cannot open configfile.
    [10:32:11] INFO: ==============================================================================
    [10:32:11] INFO: ==============================================================================
    [10:32:11] INFO:
    [10:32:11] INFO: ==============================================================================
    [10:32:11] INFO: Starting vzlogger
    [Aug 04 10:32:11][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:11] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:11] Failed to parse configuration due to: Cannot open configfile.
    [10:32:12] INFO: ==============================================================================
    [10:32:12] INFO: ==============================================================================
    [10:32:12] INFO:
    [10:32:12] INFO: ==============================================================================
    [10:32:12] INFO: Starting vzlogger
    [Aug 04 10:32:12][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:12] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:12] Failed to parse configuration due to: Cannot open configfile.
    [10:32:13] INFO: ==============================================================================
    [10:32:13] INFO: ==============================================================================
    [10:32:13] INFO:
    [10:32:13] INFO: ==============================================================================
    [10:32:13] INFO: Starting vzlogger
    [Aug 04 10:32:13][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:13] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:13] Failed to parse configuration due to: Cannot open configfile.
    [10:32:14] INFO: ==============================================================================
    [10:32:14] INFO: ==============================================================================
    [10:32:14] INFO:
    [10:32:14] INFO: ==============================================================================
    [10:32:14] INFO: Starting vzlogger
    [Aug 04 10:32:14][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:14] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:14] Failed to parse configuration due to: Cannot open configfile.
    [10:32:15] INFO: ==============================================================================
    [10:32:15] INFO: ==============================================================================
    [10:32:15] INFO:
    [10:32:15] INFO: ==============================================================================
    [10:32:15] INFO: Starting vzlogger
    [Aug 04 10:32:15][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:15] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:15] Failed to parse configuration due to: Cannot open configfile.
    [10:32:16] INFO: ==============================================================================
    [10:32:16] INFO: ==============================================================================
    [10:32:16] INFO:
    [10:32:16] INFO: ==============================================================================
    [10:32:16] INFO: Starting vzlogger
    [Aug 04 10:32:16][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:16] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:16] Failed to parse configuration due to: Cannot open configfile.
    [10:32:17] INFO: ==============================================================================
    [10:32:17] INFO: ==============================================================================
    [10:32:17] INFO:
    [10:32:17] INFO: ==============================================================================
    [10:32:17] INFO: Starting vzlogger
    [Aug 04 10:32:17][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:17] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:17] Failed to parse configuration due to: Cannot open configfile.
    [10:32:18] INFO: ==============================================================================
    [10:32:18] INFO: ==============================================================================
    [10:32:18] INFO:
    [10:32:18] INFO: ==============================================================================
    [10:32:18] INFO: Starting vzlogger
    [Aug 04 10:32:18][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:18] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:18] Failed to parse configuration due to: Cannot open configfile.
    [10:32:19] INFO: ==============================================================================
    [10:32:19] INFO: ==============================================================================
    [10:32:19] INFO:
    [10:32:19] INFO: ==============================================================================
    [10:32:19] INFO: Starting vzlogger
    [Aug 04 10:32:19][main] vzlogger v0.8.1 based on heads/master-0-g76e868feed from Wed, 20 Apr 2022 08:39:54 +0200 started.
    [Aug 04 10:32:19] Cannot open configfile --foreground: No such file or directory
    [Aug 04 10:32:19] Failed to parse configuration due to: Cannot open configfile.

  3. Since I am using Siemens TD-3511, I than simply copy the syntax from hardware:channels:meters:power:edl-ehz:siemens_td3511 [wiki.volkszaehler.org] as my configuration:

{
“verbosity”: 10,
“log”: “/var/log/vzlogger/vzlogger.log”,
“retry”: 30,
“local”: {
“enabled”: false,
“port”: 8081,
“index”: true,
“timeout”: 0,
“buffer”: -1
},
“meters”: [
{
“enabled”: true,
“allowskip”: false,
“protocol”: “d0”,
“device”: “/dev/ttyAMA0”,
“aggtime”: -1,
“interval”: 10,
“pullseq”: “2F3F210D0A”, // “/?!\r\n” = 2F 3F 21 0D 0A
“ackseq”: “063034300D0A”, //needs to be in accordance to parameter ‘baudrate_read’
//“auto” for auto detection
“baudrate”: 300,
“baudrate_read”: 4800,
“baudrate_change_delay”: 300,
“parity”: “7e1”,
“use_local_time”: false,
“read_timeout”: 10, //?? 2200ms according to manual?
“dump_file”: “/home/pi/D0_pullSeq.txt”,
“channels”: [
{
“identifier”: “1.7.0”, //Positive active instantaneous power (A+) [kW]
“uuid”: “00000000-0000-0000-0000-000000000000”,
“api”: “influxdb”,
“host”: “http://localhost:8086”,
“database”: “vzlogger”,
“measurement_name”: “vz_measurement”,
“duplicates”: 600,
“username”: “”,
“password”: “”
}, {
“identifier”: “1.8.1”, //Positive active energy (A+) in tariff T1 [kWh]
“uuid”: “00000000-0000-0000-0000-000000000000”,
“api”: “influxdb”,
“host”: “http://localhost:8086”,
“database”: “vzlogger”,
“measurement_name”: “vz_measurement”,
“duplicates”: 600,
“username”: “”,
“password”: “”
}, {
“identifier”: “2.8.1”, //Negative active energy (A+) in tariff T1 [kWh]
“uuid”: “00000000-0000-0000-0000-000000000000”,
“api”: “influxdb”,
“host”: “http://localhost:8086”,
“database”: “vzlogger”,
“measurement_name”: “vz_measurement”,
“duplicates”: 600,
“username”: “”,
“password”: “”
}
]
}
]
}

Since I saw the config is using data base InfluxDB, I install InfluxDB in Home Assistant and create a DB “vzlogger”, an user “vzlogger” as well. This info I added later to the config.
The problem is, I do not really know how I add this configuration, so I just simply copy the adjusted script to the section vzlogger>Konfiguration (see pic “vzlogger_Konfiguration.JPG”)

  1. I restart the vzlogger and get this protokol:

hag-temp-avg gemittelte Chiptemperatur 1-0:96.50.04
hag-temp-max maximale Chiptemperatur 1-0:96.50.0
5
hag-check Kontrollnr. 1-0:96.50.06
hag-diag Diagnose 1-0:96.50.0
7
lg-counter-et Sum active energy (Total) 255-255:16.8.0255
lg-counter-ht Sum active energy (T1) 255-255:16.8.1
255
lg-counter-lt Sum active energy (T2) 255-255:16.8.2255
following APIs are supported:
volkszaehler-api
mysmartgrid-api
vzlogger 0.8.1 - volkszaehler.org logging utility
by Steffen Vogel [email protected]
send bugreports to Issues · volkszaehler/vzlogger · GitHub
[11:18:12] INFO: ==============================================================================
[11:18:12] INFO: ==============================================================================
cat: unrecognized option: 1
BusyBox v1.34.1 (2022-04-04 10:19:27 UTC) multi-call binary.
Usage: cat [-nbvteA] [FILE]…
Print FILEs to stdout
-n Number output lines
-b Number nonempty lines
-v Show nonprinting characters as ^x or M-x
-t …and tabs as ^I
-e …and end lines with $
-A Same as -vte
[11:18:12] INFO:
[11:18:12] INFO: ==============================================================================
[11:18:12] INFO: Starting vzlogger
/usr/local/bin/vzlogger: unrecognized option: 1
Usage: /usr/local/bin/vzlogger [options]
following options are available:
-c, --config configuration file
-o, --log log file
-f, --foreground run in foreground, do not daemonize
-l, --httpd activate local interface (tiny HTTPd which serves live readings)
-p, --httpd-port TCP port for HTTPd
-r, --register register device
-v, --verbose enable verbose output
-h, --help show this help
-V, --version show version of vzlogger
following protocol types are supported:
file Read from file or fifo
exec Parse program output
random Generate random values with a random walk
fluksov2 Read from Flukso’s onboard SPI fifo
s0 S0-meter directly connected to RS232
d0 DLMS/IEC 62056-21 plaintext protocol
sml Smart Message Language as used by EDL-21, eHz and SyM²
w1therm W1-therm / 1wire temperature devices
oms OMS (M-BUS) protocol based devices
following OBIS aliases are available:
power Wirkleistung (Summe) 1-0:1.7.255
255
power-l1 Wirkleistung (Phase 1) 1-0:21.7.255255
power-l2 Wirkleistung (Phase 2) 1-0:41.7.255
255
power-l3 Wirkleistung (Phase 3) 1-0:61.7.255255
voltage Spannung (Mittelwert) 1-0:12.7.255
255
voltage-l1 Spannung (Phase 1) 1-0:32.7.255255
voltage-l2 Spannung (Phase 2) 1-0:52.7.255
255
voltage-l3 Spannung (Phase 3) 1-0:72.7.255255
current Stromstaerke (Summe) 1-0:11.7.255
255
current-l1 Stromstaerke (Phase 1) 1-0:31.7.255255
current-l2 Stromstaerke (Phase 2) 1-0:51.7.255
255
current-l3 Stromstaerke (Phase 3) 1-0:71.7.255255
frequency Netzfrequenz 1-0:14.7.0
255
powerfactor Leistungsfaktor 1-0:12.7.0255
device Zaehler Seriennr. 0-0:96.1.255
255
status Zaehler Status 1-0:96.5.5255
counter Zaehlerstand Wirkleistung 1-0:1.8.255
255
counter-out Zaehlerstand Lieferg. 1-0:2.8.255255
esy-counter-t1 Active Power Counter Tariff 1 1-0:1.8.1
255
esy-counter-t2 Active Power Counter Tariff 2 1-0:1.8.2255
hag-id Eigentumsnr. 1-0:0.0.0
255
hag-status Netz Status 1-0:96.50.00
hag-frequency Netz Periode 1-0:96.50.0
1
hag-temp aktuelle Chiptemperatur 1-0:96.50.02
hag-temp-min minimale Chiptemperatur 1-0:96.50.0
3
hag-temp-avg gemittelte Chiptemperatur 1-0:96.50.04
hag-temp-max maximale Chiptemperatur 1-0:96.50.0
5
hag-check Kontrollnr. 1-0:96.50.06
hag-diag Diagnose 1-0:96.50.0
7
lg-counter-et Sum active energy (Total) 255-255:16.8.0255
lg-counter-ht Sum active energy (T1) 255-255:16.8.1
255
lg-counter-lt Sum active energy (T2) 255-255:16.8.2*255
following APIs are supported:
volkszaehler-api
mysmartgrid-api
vzlogger 0.8.1 - volkszaehler.org logging utility
by Steffen Vogel [email protected]
send bugreports to Issues · volkszaehler/vzlogger · GitHub

  1. I do not know what the next step is.

Could you kindly assist?

Vielen Dank und Gruss
Ed

I forgot the pics



Sorry, this is the protocol after restart of vzlogger. I forgot to change the correct syntax for USB:

BusyBox v1.34.1 (2022-04-04 10:19:27 UTC) multi-call binary.
Usage: cat [-nbvteA] [FILE]…
Print FILEs to stdout
-n Number output lines
-b Number nonempty lines
-v Show nonprinting characters as ^x or M-x
-t …and tabs as ^I
-e …and end lines with $
-A Same as -vte
[11:35:48] INFO:
[11:35:48] INFO: ==============================================================================
[11:35:48] INFO: Starting vzlogger
/usr/local/bin/vzlogger: unrecognized option: 1
Usage: /usr/local/bin/vzlogger [options]
following options are available:
-c, --config configuration file
-o, --log log file
-f, --foreground run in foreground, do not daemonize
-l, --httpd activate local interface (tiny HTTPd which serves live readings)
-p, --httpd-port TCP port for HTTPd
-r, --register register device
-v, --verbose enable verbose output
-h, --help show this help
-V, --version show version of vzlogger
following protocol types are supported:
file Read from file or fifo
exec Parse program output
random Generate random values with a random walk
fluksov2 Read from Flukso’s onboard SPI fifo
s0 S0-meter directly connected to RS232
d0 DLMS/IEC 62056-21 plaintext protocol
sml Smart Message Language as used by EDL-21, eHz and SyM²
w1therm W1-therm / 1wire temperature devices
oms OMS (M-BUS) protocol based devices
following OBIS aliases are available:
power Wirkleistung (Summe) 1-0:1.7.255255
power-l1 Wirkleistung (Phase 1) 1-0:21.7.255
255
power-l2 Wirkleistung (Phase 2) 1-0:41.7.255255
power-l3 Wirkleistung (Phase 3) 1-0:61.7.255
255
voltage Spannung (Mittelwert) 1-0:12.7.255255
voltage-l1 Spannung (Phase 1) 1-0:32.7.255
255
voltage-l2 Spannung (Phase 2) 1-0:52.7.255255
voltage-l3 Spannung (Phase 3) 1-0:72.7.255
255
current Stromstaerke (Summe) 1-0:11.7.255255
current-l1 Stromstaerke (Phase 1) 1-0:31.7.255
255
current-l2 Stromstaerke (Phase 2) 1-0:51.7.255255
current-l3 Stromstaerke (Phase 3) 1-0:71.7.255
255
frequency Netzfrequenz 1-0:14.7.0255
powerfactor Leistungsfaktor 1-0:12.7.0
255
device Zaehler Seriennr. 0-0:96.1.255255
status Zaehler Status 1-0:96.5.5
255
counter Zaehlerstand Wirkleistung 1-0:1.8.255255
counter-out Zaehlerstand Lieferg. 1-0:2.8.255
255
esy-counter-t1 Active Power Counter Tariff 1 1-0:1.8.1255
esy-counter-t2 Active Power Counter Tariff 2 1-0:1.8.2
255
hag-id Eigentumsnr. 1-0:0.0.0255
hag-status Netz Status 1-0:96.50.0
0
hag-frequency Netz Periode 1-0:96.50.01
hag-temp aktuelle Chiptemperatur 1-0:96.50.0
2
hag-temp-min minimale Chiptemperatur 1-0:96.50.03
hag-temp-avg gemittelte Chiptemperatur 1-0:96.50.0
4
hag-temp-max maximale Chiptemperatur 1-0:96.50.05
hag-check Kontrollnr. 1-0:96.50.0
6
hag-diag Diagnose 1-0:96.50.07
lg-counter-et Sum active energy (Total) 255-255:16.8.0
255
lg-counter-ht Sum active energy (T1) 255-255:16.8.1255
lg-counter-lt Sum active energy (T2) 255-255:16.8.2
255
following APIs are supported:
volkszaehler-api
mysmartgrid-api
vzlogger 0.8.1 - volkszaehler.org logging utility
by Steffen Vogel [email protected]
send bugreports to Issues · volkszaehler/vzlogger · GitHub
[11:35:49] INFO: ==============================================================================
[11:35:49] INFO: ==============================================================================
cat: unrecognized option: 1
BusyBox v1.34.1 (2022-04-04 10:19:27 UTC) multi-call binary.
Usage: cat [-nbvteA] [FILE]…
Print FILEs to stdout
-n Number output lines
-b Number nonempty lines
-v Show nonprinting characters as ^x or M-x
-t …and tabs as ^I
-e …and end lines with $
-A Same as -vte
[11:35:49] INFO:
[11:35:50] INFO: ==============================================================================
[11:35:50] INFO: Starting vzlogger
/usr/local/bin/vzlogger: unrecognized option: 1
Usage: /usr/local/bin/vzlogger [options]
following options are available:
-c, --config configuration file
-o, --log log file
-f, --foreground run in foreground, do not daemonize
-l, --httpd activate local interface (tiny HTTPd which serves live readings)
-p, --httpd-port TCP port for HTTPd
-r, --register register device
-v, --verbose enable verbose output
-h, --help show this help
-V, --version show version of vzlogger
following protocol types are supported:
file Read from file or fifo
exec Parse program output
random Generate random values with a random walk
fluksov2 Read from Flukso’s onboard SPI fifo
s0 S0-meter directly connected to RS232
d0 DLMS/IEC 62056-21 plaintext protocol
sml Smart Message Language as used by EDL-21, eHz and SyM²
w1therm W1-therm / 1wire temperature devices
oms OMS (M-BUS) protocol based devices

you have to create an configfile
I added on the addon an “Template” configfile
in the options you have set the path to your configfile not the configuration itself

hast du den fehler gefunden?

Servus, I have created a vzlogger.con file and put it in the folder the folder “config”.
Here is the content:
{
“verbosity”: 10,
“retry”: 30,
“local”: {
“enabled”: false,
“port”: 8081,
“index”: true,
“timeout”: 0,
“buffer”: -1
},
“meters”: [
{
“enabled”: true,
“allowskip”: false,
“protocol”: “d0”,
“device”: “/dev/ttyUSB0”,
“aggtime”: -1,
“interval”: 10,
“pullseq”: “2F3F210D0A”, // “/?!\r\n” = 2F 3F 21 0D 0A
“ackseq”: “063034300D0A”, //needs to be in accordance to parameter ‘baudrate_read’
//“auto” for auto detection
“baudrate”: 300,
“baudrate_read”: 4800,
“baudrate_change_delay”: 300,
“parity”: “7e1”,
“use_local_time”: false,
“read_timeout”: 10, //?? 2200ms according to manual?
“dump_file”: “/config/D0_pullSeq.txt”,
“channels”: [
{
“identifier”: “1.7.0”, //Positive active instantaneous power (A+) [kW]
“uuid”: “00000000-0000-0000-0000-000000000000”,
“api”: “influxdb”,
“host”: “http://localhost:8086”,
“database”: “vzlogger”,
“measurement_name”: “vz_measurement”,
“duplicates”: 600,
“username”: “”,
“password”: “”
}, {
“identifier”: “1.8.1”, //Positive active energy (A+) in tariff T1 [kWh]
“uuid”: “00000000-0000-0000-0000-000000000000”,
“api”: “influxdb”,
“host”: “http://localhost:8086”,
“database”: “vzlogger”,
“measurement_name”: “vz_measurement”,
“duplicates”: 600,
“username”: “”,
“password”: “”
}, {
“identifier”: “2.8.1”, //Negative active energy (A+) in tariff T1 [kWh]
“uuid”: “00000000-0000-0000-0000-000000000000”,
“api”: “influxdb”,
“host”: “http://localhost:8086”,
“database”: “vzlogger”,
“measurement_name”: “vz_measurement”,
“duplicates”: 600,
“username”: “”,
“password”: “”
}
]
}
]
}

In the vzlogger protokoll I get this:

[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.128, value=135.381, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.1
27, value=132.010, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.126, value=129.236, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.1
25, value=126.996, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.124, value=121.648, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.1
23, value=118.335, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.122, value=115.298, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.1
21, value=112.545, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.120, value=110.467, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.1
19, value=107.505, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.118, value=101.144, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=3.8.1
17, value=92.337, unit=)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=4.8.1, value=1188.562, unit=kvarh)
[Aug 15 01:22:43][d0] Parsed reading (OBIS code=4.8.131, value=1175.069, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
30, value=1146.070, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.129, value=1112.690, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
28, value=1086.346, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.127, value=1059.731, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
26, value=1025.498, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.125, value=989.925, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
24, value=957.524, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.123, value=923.520, unit=)
[Aug 15 01:22:44][d0] Failed to parse obis code (C.60.5.1)
[Aug 15 01:22:44][d0] Failed to parse obis code (C.60.5.2)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.1.8.1)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.1.8.2)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.1.8.3)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.1.8.4)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.1.8.5)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.1.8.6)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.2.8.1)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.2.8.2)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.2.8.3)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.2.8.4)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.2.8.5)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
22, value=889.667, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.121, value=857.148, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
20, value=824.492, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.119, value=792.462, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1
18, value=765.758, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=4.8.1*17, value=728.304, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=0.9.1, value=01:22:44, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=0.9.2, value=23-08-15, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=0.2.0, value=07.000 0998 E354, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=C.60.5.1, value=D.01, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=C.60.5.2, value=20.023 0998 1189, unit=)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=1.7.0, value=2.825, unit=kW)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=2.7.0, value=0.904, unit=kW)
[Aug 15 01:22:44][d0] Parsed reading (OBIS code=3.7.0, value=0.607, unit=kvar)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=4.7.0, value=0.657, unit=kvar)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=14.7, value=49.99, unit=Hz)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=32.7, value=239.0, unit=V)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=52.7, value=238.6, unit=V)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=72.7, value=240.2, unit=V)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=31.7, value=5.68, unit=A)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=51.7, value=6.97, unit=A)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=71.7, value=3.98, unit=A)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=91.7, value=6.25, unit=A)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=81.7.4, value=-28.9, unit=Deg)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=81.7.15, value=10.1, unit=Deg)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=81.7.26, value=160.8, unit=Deg)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=81.7.1, value=119.9, unit=Deg)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=81.7.12, value=119.7, unit=Deg)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=81.7.20, value=120.2, unit=Deg)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=32.36.0, value=0, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=52.36.0, value=0, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=72.36.0, value=0, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=32.32.0, value=0, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=52.32.0, value=0, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=72.32.0, value=0, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=C.2.1, value=22-07-22 12:42, unit=)
[Aug 15 01:22:45][d0] Parsed reading (OBIS code=C.7.0, value=5, unit=)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.7.1, value=0, unit=)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.7.2, value=0, unit=)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.7.3, value=0, unit=)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.C.1, value=0, unit=)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.1.8.1, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.1.8.2, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.1.8.3, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.1.8.4, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.1.8.5, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.1.8.6, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.2.8.1, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.2.8.2, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.2.8.6)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.2.8.3, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.2.8.4, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Parsed reading (OBIS code=C.2.8.5, value=0.0, unit=kW)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.60.4.1)
[Aug 15 01:22:46][d0] Failed to parse obis code (C.60.4.2)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.3)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.4)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.5)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.6)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.7)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.11)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.13)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.14)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.15)
[Aug 15 01:22:47][d0] Failed to parse obis code (C.60.4.16)

Not sure what next.

Kind regards

Ed

me 2, looks like something is working but something not.
did you test local on your computer? with an own vzlogger instance just 4 testing

I did the test in HA and vzlogger add-on (installed on my HP Thin Client T620).

i mean did you test with an normal vzlogger instanz before you used it on HA?

I also wanted to read the data from the Hichi USB sensor, but I can’t get the Sensor component in HomeAssistant to work. The logs from vzlogger show me that the data is read correctly but somehow isn’t send via HTTP. This is my vzlogger config file:

{
"retry" : 3,
"verbosity" : 15,
 
"local" : {
	"enabled" : true,
	"port" : 8080,
	"index" : true,
	"timeout" : 30,
	"buffer" : 600
},
 
"meters" : [
        {
        "enabled" : true,
        "device" : "/dev/ttyUSB0",
        "protocol" : "sml",
        "parity" : "8N1",
	    "baudrate" : 9600, 
	    "aggtime" : -1,
    	"aggfixedinterval" : true,
        "channels": [{
            "api": "null",
            "uuid" : "xxxxxxx",
            "identifier" : "1-0:16.7.0*255",
            "aggmode" : "MAX",
            "duplicates": 3600
            }]
        },
        {
        "enabled" : true,
        "device" : "/dev/ttyUSB1",
        "protocol" : "sml",
        "parity" : "8N1",
	    "baudrate" : 9600,
	    "aggtime" : -1,
	    "aggfixedinterval" : true,
        "channels": [{
            "api": "null",
            "uuid" : "xxxxxxx",
            "identifier" : "1-0:16.7.0*255",
            "aggmode" : "MAX",
            "duplicates": 3600
            }]
        }
    ]
}

Via the ssh client on Home Assistant and curl command I tried to check if any data is being sent over the port 8080, but I always get this error:

[core-ssh ~]$ curl -v http://192.168.0.116:8080
Trying 192.168.0.116:8080 ...
* connect to 192.168.0.116 port 8080 failed: Connection refused
* Failed to connect to 192.168.0.116 port 8080 after 0 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 192.168.0.116 port 8080 after 0 ms: Connection refused

I also tried homeassistant.local and localhost but it doesn’t receive anything. Does anybody know what’s the right IP-adress, I need to use to get the rest sensor going or do I need to change something in vzlogger config file? Btw, here is the vzlogger log (with verbose-level 15):

[14:05:46] INFO: Starting vzlogger
[Jun 25 14:05:46][main] vzlogger v0.8.0 based on heads/master-0-gccb6d8ee49 from Fri, 5 Nov 2021 03:13:34 +0100 started.
[Jun 25 14:05:46][main] log level is 15
libsml: error: unrecognized sequence
[Jun 25 14:05:46][mtr0] Creating new meter with protocol sml.
[Jun 25 14:05:46][mtr0] Meter configured, enabled.
[Jun 25 14:05:46]       New meter initialized (protocol=sml)
[Jun 25 14:05:46]       Configure channel.
[Jun 25 14:05:46][chn0] New channel initialized (uuid=...db0d05 api=null id=1-0:16.7.0*255)
[Jun 25 14:05:46][mtr1] Creating new meter with protocol sml.
[Jun 25 14:05:46][mtr1] Meter configured, enabled.
[Jun 25 14:05:46]       New meter initialized (protocol=sml)
[Jun 25 14:05:46]       Configure channel.
[Jun 25 14:05:46][chn1] New channel initialized (uuid=...e3a1f9 api=null id=1-0:16.7.0*255)
[Jun 25 14:05:46]       Have 2 meters.
[Jun 25 14:05:46][main] local=1
[Jun 25 14:05:46]       Process not daemonized...
[Jun 25 14:05:46][push] No pushDataServer defined.
[Jun 25 14:05:46][]     ===> Start meters
[Jun 25 14:05:46][mtr0] Meter connection established
[Jun 25 14:05:46][mtr0] Meter thread started
[Jun 25 14:05:46][mtr0] Meter is opened. Starting channels.
[Jun 25 14:05:46][mtr0] Number of readers: 32
[Jun 25 14:05:46][mtr0] Config.local: 1
[Jun 25 14:05:46][chn0] Logging thread started
[Jun 25 14:05:46][chn0] Start logging thread for null-api.
[Jun 25 14:05:46][chn0] Using null api- meter data available via local httpd if enabled.
[Jun 25 14:05:46][mtr1] Meter connection established
[Jun 25 14:05:46][mtr1] Meter thread started
[Jun 25 14:05:46][mtr1] Meter is opened. Starting channels.
[Jun 25 14:05:46][chn1] Logging thread started
[Jun 25 14:05:46][chn1] Start logging thread for null-api.
[Jun 25 14:05:46][http] Starting local interface HTTPd on port 8080
[Jun 25 14:05:46][mtr1] Number of readers: 32
[Jun 25 14:05:46][mtr1] Config.local: 1
[Jun 25 14:05:46][chn1] Using null api- meter data available via local httpd if enabled.
[Jun 25 14:05:46][]     Startup done.
[Jun 25 14:05:47][mtr0] Got 7 new readings from meter:
[Jun 25 14:05:47][mtr0] Reading: id=1-0:1.8.0*255/ObisIdentifier:1-0:1.8.0*255 value=12970193.30 ts=1719317147736
[Jun 25 14:05:47][mtr0] Reading: id=1-0:1.8.1*255/ObisIdentifier:1-0:1.8.1*255 value=12970193.30 ts=1719317147736
[Jun 25 14:05:47][mtr0] Reading: id=1-0:1.8.2*255/ObisIdentifier:1-0:1.8.2*255 value=0.00 ts=1719317147736
[Jun 25 14:05:47][mtr0] Reading: id=1-0:16.7.0*255/ObisIdentifier:1-0:16.7.0*255 value=608.00 ts=1719317147736
[Jun 25 14:05:47][mtr0] Reading: id=1-0:36.7.0*255/ObisIdentifier:1-0:36.7.0*255 value=515.00 ts=1719317147736
[Jun 25 14:05:47][mtr0] Reading: id=1-0:56.7.0*255/ObisIdentifier:1-0:56.7.0*255 value=80.00 ts=1719317147736
[Jun 25 14:05:47][mtr0] Reading: id=1-0:76.7.0*255/ObisIdentifier:1-0:76.7.0*255 value=11.00 ts=1719317147736
[Jun 25 14:05:47][chn0] Adding reading to queue (value=608.00 ts=1719317147736)
[Jun 25 14:05:47][MAX]  608.000000 @ 1719317147736
[Jun 25 14:05:47][MAX]  RESULT 608.000000 @ 1719317147736
[Jun 25 14:05:48][sml]  reopen called. current fd=4
[Jun 25 14:05:48][sml]  after reopen fd=4
[Jun 25 14:05:48][mtr0] Got 7 new readings from meter:
[Jun 25 14:05:48][mtr0] Reading: id=1-0:1.8.0*255/ObisIdentifier:1-0:1.8.0*255 value=12970193.50 ts=1719317148931
[Jun 25 14:05:48][mtr0] Reading: id=1-0:1.8.1*255/ObisIdentifier:1-0:1.8.1*255 value=12970193.50 ts=1719317148931
[Jun 25 14:05:48][mtr0] Reading: id=1-0:1.8.2*255/ObisIdentifier:1-0:1.8.2*255 value=0.00 ts=1719317148931
[Jun 25 14:05:48][mtr0] Reading: id=1-0:16.7.0*255/ObisIdentifier:1-0:16.7.0*255 value=579.00 ts=1719317148931
[Jun 25 14:05:48][mtr0] Reading: id=1-0:36.7.0*255/ObisIdentifier:1-0:36.7.0*255 value=487.00 ts=1719317148931
[Jun 25 14:05:48][mtr0] Reading: id=1-0:56.7.0*255/ObisIdentifier:1-0:56.7.0*255 value=79.00 ts=1719317148931
[Jun 25 14:05:48][mtr0] Reading: id=1-0:76.7.0*255/ObisIdentifier:1-0:76.7.0*255 value=12.00 ts=1719317148931
[Jun 25 14:05:48][chn0] Adding reading to queue (value=579.00 ts=1719317148931)
[Jun 25 14:05:48][MAX]  579.000000 @ 1719317148931
[Jun 25 14:05:48][MAX]  RESULT 579.000000 @ 1719317148931
[Jun 25 14:05:50][mtr0] Got 7 new readings from meter:

I am using the homeassistant ip Adress example http://192.168.2.4:8084

Check the Addon config is it set 8080,too?

Hello, I’m new at Home Assistant and my idea was to connect a volkszaehler sensor directly to my homeassistant hardware (RPi 4). So I found your conversation and thought - that’s it. But there are two basic problems, I can’t solve:

  1. I generated a ‘vzlogger.conf’ file with the content from here in the folder ‘/homeassistant/share/’ and adjusted the vzLogger Konfiguration to: /homeassistant/share/vzlogger.conf.
    results in error message:
    cat: /homeassistant/share/vzlogger.conf: No such file or directory
    [23:52:14] INFO:
    [23:52:14] INFO: ==============================================================================[23:52:14] INFO: Starting vzlogger
    [Jul 06 23:52:14][main] vzlogger v0.8.0 based on heads/master-0-gccb6d8ee49 from Fri, 5 Nov 2021 03:13:34 +0100 started.
    [Jul 06 23:52:14] Cannot open configfile /homeassistant/share/vzlogger.conf: No such file or directory
    [Jul 06 23:52:14] Failed to parse configuration due to: Cannot open configfile.
    Did I put it in the wrong docker container? But how can I get to the right container?

  2. the UUID is still something mystic to me. From where can I get the right UUID for my selfmade sensor? Or is it OK to use the UUID from your example with all zeros?

did you check the path ? /share/vzlogger.conf should be