[Bug]: 3.1.0 authenticates successfully but always returns "No houses found / No stations found / No devices found"

[Reachushere]

Client version

Unknown — running eufy-security-ws add-on 3.1.0

Node version

Unknown — Home Assistant add-on container

Operating System type

Linux

Operating system version

Home Assistant OS 18.1

Describe the bug

After configuring the Home Assistant eufy-security-ws add-on with the owner account credentials, authentication succeeds.

The add-on completes email 2FA, persists the Mega session, and establishes the push notification connection.

Immediately afterwards it reports:

HTTPApi.refreshHouseData] No houses found.
HTTPApi.refreshStationData] No stations found.
HTTPApi.refreshDeviceData] No devices found.

No devices are exposed to Home Assistant.

I tested both:

• Owner account
• Shared Admin account

Both produce identical results.

The owner account definitely owns the T8222 doorbell and the shared account can see the same device in the official Eufy Security app.

To reproduce

1. Install eufy-security-ws 3.1.0.
2. Configure the add-on with a valid Eufy owner account.
3. Complete any required email 2FA verification.
4. Allow the add-on to authenticate.
5. Observe the logs.

Expected:

Houses, stations and devices are discovered.

Actual:

MegaHTTPApi.login ok
MegaTransition.loginMega] v6 login: success, mega session persisted

HTTPApi.refreshHouseData] No houses found.
HTTPApi.refreshStationData] No stations found.
HTTPApi.refreshDeviceData] No devices found.

Push notification connection successfully established

The same result occurs with both the owner account and a shared Admin account.

Screenshots & Logfiles

Relevant log

MegaHTTPApi.login needs 2FA (token stored for verify_code)

MegaHTTPApi.login ok

MegaTransition.loginMega] v6 login: success, mega session persisted

HTTPApi.refreshHouseData] No houses found.
HTTPApi.refreshStationData] No stations found.
HTTPApi.refreshDeviceData] No devices found.

MegaTransition.registerMegaPushToken] v6 push: FCM token registered on the eufy_mega backend

Push notification connection successfully established

This demonstrates that:

• Authentication succeeds.
• Email 2FA succeeds.
• Session persistence succeeds.
• Push registration succeeds.
• Device discovery returns an empty inventory.

Additional context

Additional troubleshooting already performed:

• Tested owner account and shared Admin account
• Successfully completed CAPTCHA and email 2FA
• Verified the device is visible in the official Eufy Security app
• Changed add-on port from 3000 to 3001 to resolve a previous port conflict
• Removed and recreated authentication sessions
• Authentication, session persistence, and push registration all succeed, but device discovery always returns an empty inventory
  The T8222 doorbell is visible and fully functional in the official Eufy Security app.

I tested both:

• The owner account
• A shared Admin account

Both accounts authenticate successfully and produce the same result:

• No houses found
• No stations found
• No devices found

This appears to be a discovery/inventory issue rather than an authentication issue.