connectedhomeip VS homebridge-google-nest-sdm

Clone the Matter repository: git clone https://github.com/project-chip/connectedhomeip.git Navigate to the repository directory: cd connectedhomeip Update the submodules: git submodule update --init

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.

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. 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.

They do have example Matter projects for the ESP32-C3/S3. I assume it's over WiFi and not thread.

https://github.com/project-chip/connectedhomeip/tree/master/...

IoT is a big space right now if you look at the companies who commit to https://github.com/project-chip/connectedhomeip. They come together at the CSA Member Meeting.

I followed this doc: https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/esp32/setup_idf_chip.md

"Securing name resolution in the IoT: DNS over CoAP" https://news.ycombinator.com/item?id=32186286

From https://github.com/project-chip/connectedhomeip#architecture... :

> Matter aims to build a universal IPv6-based communication protocol for smart home devices. The protocol defines the application layer that will be deployed on devices and the different link layers to help maintain interoperability. The following diagram illustrates the normal operational mode of the stack:

> [...] It is built with market-proven technologies using Internet Protocol (IP) and is compatible with Thread and Wi-Fi network transports.

> Matter was developed by a Working Group within the Connectivity Standards Alliance (Alliance). This Working Group develops and promotes the adoption of the Matter standard, a royalty-free connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet. The vision that led major industry players to come together to build Matter is that smart connectivity should be simple, reliable, and interoperable.

> [...] The code examples show simple interactions, and are supported on multiple transports -- Wi-Fi and Thread -- starting with resource-constrained (i.e., memory, processing) silicon platforms to help ensure Matter’s scalability.

Is there already a good (security) comparison of e.g. http basic auth, x10, ZigBee, mqtt, matter?

Bloaty is a nice tool.

When I worked on Matter a couple years ago, we had the problem that its backend http://www.capstone-engine.org/ did not support Xtensa, and produced some Python tools that could take output from bloaty or similar data from readelf or elftools, and produce several kinds of report.

https://github.com/project-chip/connectedhomeip/blob/master/...

My two cents from someone who has dealt with product name changes. Most recently I worked on the Chip repo which is now known as Matter. There are numerous references in the repo to chip despite the name change. See https://github.com/project-chip/connectedhomeip

Not sure if I'm asking in the right place so I apologise ahead. I'm trying to get one of the example projects from Matter onto my esp32 (ESP-WROOM-32) using espresiff. I am doing this on my raspberry pi btw. The problem I'm having now is that it get's stuck when I'm building (idf.py build command). It's always around 800/1135 and it doesn't go past it. The one where it is currently stuck is: [804/1135] Building C object esp-idf/bt/CMakeFiles/__idf_bt.dir/host/nimble/nimble/nimble/host/src/ble_gatts_lcl.c.obj.

I maintain a Homebridge (community built system to bridge IoT devices to Apple HomeKit) plugin for Google Nest devices. The newer Nest cams use WebRTC for video streaming. This makes viewing the cameras in Apple Home a bit complex, as the bridge must setup and connect to a WebRTC stream, transcode it, and then send it out to your iPhone etc. as an RTSP stream.

https://github.com/potmat/homebridge-google-nest-sdm

Since this is for home automation the system runs on all kinds of weird devices, from RPi's to NAS's to old laptops etc. When I tried to use anything requiring platform specific binaries it was a complete mess, most of the time things would not build.

The problem may not be insurmountable if you're being paid, but since this is just done in my spare time it's not something I wanted to deal with.

What plugin are you using? I can report that I was able to use https://github.com/potmat/homebridge-google-nest-sdm instead of https://github.com/chrisjshull/homebridge-nest because I think google is deprecating the nest stuff in favor of google home.

I actually tried this plugin and it worked pretty well: https://github.com/potmat/homebridge-google-nest-sdm

The new Google Smart Device Management API is out and actually has its own camera plugin!