connectedhomeip VS homebridge-raspbian-image

ESP32s aren't really ‘lower level’ in the sense that anyone is likely to write assembly code for them (compared to, say, 8051 or PIC), other than maybe some driver author at Espressif. The big win from using RISC-V, other than name recognition, is mainstream compiler support (which is nothing to sneeze at, especially when it's largely funded by someone else).

When I worked on Matter¹, the Xtensa and RISC-V versions were basically fungible from the software point of view. (And really, so were other vendors' various ARMs.) We did find that Bloaty McBloatface² didn't support Xtensa, so I had to write an alternative.

¹ https://github.com/project-chip/connectedhomeip/

² https://github.com/google/bloaty

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

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

I'm trying to build https://github.com/project-chip/connectedhomeip on MacOS but I keep getting the following error:

"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

I checked out v1.0.0 of the Matter repo and ran

I was actually asking for other peoples experience building the matter examples and if there was any other place I could reach out to get answers to my questions, hence why I did not include any specific information.

Which is different from Ring's Doorbell, but the fact still remains, Ring doesn't have a smart watch app, nor is it natively HomeKit compatible. However if you set up Homebridge for it, you can make it so.

As for the original issue - you may have downloaded a corrupt image - if you really want to use their image (rather than build the OS then install) download it from here but check the sha256 of the downloaded file before using Etcher. I use QuickHash on my Mac but other programs exist for all platforms.

If you wanna make a pi with it, their official documentation is easy to follow. You can even use their easy ready to go image!

Here is for raspberry pi only: https://github.com/homebridge/homebridge-raspbian-image/wiki/Getting-Started

Pick up a supported Raspberry Pi model.

Spread the word: HOOBS is a waste of time and money, and is a drag on developers' precious time. Now that Config-UI-X is included and the official Homebridge image is so easy to flash and install, there's very little reason for HOOBS to exist.

link to image https://github.com/homebridge/homebridge-raspbian-image/releases/latest