UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Homer.J.]

@Dutchman Hier mal mein Auszug

Spoiler

2019-03-21 23:58:00.015 - info: host.iobroker object change system.adapter.hpcontrol.0
2019-03-21 23:58:00.017 - info: hpcontrol.0 cleaned everything up...
2019-03-21 23:58:00.016 - info: host.iobroker stopInstance system.adapter.hpcontrol.0
2019-03-21 23:58:00.016 - info: host.iobroker stopInstance system.adapter.hpcontrol.0 killing pid 9391
2019-03-21 23:58:00.026 - info: hpcontrol.0 cleaned everything up...
2019-03-21 23:58:00.066 - info: host.iobroker instance system.adapter.hpcontrol.0 terminated with code 0 (OK)
2019-03-21 23:58:02.543 - info: host.iobroker instance system.adapter.hpcontrol.0 started with pid 9531
2019-03-21 23:58:03.191 - info: hpcontrol.0 starting. Version 0.0.8 in /opt/iobroker/node_modules/iobroker.hpcontrol, node: v8.15.1
2019-03-21 23:58:03.222 - info: hpcontrol.0 ioBroker.hpcontrol started
2019-03-21 23:58:03.267 - info: hpcontrol.0 Values received
2019-03-21 23:59:00.016 - info: host.iobroker object change system.adapter.hpcontrol.0
2019-03-21 23:59:00.018 - info: hpcontrol.0 cleaned everything up...
2019-03-21 23:59:00.016 - info: host.iobroker stopInstance system.adapter.hpcontrol.0
2019-03-21 23:59:00.016 - info: host.iobroker stopInstance system.adapter.hpcontrol.0 killing pid 9531
2019-03-21 23:59:00.020 - info: javascript.0 script.js.common.Stromzähler.Strom_Verbrauchzähler_Täglich: telegram: Du hast gestern 12.430 kW/h Energie für 3.44 € , und 20.320 kW/h Energie Heizung für 3.78 € verbraucht.
2019-03-21 23:59:00.023 - info: hpcontrol.0 cleaned everything up...
2019-03-21 23:59:00.105 - info: host.iobroker instance system.adapter.hpcontrol.0 terminated with code 0 (OK)
2019-03-21 23:59:02.545 - info: host.iobroker instance system.adapter.hpcontrol.0 started with pid 9672
2019-03-21 23:59:03.194 - info: hpcontrol.0 starting. Version 0.0.8 in /opt/iobroker/node_modules/iobroker.hpcontrol, node: v8.15.1
2019-03-21 23:59:03.225 - info: hpcontrol.0 ioBroker.hpcontrol started
2019-03-21 23:59:03.272 - info: hpcontrol.0 Values received

Spoiler

