📚 Improved log file management in Backend 🖥️🔍
This commit is contained in:
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -4969,3 +4969,188 @@ WHERE users.id = ?
|
||||
2025-06-11 10:45:17 - [app] app - [INFO] INFO - [STARTUP] Starte Job Scheduler...
|
||||
2025-06-11 10:45:17 - [app] app - [INFO] INFO - [STARTUP] ✅ Job Scheduler gestartet
|
||||
2025-06-11 10:45:17 - [app] app - [INFO] INFO - [STARTUP] 🌐 Server startet auf http://0.0.0.0:5000
|
||||
2025-06-11 10:51:33 - [app] app - [WARNING] WARNING - DatabaseCleanupManager nicht verfügbar - Fallback auf Legacy-Cleanup
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\instance\printer_manager.db
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [CONFIG] Erkannte Umgebung: development
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [CONFIG] Production-Modus: False
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [CONFIG] Verwende Development-Konfiguration
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [DEVELOPMENT] Aktiviere Development-Konfiguration
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ MYP Development Environment Konfiguration aktiviert
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Environment: Development/Testing
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Debug Mode: True
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ SQL Echo: True
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [STARTUP] 🚀 Starte MYP DEVELOPMENT-Umgebung
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [STARTUP] 🏢 Mercedes-Benz TBA Marienfelde
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [STARTUP] 🔒 Air-Gapped: True
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [STARTUP] Initialisiere Datenbank...
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [STARTUP] ✅ Datenbank initialisiert
|
||||
2025-06-11 10:51:33 - [app] app - [INFO] INFO - [STARTUP] Prüfe Initial-Admin...
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - [STARTUP] ✅ Admin-Benutzer geprüft
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - [STARTUP] Starte Queue Manager...
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - [STARTUP] ✅ Queue Manager gestartet
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - [STARTUP] Starte Job Scheduler...
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - [STARTUP] ✅ Job Scheduler gestartet
|
||||
2025-06-11 10:51:34 - [app] app - [INFO] INFO - [STARTUP] 🌐 Server startet auf http://0.0.0.0:5000
|
||||
2025-06-11 10:51:35 - [app] app - [WARNING] WARNING - DatabaseCleanupManager nicht verfügbar - Fallback auf Legacy-Cleanup
|
||||
2025-06-11 10:51:35 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\instance\printer_manager.db
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [CONFIG] Erkannte Umgebung: development
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [CONFIG] Production-Modus: False
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [CONFIG] Verwende Development-Konfiguration
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [DEVELOPMENT] Aktiviere Development-Konfiguration
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ MYP Development Environment Konfiguration aktiviert
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Environment: Development/Testing
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Debug Mode: True
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ SQL Echo: True
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] 🚀 Starte MYP DEVELOPMENT-Umgebung
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] 🏢 Mercedes-Benz TBA Marienfelde
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] 🔒 Air-Gapped: True
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] Initialisiere Datenbank...
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] ✅ Datenbank initialisiert
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] Prüfe Initial-Admin...
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] ✅ Admin-Benutzer geprüft
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] Starte Queue Manager...
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] ✅ Queue Manager gestartet
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] Starte Job Scheduler...
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] ✅ Job Scheduler gestartet
|
||||
2025-06-11 10:51:36 - [app] app - [INFO] INFO - [STARTUP] 🌐 Server startet auf http://0.0.0.0:5000
|
||||
2025-06-11 10:51:37 - [app] app - [INFO] INFO - Locating template 'dashboard.html':
|
||||
1: trying loader of application '__main__'
|
||||
class: jinja2.loaders.FileSystemLoader
|
||||
encoding: 'utf-8'
|
||||
followlinks: False
|
||||
searchpath:
|
||||
- C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates
|
||||
-> found ('C:\\Users\\TTOMCZA.EMEA\\Dev\\Projektarbeit-MYP\\backend\\templates\\dashboard.html')
|
||||
2025-06-11 10:51:37 - [app] app - [INFO] INFO - Locating template 'base.html':
|
||||
1: trying loader of application '__main__'
|
||||
class: jinja2.loaders.FileSystemLoader
|
||||
encoding: 'utf-8'
|
||||
followlinks: False
|
||||
searchpath:
|
||||
- C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates
|
||||
-> found ('C:\\Users\\TTOMCZA.EMEA\\Dev\\Projektarbeit-MYP\\backend\\templates\\base.html')
|
||||
2025-06-11 10:51:37 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:37 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
|
||||
2025-06-11 10:51:37 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:38 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers/monitor/live-status
|
||||
2025-06-11 10:51:38 - [app] app - [DEBUG] DEBUG - Request: GET /api/session/status
|
||||
2025-06-11 10:51:38 - [app] app - [DEBUG] DEBUG - Request: GET /api/user/settings
|
||||
2025-06-11 10:51:38 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:38 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:38 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/static/icons/icon-192.png
|
||||
2025-06-11 10:51:38 - [app] app - [INFO] INFO - Locating template 'errors/404.html':
|
||||
1: trying loader of application '__main__'
|
||||
class: jinja2.loaders.FileSystemLoader
|
||||
encoding: 'utf-8'
|
||||
followlinks: False
|
||||
searchpath:
|
||||
- C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates
|
||||
-> found ('C:\\Users\\TTOMCZA.EMEA\\Dev\\Projektarbeit-MYP\\backend\\templates\\errors\\404.html')
|
||||
2025-06-11 10:51:39 - [app] app - [DEBUG] DEBUG - Request: POST /api/session/heartbeat
|
||||
2025-06-11 10:51:39 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:41 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 6, Status: off, Quelle: system
|
||||
2025-06-11 10:51:41 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 3, Status: off, Quelle: system
|
||||
2025-06-11 10:51:41 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 1, Status: off, Quelle: system
|
||||
2025-06-11 10:51:42 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 5, Status: off, Quelle: system
|
||||
2025-06-11 10:51:42 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 4, Status: off, Quelle: system
|
||||
2025-06-11 10:51:42 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 2, Status: off, Quelle: system
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers/monitor/live-status
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: POST /api/session/heartbeat
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/error-recovery/status
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
|
||||
2025-06-11 10:51:42 - [app] app - [INFO] INFO - ✅ Admin API: Error-Recovery-Status abgerufen
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Request: GET /api/session/status
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:42 - [app] app - [INFO] INFO - ✅ API: Statistiken abgerufen
|
||||
2025-06-11 10:51:42 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:43 - [app] app - [INFO] INFO - ✅ Admin API: System-Health abgerufen
|
||||
2025-06-11 10:51:43 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:44 - [app] app - [DEBUG] DEBUG - Request: GET /calendar
|
||||
2025-06-11 10:51:44 - [app] app - [INFO] INFO - Locating template 'calendar.html':
|
||||
1: trying loader of application '__main__'
|
||||
class: jinja2.loaders.FileSystemLoader
|
||||
encoding: 'utf-8'
|
||||
followlinks: False
|
||||
searchpath:
|
||||
- C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates
|
||||
-> found ('C:\\Users\\TTOMCZA.EMEA\\Dev\\Projektarbeit-MYP\\backend\\templates\\calendar.html')
|
||||
2025-06-11 10:51:44 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /api/calendar/events
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /api/session/status
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /api/user/settings
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 302
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 302
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 302
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Request: GET /dashboard
|
||||
2025-06-11 10:51:45 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:45 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/static/icons/icon-192.png
|
||||
2025-06-11 10:51:46 - [app] app - [DEBUG] DEBUG - Request: POST /api/session/heartbeat
|
||||
2025-06-11 10:51:46 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Request: GET /jobs
|
||||
2025-06-11 10:51:56 - [app] app - [INFO] INFO - Locating template 'jobs.html':
|
||||
1: trying loader of application '__main__'
|
||||
class: jinja2.loaders.FileSystemLoader
|
||||
encoding: 'utf-8'
|
||||
followlinks: False
|
||||
searchpath:
|
||||
- C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates
|
||||
-> found ('C:\\Users\\TTOMCZA.EMEA\\Dev\\Projektarbeit-MYP\\backend\\templates\\jobs.html')
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Request: GET /api/session/status
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Request: GET /api/user/settings
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:56 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
|
||||
2025-06-11 10:51:57 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen
|
||||
2025-06-11 10:51:57 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:51:57 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/static/icons/icon-192.png
|
||||
2025-06-11 10:51:57 - [app] app - [DEBUG] DEBUG - Request: POST /api/session/heartbeat
|
||||
2025-06-11 10:51:57 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:11 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
|
||||
2025-06-11 10:52:11 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Request: GET /api/session/status
|
||||
2025-06-11 10:52:26 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:41 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
|
||||
2025-06-11 10:52:41 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/error-recovery/status
|
||||
2025-06-11 10:52:44 - [app] app - [INFO] INFO - ✅ Admin API: Error-Recovery-Status abgerufen
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/session/status
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:44 - [app] app - [INFO] INFO - ✅ API: Statistiken abgerufen
|
||||
2025-06-11 10:52:44 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
2025-06-11 10:52:45 - [app] app - [INFO] INFO - ✅ Admin API: System-Health abgerufen
|
||||
2025-06-11 10:52:45 - [app] app - [DEBUG] DEBUG - Response: 200
|
||||
|
||||
@ -21,3 +21,4 @@
|
||||
2025-06-11 09:08:20 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-07 22:00:00+00:00 bis 2025-06-14 22:00:00+00:00
|
||||
2025-06-11 09:08:20 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-07 22:00:00+00:00 bis 2025-06-14 22:00:00+00:00
|
||||
2025-06-11 09:48:07 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-07 22:00:00+00:00 bis 2025-06-14 22:00:00+00:00
|
||||
2025-06-11 10:51:45 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-07 22:00:00+00:00 bis 2025-06-14 22:00:00+00:00
|
||||
|
||||
@ -107,3 +107,13 @@ TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
|
||||
2025-06-11 09:48:01 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
2025-06-11 10:40:53 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
|
||||
2025-06-11 10:40:53 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
2025-06-11 10:51:56 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
|
||||
2025-06-11 10:51:56 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
2025-06-11 10:52:11 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
|
||||
2025-06-11 10:52:11 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
2025-06-11 10:52:26 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
|
||||
2025-06-11 10:52:26 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
2025-06-11 10:52:26 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
|
||||
2025-06-11 10:52:26 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
2025-06-11 10:52:41 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
|
||||
2025-06-11 10:52:41 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
|
||||
|
||||
@ -69,3 +69,5 @@
|
||||
2025-06-11 10:39:17 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-11 10:45:14 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-11 10:45:17 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-11 10:51:33 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-11 10:51:36 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
|
||||
@ -651,3 +651,10 @@
|
||||
2025-06-11 10:45:14 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-11 10:45:16 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-11 10:45:16 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-11 10:51:33 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-11 10:51:33 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-11 10:51:36 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-11 10:51:36 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-11 10:51:38 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-11 10:51:38 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Prüfe Status von 6 aktiven Druckern...
|
||||
2025-06-11 10:51:42 - [printer_monitor] printer_monitor - [INFO] INFO - ✅ Status-Update abgeschlossen für 6 Drucker
|
||||
|
||||
@ -441,3 +441,9 @@
|
||||
2025-06-11 10:44:27 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-11 10:44:32 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 6 Drucker
|
||||
2025-06-11 10:44:32 - [printers] printers - [INFO] INFO - [OK] API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 4567.17ms
|
||||
2025-06-11 10:51:38 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-11 10:51:42 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 6 Drucker
|
||||
2025-06-11 10:51:42 - [printers] printers - [INFO] INFO - [OK] API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 3980.49ms
|
||||
2025-06-11 10:51:42 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-11 10:51:42 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 6 Drucker
|
||||
2025-06-11 10:51:42 - [printers] printers - [INFO] INFO - [OK] API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 1.42ms
|
||||
|
||||
@ -394,3 +394,25 @@
|
||||
2025-06-11 10:45:23 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
|
||||
2025-06-11 10:45:23 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
|
||||
2025-06-11 10:45:23 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestoppt
|
||||
2025-06-11 10:51:34 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Initialisiere neuen Queue-Manager...
|
||||
2025-06-11 10:51:34 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Zentrale Shutdown-Verwaltung erkannt - deaktiviere lokale Signal-Handler
|
||||
2025-06-11 10:51:34 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Starte Printer Queue Manager...
|
||||
2025-06-11 10:51:34 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Queue-Überwachung gestartet (Intervall: 120 Sekunden)
|
||||
2025-06-11 10:51:34 - [queue_manager] queue_manager - [INFO] INFO - ✅ Printer Queue Manager gestartet
|
||||
2025-06-11 10:51:34 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestartet
|
||||
2025-06-11 10:51:36 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Initialisiere neuen Queue-Manager...
|
||||
2025-06-11 10:51:36 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Zentrale Shutdown-Verwaltung erkannt - deaktiviere lokale Signal-Handler
|
||||
2025-06-11 10:51:36 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Starte Printer Queue Manager...
|
||||
2025-06-11 10:51:36 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Queue-Überwachung gestartet (Intervall: 120 Sekunden)
|
||||
2025-06-11 10:51:36 - [queue_manager] queue_manager - [INFO] INFO - ✅ Printer Queue Manager gestartet
|
||||
2025-06-11 10:51:36 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestartet
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Stoppe Queue-Manager...
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - ⏳ Warte auf Monitor-Thread...
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestoppt
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Stoppe Queue-Manager...
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - ⏳ Warte auf Monitor-Thread...
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
|
||||
2025-06-11 10:52:49 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestoppt
|
||||
|
||||
@ -159,3 +159,39 @@
|
||||
2025-06-11 10:45:16 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-11 10:45:17 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
|
||||
2025-06-11 10:45:17 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
|
||||
2025-06-11 10:51:33 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.100): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.100) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.100) nach 6 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.101): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.101) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:34 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.101) nach 7 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:36 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-11 10:51:36 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
|
||||
2025-06-11 10:51:36 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.102): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.102) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.102) nach 7 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.103): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.103) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.103) nach 6 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.104): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.104) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:37 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.104) nach 6 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.102): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.102) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.102) nach 7 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.103): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.103) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.103) nach 6 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.106): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.106) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.106) nach 7 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.104): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.104) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:38 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.104) nach 6 Min Leerlauf ausgeschaltet
|
||||
2025-06-11 10:51:39 - [scheduler] scheduler - [INFO] INFO - ✅ Drucker Tapo P110 (192.168.0.106): Status auf 'online' gesetzt (Steckdose ausgeschaltet - bereit)
|
||||
2025-06-11 10:51:39 - [scheduler] scheduler - [INFO] INFO - ✅ Status für Drucker Tapo P110 (192.168.0.106) erfolgreich aktualisiert
|
||||
2025-06-11 10:51:39 - [scheduler] scheduler - [INFO] INFO - 💤 Drucker Tapo P110 (192.168.0.106) nach 7 Min Leerlauf ausgeschaltet
|
||||
|
||||
@ -69,3 +69,5 @@
|
||||
2025-06-11 10:39:17 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-11 10:45:14 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-11 10:45:17 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-11 10:51:33 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-11 10:51:36 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
|
||||
@ -582,3 +582,21 @@
|
||||
2025-06-11 10:45:17 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-11 10:45:17 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-11 10:45:17 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - [START] MYP Platform Backend wird gestartet...
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - 🐍 Python Version: 3.13.3 (tags/v3.13.3:6280bb5, Apr 8 2025, 14:47:33) [MSC v.1943 64 bit (AMD64)]
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-11T10:51:33.572015
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-11 10:51:33 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - [START] MYP Platform Backend wird gestartet...
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - 🐍 Python Version: 3.13.3 (tags/v3.13.3:6280bb5, Apr 8 2025, 14:47:33) [MSC v.1943 64 bit (AMD64)]
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-11T10:51:36.311850
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-11 10:51:36 - [startup] startup - [INFO] INFO - ==================================================
|
||||
|
||||
@ -467,3 +467,64 @@
|
||||
2025-06-11 10:45:23 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.104 erfolgreich: unbekannt
|
||||
2025-06-11 10:45:23 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.104)' (192.168.0.104) gefunden - status: off
|
||||
2025-06-11 10:45:23 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 3/6: 192.168.0.100
|
||||
2025-06-11 10:51:33 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert
|
||||
2025-06-11 10:51:34 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.100 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:34 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.101 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:35 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 starte automatische tapo-steckdosenerkennung...
|
||||
2025-06-11 10:51:35 - [tapo_controller] tapo_controller - [INFO] INFO - 🔄 teste 6 standard-ips aus der konfiguration
|
||||
2025-06-11 10:51:35 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 1/6: 192.168.0.103
|
||||
2025-06-11 10:51:36 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert
|
||||
2025-06-11 10:51:36 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ versuch 1/3 fehlgeschlagen beim ausschalten von 192.168.0.102: HTTPConnectionPool(host='192.168.0.102', port=80): Read timed out. (read timeout=2)
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.102 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.103 ist erreichbar
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.103 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.103 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.103)' (192.168.0.103) gefunden - status: off
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 2/6: 192.168.0.104
|
||||
2025-06-11 10:51:37 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.104 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.102 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 starte automatische tapo-steckdosenerkennung...
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - 🔄 teste 6 standard-ips aus der konfiguration
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 1/6: 192.168.0.103
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.103 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.106 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:38 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.104 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:39 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 192.168.0.106 erfolgreich ausgeschaltet
|
||||
2025-06-11 10:51:39 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.104 ist erreichbar
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.104 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.104)' (192.168.0.104) gefunden - status: off
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 3/6: 192.168.0.100
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.103 ist erreichbar
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.103 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.103)' (192.168.0.103) gefunden - status: off
|
||||
2025-06-11 10:51:40 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 2/6: 192.168.0.104
|
||||
2025-06-11 10:51:42 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.100 ist erreichbar
|
||||
2025-06-11 10:51:42 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.100 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:42 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.100)' (192.168.0.100) gefunden - status: off
|
||||
2025-06-11 10:51:42 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 4/6: 192.168.0.101
|
||||
2025-06-11 10:51:42 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.104 ist erreichbar
|
||||
2025-06-11 10:51:43 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.104 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:43 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.104)' (192.168.0.104) gefunden - status: off
|
||||
2025-06-11 10:51:43 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 3/6: 192.168.0.100
|
||||
2025-06-11 10:51:44 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.101 ist erreichbar
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.101 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.101)' (192.168.0.101) gefunden - status: off
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 5/6: 192.168.0.102
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.100 ist erreichbar
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.100 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.100)' (192.168.0.100) gefunden - status: off
|
||||
2025-06-11 10:51:45 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 4/6: 192.168.0.101
|
||||
2025-06-11 10:51:47 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.102 ist erreichbar
|
||||
2025-06-11 10:51:47 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.102 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:47 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.102)' (192.168.0.102) gefunden - status: off
|
||||
2025-06-11 10:51:47 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 6/6: 192.168.0.105
|
||||
2025-06-11 10:51:48 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.101 ist erreichbar
|
||||
2025-06-11 10:51:48 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.101 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:48 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.101)' (192.168.0.101) gefunden - status: off
|
||||
2025-06-11 10:51:48 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 5/6: 192.168.0.102
|
||||
2025-06-11 10:51:50 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdose mit ip 192.168.0.102 ist erreichbar
|
||||
2025-06-11 10:51:50 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.102 erfolgreich: unbekannt
|
||||
2025-06-11 10:51:50 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo-steckdose 'tapo p110 (192.168.0.102)' (192.168.0.102) gefunden - status: off
|
||||
2025-06-11 10:51:50 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 6/6: 192.168.0.105
|
||||
2025-06-11 10:51:53 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdosen-erkennung abgeschlossen: 5/6 steckdosen gefunden in 18.0s
|
||||
2025-06-11 10:51:56 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ steckdosen-erkennung abgeschlossen: 5/6 steckdosen gefunden in 18.7s
|
||||
|
||||
@ -124,3 +124,5 @@
|
||||
2025-06-11 10:40:21 - [user] user - [INFO] INFO - User admin retrieved settings via API
|
||||
2025-06-11 10:40:53 - [user] user - [INFO] INFO - User admin retrieved settings via API
|
||||
2025-06-11 10:41:12 - [user] user - [INFO] INFO - User admin retrieved settings via API
|
||||
2025-06-11 10:51:38 - [user] user - [INFO] INFO - User admin retrieved settings via API
|
||||
2025-06-11 10:51:56 - [user] user - [INFO] INFO - User admin retrieved settings via API
|
||||
|
||||
@ -138,3 +138,11 @@
|
||||
2025-06-11 10:45:16 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-11 10:45:16 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-11 10:45:16 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
2025-06-11 10:51:32 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
|
||||
2025-06-11 10:51:32 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-11 10:51:32 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-11 10:51:32 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
2025-06-11 10:51:35 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
|
||||
2025-06-11 10:51:35 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-11 10:51:35 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-11 10:51:35 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
|
||||
Reference in New Issue
Block a user