maximunited / imou_life / 25137776288

90%

push

github

feat: Improve API server selector UI with auto-populated URL field (#12)

* feat: improve API server selector UI with auto-populated URL field

Enhance the config flow login step with better server selection UX:

**UI Improvements:**
- Renamed "oregon" to "virginia" (geo-located to Virginia Beach, USA not Oregon)
- Dropdown now shows proper capitalized names with countries:
  - "Global (openapi.easy4ip.com)"
  - "Frankfurt (Germany)"
  - "Singapore"
  - "Virginia (USA)"
  - "China"
  - "Custom"
- API Base URL field now auto-populates with the selected server's URL
- Clearer field labels: "API Server" and "API Base URL"
- Improved descriptions explaining when custom URL is needed

**Technical Changes:**
- Config flow displays selected server URL in the API Base URL field
- When user selects a predefined server, the URL field shows the endpoint
- When user selects "Custom", the URL field is empty for manual entry
- Updated all 8 translation files with new labels and descriptions
- Renamed API_SERVER_OPTIONS key "oregon" -> "virginia" in const.py

**Geo-location Verification:**
- 8.219.71.80 (Global/Singapore) -> Singapore
- 47.245.141.21 (Frankfurt) -> Frankfurt am Main, Germany
- 47.90.226.98 (Virginia) -> Virginia Beach, Virginia, USA
- openapi-or.easy4ip.com resolves to us-east-1 (not Oregon!)

**Tests:**
- All 229 unit tests passing
- Updated test_all_server_options to use "virginia" instead of "oregon"
- Pre-commit hooks passing

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* fix: handle rate limit errors gracefully during device discovery

When users hit API rate limits during the initial config flow discovery step,
the integration now:
- Detects OP1013 rate limit errors specifically
- Shows a helpful error message explaining the situation
- Automatically redirects to manual device entry instead of looping
- Prevents repeated API calls that would continue hitting the rate limit

**Problem:**
Users experiencing rate limits during disc... (continued)

0 of 14 new or added lines in 1 file covered. (0.0%)

917 of 1285 relevant lines covered (71.36%)

2.14 hits per line