2019-03-22 00:00:00.023 - info: javascript.0 script.js.common.Fenster.Skript1: Ausgelöst bei Timer
2019-03-22 00:00:00.024 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 0: Fensterkontakt Flur:0.LOW_BAT: false
2019-03-22 00:00:00.024 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 1: Fensterkontakt Balkontür:0.LOW_BAT: false
2019-03-22 00:00:00.024 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 2: Fensterkontakt Bad:0.LOW_BAT: false
2019-03-22 00:00:00.025 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 3: Thermostat Bad:0.LOW_BAT: false
2019-03-22 00:00:00.025 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 4: Bewegungsmelder HWR:0.LOW_BAT: false
2019-03-22 00:00:00.025 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 5: Fensterkontakt KZ:0.LOW_BAT: false
2019-03-22 00:00:00.025 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 6: Licht TV:0.LOW_BAT: false
2019-03-22 00:00:00.025 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 7: Fenstergriff Küche:0.LOW_BAT: false
2019-03-22 00:00:00.025 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 8: Bewegungsmelder Bad:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 9: Fensterkontakt SZ:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 10: Bewegungsmelder WZ:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 11: Fenstergriff Flur:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 12: Bewegungsmelder Flur:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 13: Bewegungsmelder SZ:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Geräte Nr. 14: Fensterkontakt WZ:0.LOW_BAT: false
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Text:
2019-03-22 00:00:00.026 - info: javascript.0 script.js.common.Fenster.Skript1: Anzahl Geräte: 15 # davon LOW_BAT erkannt: 0
2019-03-22 00:00:00.044 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Zählerstand.Verbrauch._Tag.Tag_8" does not exist
2019-03-22 00:00:00.045 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Zählerstand.Kosten._Tag.Tag_8" does not exist
2019-03-22 00:00:00.047 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Mietwohnung.Verbrauch._Tag.Tag_8" does not exist
2019-03-22 00:00:00.048 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Mietwohnung.Kosten._Tag.Tag_8" does not exist
2019-03-22 00:00:00.049 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Wärmepumpe.Verbrauch._Tag.Tag_8" does not exist
2019-03-22 00:00:00.050 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Wärmepumpe.Kosten._Tag.Tag_8" does not exist
2019-03-22 00:00:00.051 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Waschmaschine.Verbrauch._Tag.Tag_8" does not exist
2019-03-22 00:00:00.052 - warn: javascript.0 Object "javascript.0.Verbrauchszaehler.Stromzähler_Waschmaschine.Kosten._Tag.Tag_8" does not exist
2019-03-22 00:00:00.028 - info: host.iobroker instance system.adapter.dwd.0 started with pid 9801
2019-03-22 00:00:00.058 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 9807
2019-03-22 00:00:00.520 - info: hpcontrol.0 cleaned everything up...
2019-03-22 00:00:00.167 - info: host.iobroker instance system.adapter.ical.0 started with pid 9813
2019-03-22 00:00:00.773 - info: hpcontrol.0 cleaned everything up...
2019-03-22 00:00:00.374 - info: host.iobroker instance system.adapter.ical.1 started with pid 9821
2019-03-22 00:00:00.518 - info: host.iobroker object change system.adapter.hpcontrol.0
2019-03-22 00:00:00.519 - info: host.iobroker stopInstance system.adapter.hpcontrol.0
2019-03-22 00:00:00.519 - info: host.iobroker stopInstance system.adapter.hpcontrol.0 killing pid 9672
2019-03-22 00:00:00.573 - info: host.iobroker instance system.adapter.ical.2 started with pid 9827
2019-03-22 00:00:00.874 - info: host.iobroker instance system.adapter.ical.3 started with pid 9834
2019-03-22 00:00:01.035 - info: host.iobroker instance system.adapter.hpcontrol.0 terminated with code 0 (OK)
2019-03-22 00:00:01.123 - info: host.iobroker instance system.adapter.feiertage.0 started with pid 9843
2019-03-22 00:00:01.518 - info: dwd.0 starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v8.15.1
2019-03-22 00:00:02.132 - info: daswetter.0 starting. Version 2.8.0 in /opt/iobroker/node_modules/iobroker.daswetter, node: v8.15.1
2019-03-22 00:00:02.565 - info: ical.1 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.15.1
2019-03-22 00:00:03.714 - info: host.iobroker instance system.adapter.hpcontrol.0 started with pid 9879
2019-03-22 00:00:03.837 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 0 (OK)
2019-03-22 00:00:03.955 - info: ical.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.15.1
2019-03-22 00:00:04.326 - info: ical.2 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.15.1
2019-03-22 00:00:04.687 - info: ical.3 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v8.15.1
2019-03-22 00:00:04.693 - info: feiertage.0 starting. Version 1.0.11 in /opt/iobroker/node_modules/iobroker.feiertage, node: v8.15.1
2019-03-22 00:00:04.935 - info: ical.1 processing URL: calendar1 http://p18-calendars.icloud.com/published/2/qc0xx1mqQjY2I8rOiXoENZ9mOXeEWmMtB6ahaEmfdsmBYAqHlDIlsg_bysIrkM0wJziUuQC0B4qR9e5jJ1wwgy11OBWfwkXiwxEP8naEmLk
2019-03-22 00:00:05.130 - info: ical.0 processing URL: calendar1 http://p18-calendars.icloud.com/published/2/_xd1v5iM7YSKfsX8I_QgN15Fpo_3Op7-WrSIyuvL55uZ1mYD8PADFUNtQmu5ztA22gsve-sil8Um3SNXqZyaT64_UZ0mm2gweehbKJXU_mQ
2019-03-22 00:00:05.193 - info: feiertage.0 Next holiday: Karfreitag is in 28 days on 19.04.2019
2019-03-22 00:00:05.197 - info: feiertage.0 adapter feiertage objects written
2019-03-22 00:00:05.538 - info: daswetter.0 got wrong data structure! trying to repair...
2019-03-22 00:00:06.456 - info: host.iobroker instance system.adapter.feiertage.0 terminated with code 0 (OK)
2019-03-22 00:00:06.555 - info: hpcontrol.0 starting. Version 0.0.8 in /opt/iobroker/node_modules/iobroker.hpcontrol, node: v8.15.1
2019-03-22 00:00:06.589 - info: hpcontrol.0 ioBroker.hpcontrol started
2019-03-22 00:00:06.639 - info: hpcontrol.0 Values received
2019-03-22 00:00:06.741 - info: ical.2 processing URL: Ferien https://www.schulferien.org/media/ical/deutschland/ferien_sachsen-anhalt_2019.ics?k=fdMJJtP-ePIynaQ0xI4EhH7uGu027M9QQLxUeUpGciJnCmnm81k6G5j-JuTfdVU6WHl-CMnEBlmzR8WvsVAo79Gk8DbvGZx2VI4uh-K6qiI
2019-03-22 00:00:06.780 - info: ical.3 processing URL: Feiertage https://www.schulferien.org/media/ical/deutschland/feiertage_sachsen-anhalt_2019.ics?k=OVrJlUsyaaQh2bqxoQjXo0HoCGJRnWM6pdu1IMTEGbWorSMEqEf9vA-gEwRO4EXWI88cFLSJdgNRuhErZcfd73SwfJpVf9XplvURvT9P0A8
2019-03-22 00:00:10.706 - info: host.iobroker instance system.adapter.ical.1 terminated with code 0 (OK)
2019-03-22 00:00:10.968 - info: host.iobroker instance system.adapter.ical.0 terminated with code 0 (OK)
2019-03-22 00:00:12.427 - info: host.iobroker instance system.adapter.ical.2 terminated with code 0 (OK)
2019-03-22 00:00:12.432 - info: host.iobroker instance system.adapter.ical.3 terminated with code 0 (OK)
2019-03-22 00:00:18.211 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (Desired termination)
2019-03-22 00:01:00.015 - info: host.iobroker object change system.adapter.hpcontrol.0
2019-03-22 00:01:00.017 - info: hpcontrol.0 cleaned everything up...
2019-03-22 00:01:00.016 - info: host.iobroker stopInstance system.adapter.hpcontrol.0
2019-03-22 00:01:00.016 - info: host.iobroker stopInstance system.adapter.hpcontrol.0 killing pid 9879
2019-03-22 00:01:00.023 - info: hpcontrol.0 cleaned everything up...
2019-03-22 00:01:00.088 - info: host.iobroker instance system.adapter.hpcontrol.0 terminated with code 0 (OK)
2019-03-22 00:01:02.548 - info: host.iobroker instance system.adapter.hpcontrol.0 started with pid 10075
2019-03-22 00:01:03.185 - info: hpcontrol.0 starting. Version 0.0.8 in /opt/iobroker/node_modules/iobroker.hpcontrol, node: v8.15.1
2019-03-22 00:01:03.215 - info: hpcontrol.0 ioBroker.hpcontrol started
2019-03-22 00:01:03.260 - info: hpcontrol.0 Values received
2019-03-22 00:01:23.285 - info: tankerkoenig.0 Reading data from tankerkoenig ...
2019-03-22 00:02:00.022 - info: host.iobroker object change system.adapter.hpcontrol.0
2019-03-22 00:02:00.024 - info: hpcontrol.0 cleaned everything up...
2019-03-22 00:02:00.022 - info: host.iobroker stopInstance system.adapter.hpcontrol.0
2019-03-22 00:02:00.022 - info: host.iobroker stopInstance system.adapter.hpcontrol.0 killing pid 10075
2019-03-22 00:02:00.033 - info: hpcontrol.0 cleaned everything up...
2019-03-22 00:02:00.061 - info: host.iobroker instance system.adapter.hpcontrol.0 terminated with code 0 (OK)
2019-03-22 00:02:02.552 - info: host.iobroker instance system.adapter.hpcontrol.0 started with pid 10204
2019-03-22 00:02:03.213 - info: hpcontrol.0 starting. Version 0.0.8 in /opt/iobroker/node_modules/iobroker.hpcontrol, node: v8.15.1
2019-03-22 00:02:03.243 - info: hpcontrol.0 ioBroker.hpcontrol started
2019-03-22 00:02:03.288 - info: hpcontrol.0 Values received

