core/Projektarbeit-MYP
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: Änderungen commited

Browse Source
This commit is contained in:
Till Tomczak
2025-06-16 08:28:45 +02:00
parent d4d5647d40
commit 4491156902
294 changed files with 1476 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
backend/logs/admin/admin.log
View File

@@ -384,3 +384,67 @@
2025-06-16 07:03:56 - [admin] admin - [INFO] INFO - Admin-Check für Funktion get_pending_guest_otps_api: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 07:03:56 - [admin] admin - [INFO] INFO - Aktive OTP-Codes abgerufen: 3 Codes
2025-06-16 07:03:56 - [admin] admin - [INFO] INFO - Gastanfragen abgerufen: 3 Einträge für Admin Administrator
2025-06-16 08:00:40 - [admin] admin - [INFO] INFO - Admin-Check für Funktion admin_dashboard: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:00:40 - [admin] admin - [INFO] INFO - Admin-Dashboard geladen von admin
2025-06-16 08:00:40 - [admin] admin - [ERROR] ERROR - Fehler beim Laden des Admin-Dashboards: 'dict object' has no attribute 'online_printers'
2025-06-16 08:00:41 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:00:41 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:00:43 - [admin] admin - [INFO] INFO - Admin-Check für Funktion guest_requests: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:28 - [admin] admin - [INFO] INFO - Admin-Check für Funktion admin_dashboard: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:28 - [admin] admin - [INFO] INFO - Admin-Dashboard geladen von admin
2025-06-16 08:08:28 - [admin] admin - [ERROR] ERROR - Fehler beim Laden des Admin-Dashboards: 'dict object' has no attribute 'online_printers'
2025-06-16 08:08:29 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:29 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:33 - [admin] admin - [INFO] INFO - Admin-Check für Funktion guest_requests: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:56 - [admin] admin - [INFO] INFO - Admin-Check für Funktion admin_dashboard: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:56 - [admin] admin - [INFO] INFO - Admin-Dashboard geladen von admin
2025-06-16 08:08:56 - [admin] admin - [ERROR] ERROR - Fehler beim Laden des Admin-Dashboards: 'dict object' has no attribute 'online_printers'
2025-06-16 08:08:57 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:08:57 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:09:01 - [admin] admin - [INFO] INFO - Admin-Check für Funktion guest_otps_management: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:09:01 - [admin] admin - [INFO] INFO - Gast-OTP-Verwaltung aufgerufen von Admin Administrator
2025-06-16 08:09:02 - [admin] admin - [INFO] INFO - Admin-Check für Funktion get_guest_requests_api: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:09:02 - [admin] admin - [INFO] INFO - Gastanfragen abgerufen: 5 Einträge für Admin Administrator
2025-06-16 08:09:02 - [admin] admin - [INFO] INFO - Admin-Check für Funktion get_pending_guest_otps_api: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:09:02 - [admin] admin - [INFO] INFO - Aktive OTP-Codes abgerufen: 5 Codes
2025-06-16 08:15:06 - [admin] admin - [INFO] INFO - Admin-Check für Funktion admin_dashboard: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:06 - [admin] admin - [INFO] INFO - Admin-Dashboard geladen von admin
2025-06-16 08:15:06 - [admin] admin - [ERROR] ERROR - Fehler beim Laden des Admin-Dashboards: 'dict object' has no attribute 'online_printers'
2025-06-16 08:15:07 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:07 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:12 - [admin] admin - [INFO] INFO - Admin-Check für Funktion printers_overview: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:12 - [admin] admin - [INFO] INFO - Druckerübersicht geladen von admin
2025-06-16 08:15:12 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:12 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:14 - [admin] admin - [INFO] INFO - Admin-Check für Funktion users_overview: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:14 - [admin] admin - [INFO] INFO - Benutzerübersicht geladen von admin
2025-06-16 08:15:14 - [admin] admin - [ERROR] ERROR - Fehler beim Laden der Benutzerübersicht: 'dict object' has no attribute 'online_printers'
2025-06-16 08:15:14 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:14 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:44 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_error_recovery_status: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:44 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:15:44 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:19:25 - [admin] admin - [INFO] INFO - Admin-Check für Funktion admin_dashboard: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:19:25 - [admin] admin - [INFO] INFO - Admin-Dashboard geladen von admin
2025-06-16 08:19:25 - [admin] admin - [ERROR] ERROR - Fehler beim Laden des Admin-Dashboards: 'dict object' has no attribute 'online_printers'
2025-06-16 08:19:25 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:19:25 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:19:30 - [admin] admin - [INFO] INFO - Admin-Check für Funktion tapo_monitoring: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:19:30 - [admin] admin - [INFO] INFO - Tapo-Monitoring aufgerufen von admin
2025-06-16 08:19:34 - [admin] admin - [INFO] INFO - Tapo-Monitoring geladen: 6 Steckdosen, 0 online
2025-06-16 08:19:43 - [admin] admin - [INFO] INFO - Admin-Check für Funktion tapo_monitoring: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:19:43 - [admin] admin - [INFO] INFO - Tapo-Monitoring aufgerufen von admin
2025-06-16 08:19:46 - [admin] admin - [INFO] INFO - Tapo-Monitoring geladen: 6 Steckdosen, 0 online
2025-06-16 08:19:50 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_tapo_health_check: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:20:17 - [admin] admin - [INFO] INFO - Admin-Check für Funktion tapo_monitoring: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:20:17 - [admin] admin - [INFO] INFO - Tapo-Monitoring aufgerufen von admin
2025-06-16 08:20:21 - [admin] admin - [INFO] INFO - Tapo-Monitoring geladen: 6 Steckdosen, 0 online
2025-06-16 08:20:31 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_bulk_tapo_control: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:21:24 - [admin] admin - [INFO] INFO - Admin-Check für Funktion admin_dashboard: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:21:24 - [admin] admin - [INFO] INFO - Admin-Dashboard geladen von admin
2025-06-16 08:21:24 - [admin] admin - [ERROR] ERROR - Fehler beim Laden des Admin-Dashboards: 'dict object' has no attribute 'online_printers'
2025-06-16 08:21:24 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health_alias: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:21:24 - [admin] admin - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:21:27 - [admin] admin - [INFO] INFO - Admin-Check für Funktion advanced_settings: User authenticated: True, User ID: 1, Is Admin: True
2025-06-16 08:21:27 - [admin] admin - [INFO] INFO - Erweiterte Einstellungen geladen von admin
2025-06-16 08:21:27 - [admin] admin - [ERROR] ERROR - Fehler beim Laden der erweiterten Einstellungen: 'maintenance_info' is undefined

45
backend/logs/admin_api/admin_api.log
View File

