| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
An H200 or H500 hub without paired children answers getChildDeviceList and getChildDeviceComponentList with only start_index and sum. The pagination helper then called next() on an empty iterator, which inside a coroutine surfaces as "RuntimeError: coroutine raised StopIteration" and aborts setup. Return early when no list is present, and read the child lists with a default where the code indexed them directly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## master #1785 +/- ##
=======================================
Coverage 93.41% 93.41%
=======================================
Files 159 159
Lines 10113 10115 +2
Branches 1043 1044 +1
=======================================
+ Hits 9447 9449 +2
Misses 472 472
Partials 194 194 ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
An H200 (or H500) hub without paired children answers
getChildDeviceList / getChildDeviceComponentList with only
start_index and sum, no list. _handle_response_lists then calls
next() on an empty iterator, which inside a coroutine becomes
RuntimeError: coroutine raised StopIteration and aborts setup in
Home Assistant.
with a default instead of indexing them, so the list-less response is
treated as "no children" (smart and smartcam).
This is the change proposed in the issue by a user who confirmed it on an
empty hub; with children present the behaviour is unchanged.
Tests:
StopIteration from the issue on master.
omitted and asserts no error is logged; on master all 9 hub fixtures fail.
Fixes #1728
Related: #1773 (same traceback on an H500)
🤖 Generated with Claude Code