Nein so wie es aussieht nicht, es scheint eine Abfrage zu geben, aber es werden keine Werte geschrieben, so wie ich das Log verstehe
Das steht im LOG
host.raspberrypi 2017-12-30 23:00:03.389 info instance system.adapter.tankerkoenig.0 terminated with code 0 (OK)
ical.0 2017-12-30 23:00:03.222 info starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.ical, node: v4.8.4
ical.1 2017-12-30 23:00:03.101 info starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.ical, node: v4.8.4
tankerkoenig.0 2017-12-30 23:00:02.808 info starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v4.8.4
host.raspberrypi 2017-12-30 23:00:00.153 info instance system.adapter.ical.0 started with pid 16526
host.raspberrypi 2017-12-30 23:00:00.115 info instance system.adapter.ical.1 started with pid 16520
host.raspberrypi 2017-12-30 23:00:00.059 info instance system.adapter.tankerkoenig.0 started with pid 16514
Da steht nix von schreiben von Daten.
Wenn ich manuell anstosse sieht das Log dann so aus:
host.raspberrypi 2017-12-30 23:39:56.611 info instance system.adapter.tankerkoenig.0 terminated with code 0 (OK)
tankerkoenig.0 2017-12-30 23:39:56.276 info objects written
tankerkoenig.0 2017-12-30 23:39:56.033 info starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v4.8.4
host.raspberrypi 2017-12-30 23:39:53.469 info instance system.adapter.tankerkoenig.0 started with pid 16705
host.raspberrypi 2017-12-30 23:39:53.425 info instance scheduled system.adapter.tankerkoenig.0 */30 * * * *
host.raspberrypi 2017-12-30 23:39:50.877 info stopInstance canceled schedule system.adapter.tankerkoenig.0
host.raspberrypi 2017-12-30 23:39:50.874 info stopInstance system.adapter.tankerkoenig.0
host.raspberrypi 2017-12-30 23:39:50.868 info object change system.adapter.tankerkoenig.0
Dann schreibt er was und meine Anzeigen sind auch korrekt