[vz-users] vzlogger produziert Fehlermeldungen
Maik Weidemann
m+vz at weidemann.online
Do Apr 20 23:13:45 CEST 2023
Hi,
die Fehlermeldung deutet auf ein Problem mit der Datenbank hin. Dort
soll etwas geschrieben werden, was schon existiert.
Gruß
Maik
Am 20.04.23 um 15:23 schrieb applicationMGR:
> Hallo,
>
> habe eben wieder ins Log des vzloggers geschaut, weil das Frontend
> nicht so recht funktioniert und es scheint Probleme mit der Middleware
> bei chn0 und chn4 zu geben (siehe vzlogger.conf weiter unten).
>
> Hat jemand damit Erfahrung und weiß möglicherweise, woher das kommen kann?
>
> [Apr 20 11:36:41][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:36:41][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:37:40][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:37:41][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:38:41][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:38:41][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:39:52][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:39:55][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:41:06][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:41:08][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:41:40][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:41:41][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:42:40][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:42:41][chn0] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?),
> (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?,?), (3,?
> [Apr 20 11:43:40][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:44:41][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
> [Apr 20 11:45:41][chn4] CURL Error from middleware:
> '*UniqueConstraintViolationException*': 'An exception occurred while
> executing 'INSERT INTO data (channel_id, timestamp, value) VALUES
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?),
> (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?,?), (7,?
>
> Freue mich über Eure Hilfe!
>
> Viele Grüße
> Armin
>
>
>> Anfang der weitergeleiteten Nachricht:
>>
>> *Von: *applicationMGR <applicationMGR at ecoCuyo.de>
>> *Betreff: **Aw: Push-Server sendet keine Null-Werte*
>> *Datum: *17. April 2023 um 19:59:04 MESZ
>> *An: *volkszaehler-users <volkszaehler-users at demo.volkszaehler.org>
>>
>> Hallo,
>>
>> kann es ein Performance-Problem mit der MariaDB sein? Die
>> Installation läuft auf einem Raspberry Pi 3 Model B Rev 1.2 mit
>> SanDisk Ultra 16 GB microSDHC Memory Card.
>>
>> Die Datenbank selbst scheint beim Neustart heute Morgen i.O:
>>
>> Apr 17 10:19:32 ecoRaspi01 systemd[1]: Starting *MariaDB*10.5.15
>> database server...
>> Apr 17 10:19:34 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:34 0
>> [Note] /usr/sbin/*mariadb*d (mysqld 10.5.15-*MariaDB*-0+deb11u1)
>> starting as process 560 ...
>> Apr 17 10:19:34 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:34 0
>> [Note] InnoDB: Uses event mutexes
>> Apr 17 10:19:34 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:34 0
>> [Note] InnoDB: Compressed tables use zlib 1.2.11
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Number of pools: 1
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Using generic crc32 instructions
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Using Linux native AIO
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Initializing buffer pool, total size = 134217728,
>> chunk size = 134217728
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Completed initialization of buffer pool
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: 128 rollback segments are active.
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Creating shared tablespace for temporary tables
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically
>> writing the file full; Please wait ...
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: File './ibtmp1' size is now 12 MB.
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: 10.5.15 started; log sequence number 988900435;
>> transaction id 1390134
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] Plugin 'FEEDBACK' is disabled.
>> Apr 17 10:19:35 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:35 0
>> [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
>> Apr 17 10:19:36 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:36 0
>> [Note] Server socket created on IP: '127.0.0.1'.
>> Apr 17 10:19:36 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:36 0
>> [Note] Reading of all Master_info entries succeeded
>> Apr 17 10:19:36 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:36 0
>> [Note] Added new Master_info '' to hash table
>> Apr 17 10:19:36 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:36 0
>> [Note] /usr/sbin/*mariadb*d: ready for connections.
>> Apr 17 10:19:36 ecoRaspi01 *mariadb*d[560]: Version:
>> '10.5.15-*MariaDB*-0+deb11u1' socket: '/run/mysqld/mysqld.sock'
>> port: 3306 Raspbian 11
>> Apr 17 10:19:37 ecoRaspi01 *mariadb*d[560]: 2023-04-17 10:19:37 0
>> [Note] InnoDB: Buffer pool(s) load completed at 230417 10:19:37
>> Apr 17 10:19:38 ecoRaspi01 systemd[1]: Started *MariaDB*10.5.15
>> database server.
>> Apr 17 10:19:38 ecoRaspi01 /etc/mysql/debian-start[652]: This
>> installation of *MariaDB*is already upgraded to 10.5.15-*MariaDB*.
>> Apr 17 10:19:38 ecoRaspi01 /etc/mysql/debian-start[652]: There is no
>> need to run mysql_upgrade again for 10.5.15-*MariaDB*.
>>
>>
>> Im syslog standen davor unzählige Errors:
>>
>> Apr 17 08:44:23 MeinHost mariadbd[559]: 2023-04-17 8:43:29 2046
>> [Warning] Aborted connection 2046 to db: 'volkszaehler' user: 'vz'
>> host: 'localhost' (Got an *error*reading communication packets)
>> Apr 17 08:44:26 MeinHost mariadbd[559]: 2023-04-17 8:43:38 2047
>> [Warning] Aborted connection 2047 to db: 'volkszaehler' user: 'vz'
>> host: 'localhost' (Got an *error*reading communication packets)
>> Apr 17 08:44:31 MeinHost mariadbd[559]: 2023-04-17 8:44:04 2048
>> [Warning] Aborted connection 2048 to db: 'volkszaehler' user: 'vz'
>> host: 'localhost' (Got an *error*reading communication packets)
>> Apr 17 08:44:36 MeinHost mariadbd[559]: 2023-04-17 8:44:05 2049
>> [Warning] Aborted connection 2049 to db: 'volkszaehler' user: 'vz'
>> host: 'localhost' (Got an *error*reading communication packets)
>> Apr 17 08:44:40 MeinHost mariadbd[559]: 2023-04-17 8:44:16 2050
>> [Warning] Aborted connection 2050 to db: 'volkszaehler' user: 'vz'
>> host: 'localhost' (Got an *error*reading communication packets)
>> Apr 17 08:44:42 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info]
>> User Deprecated: Method
>> "Psr\Http\Message\RequestInterface::getMethod()" might add "string"
>> as a native return type declaration in the future. Do the same in
>> implementation "RingCentral\Psr7\Request" now to avoid *error*s or
>> add an explicit @return annotation to suppress this message.
>> Apr 17 08:44:44 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info]
>> User Deprecated: Method
>> "Psr\Http\Message\RequestInterface::withMethod()" might add "static"
>> as a native return type declaration in the future. Do the same in
>> implementation "RingCentral\Psr7\Request" now to avoid *error*s or
>> add an explicit @return annotation to suppress this message.
>> Apr 17 08:44:47 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info]
>> User Deprecated: Method "Psr\Http\Message\RequestInterface::getUri()"
>> might add "UriInterface" as a native return type declaration in the
>> future. Do the same in implementation "RingCentral\Psr7\Request" now
>> to avoid *error*s or add an explicit @return annotation to suppress
>> this message.
>> Apr 17 08:44:52 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info]
>> User Deprecated: Method
>> "Psr\Http\Message\RequestInterface::withUri()" might add "static" as
>> a native return type declaration in the future. Do the same in
>> implementation "RingCentral\Psr7\Request" now to avoid *error*s or
>> add an explicit @return annotation to suppress this message.
>> Apr 17 08:44:58 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info]
>> User Deprecated: Method
>> "Psr\Http\Message\MessageInterface::withHeader()" might add "static"
>> as a native return type declaration in the future. Do the same in
>> implementation "RingCentral\Psr7\Request" now to avoid *error*s or
>> add an explicit @return annotation to suppress this message.
>> Apr 17 08:45:04 MeinHost php[645]: 2023-04-17T08:39:01+02:00 [info]
>> User Deprecated: Method
>> "Psr\Http\Message\ServerRequestInterface::getServerParams()" might
>> add "array" as a native return type declaration in the future. Do the
>> same in implementation "React\Http\Message\ServerRequest" now to
>> avoid *error*s or add an explicit @return annotation to suppress this
>> message.
>>
>> Sagt das jemanden etwas hinsichtlich wo ich den/die Fehler suchen muss?
>>
>> Viele Grüße
>> Armin
>>
>>
>>
>>> Am 17.04.2023 um 11:20 schrieb applicationMGR
>>> <applicationMGR at ecoCuyo.de>:
>>>
>>> Hallo,
>>>
>>> seit der Umsrtellung auf vzlogger v0.8.1 based on
>>> heads/direction_from_status-0-g408df91556 from Sun, 15 Jan 2023
>>> 02:00:27 +0100 laufen in der vzlogger.log massenhaft Fehler auf und
>>> der Server stürzt regelmäßig ab.
>>>
>>>
>>> *$*tail -f /var/log/vzlogger/vzlogger.log
>>> [Apr 17 10:16:15][chn1] CURL: Timeout was reached
>>> [Apr 17 10:16:45][chn2] CURL: Timeout was reached
>>> [Apr 17 10:17:16][chn3] CURL: Timeout was reached
>>> [Apr 17 10:17:31][chn0] CURL Error from middleware: unexpected character
>>> [Apr 17 10:18:02][chn2] CURL: Timeout was reached
>>> [Apr 17 10:18:04][push] CURL: http://127.0.0.1:5582 Timeout was reached
>>> [Apr 17 10:18:33][chn3] CURL: Timeout was reached
>>> [Apr 17 10:18:57][push] CURL: http://127.0.0.1:5582 Timeout was reached
>>> [Apr 17 10:19:03][chn0] CURL: Timeout was reached
>>> [Apr 17 10:19:18][push] CURL: http://127.0.0.1:5582 Failure when
>>> receiving data from the peer
>>>
>>> Die Konfiguration sieht so aus:
>>>
>>> {
>>> "verbosity": 1,
>>> "log": "/var/log/vzlogger/vzlogger.log",
>>> "retry": 30,
>>>
>>> "local": {
>>> "enabled": true,
>>> "port": 8081,
>>> "index": true,
>>> "timeout": 30,
>>> "buffer": -2
>>> },
>>>
>>> "push": [
>>> {
>>> "url": "http://127.0.0.1:5582"
>>> }
>>> ],
>>>
>>> "mqtt": {
>>> "enabled": false, // enable mqtt client. needs host and port as well
>>> "host": "test.mosquitto.org <http://test.mosquitto.org/>", // mqtt
>>> server addr
>>> "port": 1883, // 1883 for unencrypted, 8883 enc, 8884 enc cert needed,
>>> "cafile": "", // optional file with server CA
>>> "capath": "", // optional path for server CAs. see mosquitto.conf.
>>> Specify only cafile or capath
>>> "certfile": "", // optional file for your client certificate (e.g.
>>> client.crt)
>>> "keyfile": "", // optional path for your client certficate private
>>> key (e.g. client.key)
>>> "keypass": "", // optional password for your private key
>>> "keepalive": 30, // optional keepalive in seconds.
>>> "topic": "vzlogger/data", // optional topic dont use $ at start and
>>> no / at end
>>> "id": "", // optional static id, if not set "vzlogger_<pid>" will be
>>> used
>>> "user": "", // optional user name for the mqtt server
>>> "pass": "", // optional password for the mqtt server
>>> "retain": false, // optional use retain message flag
>>> "rawAndAgg": false, // optional publish raw values even if agg mode
>>> is used
>>> "qos": 0, // optional quality of service, default is 0
>>> "timestamp": false // optional whether to include a timestamp in the
>>> payload
>>> },
>>>
>>> "meters": [
>>> {
>>> "enabled" : true,
>>> "protocol" : "sml",
>>> "device" : "/dev/usb-ir-lesekopf0",
>>> "aggtime" : 60,
>>> "aggfixedinterval" : true,
>>> "channels": [{
>>> "uuid" : „8c4d02b0-xxxx-xxxx-xxxxxxxxxxxx",
>>> "middleware" : "http://localhost/middleware.php",
>>> "identifier" : "1-0:2.8.0",/* PV-2.8.0-Erzeugung */
>>> "duplicates": 3600,
>>> "aggmode" : "AVG"
>>> }, {
>>> "uuid" : "6c9c10a0--xxxx-xxxx-xxxxxxxxxxxx",
>>> "middleware" : "http://localhost/middleware.php",
>>> "identifier" : "1-0:15.7.0",/* PV-15.7.0-Wirkleistung */
>>> "aggmode" : "AVG"
>>> }]
>>> }, {
>>> "enabled" : true,
>>> "protocol" : "sml",
>>> "device" : "/dev/usb-ir-lesekopf1",
>>> "direction_from_status": true,
>>> "aggtime" : 60,
>>> "aggfixedinterval" : true,
>>> "channels" :[{
>>> "uuid" : "b9693e00-xxxx-xxxx-xxxxxxxxxxxx",
>>> "middleware" : "http://localhost/middleware.php",
>>> "identifier" : "1-0:1.8.0", /* Haus-1.8.0-Bezug */
>>> "duplicates": 3600,
>>> "aggmode" : "AVG"
>>> }, {
>>> "uuid" : "ec7c7360-xxxx-xxxx-xxxxxxxxxxxx",
>>> "middleware" : "http://localhost/middleware.php",
>>> "identifier" : "1-0:2.8.0", /* Haus-2.8.0-Lieferung */
>>> "duplicates": 3600,
>>> "aggmode" : "AVG"
>>> }, {
>>> "uuid" : "61d5d350-xxxx-xxxx-xxxxxxxxxxxx",
>>> "middleware" : "http://localhost/middleware.php",
>>> "identifier" : "1-0:15.7.0", /* Haus-15.7.0-Wirkleistung */
>>> "duplicates": 3600,
>>> "aggmode" : "AVG"
>>> }]
>>> }
>>> ]
>>> }
>>>
>>> Hat jemand eine Ahnung, was ich da ändern könnte, um wieder
>>> Stabilität ins System zu bringen?
>>>
>>> Viele Grüße
>>> Armin
>>>
>>>
>>>
>>>
>>>> Am 02.04.2023 um 17:43 schrieb Emilio ecoCuyo <Emilio at ecoCuyo.de>:
>>>>
>>>> Hallo zusammen,
>>>>
>>>> versuche aktuell per vzlogger push eine Installation von evcc zu
>>>> versorgen, um eine Wallbox PV-geführt zu betreiben.
>>>> Dabei entsteht ein Problem mit dem verwendeten EMH
>>>> Zweirichtungszähler, der den Wert der aktuellen Wirkleistung nur
>>>> vorzeichenlos ausgibt, wodurch anhand dieses Werts nicht klar wird,
>>>> ob Bezug oder Lieferung stattfindet.
>>>>
>>>> Beim Debuggen mit verbosity 15 konnte ich nachvollziehen, dass zwar
>>>> die Energiewerte aller angelegten Kanäle ge-pushed werden(mtr1 ist
>>>> der Zeirichtungszähler). Im Log sieht man an den OBIS Codes, dass
>>>> sämtliche Zählerwerte als Energiewerte in Wh sowie die aktuelle
>>>> Leistung in W ausgegeben werden, auf wenn kein Verbrauch auf der
>>>> UUID für "Bezug" stattfand.
>>>>
>>>> [Mar 27 16:20:10][mtr1] Reading:
>>>> id=1-0:1.8.0*255/ObisIdentifier:1-0:1.8.0*255 value=17886641.20
>>>> ts=1679926810623
>>>> [Mar 27 16:20:10][mtr1] Reading:
>>>> id=1-0:2.8.0*255/ObisIdentifier:1-0:2.8.0*255 value=62185513.20
>>>> ts=1679926810623
>>>> [Mar 27 16:20:10][mtr1] Reading:
>>>> id=1-0:1.8.1*255/ObisIdentifier:1-0:1.8.1*255 value=17886641.20
>>>> ts=1679926810623
>>>> [Mar 27 16:20:10][mtr1] Reading:
>>>> id=1-0:2.8.1*255/ObisIdentifier:1-0:2.8.1*255 value=62185513.30
>>>> ts=1679926810623
>>>> [Mar 27 16:20:10][mtr1] Reading:
>>>> id=1-0:1.8.2*255/ObisIdentifier:1-0:1.8.2*255 value=0.00
>>>> ts=1679926810623
>>>> [Mar 27 16:20:10][mtr1] Reading:
>>>> id=1-0:15.7.0*255/ObisIdentifier:1-0:15.7.0*255 value=3448.40
>>>> ts=1679926810623
>>>> [Mar 27 16:20:10][chn1] Adding reading to queue (value=17886641.20
>>>> ts=1679926810623)
>>>> [Mar 27 16:20:10][push] added to uuid xxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>> [Mar 27 16:20:10][chn2] Adding reading to queue (value=62185513.20
>>>> ts=1679926810623)
>>>> [Mar 27 16:20:10][push] added to uuid yyyyyyyyyyyyyyyyyyyyyyy
>>>> [Mar 27 16:20:10][chn3] Adding reading to queue (value=3448.40
>>>> ts=1679926810623)
>>>> [Mar 27 16:20:10][push] added to uuid zzzzzzzzzzzzzzzzzzzzzzzzzzz
>>>> [Mar 27 16:20:10][push] push: { "data": [ { "uuid":
>>>> "zzzzzzzzzzzzzzzzzzzzzzzzzzz", "tuples": [ [ 1679926810623,
>>>> 3448.4000000000001 ] ] }, { "uuid": "yyyyyyyyyyyyyyyyyyyyyyy",
>>>> "tuples": [ [ 1679926810623, 62185513.200000003 ] ] }, { "uuid":
>>>> "xxxxxxxxxxxxxxxxxxxxxxxxxxx", "tuples": [ [ 1679926810623,
>>>> 17886641.199999999 ] ] } ] }
>>>>
>>>> Leider wird wie mir scheint dann beim push für einen unveränderten
>>>> Energiezähler kein Wert Null für die Leistung ausgegeben, die aus
>>>> dem Differential der letzten beiden tuples berechnet wird. Ist ja
>>>> eigentlich auch nicht nötig… doch manchmal eben doch.
>>>>
>>>> Das Thema habe ich auch in
>>>> https://github.com/evcc-io/evcc/discussions/6021 adressiert, weil
>>>> das Problem eigentlich das Plugin "calc" von evcc ist. Doch bislang
>>>> hatte da noch niemand eine zündende Idee.
>>>>
>>>> Vielleicht weiß jemand weiter? So etwas wie send_zero wie beim
>>>> S0-Protokoll gibt’s wohl nicht?
>>>>
>>>> Viele Grüße
>>>> Armin
>>>
>>
>
-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://demo.volkszaehler.org/pipermail/volkszaehler-users/attachments/20230420/0cb5f120/attachment-0001.html>
Mehr Informationen über die Mailingliste volkszaehler-users