@@ -123,3 +123,48 @@
2025-06-16 07:03:00 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 07:03:00 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 07:03:00 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:00:41 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:00:41 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:00:41 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:08:29 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:08:29 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:08:29 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:08:57 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:08:57 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:08:57 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:15:07 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:07 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:15:07 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:15:12 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:12 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:15:12 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:15:14 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:14 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:15:14 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:15:44 - [admin_api] admin_api - [INFO] INFO - Error-Recovery-Status angefordert von admin
2025-06-16 08:15:44 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:44 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:15:44 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:15:45 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check für Error-Recovery fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:45 - [admin_api] admin_api - [INFO] INFO - Error-Recovery-Status abgerufen: critical
2025-06-16 08:19:25 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:19:25 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:19:25 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy
2025-06-16 08:19:50 - [admin_api] admin_api - [INFO] INFO - Tapo-Gesundheitscheck von admin
2025-06-16 08:20:11 - [admin_api] admin_api - [INFO] INFO - Tapo-Gesundheitscheck abgeschlossen: {'total': 6, 'healthy': 0, 'warning': 6, 'critical': 0}
2025-06-16 08:20:31 - [admin_api] admin_api - [INFO] INFO - Bulk-Tapo-Steuerung von admin
2025-06-16 08:20:32 - [admin_api] admin_api - [ERROR] ERROR - Fehler bei Bulk-Steuerung für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:32.412403', '192.168.0.100', None, None, None, 'system', None, None, 1114, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:32 - [admin_api] admin_api - [ERROR] ERROR - Fehler bei Bulk-Steuerung für Drucker 2: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:32.412403', '192.168.0.100', None, None, None, 'system', None, None, 1114, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:32 - [admin_api] admin_api - [ERROR] ERROR - Unerwarteter Fehler bei Bulk-Tapo-Steuerung: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:32.412403', '192.168.0.100', None, None, None, 'system', None, None, 1114, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:21:24 - [admin_api] admin_api - [ERROR] ERROR - Datenbank-Health-Check fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:21:24 - [admin_api] admin_api - [ERROR] ERROR - Speicherplatz-Check fehlgeschlagen: module 'os' has no attribute 'statvfs'
2025-06-16 08:21:24 - [admin_api] admin_api - [INFO] INFO - System-Health-Check durchgeführt: unhealthy

9
backend/logs/api/api.log
View File

@@ -42,3 +42,12 @@
2025-06-16 01:43:06 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 07:00:20 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 07:03:00 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:00:41 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:08:29 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:08:57 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:15:07 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:15:12 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:15:14 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:15:44 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:19:25 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin
2025-06-16 08:21:24 - [api] api - [INFO] INFO - Statistiken abgerufen von Benutzer admin

731
backend/logs/app/app.log
View File

