suggested further clarification of matter/thread relationship

[dduff617]

Feedback

existing text has a section called "What does Thread have to do with Matter?" and a subsection called "THREAD DEVICES DON’T NECESSARILY SUPPORT MATTER", it seems like something conspicuously absent is a corresponding subsection called "MATTER DEVICES DON’T NECESSARILY USE THREAD". it would be possible to read the current text and come away with the opposite impression.
there are many devices on the market today currently that support matter-over-WiFi and matter-over-ethernet. matter is an application-level protocol that can work over multiple different transport-layer protocols. thread is one such transport protocol (admittedly one with some unique advantages and relevance to home-automation applications).
i don't want to be pedantic, however i think this is a common point of confusion, and that's why i think it is important to clarify rather than compound the confusion.

URL

https://www.home-assistant.io/integrations/matter/

Version

2024.4.3

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/matter, mind taking a look at this feedback as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

• @home-assistant close Closes the feedback.
• @home-assistant rename Awesome new title Renames the feedback.
• @home-assistant reopen Reopen the feedback.
• @home-assistant unassign matter Removes the current integration label and assignees on the feedback, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

[marcelveldt]

I think that is exactly what we already do so I don't really get your point but I'll leave it to @c0ffeeca7 for a final view.

[dduff617]

i concede that the point is covered in the preceding text.
i suspect however that if a reader goes to the "what does thread have to do with matter?" section for clarification, many will end up thinking that to use matter, it requires thread. and subsequently having thread requires that you have a thread border router, etc...
that section does say "[thread is] a suitable transport protocol option for Matter" (emphasis mine), which again i concede is exactly correct. i just don't think that's the natural "take-away" understanding of this overall section as written.