[GreenGrassBlueOcean]

Follow-up to #777 / #781.

Problem

myhome.send_message passed every frame to handler.send(), so a status or dimension request such as *#1*52*5## went out as a command. In the #777 reporter's first trace, the F454 with a Legrand 067226 at 52 answered that request with a WHERE 0 reply and a NACK. OWNd then:

1. logged Could not send message … Retrying (1),
2. sent the request a second time, and
3. logged No more retries at ERROR.

The integration's own startup queries from the motion sensor (*#1*52*5##, *#1*52*7##) were never affected. They already go out as status requests, and the reporter's retest shows them logged as Gateway rejected status request … (NACK, 0 response(s)) at DEBUG.

Change

Status and dimension requests from send_message now go through send_status_request(), the same path the integration's own queries use:

• same queue, status priority tier
• a NACK is final and logged at DEBUG, the request is not repeated

Commands and dimension writes (*#1*52*#1*150*5##) still go through send().

Testing

• tests/test_send_message_status_requests.py (new):
  • status requests and the three dimension requests from the [2.0.0b16] Configured light removed on reload after motion sensor discovery at the same WHO 1 address (F454 / Legrand 067226) #777 capture are sent with send_status_request
  • commands and dimension writes are sent with send
• Full suite: 4408 passed.
• The new tests and tests/test_f461_live_plant.py also pass against the released OWNd 2.0.0b11 pin.
• ruff, verify_ha_standards.py and sync_documentation.py --check are clean.
• OWNd's own test_command_session_send_immediate_status_nack_is_final covers the "NACKed status request is final, logged at DEBUG" behaviour this relies on.

🤖 Generated with Claude Code

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!