connectedhomeip VS ATC_MiThermometer

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 checked out v1.0.0 of the Matter repo and ran

I'm trying to build basic examples (light device for ESP32, Python controller for Raspberry Pi) following the guides on the official repository (https://github.com/project-chip/connectedhomeip). After solving some build errors, I managed to flash the ESP32 and run the controller on the RPi. However, I couldn't manage to commission the ESP32 from the RPi, because I kept getting a weird "mDNS: Timeout" error. Did anyone here have success with it? What am I missing?

I use ESPHome to enhance existing appliances (add smart functionality to an existing aircon for example) so generally the ESP board ends up within the appliance itself with nothing visible on the outside.

For things that need to be stand-alone I'd first check if there's an existing off-the-shelf option first which generally would be more cost-effective to buy and look better than anything I could make myself.

For temp sensors specifically I generally just go with whatever off-the-shelf stuff is supported by this firmware: https://github.com/pvvx/ATC_MiThermometer

Home Assistant, with a bunch of Xiaomi BLE LYWSD03MMC sensors, running custom firmware: https://github.com/pvvx/ATC_MiThermometer

I have a handful of Xiaomi LYWSD03MMC thermometers running pvxx's firmware, and a SCD4x CO2 Sensor.

Personally, I flashed them with this firmware so I could customize the broadcast interval and use them with Home Assistant without needing a proprietary hub.

If BLE is an option for you, consider a Xiaomi Mijia Hygrometer flashed (wirelessly via Chrome) with this firmware: https://github.com/pvvx/ATC_MiThermometer

Xaomi Mija Hygrometers, wirelessly flashed with this firmware, and Home Assistant to expose them in HomeKit. Local LCD display, roughly 2yr battery life, and available from $3-5.

I've been using a Raspberry Pi as a home server, and it's been holding up amazingly well, given everything I've thrown at it:

- The excellent Home Assistant, for unifying across Homekit and Google Home and tracking historical temperatures and a couple of automations. The RPi has Bluetooth built in, so I can capture the data from a few Bluetooth thermometer/hygrometers running custom firmware (https://github.com/pvvx/ATC_MiThermometer) without a 802.15.4 bridge or similar.

- An AirPlay to Google Cast bridge, mainly for listening to Overcast or the occasional YouTube video on Google speakers

- A SMB server, for file storage and potential Time Machine backups (but I don't currently have enough storage, and locally attached SSDs are just hard to beat in terms of performance)

- A DLNA server, for watching photos and videos on my TV

- Tailscale, for the occasional use of my home connection as a VPN when traveling (really glad to be having symmetric fiber for this!)

- Caddy, as a frontend for everything web facing, to benefit from its excellent Let's Encrypt integration for automatic certificate requests and renewals

Most of this is running in Docker containers and configured via Ansible, so that if the micrSD card burns out, I can just flash a new one with an empty image and recover from there.