[puddly]

The first Hello() is sent unsolicited by embedded Ziggurat and isn't an immediate firmware reset.

We should maybe include a reset reason in the Hello() message.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (fa1edc5) to head (7ca5e41).

Additional details and impacted files

@@            Coverage Diff            @@
##               dev       #12   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines         1213      1217    +4     
=========================================
+ Hits          1213      1217    +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

🟡 Changes recommended

A WebSocket Hello received while the initial Reset request is pending can be mistaken for startup traffic, silently ignoring a real reset and leaving the request unresolved.

1 open issue

• WebSocket probe silently drops a reset Hello · New

What changed in this PR

This PR distinguishes embedded Ziggurat’s initial startup Hello from later firmware-reset notifications, preventing a false disconnect during stack startup.

Changes:

• Track whether the API has received a frame and ignore a session-opening Hello.
• Add startup coverage and update the reset-notification test to establish prior traffic.

File	Description
zigpy_ziggurat/​zigbee/​api.py	Track received frames to distinguish startup announcements from resets.
tests/​test_api.py	Test startup Hello handling and subsequent reset detection.

_{Review effort: Balanced}