@@ -38992,3 +38992,734 @@ WHERE users.id = ?
2025-06-16 08:03:07 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:03:37 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:03:37 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:04:07 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:04:07 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:04:37 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:04:37 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:05:07 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:05:07 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:05:38 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:05:38 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:06:08 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:06:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:06:38 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:06:38 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:07:08 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:07:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:07:38 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:07:38 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:07:41 - [app] app - [DEBUG] DEBUG - Request: GET /
2025-06-16 08:07:41 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:07:41 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
2025-06-16 08:07:41 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:07:48 - [app] app - [DEBUG] DEBUG - Request: GET /request
2025-06-16 08:07:48 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:09 - [app] app - [DEBUG] DEBUG - Request: POST /request
2025-06-16 08:08:09 - [app] app - [INFO] INFO - 6-stelliger OTP generiert für Guest Request 5
2025-06-16 08:08:09 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:08:09 - [app] app - [DEBUG] DEBUG - Request: GET /request/5
2025-06-16 08:08:09 - [app] app - [INFO] INFO - Locating template 'guest_status.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\\guest_status.html')
2025-06-16 08:08:09 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:14 - [app] app - [DEBUG] DEBUG - Request: GET /request/5
2025-06-16 08:08:14 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:19 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
2025-06-16 08:08:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:21 - [app] app - [DEBUG] DEBUG - Request: POST /auth/login
2025-06-16 08:08:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:23 - [app] app - [DEBUG] DEBUG - Request: GET /
2025-06-16 08:08:23 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:08:23 - [app] app - [DEBUG] DEBUG - Request: GET /dashboard
2025-06-16 08:08:23 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:23 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:08:23 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:28 - [app] app - [DEBUG] DEBUG - Request: GET /admin/
2025-06-16 08:08:28 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:29 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:08:29 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:08:29 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:29 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:29 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:08:29 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:08:29 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:33 - [app] app - [DEBUG] DEBUG - Request: GET /admin/guest-requests
2025-06-16 08:08:33 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:33 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:08:33 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/requests
2025-06-16 08:08:33 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:33 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:47 - [app] app - [DEBUG] DEBUG - Request: POST /api/requests/5/approve
2025-06-16 08:08:48 - [app] app - [INFO] INFO - 6-stelliger OTP generiert für Guest Request 5
2025-06-16 08:08:48 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:48 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/requests
2025-06-16 08:08:48 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:56 - [app] app - [DEBUG] DEBUG - Request: GET /admin/
2025-06-16 08:08:56 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:57 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:08:57 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:08:57 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:57 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:08:57 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:08:57 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:08:57 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:01 - [app] app - [DEBUG] DEBUG - Request: GET /admin/guest-otps
2025-06-16 08:09:01 - [app] app - [INFO] INFO - Locating template 'admin_guest_otps.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\\admin_guest_otps.html')
2025-06-16 08:09:01 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/guest-requests
2025-06-16 08:09:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/guest-requests/pending-otps
2025-06-16 08:09:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:09:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:20 - [app] app - [DEBUG] DEBUG - Request: POST /auth/logout
2025-06-16 08:09:20 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:09:20 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
2025-06-16 08:09:20 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:23 - [app] app - [DEBUG] DEBUG - Request: GET /request
2025-06-16 08:09:23 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:29 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:09:29 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:09:37 - [app] app - [DEBUG] DEBUG - Request: POST /api/guest/start-job
2025-06-16 08:09:37 - [app] app - [WARNING] WARNING - Ungültiger OTP-Code für Guest Request 1
2025-06-16 08:09:37 - [app] app - [WARNING] WARNING - Ungültiger OTP-Code für Guest Request 2
2025-06-16 08:09:37 - [app] app - [WARNING] WARNING - Ungültiger OTP-Code für Guest Request 3
2025-06-16 08:09:37 - [app] app - [WARNING] WARNING - Ungültiger OTP-Code für Guest Request 4
2025-06-16 08:09:38 - [app] app - [INFO] INFO - OTP erfolgreich verifiziert für Guest Request 5
2025-06-16 08:09:38 - [app] app - [INFO] INFO - OTP als verwendet markiert für Guest Request 5
2025-06-16 08:09:46 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Instance <Job at 0x17b0b5397c0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:09:46 - [app] app - [DEBUG] DEBUG - Response: 500
2025-06-16 08:10:00 - [app] app - [DEBUG] DEBUG - Request: GET /requests/overview
2025-06-16 08:10:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:10:26 - [app] app - [DEBUG] DEBUG - Request: GET /
2025-06-16 08:10:26 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:10:26 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
2025-06-16 08:10:26 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:31 - [app] app - [DEBUG] DEBUG - Request: POST /auth/login
2025-06-16 08:12:31 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:33 - [app] app - [DEBUG] DEBUG - Request: GET /
2025-06-16 08:12:33 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:12:33 - [app] app - [DEBUG] DEBUG - Request: GET /dashboard
2025-06-16 08:12:33 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:33 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:12:33 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /energy/
2025-06-16 08:12:35 - [app] app - [INFO] INFO - Locating template 'energy_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\\energy_dashboard.html')
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/statistics
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/dashboard
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:12:35 - [app] app - [ERROR] ERROR - Fehler beim Laden des Benutzers 1: tuple index out of range
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Request: GET /dashboard
2025-06-16 08:12:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:13:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:13:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:13:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:13:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:13:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:13:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:13:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:13:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:14:05 - [app] app - [ERROR] ERROR - Fehler beim Laden des Benutzers 1: tuple index out of range
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Request: GET /auth/login
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Request: GET /
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Response: 302
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Request: GET /dashboard
2025-06-16 08:14:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:14:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:14:35 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:14:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:14:35 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:15:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:15:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:06 - [app] app - [DEBUG] DEBUG - Request: GET /admin/
2025-06-16 08:15:06 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:07 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:15:07 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:15:07 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:07 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:07 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:15:07 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:07 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Request: GET /admin/printers
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:15:12 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:12 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Request: GET /admin/users
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:15:14 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:14 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/error-recovery/status
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:44 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:44 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:15:45 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:15:45 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:05 - [app] app - [DEBUG] DEBUG - Request: GET /dashboard
2025-06-16 08:16:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:05 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:16:05 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Request: GET /energy/
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:08 - [app] app - [ERROR] ERROR - Fehler beim Laden des Benutzers 1: Invalid isoformat string: ''
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/dashboard
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/statistics
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:29 - [app] app - [DEBUG] DEBUG - Request: GET /stats
2025-06-16 08:16:29 - [app] app - [INFO] INFO - Locating template 'stats.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\\stats.html')
2025-06-16 08:16:30 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:16:30 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:16:30 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:17:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:17:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:17:30 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:17:30 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:18:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:18:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:18:48 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: ./database/myp.db
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [CONFIG] Erkannte Umgebung: development
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [CONFIG] Production-Modus: False
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [CONFIG] Verwende Development-Konfiguration
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [DEVELOPMENT] Aktiviere Development-Konfiguration
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ MYP Development Environment Konfiguration aktiviert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Environment: Development/Testing
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Debug Mode: True
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ SQL Echo: True
2025-06-16 08:18:50 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Admin-Berechtigungen beim Start korrigiert: 0 erstellt, 0 aktualisiert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] 🚀 Starte MYP DEVELOPMENT-Umgebung
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] 🏢 Mercedes-Benz TBA Marienfelde
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] 🔒 Air-Gapped: True
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] Initialisiere Datenbank...
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] ✅ Datenbank initialisiert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] Prüfe Initial-Admin...
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] ✅ Admin-Benutzer geprüft
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] Initialisiere statische Drucker...
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 1 (192.168.0.100)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 2 (192.168.0.101)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 3 (192.168.0.102)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 4 (192.168.0.103)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 5 (192.168.0.104)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 6 (192.168.0.106)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - ✅ Statische Drucker-Initialisierung abgeschlossen: 0 erstellt, 6 aktualisiert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - 📍 Alle Drucker sind für Standort 'TBA Marienfelde' konfiguriert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - 🌐 IP-Bereich: 192.168.0.100-106 (außer .105)
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] ✅ Statische Drucker konfiguriert
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] Starte Queue Manager...
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] ✅ Queue Manager gestartet
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] Starte Job Scheduler...
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] ✅ Job Scheduler gestartet
2025-06-16 08:18:50 - [app] app - [INFO] INFO - [STARTUP] 🌐 Server startet auf http://0.0.0.0:5000
2025-06-16 08:18:52 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: ./database/myp.db
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [CONFIG] Erkannte Umgebung: development
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [CONFIG] Production-Modus: False
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [CONFIG] Verwende Development-Konfiguration
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [DEVELOPMENT] Aktiviere Development-Konfiguration
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ MYP Development Environment Konfiguration aktiviert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Environment: Development/Testing
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Debug Mode: True
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ SQL Echo: True
2025-06-16 08:18:54 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Admin-Berechtigungen beim Start korrigiert: 0 erstellt, 0 aktualisiert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] 🚀 Starte MYP DEVELOPMENT-Umgebung
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] 🏢 Mercedes-Benz TBA Marienfelde
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] 🔒 Air-Gapped: True
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] Initialisiere Datenbank...
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] ✅ Datenbank initialisiert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] Prüfe Initial-Admin...
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] ✅ Admin-Benutzer geprüft
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] Initialisiere statische Drucker...
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 1 (192.168.0.100)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 2 (192.168.0.101)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 3 (192.168.0.102)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 4 (192.168.0.103)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 5 (192.168.0.104)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 6 (192.168.0.106)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - ✅ Statische Drucker-Initialisierung abgeschlossen: 0 erstellt, 6 aktualisiert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - 📍 Alle Drucker sind für Standort 'TBA Marienfelde' konfiguriert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - 🌐 IP-Bereich: 192.168.0.100-106 (außer .105)
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] ✅ Statische Drucker konfiguriert
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] Starte Queue Manager...
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] ✅ Queue Manager gestartet
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] Starte Job Scheduler...
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] ✅ Job Scheduler gestartet
2025-06-16 08:18:54 - [app] app - [INFO] INFO - [STARTUP] 🌐 Server startet auf http://0.0.0.0:5000
2025-06-16 08:18:57 - [app] app - [INFO] INFO - Locating template 'stats.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\\stats.html')
2025-06-16 08:18:57 - [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-16 08:18:57 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:18:57 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:18:57 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:18:59 - [app] app - [DEBUG] DEBUG - Request: GET /printers
2025-06-16 08:18:59 - [app] app - [INFO] INFO - Locating template 'printers.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\\printers.html')
2025-06-16 08:18:59 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:18:59 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:18:59 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:18:59 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:19:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:19:00 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:19:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:19:02 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:19:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:07 - [app] app - [DEBUG] DEBUG - Request: POST /api/printers/1/connect
2025-06-16 08:19:07 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/api/printers/1/connect
2025-06-16 08:19:07 - [app] app - [DEBUG] DEBUG - Response: 404
2025-06-16 08:19:09 - [app] app - [DEBUG] DEBUG - Request: POST /api/printers/2/connect
2025-06-16 08:19:09 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/api/printers/2/connect
2025-06-16 08:19:09 - [app] app - [DEBUG] DEBUG - Response: 404
2025-06-16 08:19:12 - [app] app - [DEBUG] DEBUG - Request: GET /.well-known/appspecific/com.chrome.devtools.json
2025-06-16 08:19:12 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/.well-known/appspecific/com.chrome.devtools.json
2025-06-16 08:19:12 - [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-16 08:19:12 - [app] app - [DEBUG] DEBUG - Response: 404
2025-06-16 08:19:14 - [app] app - [DEBUG] DEBUG - Request: POST /api/printers/2/connect
2025-06-16 08:19:14 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/api/printers/2/connect
2025-06-16 08:19:14 - [app] app - [DEBUG] DEBUG - Response: 404
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Request: GET /admin/
2025-06-16 08:19:25 - [app] app - [INFO] INFO - Locating template 'admin.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\\admin.html')
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:19:25 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:19:25 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:30 - [app] app - [DEBUG] DEBUG - Request: GET /admin/tapo-monitoring
2025-06-16 08:19:34 - [app] app - [INFO] INFO - Locating template 'admin_tapo_monitoring.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\\admin_tapo_monitoring.html')
2025-06-16 08:19:34 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:34 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:19:34 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:43 - [app] app - [DEBUG] DEBUG - Request: GET /admin/tapo-monitoring
2025-06-16 08:19:46 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:46 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:19:46 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:19:50 - [app] app - [DEBUG] DEBUG - Request: POST /api/admin/tapo/health-check
2025-06-16 08:20:11 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:17 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:20:17 - [app] app - [DEBUG] DEBUG - Request: GET /admin/tapo-monitoring
2025-06-16 08:20:17 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:21 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:20:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:31 - [app] app - [DEBUG] DEBUG - Request: POST /api/admin/tapo/bulk-control
2025-06-16 08:20:32 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:32.412403', '192.168.0.100', None, None, None, 'system', None, None, 1114, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:32 - [app] app - [DEBUG] DEBUG - Response: 500
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Request: GET /energy/
2025-06-16 08:20:51 - [app] app - [INFO] INFO - Locating template 'energy_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\\energy_dashboard.html')
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/dashboard
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/statistics
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:51 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/dashboard
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/statistics
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/dashboard
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/statistics
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Request: GET /api/energy/live
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:53 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:54 - [app] app - [DEBUG] DEBUG - Request: GET /stats
2025-06-16 08:20:54 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:55 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:20:55 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:58 - [app] app - [DEBUG] DEBUG - Request: GET /jobs
2025-06-16 08:20:58 - [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-16 08:20:58 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:59 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:20:59 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
2025-06-16 08:20:59 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:59 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:20:59 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:20:59 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:20:59 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Request: GET /printers
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:00 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:21:00 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:00 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:01 - [app] app - [DEBUG] DEBUG - Request: GET /jobs
2025-06-16 08:21:01 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:21:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
2025-06-16 08:21:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:02 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:02 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:02 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:06 - [app] app - [DEBUG] DEBUG - Request: DELETE /api/jobs/3
2025-06-16 08:21:06 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:06 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
2025-06-16 08:21:06 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:08 - [app] app - [DEBUG] DEBUG - Request: DELETE /api/jobs/2
2025-06-16 08:21:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:08 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
2025-06-16 08:21:08 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:10 - [app] app - [DEBUG] DEBUG - Request: DELETE /api/jobs/1
2025-06-16 08:21:10 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:10 - [app] app - [DEBUG] DEBUG - Request: GET /api/jobs
2025-06-16 08:21:10 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Request: GET /printers
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:11 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:11 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:11 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:13 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:13 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:13 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:13 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:13 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:13 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:17 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:17 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:17 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:17 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:17 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:17 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:19 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:19 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Request: GET /printers
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:21 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Request: GET /api/printers
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:21 - [app] app - [INFO] INFO - ✅ API: 6 Drucker abgerufen (include_inactive=False)
2025-06-16 08:21:21 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Request: GET /admin/
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Request: GET /api/stats
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Request: GET /api/admin/system-health
2025-06-16 08:21:24 - [app] app - [ERROR] ERROR - Datenbank-Transaktion fehlgeschlagen: Textual SQL expression 'SELECT 1' should be explicitly declared as text('SELECT 1')
2025-06-16 08:21:24 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:27 - [app] app - [DEBUG] DEBUG - Request: GET /admin/advanced-settings
2025-06-16 08:21:27 - [app] app - [INFO] INFO - Locating template 'admin_advanced_settings.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\\admin_advanced_settings.html')
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - Unhandled Exception - ID: 20250616_082127
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - URL: http://127.0.0.1:5000/admin/advanced-settings
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - Method: GET
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - User: admin
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - Exception Type: UndefinedError
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - Exception: 'maintenance_info' is undefined
2025-06-16 08:21:27 - [app] app - [ERROR] ERROR - Traceback: Traceback (most recent call last):
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\blueprints\admin_unified.py", line 326, in advanced_settings
return render_template('admin_advanced_settings.html', stats=stats, optimization_settings=optimization_settings)
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask\templating.py", line 151, in render_template
return _render(app, template, context)
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask\templating.py", line 132, in _render
rv = template.render(context)
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\jinja2\environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\jinja2\environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates\admin_advanced_settings.html", line 1, in top-level template code
{% extends "base.html" %}
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates\base.html", line 459, in top-level template code
{% block content %}{% endblock %}
^^^^^^^^^^^^^
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates\admin_advanced_settings.html", line 532, in block 'content'
<span class="text-slate-900 dark:text-white font-semibold">{{ maintenance_info.last_backup }}</span>
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\jinja2\environment.py", line 490, in getattr
return getattr(obj, attribute)
jinja2.exceptions.UndefinedError: 'maintenance_info' is undefined
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask\app.py", line 1484, in full_dispatch_request
rv = self.dispatch_request()
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask\app.py", line 1469, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask_login\utils.py", line 290, in decorated_view
return current_app.ensure_sync(func)(*args, **kwargs)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\blueprints\admin_unified.py", line 88, in decorated_function
return f(*args, **kwargs)
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\blueprints\admin_unified.py", line 350, in advanced_settings
return render_template('admin_advanced_settings.html', stats=stats, optimization_settings=optimization_settings)
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask\templating.py", line 151, in render_template
return _render(app, template, context)
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\flask\templating.py", line 132, in _render
rv = template.render(context)
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\jinja2\environment.py", line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\jinja2\environment.py", line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates\admin_advanced_settings.html", line 1, in top-level template code
{% extends "base.html" %}
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates\base.html", line 459, in top-level template code
{% block content %}{% endblock %}
^^^^^^^^^^^^^
File "C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\templates\admin_advanced_settings.html", line 532, in block 'content'
<span class="text-slate-900 dark:text-white font-semibold">{{ maintenance_info.last_backup }}</span>
File "C:\Users\TTOMCZA.EMEA\AppData\Roaming\Python\Python313\site-packages\jinja2\environment.py", line 490, in getattr
return getattr(obj, attribute)
jinja2.exceptions.UndefinedError: 'maintenance_info' is undefined
2025-06-16 08:21:27 - [app] app - [INFO] INFO - Locating template 'errors/500.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\\500.html')
2025-06-16 08:21:27 - [app] app - [DEBUG] DEBUG - Response: 500
2025-06-16 08:21:28 - [app] app - [INFO] INFO - [SHUTDOWN] 🧹 Cleanup wird ausgeführt...
2025-06-16 08:21:28 - [app] app - [INFO] INFO - [SHUTDOWN] ✅ Queue Manager gestoppt
2025-06-16 08:21:28 - [app] app - [ERROR] ERROR - [SHUTDOWN] ❌ Cleanup-Fehler: 'BackgroundTaskScheduler' object has no attribute 'shutdown'
2025-06-16 08:21:29 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: ./database/myp.db
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [CONFIG] Erkannte Umgebung: development
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [CONFIG] Production-Modus: False
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [CONFIG] Verwende Development-Konfiguration
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [DEVELOPMENT] Aktiviere Development-Konfiguration
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ MYP Development Environment Konfiguration aktiviert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Environment: Development/Testing
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ Debug Mode: True
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [DEVELOPMENT] ✅ SQL Echo: True
2025-06-16 08:21:31 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Admin-Berechtigungen beim Start korrigiert: 0 erstellt, 0 aktualisiert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] 🚀 Starte MYP DEVELOPMENT-Umgebung
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] 🏢 Mercedes-Benz TBA Marienfelde
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] 🔒 Air-Gapped: True
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] Initialisiere Datenbank...
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] ✅ Datenbank initialisiert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] Prüfe Initial-Admin...
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] ✅ Admin-Benutzer geprüft
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] Initialisiere statische Drucker...
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 1 (192.168.0.100)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 2 (192.168.0.101)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 3 (192.168.0.102)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 4 (192.168.0.103)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 5 (192.168.0.104)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - Drucker aktualisiert: Drucker 6 (192.168.0.106)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - ✅ Statische Drucker-Initialisierung abgeschlossen: 0 erstellt, 6 aktualisiert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - 📍 Alle Drucker sind für Standort 'TBA Marienfelde' konfiguriert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - 🌐 IP-Bereich: 192.168.0.100-106 (außer .105)
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] ✅ Statische Drucker konfiguriert
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] Starte Queue Manager...
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] ✅ Queue Manager gestartet
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] Starte Job Scheduler...
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] ✅ Job Scheduler gestartet
2025-06-16 08:21:31 - [app] app - [INFO] INFO - [STARTUP] 🌐 Server startet auf http://0.0.0.0:5000
2025-06-16 08:21:32 - [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-16 08:21:32 - [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-16 08:21:32 - [app] app - [DEBUG] DEBUG - Response: 200
2025-06-16 08:21:32 - [app] app - [DEBUG] DEBUG - Request: GET /api/notifications
2025-06-16 08:21:32 - [app] app - [DEBUG] DEBUG - Response: 200

8
backend/logs/auth/auth.log
View File

@@ -97,3 +97,11 @@ WHERE users.username = ? OR users.email = ?
2025-06-16 06:59:40 - [auth] auth - [WARNING] WARNING - JSON-Parsing fehlgeschlagen: 400 Bad Request: Failed to decode JSON object: Expecting value: line 1 column 1 (char 0)
2025-06-16 06:59:41 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich erfolgreich angemeldet
2025-06-16 07:04:15 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich abgemeldet
2025-06-16 08:00:37 - [auth] auth - [WARNING] WARNING - JSON-Parsing fehlgeschlagen: 400 Bad Request: Failed to decode JSON object: Expecting value: line 1 column 1 (char 0)
2025-06-16 08:00:37 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich erfolgreich angemeldet
2025-06-16 08:01:00 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich abgemeldet
2025-06-16 08:08:21 - [auth] auth - [WARNING] WARNING - JSON-Parsing fehlgeschlagen: 400 Bad Request: Failed to decode JSON object: Expecting value: line 1 column 1 (char 0)
2025-06-16 08:08:21 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich erfolgreich angemeldet
2025-06-16 08:09:20 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich abgemeldet
2025-06-16 08:12:31 - [auth] auth - [WARNING] WARNING - JSON-Parsing fehlgeschlagen: 400 Bad Request: Failed to decode JSON object: Expecting value: line 1 column 1 (char 0)
2025-06-16 08:12:31 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich erfolgreich angemeldet

6
backend/logs/core_system/core_system.log
View File

@@ -218,3 +218,9 @@
2025-06-16 07:54:03 - [core_system] core_system - [INFO] INFO - 📊 Massive Konsolidierung: 6 Dateien → 1 Datei (88% Reduktion)
2025-06-16 08:00:34 - [core_system] core_system - [INFO] INFO - ✅ Core System Management Module erfolgreich initialisiert
2025-06-16 08:00:34 - [core_system] core_system - [INFO] INFO - 📊 Massive Konsolidierung: 6 Dateien → 1 Datei (88% Reduktion)
2025-06-16 08:18:48 - [core_system] core_system - [INFO] INFO - ✅ Core System Management Module erfolgreich initialisiert
2025-06-16 08:18:48 - [core_system] core_system - [INFO] INFO - 📊 Massive Konsolidierung: 6 Dateien → 1 Datei (88% Reduktion)
2025-06-16 08:18:52 - [core_system] core_system - [INFO] INFO - ✅ Core System Management Module erfolgreich initialisiert
2025-06-16 08:18:52 - [core_system] core_system - [INFO] INFO - 📊 Massive Konsolidierung: 6 Dateien → 1 Datei (88% Reduktion)
2025-06-16 08:21:29 - [core_system] core_system - [INFO] INFO - ✅ Core System Management Module erfolgreich initialisiert
2025-06-16 08:21:29 - [core_system] core_system - [INFO] INFO - 📊 Massive Konsolidierung: 6 Dateien → 1 Datei (88% Reduktion)

6
backend/logs/data_management/data_management.log
View File

@@ -563,3 +563,9 @@
2025-06-16 07:54:03 - [data_management] data_management - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:00:34 - [data_management] data_management - [INFO] INFO - ✅ Data Management Module initialisiert
2025-06-16 08:00:34 - [data_management] data_management - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:18:48 - [data_management] data_management - [INFO] INFO - ✅ Data Management Module initialisiert
2025-06-16 08:18:48 - [data_management] data_management - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:18:52 - [data_management] data_management - [INFO] INFO - ✅ Data Management Module initialisiert
2025-06-16 08:18:52 - [data_management] data_management - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:21:30 - [data_management] data_management - [INFO] INFO - ✅ Data Management Module initialisiert
2025-06-16 08:21:30 - [data_management] data_management - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)

44
backend/logs/energy_monitoring/energy_monitoring.log
View File

@@ -420,3 +420,47 @@
2025-06-16 07:54:01 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiemonitoring-Blueprint initialisiert
2025-06-16 07:54:05 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiemonitoring-Blueprint initialisiert
2025-06-16 08:00:36 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiemonitoring-Blueprint initialisiert
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - 🔋 Energiemonitoring-Dashboard aufgerufen von admin
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📊 API-Energiemonitoring-Dashboard von admin
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📈 API-Energiestatistiken (today) von admin
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiestatistiken erfolgreich erstellt für Zeitraum: today
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiestatistiken 'api_energy_statistics' erfolgreich in 9.96ms
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Dashboard-Daten erfolgreich erstellt: 0 Geräte online
2025-06-16 08:12:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiemonitoring-Dashboard 'api_energy_dashboard' erfolgreich in 11.66ms
2025-06-16 08:13:05 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 2.87ms
2025-06-16 08:13:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 4.26ms
2025-06-16 08:14:35 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 2.96ms
2025-06-16 08:15:05 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 2.63ms
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - 🔋 Energiemonitoring-Dashboard aufgerufen von admin
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📈 API-Energiestatistiken (today) von admin
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📊 API-Energiemonitoring-Dashboard von admin
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 7.00ms
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Dashboard-Daten erfolgreich erstellt: 0 Geräte online
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiemonitoring-Dashboard 'api_energy_dashboard' erfolgreich in 13.65ms
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiestatistiken erfolgreich erstellt für Zeitraum: today
2025-06-16 08:16:08 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiestatistiken 'api_energy_statistics' erfolgreich in 16.82ms
2025-06-16 08:18:50 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiemonitoring-Blueprint initialisiert
2025-06-16 08:18:54 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiemonitoring-Blueprint initialisiert
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - 🔋 Energiemonitoring-Dashboard aufgerufen von admin
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📊 API-Energiemonitoring-Dashboard von admin
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📈 API-Energiestatistiken (today) von admin
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Dashboard-Daten erfolgreich erstellt: 0 Geräte online
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiemonitoring-Dashboard 'api_energy_dashboard' erfolgreich in 11.04ms
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiestatistiken erfolgreich erstellt für Zeitraum: today
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiestatistiken 'api_energy_statistics' erfolgreich in 18.93ms
2025-06-16 08:20:51 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 9.74ms
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📈 API-Energiestatistiken (today) von admin
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📊 API-Energiemonitoring-Dashboard von admin
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiestatistiken erfolgreich erstellt für Zeitraum: today
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiestatistiken 'api_energy_statistics' erfolgreich in 9.79ms
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Dashboard-Daten erfolgreich erstellt: 0 Geräte online
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiemonitoring-Dashboard 'api_energy_dashboard' erfolgreich in 11.98ms
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 11.16ms
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📊 API-Energiemonitoring-Dashboard von admin
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Dashboard-Daten erfolgreich erstellt: 0 Geräte online
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiemonitoring-Dashboard 'api_energy_dashboard' erfolgreich in 3.98ms
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - 📈 API-Energiestatistiken (today) von admin
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Live-Energiedaten 'api_live_energy_data' erfolgreich in 5.39ms
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiestatistiken erfolgreich erstellt für Zeitraum: today
2025-06-16 08:20:53 - [energy_monitoring] energy_monitoring - [INFO] INFO - [OK] API-Energiestatistiken 'api_energy_statistics' erfolgreich in 6.19ms
2025-06-16 08:21:31 - [energy_monitoring] energy_monitoring - [INFO] INFO - ✅ Energiemonitoring-Blueprint initialisiert

201
backend/logs/hardware_integration/hardware_integration.log
View File

@@ -2149,3 +2149,204 @@
2025-06-16 08:00:34 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Printer Monitor initialisiert
2025-06-16 08:00:34 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Hardware Integration Module initialisiert
2025-06-16 08:00:34 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Massive Konsolidierung: 2 Dateien → 1 Datei (50% Reduktion)
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:12:35 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:13:05 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:13:35 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:14:35 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:15:05 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:16:08 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:18:48 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ PyP100 (TP-Link Tapo) verfügbar
2025-06-16 08:18:48 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Printer Monitor initialisiert
2025-06-16 08:18:48 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Hardware Integration Module initialisiert
2025-06-16 08:18:48 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Massive Konsolidierung: 2 Dateien → 1 Datei (50% Reduktion)
2025-06-16 08:18:52 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ PyP100 (TP-Link Tapo) verfügbar
2025-06-16 08:18:52 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Printer Monitor initialisiert
2025-06-16 08:18:52 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Hardware Integration Module initialisiert
2025-06-16 08:18:52 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Massive Konsolidierung: 2 Dateien → 1 Datei (50% Reduktion)
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:51 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 🔋 Sammle Energiestatistiken von allen P110 Steckdosen...
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 1 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 2 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 3 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 4 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 5 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [WARNING] WARNING - ⚠️ Konnte Energiedaten für Drucker 6 nicht abrufen: module 'PyP100.PyP100' has no attribute 'P110'
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Energiestatistiken erfolgreich gesammelt: 0/6 Geräte online
2025-06-16 08:20:53 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Gesamtverbrauch: 0.0W aktuell, 0.0Wh heute
2025-06-16 08:21:30 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ PyP100 (TP-Link Tapo) verfügbar
2025-06-16 08:21:30 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Printer Monitor initialisiert
2025-06-16 08:21:30 - [hardware_integration] hardware_integration - [INFO] INFO - ✅ Hardware Integration Module initialisiert
2025-06-16 08:21:30 - [hardware_integration] hardware_integration - [INFO] INFO - 📊 Massive Konsolidierung: 2 Dateien → 1 Datei (50% Reduktion)

14
backend/logs/job_queue_system/job_queue_system.log
View File

@@ -1105,3 +1105,17 @@
2025-06-16 08:00:34 - [job_queue_system] job_queue_system - [INFO] INFO - ✅ Job & Queue System Module initialisiert
2025-06-16 08:00:34 - [job_queue_system] job_queue_system - [INFO] INFO - 📊 MASSIVE Konsolidierung: 4 Dateien → 1 Datei (75% Reduktion)
2025-06-16 08:00:36 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestartet (Legacy-Kompatibilität)
2025-06-16 08:18:33 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestoppt (Legacy-Kompatibilität)
2025-06-16 08:18:33 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestoppt (Legacy-Kompatibilität)
2025-06-16 08:18:48 - [job_queue_system] job_queue_system - [INFO] INFO - ✅ Job & Queue System Module initialisiert
2025-06-16 08:18:48 - [job_queue_system] job_queue_system - [INFO] INFO - 📊 MASSIVE Konsolidierung: 4 Dateien → 1 Datei (75% Reduktion)
2025-06-16 08:18:50 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestartet (Legacy-Kompatibilität)
2025-06-16 08:18:52 - [job_queue_system] job_queue_system - [INFO] INFO - ✅ Job & Queue System Module initialisiert
2025-06-16 08:18:52 - [job_queue_system] job_queue_system - [INFO] INFO - 📊 MASSIVE Konsolidierung: 4 Dateien → 1 Datei (75% Reduktion)
2025-06-16 08:18:54 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestartet (Legacy-Kompatibilität)
2025-06-16 08:21:28 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestoppt (Legacy-Kompatibilität)
2025-06-16 08:21:30 - [job_queue_system] job_queue_system - [INFO] INFO - ✅ Job & Queue System Module initialisiert
2025-06-16 08:21:30 - [job_queue_system] job_queue_system - [INFO] INFO - 📊 MASSIVE Konsolidierung: 4 Dateien → 1 Datei (75% Reduktion)
2025-06-16 08:21:31 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestartet (Legacy-Kompatibilität)
2025-06-16 08:21:37 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestoppt (Legacy-Kompatibilität)
2025-06-16 08:21:37 - [job_queue_system] job_queue_system - [INFO] INFO - Queue Manager gestoppt (Legacy-Kompatibilität)

16
backend/logs/jobs/jobs.log
View File

@@ -919,3 +919,19 @@ sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) FOREIGN KEY constraint f
2025-06-16 01:38:32 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
2025-06-16 01:43:33 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
2025-06-16 01:43:33 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)
2025-06-16 08:20:59 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
2025-06-16 08:20:59 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 3 von 3 (Seite 1)
2025-06-16 08:21:02 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
2025-06-16 08:21:02 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 3 von 3 (Seite 1)
2025-06-16 08:21:06 - [jobs] jobs - [INFO] INFO - 🗑️ Lösche Job 3 für Benutzer 1
2025-06-16 08:21:06 - [jobs] jobs - [INFO] INFO - ✅ Job 'Gastauftrag: Till Tomczaktet' (ID: 3) erfolgreich gelöscht von Benutzer 1
2025-06-16 08:21:06 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
2025-06-16 08:21:06 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 2 von 2 (Seite 1)
2025-06-16 08:21:08 - [jobs] jobs - [INFO] INFO - 🗑️ Lösche Job 2 für Benutzer 1
2025-06-16 08:21:08 - [jobs] jobs - [INFO] INFO - ✅ Job 'Gastauftrag: Till Tomczaktet' (ID: 2) erfolgreich gelöscht von Benutzer 1
2025-06-16 08:21:08 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
2025-06-16 08:21:08 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 1 von 1 (Seite 1)
2025-06-16 08:21:10 - [jobs] jobs - [INFO] INFO - 🗑️ Lösche Job 1 für Benutzer 1
2025-06-16 08:21:10 - [jobs] jobs - [INFO] INFO - ✅ Job 'Gastauftrag: Till Tomczaktet' (ID: 1) erfolgreich gelöscht von Benutzer 1
2025-06-16 08:21:10 - [jobs] jobs - [INFO] INFO - 📋 Jobs-Abfrage gestartet von Benutzer 1 (Admin: True)
2025-06-16 08:21:10 - [jobs] jobs - [INFO] INFO - ✅ Jobs erfolgreich abgerufen: 0 von 0 (Seite 1)

