Replies: 6 comments 3 replies
-
|
Should definitely work for proof-of-concept, but I have not tried it (only localhost with chip-tool) - unfortunately it can be really hard to debug the commissioning process I used to work on the commissioner in Google Home - if you're able to attach to your phone with USB/adb & get a logcat, you may find something useful there (e.g. a callstack) |
Beta Was this translation helpful? Give feedback.
-
|
It definitely works with Google and Alexa, and up until recently - with Apple too (now again we have mdns issues with apple). If you paste the full logs from the rpi, I might be able to help. Also describe what error the phone displays. |
Beta Was this translation helpful? Give feedback.
-
|
Just to clarify (I don't think it will matter). Just to get me started in my testing, I'm running these tests on an Ubuntu 26.04 laptop, not on the raspberry pi (but a respberry pi is my eventual target). Ok, so interactions: The MAC address below is from my phone (which makes sense). I am not seeing very much traffic in tcpdump on while this is running. I see some 5353 interactions. But I would expect to see more. I can ping the Google Home Mini on the ipv6 address. Logs: And if I do 'try again' from the phone: [2026-02-12T23:34:07Z INFO rs_matter::dm::clusters::on_off::test] Emulation: out of band toggle request |
Beta Was this translation helpful? Give feedback.
-
I think setting up stuff in "console.home.google.com" is not necessary anymore. So you could remove everything from there.
From your phone, Google Home app, tap the "+" sign in the top right corner, then from the popup menu select "Device" and scan the QR code. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
BTW - I just got your error when my Android phone lost connection to my Google controller (Nest Hub Gen 2). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is anyone available for just some basic setup help. My end goal is to use a Raspberry Pi to create a smart home device as a DIY project. I'm not interested in making something commercial.
As my first steps of this adventure, I have cloned the rs-matter repo and built everything, including the examples. For this initial learning about rs-matter I'm doing this on a laptop running Ubuntu 26.04. I'm using a Google Home Mini as the matter server. In console.home.google.com I added a test matter device with Vendor ID 0xfff1 and Product ID 0x8001.
Then trying the onoff_light_bt example. I built the example with the following options:
cargo build --bin onoff_light_bt --features avahi --features zbus --features zeroconf
Once built, it starts, I get the QR code on the console and my phone automatically will say to 'Set up your device'. On my phone I scan the QR Code in google home, it seems to try to add the device, I see messages on the console about the bluetooth service. My phone shows 'Connecting to Device'. On the console I see the handshake request and response. But then an unsubscribe request and disconnect message.
So, it seems to be trying. All devices are on the same network (2.4 GHz WiFi, I have ipv6 address on the laptop), firewall on the laptop is turned off.
I know these examples are for testing, but from the pages it sounds like this should also work as proof things work. But maybe that isn't the case.
And also, maybe this is not a good starting point for what I want to do, in which case just say so and I will try a different path.
Thanks for any and all insights and assistance.
Beta Was this translation helpful? Give feedback.
All reactions