Jump to content
View in the app

A better way to browse. Learn more.

Tinkerunity

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Maice

Members
  • Benutzer seit

  • Letzter Besuch

  1. Hallo. Fernzugriff funktioniert heute seit 07:36 Uhr wieder nicht. Im Log steht folgendes: 2026-01-18 07:36:38,067 | remote_access | Management connection disconnected 2026-01-18 07:37:18,089 | remote_access | Management request failed with internal error: Connection timed out (3) Hatte daraufhin einen Ping gemacht: 2026-01-18 10:30:01,930 | remote_access | Start pinging my.warp-charger.com(91.98.210.38) 2026-01-18 10:30:01,957 | remote_access | Ping: seqno=1, ttl=57, elapsed_time=26 ms, recv_len=64 bytes 2026-01-18 10:30:02,947 | remote_access | Ping: seqno=2, ttl=57, elapsed_time=17 ms, recv_len=64 bytes 2026-01-18 10:30:03,952 | remote_access | Ping: seqno=3, ttl=57, elapsed_time=21 ms, recv_len=64 bytes 2026-01-18 10:30:04,952 | remote_access | Ping: seqno=4, ttl=57, elapsed_time=22 ms, recv_len=64 bytes 2026-01-18 10:30:05,951 | remote_access | Ping: seqno=5, ttl=57, elapsed_time=21 ms, recv_len=64 bytes 2026-01-18 10:30:06,952 | remote_access | Ping: seqno=6, ttl=57, elapsed_time=22 ms, recv_len=64 bytes 2026-01-18 10:30:07,952 | remote_access | Ping: seqno=7, ttl=57, elapsed_time=21 ms, recv_len=64 bytes 2026-01-18 10:30:08,929 | remote_access | Ping end: packets transmitted=7, received=7, total_time_ms=150 Ping war Erfolgreich. Neustart ohne Erfolg. Gruß
  2. Hallo ffreddow, danke für die Info!!! Viele Grüße
  3. Hallo. Ich habe immer wieder mal Probleme mit dem Fernzugriff. Aktuell wieder kein Zugriff möglich. Ping funktioniert aber. Im Ereignis Log steht folgendes: 2026-01-08 00:16:20,166 | remote_access | Management request failed with internal error: Connection timed out (3) 2026-01-08 00:18:48,808 | remote_access | Start pinging my.warp-charger.com(91.98.210.38) 2026-01-08 00:18:48,832 | remote_access | Ping: seqno=1, ttl=57, elapsed_time=24 ms, recv_len=64 bytes 2026-01-08 00:18:49,837 | remote_access | Ping: seqno=2, ttl=57, elapsed_time=29 ms, recv_len=64 bytes 2026-01-08 00:18:50,833 | remote_access | Ping: seqno=3, ttl=57, elapsed_time=25 ms, recv_len=64 bytes 2026-01-08 00:18:51,832 | remote_access | Ping: seqno=4, ttl=57, elapsed_time=24 ms, recv_len=64 bytes 2026-01-08 00:18:52,831 | remote_access | Ping: seqno=5, ttl=57, elapsed_time=23 ms, recv_len=64 bytes 2026-01-08 00:18:53,831 | remote_access | Ping: seqno=6, ttl=57, elapsed_time=23 ms, recv_len=64 bytes 2026-01-08 00:18:54,807 | remote_access | Ping end: packets transmitted=6, received=6, total_time_ms=148 In der Fritzbox ist die Portfreigabe 51820 zur WARP3 freigegeben. Hat einer eine Idee? Gruß
  4. Hallo MatzeTF, der Fernzugriff schein erneut nicht zu funktionieren. Leider habe ich deine Nachricht erst gelesen, nachdem ich einen Neustart gemacht hatte. Wenn der Fernzugriff wieder funktionieren sollte, werde ich dann bei nicht Neuverbinden einen Log senden. Gruß
  5. Gibt es eine Möglichkeit, das sich der Fernzugriff wieder Automatisch einloggt? Ich musste die Wallbox neu starten. Dann war der Fernzugriff wieder verfügbar.... Gruß
  6. Ja, kann ich auch bestätigen. Fernzugriff funktioniert nicht...
  7. Hallo MatzeTF, ich habe das Ereignis Log zu ffreddow per Nachricht geschickt. Portweiterleitung habe ich noch nicht probiert. Gruß
  8. Hallo. Sorry für die späte Antowort. Heute erneut kein Fernzugriff. Vor dem Update hatte ich nicht so viele Probleme damit. Im Log steht: 2025-11-10 15:14:59,542 | remote_access | Management connection timed out 2025-11-10 15:16:29,346 | remote_access | Management connection timed out 2025-11-10 15:17:59,830 | remote_access | Management connection timed out 2025-11-10 15:19:29,189 | remote_access | Management connection timed out 2025-11-10 15:20:59,413 | remote_access | Management connection timed out 2025-11-10 15:22:29,220 | remote_access | Management connection timed out 2025-11-10 15:23:59,300 | remote_access | Management connection timed out 2025-11-10 15:25:29,478 | remote_access | Management connection timed out 2025-11-10 15:26:59,883 | remote_access | Management connection timed out 2025-11-10 15:28:29,999 | remote_access | Management connection timed out 2025-11-10 15:29:59,458 | remote_access | Management connection timed out 2025-11-10 15:31:29,729 | remote_access | Management connection timed out 2025-11-10 15:33:00,367 | remote_access | Management connection timed out 2025-11-10 15:34:29,600 | remote_access | Management connection timed out 2025-11-10 15:35:59,984 | remote_access | Management connection timed out 2025-11-10 15:37:30,357 | remote_access | Management connection timed out 2025-11-10 15:39:00,512 | remote_access | Management connection timed out 2025-11-10 15:40:30,369 | remote_access | Management connection timed out 2025-11-10 15:41:59,944 | remote_access | Management connection timed out Ich habe eine Fritzbox 6690 im Einsatz mit Vodafone Kabel. Gruß
  9. Hallo. Der Fernzugriff funktioniert leider wieder nicht. Im Log steht nun folgendes: 2025-11-06 13:02:26,426 | remote_access | Management connection timed out 2025-11-06 13:03:56,304 | remote_access | Management connection timed out 2025-11-06 13:05:25,981 | remote_access | Management connection timed out 2025-11-06 13:06:56,204 | remote_access | Management connection timed out 2025-11-06 13:08:26,235 | remote_access | Management connection timed out 2025-11-06 13:09:56,909 | remote_access | Management connection timed out 2025-11-06 13:11:27,055 | remote_access | Management connection timed out 2025-11-06 13:12:57,073 | remote_access | Management connection timed out 2025-11-06 13:14:26,314 | remote_access | Management connection timed out 2025-11-06 13:15:56,472 | remote_access | Management connection timed out 2025-11-06 13:17:26,652 | remote_access | Management connection timed out 2025-11-06 13:18:56,636 | remote_access | Management connection timed out 2025-11-06 13:19:24,573 | remote_access | Management request failed with internal error: ESP_ERR_HTTP_CONNECT (10) 2025-11-06 13:21:27,084 | remote_access | Management connection timed out 2025-11-06 13:21:54,664 | remote_access | Management request failed with internal error: ESP_ERR_HTTP_CONNECT (10) Was kann ich machen damit der Fernzugriff wieder funktioniert... Edit: Es gibt mittlerweile 2 neue Firmware Updates. Fernzugriff läuft immer noch nicht Gruß
  10. Hallo MatzeTF, Firmware habe ich installiert, Fernzugriff funktionierte gestern wieder. Ich habe gerade festgestellt, das der Fernzugriff wieder nicht funktioniert. Im Log steht: 2025-11-04 06:17:40,323 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (25963953) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 06:37:41,576 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (27165143) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 06:57:42,743 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (28366344) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:01:43,048 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (28606639) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:07:43,341 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (28966926) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:17:43,988 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (29567525) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:34:45,064 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (30588587) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:39:15,338 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (30858857) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:41:15,490 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (30979004) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:41:45,476 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (31008990) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:49:15,950 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (31459457) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 07:49:45,935 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (31489445) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 08:04:46,861 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (32390357) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 08:18:17,769 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (33201256) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 09:30:22,315 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (37525731) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 09:51:23,615 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (38787017) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 09:56:23,887 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (39087336) is the same as in the last state. Is the EVSE still reachable? 2025-11-04 10:01:24,210 | charge_manager | Received stale charger state from Tinkerforge Warp 3 (127.0.0.1). Reported EVSE uptime (39387602) is the same as in the last state. Is the EVSE still reachable? Gruß
  11. Hallo. Ich habe heute seit 12:38 Uhr wieder das Problem mit dem Fernzugriff. Im Log steht wieder dieser Fehler: 2025-11-03 22:38:09,248 | remote_access | Management connection timed out 2025-11-03 22:39:39,451 | remote_access | Management connection timed out 2025-11-03 22:41:09,544 | remote_access | Management connection timed out 2025-11-03 22:42:39,638 | remote_access | Management connection timed out 2025-11-03 22:44:10,298 | remote_access | Management connection timed out 2025-11-03 22:45:39,442 | remote_access | Management connection timed out 2025-11-03 22:47:09,723 | remote_access | Management connection timed out 2025-11-03 22:48:39,855 | remote_access | Management connection timed out 2025-11-03 22:50:09,710 | remote_access | Management connection timed out 2025-11-03 22:51:40,269 | remote_access | Management connection timed out 2025-11-03 22:53:10,348 | remote_access | Management connection timed out 2025-11-03 22:54:39,782 | remote_access | Management connection timed out 2025-11-03 22:56:09,698 | remote_access | Management connection timed out Beim letzten mal ging es nach einem Tag wieder, ich hoffe mal das es morgen auch wieder funktioniert. Edit: Ich habe gesehen das es ein Firmware Update gibt. Ich werde dieses jetzt mal installieren. Gruß
  12. Hallo CptHidi, beenden der App bringt nichts. Das Problem ist die Verbindung zum Tinkerforge Server. Intern habe ich ja Zugriff auf meine Warp3. Und im Ereignislog steht dann das Timeout zum Server... Gruß
  13. Hallo ffreddow, ich habe dir per PM mein Debug Report geschickt. Gruß
  14. Hallo. Seit gestern um habe ich keinen Fernzugriff mehr auf meine Tinkerforge Warp 3 Wallbox. Interner Zugriff funktioniert. Im Ereignis log steht : Management connection timed out. Hat jemand auch das Problem? Viele Grüße

Account

Navigation

Suche

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.