NEWS
Datum 1970
-
Hallo
mir sind heute beim Beobachten der einlaufenden Ereignisse Einträge mit einem Datum von 1970 auf gefallen.
IMHO ist das der typische Datumsstempel, wenn kein Datum übermittelt wird.
Hat jemand eine Idee, wie so etwas passieren kann ?
stateChange hm-rpc.0.LEQ0593103.1.HUMIDITY 45 true hm-rpc.0 2016-06-27 22:04:54.273 2016-06-27 21:19:50.366 stateChange hm-rpc.0.LEQ0593103.1.TEMPERATURE 24.4 true hm-rpc.0 2016-06-27 22:04:54.269 2016-06-27 21:52:14.629 stateChange hm-rpc.0.NEQ0322376.0.UPDATE_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.NEQ0322376.0.UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.NEQ0322376.0.STICKY_UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.NEQ0322376.0.LOWBAT_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.NEQ0322376.0.DEVICE_IN_BOOTLOADER_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.NEQ0322376.0.CONFIG_PENDING_ALARM true true hm-rega.0 2016-06-23T16:47:45.000Z 2016-06-23T16:45:54.000Z stateChange hm-rpc.0.MEQ0678347.0.UPDATE_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0678347.0.UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0678347.0.STICKY_UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0678347.0.DUTYCYCLE_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0678347.0.DEVICE_IN_BOOTLOADER_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0678347.0.CONFIG_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.UPDATE_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.STICKY_UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.LOWBAT_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.DUTYCYCLE_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.DEVICE_IN_BOOTLOADER_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0201012.0.CONFIG_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0272626.0.UPDATE_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0272626.0.UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0272626.0.STICKY_UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0272626.0.DUTYCYCLE_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0272626.0.DEVICE_IN_BOOTLOADER_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0272626.0.CONFIG_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0203908.0.UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0203908.0.STICKY_UNREACH_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0203908.0.LOWBAT_ALARM false true hm-rega.0 2016-06-27T19:53:30.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0203908.0.CONFIG_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-7_ALARM false true hm-rega.0 2016-06-27T20:02:57.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-6_ALARM false true hm-rega.0 2016-06-27T20:02:57.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-5_ALARM false true hm-rega.0 2016-06-27T20:02:57.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-4_ALARM false true hm-rega.0 2016-06-27T20:02:57.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-3_ALARM false true hm-rega.0 2016-06-27T20:02:57.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-2_ALARM false true hm-rega.0 2016-06-27T20:02:57.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.1.ERROR-1_ALARM false true hm-rega.0 2016-06-27T20:02:56.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.0.UPDATE_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.0.UNREACH_ALARM true true hm-rega.0 2016-06-27T02:21:28.000Z 2016-06-27T02:18:46.000Z stateChange hm-rpc.0.MEQ0283738.0.STICKY_UNREACH_ALARM true true hm-rega.0 2016-06-27T02:18:46.000Z 2016-06-27T02:18:46.000Z stateChange hm-rpc.0.MEQ0283738.0.LOWBAT_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.0.DEVICE_IN_BOOTLOADER_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z 1970-01-01T00:00:00.000Z stateChange hm-rpc.0.MEQ0283738.0.CONFIG_PENDING_ALARM false true hm-rega.0 1970-01-01T00:00:00.000Z -
C-Bibliotheken und andere Programmiersprachen beginnen die Datumszählung ab dem 1.1.1970 0:00:00. Der Wert ist dann 0. Das bedeutet, dass der Zeitstempel bei Dir 0 ist. Eigentlich sollte das so nicht der Fall sein.
656
Online32.7k
Benutzer82.4k
Themen1.3m
Beiträge