Ausfall 26.04.2024 5:27? Keine Daten im Portal

Stromzähler
1

Moin,

ich habe heute morgen 3 eMails im Postfach gehabt:
Der Zähler 62288424 … hat seit 26.04.2024 03:10:59 keine Daten gesendet.
Der Zähler … sendet seit 26.04.2024 05:27:30 wieder Daten.
Der Zähler … hat seit 26.04.2024 05:27:30 keine Daten gesendet.

LEDs am Zähler sind „normal“ (PWR, TLS und STAT leuchten grün, LMC blinkt grün), eben habe ich kurz gesehen, das auch mal nur PWR leuchtet, dann kommen aber STAT und TLS wieder und LMC blinkt auch wieder.

Ist das ein Problem bei mir, und ich sollte mal ein Reset probieren, oder ist das ein „globales“ Problem?

Christian

2

Hallo @Familienvater.

einen generellen Ausfall gibt es zum Glück nicht. Bitte versuchen Sie einen Reset.

Viele Grüße
Pablo Santiago

3

Es scheint nach dem Reset wieder zu laufen, aber was ich so in den Logs sehe, sieht das eigentlich so aus, als ob es auch die ganze Zeit hätte funktionieren sollen:

Apr 26 03:18:33 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xc067: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 03:26:09 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xc776: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 03:33:46 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x2187: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 03:41:20 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x1175: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 03:48:55 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xac82: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 03:56:28 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xac7e: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:04:03 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xcc46: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:11:39 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x5d1f: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:19:14 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xa85d: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:26:50 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x61f2: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:34:24 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x2e84: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:41:58 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xf1c3: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:49:33 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xb49c: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 04:57:09 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x1ab8: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:04:43 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x7f90: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:12:19 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x0d31: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:19:53 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x7d6c: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:27:29 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x64cc: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:35:04 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x7338: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:42:41 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xfd22: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:50:17 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x300b: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 05:57:52 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xfe0a: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:05:25 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x875f: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:13:02 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x59c3: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:20:36 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xba57: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:28:13 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x67ce: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:35:49 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xf725: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:43:26 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xea14: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:51:00 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xf5bc: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 06:58:34 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xe5db: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:06:07 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x092e: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:13:44 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x3f4a: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:21:17 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xb896: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:28:54 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x2743: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:36:30 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x9f75: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:44:07 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x4cac: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:51:40 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x1406: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 07:59:17 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xaf11: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:06:53 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xea7b: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:14:28 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xb123: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:22:02 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xaeb3: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:29:35 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xd2fc: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:37:12 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xa60d: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:44:45 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xe014: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:52:19 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xcc93: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 08:59:55 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x0428: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:07:30 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x9e83: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:15:04 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x0e51: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:22:37 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x3a45: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:30:14 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x0dd0: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:37:51 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xe703: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:45:25 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xc836: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 09:53:00 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x5f33: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:00:34 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xcd5a: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:08:11 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x1dd0: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:15:47 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xc5f0: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:23:22 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xde47: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:30:58 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x0565: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:38:35 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0xbd67: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:46:11 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x7675: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:53:46 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x92b3: gateway35.discovergy.com STD A resolved to 80.86.163.152
Apr 26 10:57:25 vdsl-vpn-voip-router PACKET_INFO: DNS for 192.168.1.7 {smartmeter}, TID: 0x2c94: gateway35.discovergy.com STD A resolved to 80.86.163.152

Apr 26 00:30:53 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 187 Tx(kB): 260 Time(s): 1800 Conn: 0
Apr 26 01:00:53 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 187 Tx(kB): 257 Time(s): 1800 Conn: 0
Apr 26 01:30:53 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 187 Tx(kB): 256 Time(s): 1799 Conn: 0
Apr 26 02:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 186 Tx(kB): 254 Time(s): 1799 Conn: 0
Apr 26 02:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 187 Tx(kB): 257 Time(s): 1799 Conn: 0
Apr 26 03:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 187 Tx(kB): 256 Time(s): 1799 Conn: 0
Apr 26 03:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 100 Tx(kB): 91 Time(s): 710 Conn: 0
Apr 26 03:51:03 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 55 Tx(kB): 6 Time(s): 106 Conn: 0
Apr 26 04:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 18 Tx(kB): 2 Time(s): 48 Conn: 0
Apr 26 04:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 157 Conn: 0
Apr 26 05:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 157 Conn: 0
Apr 26 05:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 9 Time(s): 166 Conn: 0
Apr 26 06:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 160 Conn: 0
Apr 26 06:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 157 Conn: 0
Apr 26 07:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 163 Conn: 0
Apr 26 07:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 160 Conn: 0
Apr 26 08:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 161 Conn: 0
Apr 26 08:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 156 Conn: 0
Apr 26 09:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 162 Conn: 0
Apr 26 09:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 166 Conn: 0
Apr 26 10:00:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 74 Tx(kB): 8 Time(s): 166 Conn: 0
Apr 26 10:30:52 vdsl-vpn-voip-router ACCOUNTING_INFO: User: smartmeter Peer: EBL-STATIC Rx(kB): 56 Tx(kB): 6 Time(s): 154 Conn: 0

Hauptsache, es läuft wieder…

Christian

4

Also ich hatte heut morgen auch einen Ausfall. Seitdem hängt das Portal 2h hinterher. Bzw die angezeigte Leistung stimmt mit dem momentanen Verbrauch überein, aber die aktuelle Zeit im Portal stimmt nicht.

5

Auch bei mir seit gestern 26.04.2024 17:03:12 Totalausfall. Lief die letzten Monate einigermaßen stabil, bis gestern.
Der Zähler hat Funk und WLAN, beides ist da.
LG

6

Hi @Slope,

in der Android-App oder auf der Webseite?
Die App hat „schon immer?“ das Problem, das sie im Winter 1h, und im Sommer 2h falsch liegt, Webseite zeigt bei mir aber korrekte Werte/Zeit an

Christian

7

Nach über 24h Ausfall jetzt wieder online .
LG

1 „Gefällt mir“