ioBroker / ioBroker.influxdb

Store history data in InfluxDB (not for Windows)
MIT License
36 stars 25 forks source link

Settings are ignored, date is writing without permission #381

Open unstressable opened 9 months ago

unstressable commented 9 months ago

Describe the bug
Setting says to archive data only when theres a differenz in value or time:

image

data has been written anyway without pause and without changing the value over the threshold:

image

InFlux V1, Version 4.0.2

Apollon77 commented 9 months ago

Please check/show the full configjuration. Most likely this is because the "optimize logging for charting/displaying of data" is activated. See readme what this means. Turn this off to get the exact logging as you expected

unstressable commented 9 months ago

Please check/show the full configjuration. Most likely this is because the "optimize logging for charting/displaying of data" is activated. See readme what this means. Turn this off to get the exact logging as you expected

I tried both. Checked and unchecked setting.

Same behavior:

image
Apollon77 commented 9 months ago

And this settings is not dofferet n on the datapoint itself?

So: If you still get such duplicate values with this setting being off on the datapoint/defaults and also there was no influxdb restart (which would log the current value once) then please enable the "extended Debug log" for that one affected datapoint and set the loglevel of the influxdb adapter to debug and let it run until you have again such a case .... Then check/provide log. It should be very clear why he logged the value

unstressable commented 9 months ago

Btw: It doesnt matter if i set the block-time in general at the instance settings, or in the datapoint (object) directly.

unstressable commented 9 months ago

And this settings is not dofferet n on the datapoint itself?

So: If you still get such duplicate values with this setting being off on the datapoint/defaults and also there was no influxdb restart (which would log the current value once) then please enable the "extended Debug log" for that one affected datapoint and set the loglevel of the influxdb adapter to debug and let it run until you have again such a case .... Then check/provide log. It should be very clear why he logged the value

i tried both. Directly in datapoint and in instance settings. Does not affect anything.

unstressable commented 9 months ago

Could it be, that the settings are only applied, when the datapoint is "closed". I mean, when I take a look inside live there seems to be another behavior: Look here: Yellow when "opened" and red when closed. Closed seems to be good!

image
Apollon77 commented 9 months ago

strange that the "source" is displayed that strange ... bit before we guess: post a debug log please

unstressable commented 9 months ago