[Dutchman]

Danke ! Ich kan den Fehler reproduzieren und werde ihn im laufe des morgens fixen

[hg6806]

OK, brauchst du mein Log dann nicht mehr?

[Dutchman]

@hg6806 sagte in [Neuer Adapter Beta 0.2.227] SourceAnalytix (Verbrauch Protokollierung von Strom/Gas/Flüssigkeiten):

OK, brauchst du mein Log dann nicht mehr?

doch bitte jede extra information hilft.
Meine Vermutung um moment is das der umbau nach compact mode die Funktion zerschossen hat um die tageswerte zu resetten.

[sigi234]

@Dutchman

So ein neuer Debug Log, habe jetzt nur mehr Die Homematic Funksteckdose..........

sourceanalytix.0	2019-03-22 09:54:21.086	debug	Meter Calculation executed
sourceanalytix.0	2019-03-22 09:54:21.086	debug	calculated cost year : 0.67
sourceanalytix.0	2019-03-22 09:54:21.086	debug	calculated cost quarter : 0.67
sourceanalytix.0	2019-03-22 09:54:21.086	debug	calculated cost month : 0.67
sourceanalytix.0	2019-03-22 09:54:21.086	debug	calculated cost week : 0.22
sourceanalytix.0	2019-03-22 09:54:21.086	debug	calculated cost day : 0.07
sourceanalytix.0	2019-03-22 09:54:21.086	debug	example state string : sourceanalytix.0.hm-rpc__1__NEQ1662322__2__ENERGY_COUNTER.cost.01_current_day
sourceanalytix.0	2019-03-22 09:54:21.086	debug	delivery type .consumption.
sourceanalytix.0	2019-03-22 09:54:21.086	debug	cost type .cost.
sourceanalytix.0	2019-03-22 09:54:21.086	debug	objroot sourceanalytix.0.hm-rpc__1__NEQ1662322__2__ENERGY_COUNTER
sourceanalytix.0	2019-03-22 09:54:21.086	debug	year consumed 9.9656
sourceanalytix.0	2019-03-22 09:54:21.085	debug	quarter consumed 9.9656
sourceanalytix.0	2019-03-22 09:54:21.085	debug	month consumed 9.9656
sourceanalytix.0	2019-03-22 09:54:21.085	debug	week consumed 3.3359000000000005
sourceanalytix.0	2019-03-22 09:54:21.085	debug	day consumed 1.038499999999999
sourceanalytix.0	2019-03-22 09:54:21.085	debug	calculated reading day : 9.966
sourceanalytix.0	2019-03-22 09:54:21.085	debug	calculated reading quarter : 9.966
sourceanalytix.0	2019-03-22 09:54:21.085	debug	calculated reading month : 9.966
sourceanalytix.0	2019-03-22 09:54:21.085	debug	calculated reading week : 3.336
sourceanalytix.0	2019-03-22 09:54:21.085	debug	calculated reading day : 1.038
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Start consumption calculations
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Delivery state set to : .consumption.
sourceanalytix.0	2019-03-22 09:54:21.085	debug	year start : 0
sourceanalytix.0	2019-03-22 09:54:21.085	debug	quarter start 0
sourceanalytix.0	2019-03-22 09:54:21.085	debug	month start 0
sourceanalytix.0	2019-03-22 09:54:21.085	debug	week start : 6.6297
sourceanalytix.0	2019-03-22 09:54:21.085	debug	day start : 8.927100000000001
sourceanalytix.0	2019-03-22 09:54:21.085	debug	reading_start : 0
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Handle meter history : true
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Handle consumption calculations : true
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Cost unit : 0.067
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Cost basic : 4
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Calculation Factor : 0.067
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Handle cost calculations : true
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Meter calculated reading : 9.9656
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Meter current reading : 9965.6
sourceanalytix.0	2019-03-22 09:54:21.085	debug	State value output of unit factore calculation : 9.9656
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Test unit : wh
sourceanalytix.0	2019-03-22 09:54:21.085	debug	State value input for unit factore calculation : 9965.6
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Object array input for unit factore calculation : {"type":"state","common":{"def":0,"type":"number","read":true,"write":false,"min":0,"max":838860.7,"unit":"Wh","name":"Steckdose Geschirrspüler Messwe
sourceanalytix.0	2019-03-22 09:54:21.085	debug	Case result : Electricity consumption
sourceanalytix.0	2019-03-22 09:54:21.085	debug	State object custom content: {"enabled":true,"alias":"","state_type":"kWh_consumption","state_unit":"automatically","costs":true,"consumption":true,"meter_values":true,"start_day":8.927100000000001,"s
sourceanalytix.0	2019-03-22 09:54:21.085	debug	State object content: {"type":"state","common":{"def":0,"type":"number","read":true,"write":false,"min":0,"max":838860.7,"unit":"Wh","name":"Steckdose Geschirrspüler Messwert.ENERGY_COUNTER","custom":
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Object array of all activated states : ["hm-rpc.1.NEQ1662322.2.ENERGY_COUNTER"]
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Object array : ["hm-rpc.1.NEQ1662322.2.ENERGY_COUNTER"]
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Calc obj root sourceanalytix.0.hm-rpc__1__NEQ1662322__2__ENERGY_COUNTER
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Write calculations for : hm-rpc.1.NEQ1662322.2.ENERGY_COUNTER
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Instance name : sourceanalytix.0
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Initialization finished for : hm-rpc__1__NEQ1662322__2__ENERGY_COUNTER
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Create channel name : Meter_Readings
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Create channel id : Meter_Readings
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Parent device : hm-rpc__1__NEQ1662322__2__ENERGY_COUNTER
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Create channel name : cost
sourceanalytix.0	2019-03-22 09:54:20.972	debug	Create channel id : cost

[Dutchman]

@sigi234 sagte in [Neuer Adapter Beta 0.2.227] SourceAnalytix (Verbrauch Protokollierung von Strom/Gas/Flüssigkeiten):

So ein neuer Debug Log, habe jetzt nur mehr Die Homematic Funksteckdose..........

das sieht alles sehr gut aus danke !

@all

Ich habe soeben version 0.2.273 veröffentlicht, hierin ist der bug behoben fuer den täglichen reset.
Wer gestern 0.2.272 installiert hat sollte heute einmalig den Tages startwert Manuel eintragen damit die Berechnungen stimmen

Changelog:

0.2.273

• (Dutchman) fix issue in daily reset of start values
• (Dutchman) Fix badges in readme
• (Dutchman) exclude calculations of w from current routines (will be implemented in next version(s)

[Palm_Maniac]

@Dutchman Hi. Über Admin wird mir jetzt die 0.2.272 angeboten. Ist das trotzdem schon die 0.2.273 oder soll ich mit dem Update noch warten?

[Dutchman]

@Palm_Maniac sagte in [Neuer Adapter Beta 0.2.273] SourceAnalytix (Verbrauch Protokollierung von Strom/Gas/Flüssigkeiten):

@Dutchman Hi. Über Admin wird mir jetzt die 0.2.272 angeboten. Ist das trotzdem schon die 0.2.273 oder soll ich mit dem Update noch warten?

du kannst entweder direkt über git installieren, oder bis heute mittag (so ungefähr 14.30) warten.
Unsere repositorys werden 2-mal am tag neu gebaut, 14.00 und 02.00 danach werden neue Versionen im admin angeboten.

oder, das würde auch gehen, auf der console (im iobroker Verzeichnis!) das hier eingeben :

npm i iobroker.sourceanalytix@latest

[Palm_Maniac]

@Dutchman Ok, dann warte ich. :) Vielen Dank.

[crunchip]

habe es gerade auch mal versucht mit 0.2.273
jedoch werden keine Gaswerte mehr angezeigt. Strom funktionierte noch.
Folgende Fehlermeldungen

Spoiler

Caught 2019-03-22 19:07:38.608 error by controller[9]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.608 error by controller[8]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.608 error by controller[8]: at <anonymous>
Caught 2019-03-22 19:07:38.608 error by controller[8]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.608 error by controller[8]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.608 error by controller[7]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.608 error by controller[7]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.607 error by controller[7]: at <anonymous>
Caught 2019-03-22 19:07:38.607 error by controller[7]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.605 error by controller[7]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.605 error by controller[6]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.605 error by controller[5]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.605 error by controller[5]: at <anonymous>
Caught 2019-03-22 19:07:38.605 error by controller[5]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.605 error by controller[5]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.604 error by controller[4]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.604 error by controller[4]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.604 error by controller[4]: at <anonymous>
Caught 2019-03-22 19:07:38.604 error by controller[4]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.604 error by controller[4]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.604 error by controller[3]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.604 error by controller[3]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.604 error by controller[3]: at <anonymous>
Caught 2019-03-22 19:07:38.604 error by controller[3]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.604 error by controller[3]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.604 error by controller[3]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.604 error by controller[3]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.603 error by controller[3]: at <anonymous>
Caught 2019-03-22 19:07:38.603 error by controller[3]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.603 error by controller[3]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.603 error by controller[3]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.603 error by controller[3]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.603 error by controller[3]: at <anonymous>
Caught 2019-03-22 19:07:38.603 error by controller[3]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.603 error by controller[3]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.603 error by controller[2]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.603 error by controller[2]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.602 error by controller[2]: at <anonymous>
Caught 2019-03-22 19:07:38.602 error by controller[2]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.602 error by controller[2]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
Caught 2019-03-22 19:07:38.602 error by controller[1]: (node:24531) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecti
Caught 2019-03-22 19:07:38.602 error by controller[1]: at process._tickCallback (internal/process/next_tick.js:189:7)
Caught 2019-03-22 19:07:38.602 error by controller[1]: at <anonymous>
Caught 2019-03-22 19:07:38.602 error by controller[1]: at Sourceanalytix.calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:647:42)
Caught 2019-03-22 19:07:38.602 error by controller[1]: (node:24531) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
sourceanalytix.0 2019-03-22 19:07:38.574 info Adapter SourceAnalytix stopped !

bin dann wieder zurück auf 0.2.26 fehlerfrei

[Dutchman]

@crunchip sagte in [Neuer Adapter Beta 0.2.273] SourceAnalytix (Verbrauch Protokollierung von Strom/Gas/Flüssigkeiten):

jedoch werden keine Gaswerte mehr angezeigt. Strom funktionierte noch.

hmm da geht was schief beim internen Aufruf der state Daten, könntest du mir einen gefallen tun bitte ?

• Den adapter bitte mal auf debug stellen und dan den adapter starten.
• Bitte mal von dem betreffende state die raw Daten (state öffnen mit Bleistift, tabblad raw)

Ich brauche die debug Informationen befohr der Fehler auftritt also ein komplettes log währe sehr hilfreich !
(eventueel auch per PN)

Danke schonmal !

Dutch

[crunchip]

@Dutchman ui ui ui
also debug ausgabe vom aktuellen Stand?
und dann nochmal 0.2.273 installieren?
Welche raw Daten? Ein Beispiel Raw?

{
  "from": "system.adapter.sourceanalytix.0",
  "ts": 1550937848225,
  "common": {
    "name": "current Day ",
    "type": "number",
    "role": "value.week",
    "unit": "m3",
    "def": 0,
    "read": true
  },
  "native": {},
  "acl": {
    "object": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator",
    "state": 1636
  },
  "_id": "sourceanalytix.0.wiffi-wz__0__root__192_168_178_33__w_counter_2.consumption.01_current_day",
  "type": "state"
}

in den Ordnern consumption und cost wurde als wert nur "n.a." überall angezeigt

[Dutchman]

@crunchip sagte in [Neuer Adapter Beta 0.2.273] SourceAnalytix (Verbrauch Protokollierung von Strom/Gas/Flüssigkeiten):

Welche raw Daten? Ein Beispiel Raw?

ja genau danke !

hmm deine states fehlen ein par Attribute fur SourceAnalytix, deaktivier Sourcenalytix mal bei allen und aktiviere es erneut dan sollte im raw mehr Daten stehen

Edit : ups warte das ist ja ein state von sourceanalytix, ich meinte den state welche du analysieren möchtest ;)

[crunchip]

@Dutchman probier ich gleich mal
hier der debug..da kommt nicht viel

Spoiler

2019-03-22 20:26:01.422 - info: host.IoBroker object change system.adapter.sourceanalytix.0
2019-03-22 20:26:01.424 - warn: sourceanalytix.0 Adapter SourceAnalytix stopped !
2019-03-22 20:26:01.422 - info: host.IoBroker "system.adapter.sourceanalytix.0" disabled
2019-03-22 20:26:01.422 - info: host.IoBroker stopInstance system.adapter.sourceanalytix.0
2019-03-22 20:26:01.422 - info: host.IoBroker stopInstance system.adapter.sourceanalytix.0 killing pid 24821
2019-03-22 20:26:01.445 - warn: sourceanalytix.0 Adapter SourceAnalytix stopped !
2019-03-22 20:26:01.483 - info: host.IoBroker instance system.adapter.sourceanalytix.0 terminated with code 0 (OK)
2019-03-22 20:26:15.835 - info: host.IoBroker object change system.adapter.sourceanalytix.0
2019-03-22 20:26:33.396 - info: host.IoBroker object change system.adapter.sourceanalytix.0
2019-03-22 20:26:33.397 - info: host.IoBroker "system.adapter.sourceanalytix.0" enabled
2019-03-22 20:26:33.416 - info: host.IoBroker instance system.adapter.sourceanalytix.0 started with pid 26093
2019-03-22 20:26:33.962 - debug: sourceanalytix.0 objectDB connected
2019-03-22 20:26:34.004 - debug: sourceanalytix.0 statesDB connected
2019-03-22 20:26:34.112 - info: sourceanalytix.0 starting. Version 0.2.26 in /opt/iobroker/node_modules/iobroker.sourceanalytix, node: v8.15.1
2019-03-22 20:26:34.244 - info: sourceanalytix.0 Activate SourceAnalytix for : wiffi-wz.0.root.192_168_178_xx.w_counter_1
2019-03-22 20:26:34.411 - info: sourceanalytix.0 Activate SourceAnalytix for : wiffi-wz.0.root.192_168_178_xx.w_counter_2

[Dutchman]

@crunchip sagte in [Neuer Adapter Beta 0.2.273] SourceAnalytix (Verbrauch Protokollierung von Strom/Gas/Flüssigkeiten):

hier der debug..da kommt nicht viel

hmm das ist aber sehr wenig

[crunchip]

nach dem beenden vom debug
kommt wieder folgendes

Spoiler

2019-03-22 20:32:47.937 - warn: sourceanalytix.0 Adapter SourceAnalytix stopped !
2019-03-22 20:32:47.962 - error: Caught by controller[1]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.962 - error: Caught by controller[1]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.962 - error: Caught by controller[1]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.962 - error: Caught by controller[1]: at
2019-03-22 20:32:47.963 - error: Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.963 - error: Caught by controller[1]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 95)
2019-03-22 20:32:47.963 - error: Caught by controller[2]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.963 - error: Caught by controller[2]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.963 - error: Caught by controller[2]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.963 - error: Caught by controller[2]: at
2019-03-22 20:32:47.963 - error: Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.963 - error: Caught by controller[2]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 96)
2019-03-22 20:32:47.963 - error: Caught by controller[2]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.963 - error: Caught by controller[2]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.963 - error: Caught by controller[2]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.964 - error: Caught by controller[2]: at
2019-03-22 20:32:47.964 - error: Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.964 - error: Caught by controller[2]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 97)
2019-03-22 20:32:47.964 - error: Caught by controller[3]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.964 - error: Caught by controller[3]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.964 - error: Caught by controller[3]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.964 - error: Caught by controller[3]: at
2019-03-22 20:32:47.964 - error: Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.964 - error: Caught by controller[3]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 98)
2019-03-22 20:32:47.964 - error: Caught by controller[4]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.964 - error: Caught by controller[4]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.964 - error: Caught by controller[4]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.965 - error: Caught by controller[4]: at
2019-03-22 20:32:47.965 - error: Caught by controller[4]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.965 - error: Caught by controller[4]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 99)
2019-03-22 20:32:47.965 - error: Caught by controller[5]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.967 - error: Caught by controller[5]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.967 - error: Caught by controller[5]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.968 - error: Caught by controller[5]: at
2019-03-22 20:32:47.968 - error: Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.968 - error: Caught by controller[5]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 100)
2019-03-22 20:32:47.968 - error: Caught by controller[5]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.968 - error: Caught by controller[5]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.968 - error: Caught by controller[5]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.968 - error: Caught by controller[5]: at
2019-03-22 20:32:47.968 - error: Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.968 - error: Caught by controller[5]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 101)
2019-03-22 20:32:47.968 - error: Caught by controller[6]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.968 - error: Caught by controller[6]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.968 - error: Caught by controller[6]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.969 - error: Caught by controller[6]: at
2019-03-22 20:32:47.969 - error: Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.969 - error: Caught by controller[6]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 102)
2019-03-22 20:32:47.969 - error: Caught by controller[7]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.969 - error: Caught by controller[7]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.969 - error: Caught by controller[7]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.969 - error: Caught by controller[7]: at
2019-03-22 20:32:47.969 - error: Caught by controller[7]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.969 - error: Caught by controller[7]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 103)
2019-03-22 20:32:47.969 - error: Caught by controller[8]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.969 - error: Caught by controller[8]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.970 - error: Caught by controller[8]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.970 - error: Caught by controller[8]: at
2019-03-22 20:32:47.970 - error: Caught by controller[8]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.970 - error: Caught by controller[8]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 104)
2019-03-22 20:32:47.970 - error: Caught by controller[9]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.970 - error: Caught by controller[9]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.970 - error: Caught by controller[9]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.970 - error: Caught by controller[9]: at
2019-03-22 20:32:47.970 - error: Caught by controller[9]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.970 - error: Caught by controller[9]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 105)
2019-03-22 20:32:47.970 - error: Caught by controller[10]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.971 - error: Caught by controller[10]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.971 - error: Caught by controller[10]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.971 - error: Caught by controller[10]: at
2019-03-22 20:32:47.971 - error: Caught by controller[10]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.971 - error: Caught by controller[10]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 106)
2019-03-22 20:32:47.971 - error: Caught by controller[11]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.971 - error: Caught by controller[11]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.971 - error: Caught by controller[11]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.971 - error: Caught by controller[11]: at
2019-03-22 20:32:47.971 - error: Caught by controller[11]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.971 - error: Caught by controller[11]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 107)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 108)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at
2019-03-22 20:32:47.972 - error: Caught by controller[12]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.972 - error: Caught by controller[12]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 109)
2019-03-22 20:32:47.973 - error: Caught by controller[13]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.973 - error: Caught by controller[13]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.973 - error: Caught by controller[13]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.973 - error: Caught by controller[13]: at
2019-03-22 20:32:47.973 - error: Caught by controller[13]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.973 - error: Caught by controller[13]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 110)
2019-03-22 20:32:47.973 - error: Caught by controller[14]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.973 - error: Caught by controller[14]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.973 - error: Caught by controller[14]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.973 - error: Caught by controller[14]: at
2019-03-22 20:32:47.973 - error: Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.974 - error: Caught by controller[14]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 111)
2019-03-22 20:32:47.974 - error: Caught by controller[15]: (node:26093) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'sourceanalytix.0' of undefined
2019-03-22 20:32:47.974 - error: Caught by controller[15]: at unit_calc_fact (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:753:36)
2019-03-22 20:32:47.974 - error: Caught by controller[15]: at calculation_handler (/opt/iobroker/node_modules/iobroker.sourceanalytix/main.js:314:23)
2019-03-22 20:32:47.974 - error: Caught by controller[15]: at
2019-03-22 20:32:47.974 - error: Caught by controller[15]: at process._tickCallback (internal/process/next_tick.js:189:7)
2019-03-22 20:32:47.974 - error: Caught by controller[15]: (node:26093) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 112)

[Dutchman]

gib mir mal bitte die raw Daten von dem entsprechenden state

[crunchip]

@Dutchman hatte ich dir per chat gesendet, oder meinst du einen anderen?

[crunchip]

und was ich noch fragen wollte,

wie ich die Werte für Zählerstände bekomme, wird bei mir nichts aktualisiert

[Palm_Maniac]

Hi. Also bis jetzt läuft die neue Version bei mir ohne Probleme und Fehlermeldungen. Alles was vorher lief, läuft auch jetzt. Wegen mir kann es weiter gehen mit dem Einbau neuer und noch fehlender Funktionen. :)