connectedhomeip

Matter (formerly Project CHIP) creates more connections between more objects, simplifying development for manufacturers and increasing compatibility for consumers, guided by the Connectivity Standards Alliance.

Robotics & IoT

Explore on GitHub Read Hacker News discussions

18Distinct people

25Mentions

0Explicit recommenders

9KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year25 dated mentions

Observed mentions: 2020-07-01 20:01:15 UTC to 2024-08-06 16:14:16 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	4	2	2
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	2	0	2
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	12	2	10
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	6	0	6
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	0	1

What Hacker News says

1 sources

jauntywundrkind·Aug 6, 2024

There's a lot of Matter Cast that feels fairly reasonable as a protocol, but the flaws here are so wildly absurd. I want this effort to sink so bad. As a protocol I vastly prefer Open Screen Protocol, which was begat to support W3c Secondary Screen wg's Presentstion API. https://w3c.github.io/openscreenprotocol/ https://www.w3.org/TR/presentation-api/ Matter Cast has what to me are grevious limitations: 1. Connecting clients can only talk to existing Endpoints running on the target device. If I use Tidal for example, the smart speaker or smart TV needs to already be setup with that app, and needs to be willing to let a background service run & register itself with the platform. https://github.com/project-chip/connectedhomeip/blob/master/... 2. Only native apps are supported. There's no protocol to say open a webpage & control that. As a s

Read the rest

olo dev I can throw together a universal Presentation API multi-display experience in hours. Shipping even one native app would take many weekends & lots of legal hoops. Getting on the apps store for even 50% of TV's or speakers seems daunting beyond imagining. 3. No support for multi-party sessions. Only one user can interact at a time. 4. No support for the Web's Presentation API. Since it's not based around urls & web pages, it would require lots of additional work to make it support the standard web pages have to spawn a remote display. By compare, Open Screen Protocol lets any target device open any web page, which is very similar to how Chromecast development works today (and how DIAL worked before). Whether the target device is Android, Apple, WebOS, Windows, Tizen, or other, the expectation that I could Open Screen Protocol cast to it remains the same. Where-as Matter Cast requires a native app on the device & the app has to be installed & potentially even greenlit by the target device platform itself. OpenScreenProtocol really looks to have it all, & the model is so much more universal. Really wish we saw some device makers pushing for it these days.

In Moments in Chromecast's history