Wasserzähler - Version 2 - all-in-device
-
@joergh ja genau und die soll ja nicht funktionieren, macht es aber wenn ich fest auf den Klemmverschluss drücke
-
@samot Ok, danke. Ich habe nämlich gerade wieder drei von denen gekauft, weil ich nicht wusste, dass die nicht funktionieren sollen...die probiere ich dann mal bei Gelegenheit.
Ursprünglich hatte ich 4 Stück gekauft und die liefen auch nach anfänglichen Problemen mit dem flashen auch alle einwandfrei, habe dann aber beim entsiegeln einer Kamera diese beschädigt. Danach dachte ich bestelle ich einfach noch ein Komplettmodul, inkl. der USB Platine. Leider war das bisher eher frustrierend, denn keine der inzwischen drei Varianten lief richtig. Entweder ließen sie sich nicht flashen oder die Kameras liefen nicht. Dachte ich bin zu doof, aber sehe nun, dass es tatsächlich nicht an mir liegt.
-
@jomjol
Nach dem Update auf die Version 10 habe ich die folgende FM im Log:mqtt.1 2021-12-30 23:30:33.598 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:29:52"} mqtt.0 2021-12-30 23:30:13.607 error Client [wasser] Cannot parse {"value":288.5381,"raw":"00288.5381,"error":"no error","rate":0.001315,"timestamp":"2021-12-30T23:29:28"} mqtt.0 2021-12-30 23:29:19.660 error adapter disabled mqtt.1 2021-12-30 23:25:42.668 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:25:01"} mqtt.0 2021-12-30 23:25:22.845 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:24:37"} mqtt.1 2021-12-30 23:20:51.525 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:20:10"} mqtt.0 2021-12-30 23:20:31.659 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:19:46"} mqtt.1 2021-12-30 23:16:00.641 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:15:19"} mqtt.0 2021-12-30 23:15:40.509 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:14:55"} mqtt.1 2021-12-30 23:11:09.565 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:10:28"} mqtt.0 2021-12-30 23:10:49.537 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:10:04"} mqtt.1 2021-12-30 23:06:18.614 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:05:37"} mqtt.0 2021-12-30 23:05:58.453 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:05:13"} mqtt.1 2021-12-30 23:01:27.446 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:00:46"} mqtt.0 2021-12-30 23:01:07.510 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T23:00:22"} mqtt.1 2021-12-30 22:56:36.819 warn Cannot parse "gaszaehler/main/json": {"value":18008.74,"raw":"18008.74,"error":"no error","rate":0.004027,"timestamp":"2021-12-30T22:55:55"} mqtt.0 2021-12-30 22:56:16.829 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:55:31"} mqtt.0 2021-12-30 22:56:16.803 warn State "mqtt.0.wasserzaehler.main.rate" has no existing object, this might lead to an error in future versions mqtt.1 2021-12-30 22:51:45.472 warn Cannot parse "gaszaehler/main/json": {"value":18008.72,"raw":"18008.72,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:51:04"} mqtt.0 2021-12-30 22:51:25.415 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:50:40"} mqtt.0 2021-12-30 22:51:25.392 warn State "mqtt.0.wasserzaehler.main.rate" has no existing object, this might lead to an error in future versions mqtt.1 2021-12-30 22:46:55.224 warn Cannot parse "gaszaehler/main/json": {"value":18008.72,"raw":"18008.72,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:46:13"} mqtt.0 2021-12-30 22:46:34.581 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:45:49"} mqtt.0 2021-12-30 22:46:34.559 warn State "mqtt.0.wasserzaehler.main.rate" has no existing object, this might lead to an error in future versions mqtt.1 2021-12-30 22:45:41.036 warn Cannot parse "gaszaehler/main/json": {"value":18008.72,"raw":"18008.72,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:44:58"} mqtt.1 2021-12-30 22:42:31.555 warn State "mqtt.1.gaszaehler.main.rate" has no existing object, this might lead to an error in future versions mqtt.0 2021-12-30 22:41:43.894 error Client [wasser] Cannot parse {"value":288.5317,"raw":"00288.5317,"error":"no error","rate":0.000000,"timestamp":"2021-12-30T22:40:59"}Als Broker verwende ich im MQTT.0 noch den internen Server im IOBROKER und der.1 ist als Client an einem Mosqiutto Broker.
Debugger listening on ws://127.0.0.1:9229/d6003680-5783-40d2-b432-887a07aef4c3 For help, see: https://nodejs.org/en/docs/inspector 2021-12-31 00:07:37.860 - debug: mqtt.0 (796659) Redis Objects: Use Redis connection: 127.0.0.1:9001 2021-12-31 00:07:37.876 - debug: mqtt.0 (796659) Objects client ready ... initialize now 2021-12-31 00:07:37.876 - debug: mqtt.0 (796659) Objects create System PubSub Client 2021-12-31 00:07:37.877 - debug: mqtt.0 (796659) Objects create User PubSub Client 2021-12-31 00:07:37.877 - debug: mqtt.0 (796659) Objects client initialize lua scripts 2021-12-31 00:07:37.883 - debug: mqtt.0 (796659) Objects connected to redis: 127.0.0.1:9001 2021-12-31 00:07:37.886 - debug: mqtt.0 (796659) objectDB connected 2021-12-31 00:07:37.886 - debug: mqtt.0 (796659) Redis States: Use Redis connection: 127.0.0.1:9000 2021-12-31 00:07:37.890 - debug: mqtt.0 (796659) States create System PubSub Client 2021-12-31 00:07:37.890 - debug: mqtt.0 (796659) States create User PubSub Client 2021-12-31 00:07:37.894 - debug: mqtt.0 (796659) States connected to redis: 127.0.0.1:9000 2021-12-31 00:07:37.895 - debug: mqtt.0 (796659) statesDB connected 2021-12-31 00:07:38.015 - debug: mqtt.0 (796659) Plugin sentry Initialize Plugin (enabled=true) 2021-12-31 00:07:38.063 - error: mqtt.0 (796659) adapter disabled 2021-12-31 00:07:38.064 - info: mqtt.0 (796659) starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.mqtt, node: v14.18.2, js-controller: 3.3.22 2021-12-31 00:07:38.143 - info: mqtt.0 (796659) Starting MQTT authenticated server on 0.0.0.0:1883 2021-12-31 00:07:38.143 - info: mqtt.0 (796659) Starting MQTT-WebSocket authenticated server on 0.0.0.0:1884 2021-12-31 00:07:38.192 - debug: mqtt.0 (796659) stateChange mqtt.0.info.connection: {"val":"","ack":true,"ts":1640905658191,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905658191} 2021-12-31 00:07:38.193 - debug: mqtt.0 (796659) onStateChange mqtt.0.info.connection: {"val":"","ack":true,"ts":1640905658191,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905658191} 2021-12-31 00:07:41.873 - info: mqtt.0 (796659) Client [wasser] connected with secret 1640905661865_7445 2021-12-31 00:07:41.906 - debug: mqtt.0 (796659) Client [wasser] with last will {"retain":true,"qos":0,"topic":"wasserzaehler/connection","payload":{"type":"Buffer","data":[99,111,110,110,101,99,116,105,111,110,32,108,111,115,116]}} 2021-12-31 00:07:41.906 - debug: mqtt.0 (796659) Client [wasser] with keepalive 60 set timeout to 90 seconds 2021-12-31 00:07:41.914 - debug: mqtt.0 (796659) stateChange mqtt.0.info.connection: {"val":"wasser","ack":true,"ts":1640905661913,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905661913} 2021-12-31 00:07:41.915 - debug: mqtt.0 (796659) onStateChange mqtt.0.info.connection: {"val":"wasser","ack":true,"ts":1640905661913,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905661913} 2021-12-31 00:07:42.910 - debug: mqtt.0 (796659) Client [wasser] pingreq 2021-12-31 00:08:12.919 - debug: mqtt.0 (796659) Client [wasser] pingreq 2021-12-31 00:08:43.008 - debug: mqtt.0 (796659) Client [wasser] pingreq 2021-12-31 00:09:13.209 - debug: mqtt.0 (796659) Client [wasser] pingreq 2021-12-31 00:09:38.843 - info: mqtt.0 (796659) Client [wasser] reconnected. Old secret 1640905661865_7445. New secret 1640905778840_6011 2021-12-31 00:09:38.845 - debug: mqtt.0 (796659) Client [wasser] with last will {"retain":true,"qos":0,"topic":"wasserzaehler/connection","payload":{"type":"Buffer","data":[99,111,110,110,101,99,116,105,111,110,32,108,111,115,116]}} 2021-12-31 00:09:38.846 - debug: mqtt.0 (796659) Client [wasser] with keepalive 60 set timeout to 90 seconds 2021-12-31 00:09:38.857 - debug: mqtt.0 (796659) stateChange mqtt.0.info.connection: {"val":"wasser","ack":true,"ts":1640905778852,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905661913} 2021-12-31 00:10:08.860 - debug: mqtt.0 (796659) Client [wasser] pingreq 2021-12-31 00:10:31.997 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.connection: {"val":"connected","ack":true,"ts":1640905831993,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640416562800} 2021-12-31 00:10:32.007 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.uptime: {"val":60,"ack":true,"ts":1640905832001,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905479400} 2021-12-31 00:10:32.016 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.freeMem: {"val":2987715,"ack":true,"ts":1640905832009,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905832009} 2021-12-31 00:10:32.017 - debug: mqtt.0 (796659) onStateChange mqtt.0.wasserzaehler.freeMem: {"val":2987715,"ack":true,"ts":1640905832009,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905832009} 2021-12-31 00:10:32.024 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.main.value: {"val":288.5381,"ack":true,"ts":1640905832018,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640903413572} 2021-12-31 00:10:32.032 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.main.error: {"val":"no error","ack":true,"ts":1640905832028,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640889028083} 2021-12-31 00:10:32.034 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.main.rate: {"val":0,"ack":true,"ts":1640905832029,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640903704690} 2021-12-31 00:10:32.045 - error: mqtt.0 (796659) Client [wasser] Cannot parse {"value":288.5381,"raw":"00288.5381,"error":"no error","rate":0.000000,"timestamp":"2021-12-31T00:09:47"} 2021-12-31 00:10:32.048 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.main.raw: {"val":"00288.5381","ack":true,"ts":1640905832046,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640903413590} 2021-12-31 00:10:32.050 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.main.timestamp: {"val":"2021-12-31T00:09:47","ack":true,"ts":1640905832048,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905832048} 2021-12-31 00:10:32.050 - debug: mqtt.0 (796659) onStateChange mqtt.0.wasserzaehler.main.timestamp: {"val":"2021-12-31T00:09:47","ack":true,"ts":1640905832048,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905832048} 2021-12-31 00:10:32.138 - debug: mqtt.0 (796659) stateChange mqtt.0.wasserzaehler.main.json: {"val":"{\"value\":288.5381,\"raw\":\"00288.5381,\"error\":\"no error\",\"rate\":0.000000,\"timestamp\":\"2021-12-31T00:09:47\"}","ack":true,"ts":1640905832134,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905832134} 2021-12-31 00:10:32.139 - debug: mqtt.0 (796659) onStateChange mqtt.0.wasserzaehler.main.json: {"val":"{\"value\":288.5381,\"raw\":\"00288.5381,\"error\":\"no error\",\"rate\":0.000000,\"timestamp\":\"2021-12-31T00:09:47\"}","ack":true,"ts":1640905832134,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1640905832134} Andreas@iobroker:~$ all ws gone! 2021-12-31 00:10:51.102 - debug: mqtt.0 (796659) Plugin sentry destroyed 2021-12-31 00:10:51.103 - info: mqtt.0 (796659) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reasonLaut Apollon77:
{"value":288.5381,"raw":"00288.5381,"error":"no error","rate":0.000000,"timestamp":"2021-12-31T00:09:47"}
Check the "raw" value ... is starts as a string, but there are mo double quotes afte rthe number and before error field.To be correct it wuld be needed to be that way:
{"value":288.5381,"raw":"00288.5381","error":"no error","rate":0.000000,"timestamp":"2021-12-31T00:09:47"}
-
@andreas_z sagte in Wasserzähler - Version 2 - all-in-device:
timestamp
Danke für den Hinweis - habe gerade einen Patch hochgeladen (v10.0.1)
-
@jomjol
Der Dank geht an Apollo77
Ich habe aber noch einen weiteren Parse-Fehler bei Neg-Read:mqtt.1 2021-12-31 14:14:53.026 warn Cannot parse "gaszaehler/main/json": {"value":,"raw":"18010.06","error":"Neg. Rate - Read: 18010.06 - Raw: 18010.06 - Pre: 18010.94 ","rate":"","timestamp":""} mqtt.1 2021-12-31 14:10:02.039 warn Cannot parse "gaszaehler/main/json": {"value":,"raw":"18010.05","error":"Neg. Rate - Read: 18010.05 - Raw: 18010.05 - Pre: 18010.94 ","rate":"","timestamp":""} mqtt.1 2021-12-31 14:00:20.035 warn Cannot parse "gaszaehler/main/json": {"value":,"raw":"18010.03","error":"Neg. Rate - Read: 18010.03 - Raw: 18010.03 - Pre: 18010.93 ","rate":"","timestamp":""} -
@steffi
Das Problem mit Spiegelung konnte ich mit Hilfe der "Einleger aus 3D Drucker" in Griff bekommen.
-
@andreas_z sagte in Wasserzähler - Version 2 - all-in-device:
@jomjol
Der Dank geht an Apollo77
Ich habe aber noch einen weiteren Parse-Fehler bei Neg-Read:mqtt.1 2021-12-31 14:14:53.026 warn Cannot parse "gaszaehler/main/json": {"value":,"raw":"18010.06","error":"Neg. Rate - Read: 18010.06 - Raw: 18010.06 - Pre: 18010.94 ","rate":"","timestamp":""} mqtt.1 2021-12-31 14:10:02.039 warn Cannot parse "gaszaehler/main/json": {"value":,"raw":"18010.05","error":"Neg. Rate - Read: 18010.05 - Raw: 18010.05 - Pre: 18010.94 ","rate":"","timestamp":""} mqtt.1 2021-12-31 14:00:20.035 warn Cannot parse "gaszaehler/main/json": {"value":,"raw":"18010.03","error":"Neg. Rate - Read: 18010.03 - Raw: 18010.03 - Pre: 18010.93 ","rate":"","timestamp":""}Danke für den Hinweis - Version 10.0.2 beseitigt auch diesen Bug.
-
@michmein
Mein Wasserzähler sieht genauso aus wie der auf deinem Bild. Ich würde deine Lösung gerne übernehmen. Hast du den Ausschnitt für den weißen Deckel "von Hand" reingeschnitten oder das stl-File des Wasseruhr-Adapters modifiziert? -
@alexho coole Idee!
-
-
@jomjol
Ich hätte da noch einen weiteren Interessanten Fehler:mqtt.1 2022-01-02 21:36:56.202 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 19:44:17.605 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 18:41:14.522 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:36:23.759 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:31:32.678 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:26:41.703 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:21:23.913 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:16:32.771 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:11:41.903 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:06:50.754 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 18:01:59.758 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:57:09.044 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:52:17.754 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:47:26.849 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:42:35.905 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:37:12.179 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:32:21.008 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:27:29.951 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:22:39.043 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:17:48.147 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:12:56.814 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:08:05.759 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 17:03:15.105 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:58:24.006 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:53:33.176 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:43:06.194 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:38:15.114 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:33:24.050 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:28:33.292 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:23:42.145 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:18:51.085 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:14:00.206 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:09:09.302 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 16:04:18.218 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 15:44:54.267 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 15:40:03.161 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 15:35:12.249 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 15:30:21.306 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 15:25:30.239 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 15:20:39.243 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "string" but received type "number" mqtt.1 2022-01-02 14:46:57.126 info send2Server mqtt.1.awtrix.notify[awtrix/notify] mqtt.1 2022-01-02 14:46:52.131 info send2Server mqtt.1.awtrix.notify[awtrix/notify] mqtt.1 2022-01-02 14:07:25.489 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 09:48:52.413 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 08:45:49.740 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 05:48:51.180 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 05:11:43.492 info send2Server mqtt.1.awtrix.customapp[awtrix/customapp] mqtt.1 2022-01-02 05:01:43.493 info send2Server mqtt.1.awtrix.customapp[awtrix/customapp] mqtt.1 2022-01-02 03:12:04.256 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 03:07:13.467 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 02:47:49.248 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string" mqtt.1 2022-01-02 02:42:58.285 info State value to set for "mqtt.1.gaszaehler.main.raw" has to be type "number" but received type "string"Mal darfs "number" sein und dann wieder "string". Kein Reboot in dem Zeitraum laut Log
-
@alexho sagte in Wasserzähler - Version 2 - all-in-device:
@steffi
Das Problem mit Spiegelung konnte ich mit Hilfe der "Einleger aus 3D Drucker" in Griff bekommen. Das Problem kommt daher, dass seit Version 10 bei einem fehlerhaften Wert kein Value übertragen wird, sondern ein leerer String: "". Wenn jemand eine bessere Idee hat, bitte gerne melden. Das scheint bei mehrerer zu Verwirrung zu führen.
-
@jomjol
Hallo und gesundes neues Jahr.
Ich hab zum Jahreswechsel meinen Gas und Wasserzähler von 6.4 auf 10.2 upgedatet.
Wasser läuft soweit prima aber Gas macht mir die 6 und 9 Probleme.
Du hast mir damals die dig0840s1q.tflite dafür gebaut. Die hab ich jetzt auch probiert aber er erkennt mir die 9 an der dritten Stelle immer wieder mal als 0 obwohl die sich ja gar nicht ändert. An der 5 und 6 Stelle erkennt er die 6 und 9 bisher ganz gut. Anbei die Ziffern 5, 6 und 9.
9_dig3_20220103-105110.zip
Hab jetzt auch schon mit der Größe gespielt aber nach mehreren richtigen kommt immer wieder die 0.
Was genau macht eigentlich der Eintrag "ModelInputSize = 20 32" kann man da ev. was tun?
Die Größe der Zahlen beim Konfigurieren ist dx 60 dy 107
Anbei auch meine Config.ini config.ini
Freu mich schon auf deine Antwort
LG Horst -
@jomjol Erstmal, geiles Projekt!
@all
Ich hätte zwei Fragen zu dem Projekt, neben der normalen Wasseruhr würde ich gerne meine Warmwasserzähler tracken.-
Ich hab schon gesehen, dass nicht unbedingt 4 Analogzeiger zum errechnen des Zählerstandes notwendig sind, Frage ob der Wasserzähler im Bild funktioniert, ich gehe da aktuell davon aus.
-
Wie man ebenfalls auf dem Bild erkennt hab ich im Heizkreisverteiler nur 7-8 cm Platz, die Linse wäre dann nur ca. 5cm von der Uhr weg. Krieg ich das scharf, reicht der Winkel vom Objektiv und ist die Bilderkennung darauf angewiesen die volle Rundung der Uhr zu erkennen?
-
-
@alexho
Ist ja lustig, selber Zähler und Zählerstand
-
@fanatikz said in Wasserzähler - Version 2 - all-in-device:
Ich hab schon gesehen, dass nicht unbedingt 4 Analogzeiger zum errechnen des Zählerstandes notwendig sind, Frage ob der Wasserzähler im Bild funktioniert, ich gehe da aktuell davon aus.
Ja, der geht. Du musst den Parameter DecimalShift = -3 setzen.
Wie man ebenfalls auf dem Bild erkennt hab ich im Heizkreisverteiler nur 7-8 cm Platz, die Linse wäre dann nur ca. 5cm von der Uhr weg. Krieg ich das scharf, reicht der Winkel vom Objektiv und ist die Bilderkennung darauf angewiesen die volle Rundung der Uhr zu erkennen?
Die volle Rundung ist nicht nötig. Wenn Du das Bild nicht scharf bekommst oder die kurze Entfernung zu starke Verzerrung erzeugt, versuch's mit einem Spiegel.
-
@rupert-s sagte in Wasserzähler - Version 2 - all-in-device:
@fanatikz said in Wasserzähler - Version 2 - all-in-device:
Ich hab schon gesehen, dass nicht unbedingt 4 Analogzeiger zum errechnen des Zählerstandes notwendig sind, Frage ob der Wasserzähler im Bild funktioniert, ich gehe da aktuell davon aus.
Ja, der geht. Du musst den Parameter DecimalShift = -3 setzen.
Bist du dir hier sicher?
Es geht ja bei DecimalShift und die digitalen Ziffern?
Bei der Beschreibung zu DecimalShif steht: Shift the digit separator within the digital digits (positiv and negativ)Ich habe bei mir in den analogen ROI's einfach nur 3 angelegt und somit auch nur 3 Kreise um die analogen Zeiger gemacht. Bisher klappt das gut.
Bei DecimalShift steht bei mir 0
-
Erstmal vielen Dank für deine tolle Arbeit. Schätze ich wirklich sehr!
Ich hätte aber nochmal eine Frage zu den Werten.
Habe die neuste Version geflasht über das OTA Update:
Und hier gleich das Bild mit den Zählerständen.
Die analogen Zeiger werden richtig ausgelesen (der letzte Zeiger würde zwar schon auf der 4 stehen, aber das ist nicht so schlimm), allerdings, wird oben schon 310 erkannt. Ist zwar grundsätzlich von der Erkennung richtig, aber dennoch Logik mäßig falsch. Es sind nämlich 309.953
Heißt ich habe noch knapp 50 Liter bis wirklich 310 richtig wäre. Ich weiß das ist jetzt ein blödes Beispiel, aber das passiert auch, wenn es noch ungefähr 200 Liter sind.Kann hier von meiner Seite aus in der Config was verbessert werden?
Oder ist hier die Programmierlogik gefragt?Danke
-
@hasont Hallo Horst,
ich nehme dein Bilder ins nächste Training auf. Aber wenn du die dig0840s1q.tflite verwendest, darf sich an der Erkennungsgenauigkeit nichts ändern. Daran hat sich nichts geändert.
Gruß,
jomjol -
@rupert-s vielen dank, ich probier es mal aus.