`

influxdb.0 | 2024-02-17 14:30:52.195 | debug | Send: 51 of: 52 in: 37ms -- | -- | -- | -- influxdb.0 | 2024-02-17 14:30:52.160 | debug | Query to execute: SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time <= '2024-02-17T12:31:00.000Z' ORDER BY time DESC LIMIT 1;SELECT * from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time > '2024-02-17T12:31:00.000Z' AND time < '2024-02-17T13:31:00.000Z' ORDER BY time DESC LIMIT 500;SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time >= '2024-02-17T13:31:00.000Z' LIMIT 1 influxdb.0 | 2024-02-17 14:30:52.158 | debug | javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv17081766521580.5454910780754418 getHistory message: {"id":"javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv","options":{"instance":"influxdb.0","start":1708173060000,"end":1708176660000,"from":true,"ack":true,"q":true,"addID":false,"aggregate":"none","returnNewestEntries":true,"user":"system.user.admin"}} influxdb.0 | 2024-02-17 14:30:52.157 | debug | Incoming message getHistory from system.adapter.admin.0 influxdb.0 | 2024-02-17 14:30:52.116 | debug | Send: 500 of: 500 in: 411ms influxdb.0 | 2024-02-17 14:30:51.736 | debug | Query to execute: SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time <= '1999-12-31T23:00:00.000Z' ORDER BY time DESC LIMIT 1;SELECT * from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time > '1999-12-31T23:00:00.000Z' AND time < '2024-02-17T13:30:52.744Z' ORDER BY time ASC LIMIT 500;SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time >= '2024-02-17T13:30:52.744Z' LIMIT 1 influxdb.0 | 2024-02-17 14:30:51.709 | debug | writePoints 5 for javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv at once influxdb.0 | 2024-02-17 14:30:51.707 | debug | Store 5 buffered influxDB history points for javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv influxdb.0 | 2024-02-17 14:30:51.705 | debug | javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv17081766517050.714054862168376 getHistory message: {"id":"javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv","options":{"instance":"influxdb.0","start":946681200000,"end":1708176652744,"limit":1,"from":false,"ack":false,"q":false,"addID":false,"aggregate":"none","user":"system.user.admin"}} influxdb.0 | 2024-02-17 14:30:51.702 | debug | Incoming message getHistory from system.adapter.admin.0 influxdb.0 | 2024-02-17 14:30:51.613 | debug | Incoming message features from system.adapter.admin.0 influxdb.0 | 2024-02-17 14:30:41.423 | debug | connected set to true influxdb.0 | 2024-02-17 14:30:41.422 | debug | connected set to true influxdb.0 | 2024-02-17 14:30:41.137 | debug | Direct writePoint("solarmanpv.0.1863903.generationPower - 505 / Sat Feb 17 2024 14:30:41 GMT+0100 (Mitteleuropäische Normalzeit)") influxdb.0 | 2024-02-17 14:30:40.595 | info | enabled logging of javascript.0.Variablen.Aliasse.Gefrierschrank_UG_Power, Alias=false, 79 points now activated influxdb.0 | 2024-02-17 14:30:40.595 | info | enabled logging of javascript.0.Variablen.Aliasse.Wäschetrockner_Power, Alias=false, 78 points now activated influxdb.0 | 2024-02-17 14:30:40.595 | info | enabled logging of javascript.0.Variablen.Aliasse.Waschmaschine_Rechts_Power, Alias=false, 77 points now activated influxdb.0 | 2024-02-17 14:30:40.594 | info | enabled logging of javascript.0.Variablen.Aliasse.Waschmaschine_Links_Power, Alias=false, 76 points now activated influxdb.0 | 2024-02-17 14:30:40.594 | info | enabled logging of javascript.0.Variablen.Aliasse.Spülmaschine_EG_Power, Alias=false, 75 points now activated influxdb.0 | 2024-02-17 14:30:40.593 | info | enabled logging of javascript.0.Variablen.Aliasse.Kühlschrank_EG_Power, Alias=false, 74 points now activated influxdb.0 | 2024-02-17 14:30:40.592 | info | enabled logging of javascript.0.Variablen.Aliasse.Kühlschrank_UG_Power, Alias=false, 73 points now activated influxdb.0 | 2024-02-17 14:30:40.592 | info | enabled logging of ems-esp.0.thermostat.hc1.targetflowtemp, Alias=false, 72 points now activated influxdb.0 | 2024-02-17 14:30:40.592 | info | enabled logging of ems-esp.0.boiler.curburnpow, Alias=false, 71 points now activated influxdb.0 | 2024-02-17 14:30:40.591 | info | enabled logging of km200.0.system.sensors.temperatures.return, Alias=true, 70 points now activated influxdb.0 | 2024-02-17 14:30:40.591 | debug | Found Alias: ems-esp.0.boiler.rettemp --> km200.0.system.sensors.temperatures.return influxdb.0 | 2024-02-17 14:30:40.591 | info | enabled logging of km200.0.system.sensors.temperatures.supply_t1, Alias=true, 69 points now activated influxdb.0 | 2024-02-17 14:30:40.590 | debug | Found Alias: ems-esp.0.boiler.curflowtemp --> km200.0.system.sensors.temperatures.supply_t1 influxdb.0 | 2024-02-17 14:30:40.590 | info | enabled logging of km200.0.system.sensors.temperatures.hotWater_t2, Alias=true, 68 points now activated influxdb.0 | 2024-02-17 14:30:40.590 | debug | Found Alias: ems-esp.0.boiler.wwcurtemp --> km200.0.system.sensors.temperatures.hotWater_t2 influxdb.0 | 2024-02-17 14:30:40.589 | info | enabled logging of km200.0.dhwCircuits.dhw1.currentSetpoint, Alias=true, 67 points now activated influxdb.0 | 2024-02-17 14:30:40.589 | debug | Found Alias: ems-esp.0.boiler.wwsettemp --> km200.0.dhwCircuits.dhw1.currentSetpoint influxdb.0 | 2024-02-17 14:30:40.588 | info | enabled logging of solarmanpv.0.1863903.generationPower, Alias=false, 66 points now activated influxdb.0 | 2024-02-17 14:30:40.588 | info | enabled logging of easee.0.EHDAMBDW.status.lifetimeEnergy, Alias=false, 65 points now activated influxdb.0 | 2024-02-17 14:30:40.588 | info | enabled logging of easee.0.EHDAMBDW.status.totalPower, Alias=false, 64 points now activated influxdb.0 | 2024-02-17 14:30:40.587 | info | enabled logging of knx.0.OG.Heizung.Schlafzimmer_Temperatur_Soll, Alias=false, 63 points now activated influxdb.0 | 2024-02-17 14:30:40.587 | info | enabled logging of knx.0.OG.Heizung.Schlafzimmer_Temperatur_Ist, Alias=false, 62 points now activated influxdb.0 | 2024-02-17 14:30:40.586 | info | enabled logging of knx.0.UG.Energiemessung.Gaszähler, Alias=false, 61 points now activated influxdb.0 | 2024-02-17 14:30:40.585 | info | enabled logging of javascript.0.Variablen.Gasverbrauch.Zähler_Gesamt, Alias=false, 60 points now activated influxdb.0 | 2024-02-17 14:30:40.584 | info | enabled logging of knx.0.UG.Energiemessung.Erzeugung_Zähler, Alias=false, 59 points now activated influxdb.0 | 2024-02-17 14:30:40.584 | info | enabled logging of knx.0.UG.Energiemessung.Leistung_Zähler, Alias=false, 58 points now activated influxdb.0 | 2024-02-17 14:30:40.583 | info | enabled logging of knx.0.UG.Energiemessung.Erzeugung_L3, Alias=false, 57 points now activated influxdb.0 | 2024-02-17 14:30:40.582 | info | enabled logging of knx.0.UG.Energiemessung.Erzeugung_L2, Alias=false, 56 points now activated influxdb.0 | 2024-02-17 14:30:40.582 | info | enabled logging of knx.0.UG.Energiemessung.Erzeugung_L1, Alias=false, 55 points now activated influxdb.0 | 2024-02-17 14:30:40.581 | info | enabled logging of knx.0.UG.Energiemessung.Leistung_L3, Alias=false, 54 points now activated influxdb.0 | 2024-02-17 14:30:40.580 | info | enabled logging of knx.0.UG.Energiemessung.Leistung_L2, Alias=false, 53 points now activated influxdb.0 | 2024-02-17 14:30:40.580 | info | enabled logging of knx.0.UG.Energiemessung.Leistung_L1, Alias=false, 52 points now activated influxdb.0 | 2024-02-17 14:30:40.579 | info | enabled logging of javascript.0.Variablen.Wetter.Regen.Aktuell, Alias=false, 51 points now activated influxdb.0 | 2024-02-17 14:30:40.579 | info | enabled logging of knx.0.EG-A.Magnetkontakte.Gartenhaustür, Alias=false, 50 points now activated influxdb.0 | 2024-02-17 14:30:40.579 | info | enabled logging of javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv, Alias=false, 49 points now activated

`

unstressable commented 9 months ago
2024-02-17 14:30:51.705 - debug: influxdb.0 (5343) javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv17081766517050.714054862168376 getHistory message: {"id":"javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv","options":{"instance":"influxdb.0","start":946681200000,"end":1708176652744,"limit":1,"from":false,"ack":false,"q":false,"addID":false,"aggregate":"none","user":"system.user.admin"}} -- 2024-02-17 14:30:51.707 - debug: influxdb.0 (5343) Store 5 buffered influxDB history points for javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv 2024-02-17 14:30:51.709 - debug: influxdb.0 (5343) writePoints 5 for javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv at once 2024-02-17 14:30:51.736 - debug: influxdb.0 (5343) Query to execute: SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time <= '1999-12-31T23:00:00.000Z' ORDER BY time DESC LIMIT 1;SELECT * from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time > '1999-12-31T23:00:00.000Z' AND time < '2024-02-17T13:30:52.744Z' ORDER BY time ASC LIMIT 500;SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time >= '2024-02-17T13:30:52.744Z' LIMIT 1 2024-02-17 14:30:52.116 - debug: influxdb.0 (5343) Send: 500 of: 500 in: 411ms 2024-02-17 14:30:52.157 - debug: influxdb.0 (5343) Incoming message getHistory from system.adapter.admin.0 2024-02-17 14:30:52.158 - debug: influxdb.0 (5343) javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv17081766521580.5454910780754418 getHistory message: {"id":"javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv","options":{"instance":"influxdb.0","start":1708173060000,"end":1708176660000,"from":true,"ack":true,"q":true,"addID":false,"aggregate":"none","returnNewestEntries":true,"user":"system.user.admin"}} 2024-02-17 14:30:52.160 - debug: influxdb.0 (5343) Query to execute: SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time <= '2024-02-17T12:31:00.000Z' ORDER BY time DESC LIMIT 1;SELECT * from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time > '2024-02-17T12:31:00.000Z' AND time < '2024-02-17T13:31:00.000Z' ORDER BY time DESC LIMIT 500;SELECT value from "javascript.0.Variablen.Stromverbrauch.Leistung_Gesamt_effektiv" WHERE time >= '2024-02-17T13:31:00.000Z' LIMIT 1
unstressable commented 9 months ago

Format doesnt fit very well :(

Apollon77 commented 9 months ago

please simply take the debug log from the logfile on disk in /opt/iobroker/log/... and attach as text file. thank you

Apollon77 commented 9 months ago

And please add more logs ... I can filter myself if you tell which value when ... please always add some minutes more of log