Reolink integration fails on Home Assistant Core 2025.10.4 (token not reused after login)

Configuration
1

That’s a very detailed and well-structured report! I’ll format it into a cohesive post suitable for the Home Assistant (HA) forum, using the typical structure: a clear title, problem description, detailed environment and steps, and logs.

Here is the formatted question:

Reolink Home Hub Pro (HTTP/Port 80) Login Successful but Token Immediately Lost/Empty

Problem Description

The built-in Reolink integration in Home Assistant is failing to maintain a valid session token when connecting to a Reolink Home Hub Pro over HTTP (port 80).

The initial login via port 80 is successful, and the hub returns a valid token. However, the very next API call from the integration immediately sends an empty token (' ') in the request parameters, causing the connection attempt to fail repeatedly until Home Assistant is rebooted.

This issue began after updating from HA Core 2025.9.3 to 2025.9.4 and persists in 2025.10.4.

Environment

Component Version / Info
Home Assistant Core 2025.10.4
Supervisor 2025.10.2
Installation type Home Assistant OS on Intel NUC
Integration Reolink (built-in)
Device Reolink Home Hub Pro
Firmware v6.18.123_24091100
Connection LAN, HTTP port 80 enabled, HTTPS disabled
Account used Local admin account (also tested with a new ha user)

Expected Behavior

The Reolink integration should:

  1. Connect over HTTP (port 80).
  2. Successfully log in and obtain a valid token (829cd239c0a23e9).
  3. Use this valid token for all subsequent API calls (e.g., GetChannelstatus, GetDevInfo).

Actual Behavior

  • Integration setup eventually fails with a generic “Unexpected error” after numerous retries.
  • The setup log immediately attempts HTTPS (port 443), fails, and then successfully logs in over HTTP (port 80).
  • The next request immediately sends an empty token ({'token': ''}).
  • This cycle of successful login followed by a failed request with an empty token repeats endlessly.

Steps Taken & Troubleshooting

  • Verified Reolink Home Hub accessible via browser at http://192.168.10.32.
  • Confirmed HTTP enabled and HTTPS disabled on the Reolink device.
  • Created a new local “ha” user with a simple password—no change.
  • Removed .storage/core.config_entries and restarted HA to force a clean setup attempt.
  • A curl test confirms direct HTTP login works correctly and returns a token.
  • The same behavior occurs whether I manually specify port 80 or 443 during setup.
  • Integration worked without issue on HA Core 2025.9.3.

Relevant Debug Excerpt (Trimmed)

2025-10-30 16:33:00.417 DEBUG (MainThread) [reolink_aio.api] Host 192.168.10.32:443, trying to login with user admin...
2025-10-30 16:33:00.419 DEBUG (MainThread) [reolink_aio.api] Host 192.168.10.32:443: connection error: Cannot connect to host 192.168.10.32:443 ssl:default [Connect call failed ('192.168.10.32', 443)]
2025-10-30 16:33:00.423 DEBUG (MainThread) [reolink_aio.api] Host 192.168.10.32:80, trying to login with user admin...
2025-10-30 16:33:00.510 DEBUG (MainThread) [reolink_aio.api] Got login response from 192.168.10.32:80: [{'cmd': 'Login', 'code': 0, 'value': {'Token': {'leaseTime': 3600, 'name': '829cd239c0a23e9'}}}]
2025-10-30 16:33:00.510 DEBUG (MainThread) [reolink_aio.api] Logged in at host 192.168.10.32:80. Leasetime 30-10-2025 17:33, token 829cd239c0a23e9
2025-10-30 16:33:00.510 DEBUG (MainThread) [reolink_aio.api] Unknown/192.168.10.32:80::send() HTTP Request params =
{'token': ''}

Is anyone else experiencing this token loss issue with the Reolink integration on version 2025.9.4 or later when using a device that prefers or requires HTTP (port 80)?