-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with Google Home #4
Comments
Could you provide more details? After you deploy a correctly configured device node, when you open its config page again you don't see the QR code? What the UI tells you? It will provide you with a message that explains why the QR code is not there. |
If you double click on any of the matter-device configuration nodes you should see a QR code. |
Sorry to be thick but thats not makin sense - in the example - I see a couple of light control nodes - a status node and on the right of the screen the matter server 1 - configuration nodes? I tried double-clicking on all the nodes in the example - no QR... What piece of the puzzle am I missing here? |
Oh and my Google device is the Google Nest Mini - 2nd generation. |
Can you confirm you deployed the flow? if so, please enable the trace logging level in Node-RED and provide full logs |
I will need the logs I requested before I can provide more assistance. |
Hi
|
Set If you start with from systemctl you will have to use |
Just to add a comment to this, I've just followed through the flow importing the example and the only way I could get the pairing codes to show up was to delete and recreate the 3 devices from scratch |
I have a Raspberry Pi 4 running Node-Red 3.1 and all fully up to date. I installed this node set and put in the example flow. I have the Google Home Speaker which is Matter compatible running and talking to various Matter devices but can't seem to get the example to bring up the QR code for Google to respond to... probably just idiocy on my behalf but normally I get to grips with nodes quite quickly...
The text was updated successfully, but these errors were encountered: