Skip to content
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

Open
scargill opened this issue Sep 8, 2023 · 11 comments
Open

Not working with Google Home #4

scargill opened this issue Sep 8, 2023 · 11 comments

Comments

@scargill
Copy link

scargill commented Sep 8, 2023

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

@FezVrasta
Copy link
Owner

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.

@scargill
Copy link
Author

scargill commented Sep 8, 2023

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.

As I don't yet know what I'm doing with this node set, I followed the instructions and simply inserted the example flow.

image

Over on the right I see reference to matter server 1... which has the name matter server 1 and that's it.
image

@FezVrasta
Copy link
Owner

If you double click on any of the matter-device configuration nodes you should see a QR code.

@scargill
Copy link
Author

scargill commented Sep 8, 2023

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

image

What piece of the puzzle am I missing here?

@scargill
Copy link
Author

scargill commented Sep 8, 2023

Oh and my Google device is the Google Nest Mini - 2nd generation.

@FezVrasta
Copy link
Owner

Can you confirm you deployed the flow? if so, please enable the trace logging level in Node-RED and provide full logs

@scargill
Copy link
Author

scargill commented Sep 8, 2023

The image shows it sitting on a page in Node-Red - having pasted it directly in. Did I miss a step.... I did no configuration, just used the "Manage Pallette" to get the Matter nodes into NR..

image
then pasted in that flow example.

And yes my Google Nest Mini is plugged in as usual and working. I am also using Node-red-contrib-googlehome and made a virtual device which then controls the various lights in my office in response to "hey google - mancave on". So all of that is working. I'm just failing to get to grips with the Matter node-set-up here,

I've enabled the "TRACE-LEVEL LOGGING" in node-red - not something I've ever done (I've been using node-red for years and written several nodes for it - I just seem to be having trouble getting into your mind-set here).

@FezVrasta
Copy link
Owner

I will need the logs I requested before I can provide more assistance.

@scargill
Copy link
Author

scargill commented Sep 8, 2023

I will need the logs I requested before I can provide more assistance.

Hi
In my .node-red settings.js file this is currently set up - what do I need to change....

logging: {
        // Only console logging is currently supported
        console: {
            // Level of logging to be recorded. Options are:
            // fatal - only those errors which make the application unusable should be recorded
            // error - record errors which are deemed fatal for a particular request + fatal errors
            // warn - record problems which are non fatal + errors + fatal errors
            // info - record information about the general running of the application + warn + error + fatal errors
            // debug - record information which is more verbose than info + info + warn + error + fatal errors
            // trace - record very detailed logging + debug + info + warn + error + fatal errors
            // off - turn off all logging (doesn't affect metrics or audit)
            level: "info",
            // Whether or not to include metric events in the log output
            metrics: false,
            // Whether or not to include audit events in the log output
            audit: false
        }
    }

@FezVrasta
Copy link
Owner

Set level to trace, then start Node-RED and provide all its logs.

If you start with from systemctl you will have to use journalctl -u service-name to see them. Otherwise, just run npx node-red or whatever command you usually use to run Node-red, and the logs will show up.

@AidenDawn
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants