-
-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Description
Version of the custom_component
3.0.10-beta.11
Configuration
Add your logs here.
Describe the bug
Entities no longer being provided by integration. This occurred after an update from HA 2025.12.0 to 2025.12.3. Restoring backup of 2025.12.0 did not fix the issue so I'm not confident this is the issue. I've tried removing and re-adding the devices but it only adds the configuration after the wizard and does not add any devices. I do see some errors in the logs after turning on debug and disabling/enabling the device.
Debug log
2025-12-13 11:05:07.589 WARNING (MainThread) [custom_components.uniled.lib.net.device] SP530E L: Response Header Error: read 0, expected 13
2025-12-13 11:05:07.589 ERROR (MainThread) [custom_components.uniled.coordinator] Error fetching SP530E L data: Device update failed
2025-12-13 11:05:07.589 DEBUG (MainThread) [custom_components.uniled.coordinator] Finished fetching SP530E L data in 5.007 seconds (success: False)
2025-12-13 11:05:15.814 DEBUG (MainThread) [custom_components.uniled.lib.net.device] SP530E R: Update!
2025-12-13 11:05:15.815 DEBUG (MainThread) [custom_components.uniled.lib.net.device] SP530E R => 53505445434800020000000000 (13)
2025-12-13 11:05:15.815 DEBUG (MainThread) [custom_components.uniled.lib.net.device] SP530E R: Set available: _send_bytes was successful
2025-12-13 11:05:15.924 DEBUG (MainThread) [custom_components.uniled.lib.net.device] SP530E R: socket error (10.0.0.216): [Errno 104] Connection reset by peer
2025-12-13 11:05:21.040 WARNING (MainThread) [custom_components.uniled.lib.net.device] SP530E R: Response Header Error: read 0, expected 13
2025-12-13 11:05:21.040 ERROR (MainThread) [custom_components.uniled.coordinator] Error fetching SP530E R data: Device update failed
2025-12-13 11:05:21.040 DEBUG (MainThread) [custom_components.uniled.coordinator] Finished fetching SP530E R data in 5.226 seconds (success: False)
Metadata
Metadata
Assignees
Labels
No labels