2
backend/logs/models/models.log
View File

@@ -14,3 +14,5 @@
2025-06-16 06:58:54 - [models] models - [INFO] INFO - Erfolgreich 1 Benachrichtigungen erstellt für 'guest_request'
2025-06-16 08:00:26 - [models] models - [INFO] INFO - Gefunden: 1 Genehmiger für Benachrichtigung 'guest_request'
2025-06-16 08:00:26 - [models] models - [INFO] INFO - Erfolgreich 1 Benachrichtigungen erstellt für 'guest_request'
2025-06-16 08:08:09 - [models] models - [INFO] INFO - Gefunden: 1 Genehmiger für Benachrichtigung 'guest_request'
2025-06-16 08:08:09 - [models] models - [INFO] INFO - Erfolgreich 1 Benachrichtigungen erstellt für 'guest_request'

6
backend/logs/monitoring_analytics/monitoring_analytics.log
View File

@@ -563,3 +563,9 @@
2025-06-16 07:54:05 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - 📊 MASSIVE Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:00:36 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - ✅ Monitoring & Analytics Module initialisiert
2025-06-16 08:00:36 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - 📊 MASSIVE Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:18:50 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - ✅ Monitoring & Analytics Module initialisiert
2025-06-16 08:18:50 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - 📊 MASSIVE Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:18:54 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - ✅ Monitoring & Analytics Module initialisiert
2025-06-16 08:18:54 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - 📊 MASSIVE Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:21:31 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - ✅ Monitoring & Analytics Module initialisiert
2025-06-16 08:21:31 - [monitoring_analytics] monitoring_analytics - [INFO] INFO - 📊 MASSIVE Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)

3
backend/logs/permissions/permissions.log
View File

@@ -235,3 +235,6 @@ WHERE users.role = ?]
2025-06-16 08:08:33 - [permissions] permissions - [INFO] INFO - UserPermission für Admin-Benutzer 1 aktualisiert
2025-06-16 08:08:47 - [permissions] permissions - [INFO] INFO - UserPermission für Admin-Benutzer 1 aktualisiert
2025-06-16 08:08:48 - [permissions] permissions - [INFO] INFO - UserPermission für Admin-Benutzer 1 aktualisiert
2025-06-16 08:18:50 - [permissions] permissions - [INFO] INFO - Admin-Berechtigungen korrigiert: 0 erstellt, 0 aktualisiert
2025-06-16 08:18:54 - [permissions] permissions - [INFO] INFO - Admin-Berechtigungen korrigiert: 0 erstellt, 0 aktualisiert
2025-06-16 08:21:31 - [permissions] permissions - [INFO] INFO - Admin-Berechtigungen korrigiert: 0 erstellt, 0 aktualisiert

109
backend/logs/scheduler/scheduler.log
View File

@@ -1952,3 +1952,112 @@
2025-06-16 08:13:15 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:13:23 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f5a26d0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:13:23 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b53b4d0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:13:45 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:13:45 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:13:53 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f5ca0b0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:13:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b53b200> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:14:15 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:14:16 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:14:23 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f608c90> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:14:24 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b59c6e0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:14:45 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:14:46 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:14:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f5a3af0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:14:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b539c70> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:15:16 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:15:16 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:15:24 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f5a1710> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:15:24 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b53ab70> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:15:46 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:15:46 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:15:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f2060b0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:15:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b53b890> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:16:16 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:16:17 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:16:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f632430> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:16:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0bdfb200> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:16:47 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:16:47 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:16:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f5ca270> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:16:56 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b59ce60> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:17:17 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:17:18 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:17:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f6092b0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:17:26 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b53b110> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:17:47 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:17:48 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:17:56 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f5a1390> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:17:57 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b59c140> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:18:18 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:18:19 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:18:26 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x2495f64b930> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:18:27 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x17b0b59ee40> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:18:48 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-16 08:18:50 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
2025-06-16 08:18:50 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
2025-06-16 08:18:50 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:18:51 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:18:51.164458', '192.168.0.100', None, None, None, 'system', None, None, 243, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:18:51 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x24fe1d7f380> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:18:52 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-16 08:18:54 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
2025-06-16 08:18:54 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
2025-06-16 08:18:54 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:18:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:18:54.909040', '192.168.0.100', None, None, None, 'system', None, None, 329, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:18:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x293bd2b7230> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:19:21 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:19:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:19:21.421321', '192.168.0.100', None, None, None, 'system', None, None, 236, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:19:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x24fe2034d60> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:19:24 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:19:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:19:25.115195', '192.168.0.100', None, None, None, 'system', None, None, 184, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:19:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x293bd791ba0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:19:51 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:19:51 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:19:51.648696', '192.168.0.100', None, None, None, 'system', None, None, 206, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:19:51 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x24fe21256a0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:19:55 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:19:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:19:55.286634', '192.168.0.100', None, None, None, 'system', None, None, 155, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:19:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x293bd64e9c0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:20:21 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:20:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:21.854644', '192.168.0.100', None, None, None, 'system', None, None, 185, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x24fe20db950> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:20:25 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:20:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:25.471655', '192.168.0.100', None, None, None, 'system', None, None, 161, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x293bd746950> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:20:51 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:20:52 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:52.066894', '192.168.0.100', None, None, None, 'system', None, None, 187, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:52 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x24fe218d9b0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:20:55 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: Gastauftrag: Till Tomczaktet
2025-06-16 08:20:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Steckdose für Drucker 1: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (sqlite3.IntegrityError) NOT NULL constraint failed: plug_status_logs.printer_id
[SQL: INSERT INTO plug_status_logs (printer_id, status, timestamp, ip_address, power_consumption, voltage, current, source, user_id, notes, response_time_ms, error_message, firmware_version) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: (None, 'on', '2025-06-16 08:20:55.711965', '192.168.0.100', None, None, None, 'system', None, None, 221, None, None)]
(Background on this error at: https://sqlalche.me/e/20/gkpj) (Background on this error at: https://sqlalche.me/e/20/7s2a)
2025-06-16 08:20:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler bei Überprüfung der Jobs: Instance <Job at 0x293be8820b0> is not bound to a Session; attribute refresh operation cannot proceed (Background on this error at: https://sqlalche.me/e/20/bhk3)
2025-06-16 08:21:30 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-16 08:21:31 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
2025-06-16 08:21:31 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet

9
backend/logs/security_suite/security_suite.log
View File

@@ -845,3 +845,12 @@
2025-06-16 08:00:34 - [security_suite] security_suite - [INFO] INFO - ✅ Security Suite Module initialisiert
2025-06-16 08:00:34 - [security_suite] security_suite - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:00:36 - [security_suite] security_suite - [INFO] INFO - 🔒 Security Suite initialisiert
2025-06-16 08:18:48 - [security_suite] security_suite - [INFO] INFO - ✅ Security Suite Module initialisiert
2025-06-16 08:18:48 - [security_suite] security_suite - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:18:50 - [security_suite] security_suite - [INFO] INFO - 🔒 Security Suite initialisiert
2025-06-16 08:18:52 - [security_suite] security_suite - [INFO] INFO - ✅ Security Suite Module initialisiert
2025-06-16 08:18:52 - [security_suite] security_suite - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:18:54 - [security_suite] security_suite - [INFO] INFO - 🔒 Security Suite initialisiert
2025-06-16 08:21:30 - [security_suite] security_suite - [INFO] INFO - ✅ Security Suite Module initialisiert
2025-06-16 08:21:30 - [security_suite] security_suite - [INFO] INFO - 📊 Massive Konsolidierung: 3 Dateien → 1 Datei (67% Reduktion)
2025-06-16 08:21:31 - [security_suite] security_suite - [INFO] INFO - 🔒 Security Suite initialisiert

27
backend/logs/startup/startup.log
View File

@@ -2202,3 +2202,30 @@
2025-06-16 08:00:36 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
2025-06-16 08:00:36 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
2025-06-16 08:00:36 - [startup] startup - [INFO] INFO - ==================================================
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - ==================================================
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - [START] MYP Platform Backend wird gestartet...
2025-06-16 08:18:50 - [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-16 08:18:50 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-16T08:18:50.477515
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
2025-06-16 08:18:50 - [startup] startup - [INFO] INFO - ==================================================
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - ==================================================
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - [START] MYP Platform Backend wird gestartet...
2025-06-16 08:18:54 - [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-16 08:18:54 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-16T08:18:54.093388
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
2025-06-16 08:18:54 - [startup] startup - [INFO] INFO - ==================================================
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - ==================================================
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - [START] MYP Platform Backend wird gestartet...
2025-06-16 08:21:31 - [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-16 08:21:31 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-16T08:21:31.485229
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
2025-06-16 08:21:31 - [startup] startup - [INFO] INFO - ==================================================

161
backend/logs/tapo_controller/tapo_controller.log
View File

@@ -2712,3 +2712,164 @@
2025-06-16 08:13:47 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99480>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:13:50 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19BF00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:13:51 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99590>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:13:53 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19A9C0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:13:53 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:13:54 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD989E0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:13:54 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:14:17 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19AAD0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:18 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98AF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:20 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19ACF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:21 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B6841EE00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:23 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F589AE0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:23 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:14:24 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD9B240>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:24 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:14:47 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F589260>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:48 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98E20>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:51 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19ACF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:51 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98C00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:54 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19B020>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:54 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:14:54 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98050>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:14:54 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:15:18 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19A8B0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:18 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B6841EE00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:21 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19BF00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:21 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD9A030>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:24 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F199AE0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:24 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:15:24 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99BF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:24 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:15:48 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F199D00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:49 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B6841F680>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:51 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19A470>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:52 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD9A8B0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:54 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F589AE0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:54 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:15:55 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99BF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:15:55 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:16:19 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F5898C0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:19 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B6841F680>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:22 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F588490>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:22 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD9A030>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:25 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19A470>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:25 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:16:25 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99590>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:25 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:16:49 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19A690>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:49 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99260>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:52 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F199AE0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:53 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99E10>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:55 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19BF00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:55 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:16:56 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98380>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:16:56 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:17:19 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19AF10>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:20 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B6841EE00>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:22 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19B020>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:23 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD9A7A0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:25 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19ACF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:25 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:17:26 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98D10>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:26 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:17:49 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F588490>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:50 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD99150>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:52 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F588160>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:54 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD9B130>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:56 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F589040>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:56 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:17:57 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD988D0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:17:57 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:18:20 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19ACF0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:18:21 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 1/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD98490>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:18:23 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19AAD0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:18:24 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 2/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B6841F680>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:18:26 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000002495F19AF10>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:18:26 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:18:27 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Versuch 3/3 fehlgeschlagen beim einschalten von 192.168.0.100: HTTPConnectionPool(host='192.168.0.100', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000017B0BD988D0>, 'Connection to 192.168.0.100 timed out. (connect timeout=2)'))
2025-06-16 08:18:27 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Alle 3 Versuche fehlgeschlagen beim einschalten der Tapo-Steckdose 192.168.0.100
2025-06-16 08:18:48 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert
2025-06-16 08:18:51 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:18:52 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert
2025-06-16 08:18:54 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:19:21 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:19:25 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100: Status = off
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.100: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.100 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.101: Status = off
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.101: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.101 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.102: Status = off
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.102: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.102 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.103: Status = off
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.103: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:31 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.103 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:33 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x00000293BD64E140>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
2025-06-16 08:19:33 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.104 fehlgeschlagen: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x00000293BD64E140>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
2025-06-16 08:19:34 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.106: Status = off
2025-06-16 08:19:34 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.106: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:34 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.106 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100: Status = off
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.100: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.100 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.101: Status = off
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.101: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.101 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.102: Status = off
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.102: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.102 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.103: Status = off
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.103: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:43 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.103 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:46 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x00000293BD4E1150>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
2025-06-16 08:19:46 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.104 fehlgeschlagen: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x00000293BD4E1150>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
2025-06-16 08:19:46 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.106: Status = off
2025-06-16 08:19:46 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.106: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:46 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.106 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:51 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:19:52 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.100 erfolgreich: unbekannt
2025-06-16 08:19:53 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100: Status = off
2025-06-16 08:19:53 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.100: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:53 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.100 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:55 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:19:55 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.101 erfolgreich: unbekannt
2025-06-16 08:19:55 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.101: Status = off
2025-06-16 08:19:55 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.101: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:55 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.101 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:57 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.102 erfolgreich: unbekannt
2025-06-16 08:19:57 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.102: Status = off
2025-06-16 08:19:57 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.102: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:19:57 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.102 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:00 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.103 erfolgreich: unbekannt
2025-06-16 08:20:00 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.103: Status = off
2025-06-16 08:20:00 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.103: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:00 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.103 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:11 - [tapo_controller] tapo_controller - [INFO] INFO - tapo-verbindung zu 192.168.0.106 erfolgreich: unbekannt
2025-06-16 08:20:11 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.106: Status = off
2025-06-16 08:20:11 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.106: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:11 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.106 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:18 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100: Status = off
2025-06-16 08:20:18 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.100: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:18 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.100 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.101: Status = off
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.101: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.101 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.102: Status = off
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.102: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.102 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.103: Status = off
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.103: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:19 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.103 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:21 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x00000293BD4E1150>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
2025-06-16 08:20:21 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.104 fehlgeschlagen: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x00000293BD4E1150>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
2025-06-16 08:20:21 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.106: Status = off
2025-06-16 08:20:21 - [tapo_controller] tapo_controller - [WARNING] WARNING - ⚠️ Fehler bei Tapo-Steckdosen-Status-Check 192.168.0.106: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:21 - [tapo_controller] tapo_controller - [ERROR] ERROR - ❌ Status-Check für 192.168.0.106 fehlgeschlagen: TapoController._collect_device_info() got an unexpected keyword argument 'debug'
2025-06-16 08:20:21 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:20:25 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:20:32 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:20:52 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:20:55 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ Tapo-Steckdose 192.168.0.100 erfolgreich eingeschaltet
2025-06-16 08:21:30 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert

3
backend/logs/tapo_status_manager/tapo_status_manager.log
View File

@@ -248,3 +248,6 @@
2025-06-16 07:54:00 - [tapo_status_manager] tapo_status_manager - [INFO] INFO - TapoStatusManager mit Session-Caching initialisiert
2025-06-16 07:54:03 - [tapo_status_manager] tapo_status_manager - [INFO] INFO - TapoStatusManager mit Session-Caching initialisiert
2025-06-16 08:00:34 - [tapo_status_manager] tapo_status_manager - [INFO] INFO - TapoStatusManager mit Session-Caching initialisiert
2025-06-16 08:18:48 - [tapo_status_manager] tapo_status_manager - [INFO] INFO - TapoStatusManager mit Session-Caching initialisiert
2025-06-16 08:18:52 - [tapo_status_manager] tapo_status_manager - [INFO] INFO - TapoStatusManager mit Session-Caching initialisiert
2025-06-16 08:21:30 - [tapo_status_manager] tapo_status_manager - [INFO] INFO - TapoStatusManager mit Session-Caching initialisiert

6
backend/logs/utilities_collection/utilities_collection.log
View File

@@ -733,3 +733,9 @@
2025-06-16 07:54:03 - [utilities_collection] utilities_collection - [INFO] INFO - 🚨 ALLERLETZTE MEGA-Konsolidierung: 12+ Dateien → 1 Datei (90%+ Reduktion)
2025-06-16 08:00:34 - [utilities_collection] utilities_collection - [INFO] INFO - ✅ Utilities Collection initialisiert
2025-06-16 08:00:34 - [utilities_collection] utilities_collection - [INFO] INFO - 🚨 ALLERLETZTE MEGA-Konsolidierung: 12+ Dateien → 1 Datei (90%+ Reduktion)
2025-06-16 08:18:48 - [utilities_collection] utilities_collection - [INFO] INFO - ✅ Utilities Collection initialisiert
2025-06-16 08:18:48 - [utilities_collection] utilities_collection - [INFO] INFO - 🚨 ALLERLETZTE MEGA-Konsolidierung: 12+ Dateien → 1 Datei (90%+ Reduktion)
2025-06-16 08:18:52 - [utilities_collection] utilities_collection - [INFO] INFO - ✅ Utilities Collection initialisiert
2025-06-16 08:18:52 - [utilities_collection] utilities_collection - [INFO] INFO - 🚨 ALLERLETZTE MEGA-Konsolidierung: 12+ Dateien → 1 Datei (90%+ Reduktion)
2025-06-16 08:21:29 - [utilities_collection] utilities_collection - [INFO] INFO - ✅ Utilities Collection initialisiert
2025-06-16 08:21:29 - [utilities_collection] utilities_collection - [INFO] INFO - 🚨 ALLERLETZTE MEGA-Konsolidierung: 12+ Dateien → 1 Datei (90%+ Reduktion)

6
backend/logs/windows_fixes/windows_fixes.log
View File

@@ -221,3 +221,9 @@
2025-06-16 07:54:03 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
2025-06-16 08:00:34 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
2025-06-16 08:00:34 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
2025-06-16 08:18:48 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
2025-06-16 08:18:48 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
2025-06-16 08:18:52 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
2025-06-16 08:18:52 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
2025-06-16 08:21:29 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
2025-06-16 08:21:29 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet