InfluxDB

[Rushmed]

Hallo,

habe heute meinen Influx Adapter auf 3.1.7 aktualisiert und bekomme seitdem häüfig diese Meldung:

HttpError: runtime error @4:12-4:157: filter: type conflict: bool != string

Was kann ich tun um das zu bereingen?

[Thomas Braun]

@rushmed

Gibt es da auch noch die vollständigen Zeilen davor und danach? Das sieht für mich nach etwas aus dem Zusammenhang gerissen aus. Welches Log ist das überhaupt?

[Rushmed]

@thomas-braun Hier mal ein etwas größerer log Auszug:

2022-07-20 22:49:43.928 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.5c0272fffe88b629.colortemp, sourceObj={"type":"state","common":{"name":"Color temperature","type":"number","read":true,"write":true,"role":"level.color.temperature","min":250,"max":454},"native":{},"_id":"zigbee.0.5c0272fffe88b629.colortemp","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"},"from":"system.adapter.admin.0","user":"system.user.admin","ts":1656703796573}
2022-07-20 22:49:43.929 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.5c0272fffe88b629.colortemp_move, sourceObj={"type":"state","common":{"name":"Colortemp change","type":"number","read":false,"write":true,"role":"state","min":-50,"max":50},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1656702673982,"_id":"zigbee.0.5c0272fffe88b629.colortemp_move","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.929 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.5c0272fffe88b629.transition_time, sourceObj={"type":"state","common":{"name":"Transition time","type":"number","unit":"sec","read":false,"write":true,"role":"state"},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1656702673982,"_id":"zigbee.0.5c0272fffe88b629.transition_time","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.930 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.5c0272fffe88b629.state, sourceObj={"type":"state","common":{"name":"Switch state","type":"boolean","read":true,"write":true,"role":"switch"},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1656702673982,"_id":"zigbee.0.5c0272fffe88b629.state","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.934 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.0017880108ff0d07.brightness, sourceObj={"type":"state","common":{"name":"Brightness","type":"number","unit":"","read":true,"write":true,"role":"level.dimmer","min":0,"max":100},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652201960898,"_id":"zigbee.0.0017880108ff0d07.brightness","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.935 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.0017880108ff0d07.state, sourceObj={"type":"state","common":{"name":"Switch state","type":"boolean","read":true,"write":true,"role":"switch"},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652201960897,"_id":"zigbee.0.0017880108ff0d07.state","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.936 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.ec1bbdfffeb19154.brightness, sourceObj={"type":"state","common":{"name":"Brightness","type":"number","unit":"","read":true,"write":true,"role":"level.dimmer","min":0,"max":100},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652202840199,"_id":"zigbee.0.ec1bbdfffeb19154.brightness","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.937 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.ec1bbdfffeb19154.state, sourceObj={"type":"state","common":{"name":"Switch state","type":"boolean","read":true,"write":true,"role":"switch"},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652202840199,"_id":"zigbee.0.ec1bbdfffeb19154.state","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.938 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.ec1bbdfffe94bbcb.brightness, sourceObj={"type":"state","common":{"name":"Brightness","type":"number","unit":"","read":true,"write":true,"role":"level.dimmer","min":0,"max":100},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652205181033,"_id":"zigbee.0.ec1bbdfffe94bbcb.brightness","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.939 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.ec1bbdfffe94bbcb.colortemp, sourceObj={"type":"state","common":{"name":"Color temperature","type":"number","read":true,"write":true,"role":"level.color.temperature"},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652205181033,"_id":"zigbee.0.ec1bbdfffe94bbcb.colortemp","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.939 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=zigbee.0.ec1bbdfffe94bbcb.state, sourceObj={"type":"state","common":{"name":"Switch state","type":"boolean","read":true,"write":true,"role":"switch"},"native":{},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1652205181033,"_id":"zigbee.0.ec1bbdfffe94bbcb.state","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.940 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=sonoff.0.WiFi-Plug11.POWER, sourceObj={"_id":"sonoff.0.WiFi-Plug11.POWER","common":{"type":"boolean","role":"switch","read":true,"write":true,"storeMap":true,"name":"WiFi-Plug11 POWER"},"native":{},"type":"state","from":"system.adapter.sonoff.0","user":"system.user.admin","ts":1620320875797,"acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
2022-07-20 22:49:43.940 - error: admin.0 (926) Alias subscription error. Please check your alias definitions: sourceId=shelly.0.SHSW-1#8CAAB54BD7A3#1.Relay0.Switch, sourceObj={"type":"state","common":{"type":"boolean","read":true,"write":true,"name":"Switch","role":"switch","def":false,"smartName":false,"custom":{"influxdb.0":{"enabled":true,"storageType":"Boolean","aliasId":"","changesOnly":true,"debounce":1000,"changesRelogInterval":"3600","changesMinDelta":0}}},"native":{},"_id":"shelly.0.SHSW-1#8CAAB54BD7A3#1.Relay0.Switch","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"},"from":"system.adapter.shelly.0","user":"system.user.admin","ts":1658343582586}
2022-07-20 22:49:44.049 - error: influxdb.0 (68151) HttpError: runtime error @4:12-4:157: filter: type conflict: bool != string
2022-07-20 22:49:44.093 - error: influxdb.0 (68151) HttpError: runtime error @4:12-4:157: filter: type conflict: bool != string
2022-07-20 22:49:44.101 - error: influxdb.0 (68151) HttpError: runtime error @4:12-4:157: filter: type conflict: bool != string
2022-07-20 22:50:00.068 - info: host.Smartazamba instance system.adapter.weatherunderground.0 started with pid 68441
2022-07-20 22:50:02.455 - info: weatherunderground.0 (68441) starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.weatherunderground, node: v16.16.0, js-controller: 4.0.23
2022-07-20 22:50:05.793 - error: influxdb.0 (68151) HttpError: runtime error @4:12-4:157: filter: type conflict: bool != string
2022-07-20 22:50:12.653 - info: weatherunderground.0 (68441) Terminated (NO_ERROR): Without reason
2022-07-20 22:50:13.183 - info: host.Smartazamba instance system.adapter.weatherunderground.0 terminated with code 0 (NO_ERROR)
2022-07-20 22:50:13.801 - info: smartmeter.1 (1229) Received 97 values, 1 updated
2022-07-20 22:50:19.777 - error: influxdb.0 (68151) HttpError: runtime error @4:12-4:157: filter: type conflict: bool != string
2022-07-20 22:50:36.929 - info: smartmeter.0 (1205) Received 4 values, 2 updated
2022-07-20 22:50:54.406 - info: linux-control.0 (1982) getting data from UDM_Pro (192.168.178.1:22)
2022-07-20 22:50:54.473 - info: linux-control.0 (1982) successful received data from UDM_Pro (192.168.178.1:22)
2022-07-20 22:51:24.678 - info: admin.0 (926) <== Disconnect system.user.admin from ::ffff:192.168.178.38 admin
2022-07-20 22:51:25.246 - info: smartmeter.1 (1229) Received 97 values, 1 updated
2022-07-20 22:51:26.299 - info: admin.0 (926) ==> Connected system.user.admin from ::ffff:192.168.178.38
2022-07-20 22:51:29.822 - info: admin.0 (926) ==> Connected system.user.admin from ::ffff:192.168.178.38

[Thomas Braun]

@rushmed sagte in InfluxDB:

Please check your alias definitions

Da kommen falsche Datentypen an.

[Rushmed]

@thomas-braun Ich finde in den Objektdaten leider keinen Fehler.
Bspw. hier:

{
  "common": {
    "name": "WC Spiegel switch State",
    "type": "boolean",
    "role": "switch",
    "read": true,
    "write": true,
    "smartName": {
      "de": "WC Spiegel",
      "smartType": "LIGHT"
    },
    "alias": {
      "id": "shelly.0.SHSW-1#8CAAB54BD7A3#1.Relay0.Switch"
    },
    "custom": {
      "influxdb.0": {
        "enabled": true,
        "changesOnly": true,
        "debounce": "",
        "maxLength": 10,
        "retention": "15811200",
        "changesRelogInterval": "3600",
        "changesMinDelta": "",
        "storageType": "",
        "aliasId": ""
      }
    }
  },
  "native": {},
  "acl": {
    "object": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator",
    "state": 1636
  },
  "_id": "alias.0.WC_Spiegel_switch_State",
  "type": "state",
  "from": "system.adapter.admin.0",
  "user": "system.user.admin",
  "ts": 1653158800169
}

Jetzt bekomm ich die Meldung auch noch als Popup:

[Sirfauntleroy]

@rushmed

hast Du das Problem mittlerweile lösen können?
Ich bekomme die gleiche Meldung und zwar zu dem Zeitpunkt, an dem ich die IO-Broker-App (Android) öffne und die Verbindung hergestellt wird.

[Rushmed]

@sirfauntleroy Ich habe das Problem nichtmehr. Wie das gelöst wurde weiß ich nicht mehr.

[Ben1983]

Ich habe die Fehlermeldung auch manchmal.
Auf dem gleichen DP kommt die Meldung von 100 mal beschreiben zwischen 1-5 mal).
In der Influx DB stehe die richtigen strings drin

Oder das hier:

influxdb.0
2025-09-12 13:32:42.690	warn	Error on writePoint("{"value":20512,"time":"2025-09-12T11:32:42.624Z","from":"system.adapter.lorawan.1","q":0,"ack":true}): HttpError: failure writing points to database: partial write: field type conflict: input field "value" on measurement "lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex" is type float, already exists as type string dropped=1 / "failure writing points to database: partial write: field type conflict: input field \"value\" on measurement \"lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex\" is type float, already exists as type string dropped=1""

influxdb.0
2025-09-12 13:32:42.689	warn	Point could not be written to database: iobroker

Der Datenpunkt:

(Ist in einem String)

[Marc Berg]

@ben1983 sagte in InfluxDB:

In der Influx DB stehe die richtigen strings drin

Das ist aber prinzipbedingt, Hex-Werte kann die InfluxDB nur als Strings speichern (wenn der Adapter diese nicht vorher als Dezimal umrechnet). Wenn dann ein Hex-Wert wie "020512" daher kommt, denkt die Datenbank, es sei ein float.

Wenn du das unfallfrei umsetzen willst, solltest du Hexwerte mit "0x" als Prefix speichern, also "0x020512".

[Ben1983]

@marc-berg ok.

Und was soll mir das hier sagen?
Das kommt einfach zwischendrin.
Auf den state wird nicht geschrieben, er steht nicht auf irgend einem zyklus... usw.

2025-09-12 14:06:56.848 - debug: influxdb.0 (85451) Point written to iobroker
2025-09-12 14:06:56.984 - debug: influxdb.0 (85451) Incoming message getHistory from system.adapter.admin.0
2025-09-12 14:06:56.984 - debug: influxdb.0 (85451) lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex17576788169840.9024760788821555 getHistory message: {"id":"lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex","options":{"instance":"influxdb.0","start":1757592000000,"end":1757678816918,"step":3600000,"from":false,"ack":false,"q":false,"addId":false,"aggregate":"minmax","user":"system.user.admin"}}
2025-09-12 14:06:56.986 - debug: influxdb.0 (85451) Query to execute:
from(bucket: "iobroker")
|> range(start: 2025-09-11T12:00:00.000Z, stop: 2025-09-12T12:06:56.918Z)
|> filter(fn: (r) => r["_field"] == "value")
|> filter(fn: (r) => r["_measurement"] == "lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex" and contains(value: r._value, set: [true, false]))
|> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
|> group()
2025-09-12 14:06:56.996 - debug: influxdb.0 (85451) Query to execute: from(bucket: "iobroker")
|> range(start: 2024-09-11T12:00:00.000Z, stop: 2025-09-11T11:59:59.999Z)
|> filter(fn: (r) => r["_measurement"] == "lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex")
|> last()
|> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
2025-09-12 14:06:57.006 - debug: influxdb.0 (85451) Query to execute: from(bucket: "iobroker") |> range(start: 2025-09-11T12:00:00.000Z, stop: 2025-09-12T12:06:56.918Z) |> filter(fn: (r) => r["_measurement"] == "lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex") |> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value") |> sort(columns:["_time"], desc: false)
2025-09-12 14:06:57.026 - debug: influxdb.0 (85451) Query to execute: from(bucket: "iobroker")
|> range(start: 2025-09-12T12:06:56.919Z)
|> filter(fn: (r) => r["_measurement"] == "lorawan.1.bbea74d6-1fc5-4238-af20-d2aecdbb4f8e.devices.70b3d52dd301b3cc.downlink.lastSend.hex")
|> first()
|> pivot(rowKey:["_time"], columnKey: ["_field"], valueColumn: "_value")
2025-09-12 14:06:57.039 - error: influxdb.0 (85451) HttpError: runtime error @5:12-5:197: filter: type conflict: bool != string
2025-09-12 14:06:58.018 - debug: influxdb.0 (85451) Write Point: alias.0.Allgemein.Leistung.WirkleistungGesamt values:{"value":-910.1451416015625,"time":"2025-09-12T12:06:58.009Z","from":"system.adapter.janitza-gridvis.0","q":0,"ack":true} options: null
2025-09-12 14:06:58.018 - debug: influxdb.0 (85451) Write Point: alias.0.Talstrasse1A.Zaehlerstaende.1A values:{"value":35147732,"time":"2025-09-12T12:06:58.009Z","from":"system.adapter.janitza-gridvis.0","q":0,"ack":true} options: null
2025-09-12 14:06:58.022 - debug: influxdb.0 (85451) Write Point: alias.0.Eigennutz.Zaehlerstaende.DirektverbrauchUndSpeicherentladung values:{"value":31713690,"time":"2025-09-12T12:06:58.010Z","from":"system.adapter.janitza-gridvis.0","q":0,"ack":true} options: null
2025-09-12 14:06:58.023 - debug: influxdb.0 (85451) Write Point: alias.0.PV+Speicher.Leistung.WirkleistungPv+Speicher values:{"value":-1842.1007080078125,"time":"2025-09-12T12:06:58.010Z","from":"system.adapter.janitza-gridvis.0","q":0,"ack":true} options: null

Der error ist ja auch irgendwie blöd, denn es steht ja nicht mal an welchem dp der error sit.

[Marc Berg]

@ben1983

Das sind zwei ganz verschiedene Sachverhalte.

In deinem ersten Beispiel schreibst du Werte von deinem Adapter aus in die InfluxDB. Da die InfluxDB nur drei Datentypen kennt und beim ersten Schreiben eines Feldes der Datentyp festgelegt wird, bekommst du eine Fehlermeldung, sobald du einen numerischen Wert in ein mit "String" initialisiertes Feld schreiben willst. Diesen Fehler kannst du z.B. umgehen, indem du "0x" als Prefix verwendest. Damit ist für die DB klar, es ist ein String. Der User weiß, es ist ein Hex-Wert, was bei "1111" unmöglich wäre zu erkennen.

In zweiten Beispiel geht es um Abfragen auf die DB. Ich vermute, die Meldungen kommen, wenn du das History-Fenster im Admin öffnest. Diese Fehler können umgangen werden, indem man den Datentyp auf "automatic" stellt.

siehe https://github.com/ioBroker/ioBroker.influxdb/issues/435

tipp88 created this issue in ioBroker/ioBroker.influxdb

closed HttpError: runtime error #435

[Ben1983]

@marc-berg OK,

wo kann ich Automatic einstzellen?
finde ich leider nicht.

2. Steht der Hextring in einem Adapter DP.
   Da stehe immer hex werte drin.
   aber der Adapter gibt es aus verschiedenen gründen nicht mit führenden 0x aus

[Marc Berg]

@ben1983 sagte in InfluxDB:

@marc-berg OK,

wo kann ich Automatic einstzellen?
finde ich leider nicht.

Zahnrad --> Custom Settings --> Store as

2. Steht der Hextring in einem Adapter DP.
   Da stehe immer hex werte drin.
   aber der Adapter gibt es aus verschiedenen gründen nicht mit führenden 0x aus

Der Adapter ist doch von dir, oder? Das lässt sich nicht ändern?

[Ben1983]

@marc-berg

influxdb.0
2025-09-12 15:25:45.498	warn	Error on writePoint("{"value":0,"time":"2025-09-12T13:25:45.455Z","from":"system.adapter.admin.0","q":0,"ack":false}): HttpError: failure writing points to database: partial write: field type conflict: input field "value" on measurement "0_userdata.0._Test.Teststring" is type float, already exists as type string dropped=1 / "failure writing points to database: partial write: field type conflict: input field \"value\" on measurement \"0_userdata.0._Test.Teststring\" is type float, already exists as type string dropped=1""

influxdb.0
2025-09-12 15:25:45.497	warn	Point could not be written to database: iobroker

Also meines Erachtens sollte hier bei einem Typ String (egal was drin steht, auch immer string erkannt werden, oder?

Übrigens.... stellt man auf Automatisch, dann wird ein string rein geschrieben, dann ändert es sich wieder auf text