NEWS
Seltsames Verhalten MQTT-Adapter
-
Moin,
das folgende Verhalten tritt machmal auf. Ein Adapter-Neustart hilft dann eine Weile.
Das bringt leider alle möglichen Scripte durcheinander. Hat da jemand eine Idee? Es ist hier nicht nur der Sigenstor betroffen sondern alle möglichen MQTT-Clients.mqtt.0 2025-06-15 21:24:26.191 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_plant_power_factor_adjustment_target_value.state" from "string" to "number" mqtt.0 2025-06-15 21:24:23.661 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_plant_phase_b_q_s_fixed_adjustment_target_value.state" from "number" to "string" influxdb.0 2025-06-15 21:24:20.855 info changed history configuration to pin detected datatype for mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state influxdb.0 2025-06-15 21:24:20.853 info enabled logging of mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state, Alias=false influxdb.0 2025-06-15 21:24:20.850 warn Add mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state to conflicting Points (8 now) influxdb.0 2025-06-15 21:24:20.850 warn Error on writePoint("{"value":"[0, -26398]","time":"2025-06-15T19:24:20.830Z","from":"system.adapter.influxdb.0","q":0,"ack":true}): Error: {"error":"partial write: field type conflict: input field \"value\" on measurement \"mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state\" is type string, already exists as type float dropped=1"} / "{\"error\":\"partial write: field type conflict: input field \\\"value\\\" on measurement \\\"mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state\\\" is type string, already exists as type float dropped=1\"}\n"" influxdb.0 2025-06-15 21:24:20.829 info enabled logging of mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state, Alias=false mqtt.0 2025-06-15 21:24:20.821 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state" from "string" to "number" ring.0 2025-06-15 21:23:45.418 debug Device 200421625 ("Haustür"): Update Health Callback ring.0 2025-06-15 21:23:45.058 debug Device 200421625 ("Haustür"): Received Update mqtt.0 2025-06-15 21:23:23.069 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_power_factor.state" from "string" to "number" mqtt.0 2025-06-15 21:23:23.029 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_insulation_resistance.state" from "number" to "string" mqtt.0 2025-06-15 21:23:03.139 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_power_factor.state" from "number" to "string" mqtt.0 2025-06-15 21:22:28.068 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_plant_power_factor_adjustment_target_value.state" from "number" to "string"Matze
-
Moin,
das folgende Verhalten tritt machmal auf. Ein Adapter-Neustart hilft dann eine Weile.
Das bringt leider alle möglichen Scripte durcheinander. Hat da jemand eine Idee? Es ist hier nicht nur der Sigenstor betroffen sondern alle möglichen MQTT-Clients.mqtt.0 2025-06-15 21:24:26.191 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_plant_power_factor_adjustment_target_value.state" from "string" to "number" mqtt.0 2025-06-15 21:24:23.661 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_plant_phase_b_q_s_fixed_adjustment_target_value.state" from "number" to "string" influxdb.0 2025-06-15 21:24:20.855 info changed history configuration to pin detected datatype for mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state influxdb.0 2025-06-15 21:24:20.853 info enabled logging of mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state, Alias=false influxdb.0 2025-06-15 21:24:20.850 warn Add mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state to conflicting Points (8 now) influxdb.0 2025-06-15 21:24:20.850 warn Error on writePoint("{"value":"[0, -26398]","time":"2025-06-15T19:24:20.830Z","from":"system.adapter.influxdb.0","q":0,"ack":true}): Error: {"error":"partial write: field type conflict: input field \"value\" on measurement \"mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state\" is type string, already exists as type float dropped=1"} / "{\"error\":\"partial write: field type conflict: input field \\\"value\\\" on measurement \\\"mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state\\\" is type string, already exists as type float dropped=1\"}\n"" influxdb.0 2025-06-15 21:24:20.829 info enabled logging of mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state, Alias=false mqtt.0 2025-06-15 21:24:20.821 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_temperature.state" from "string" to "number" ring.0 2025-06-15 21:23:45.418 debug Device 200421625 ("Haustür"): Update Health Callback ring.0 2025-06-15 21:23:45.058 debug Device 200421625 ("Haustür"): Received Update mqtt.0 2025-06-15 21:23:23.069 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_power_factor.state" from "string" to "number" mqtt.0 2025-06-15 21:23:23.029 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_insulation_resistance.state" from "number" to "string" mqtt.0 2025-06-15 21:23:03.139 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_inverter_1_power_factor.state" from "number" to "string" mqtt.0 2025-06-15 21:22:28.068 info Server: Changed type of "mqtt.0.sigenergy2mqtt.sigen_0_plant_power_factor_adjustment_target_value.state" from "number" to "string"Matze
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden

