hardillb
I have just updated my hardware to a PI5, running Node Red version 4.0.9 and the pi is running Debian GNU/Linux 12. (The system was working well on Node Red version 3 software)
I can enter the user and password, then deploy. I can see the server connection flash every few seconds, but it won't connect.
I have tried the following: using a different user account. (set it up tested and then deleted when it also did not work.) Deleted and re installed the node-red-contrib-googlehome node. Tried installing via the pi terminal, which gave some NPM warnings.
Something must have changed with either the latest version of Node red or when the moved to the version 12 of Debian.
There is not much more I can check on my end. Please see if you can find the issue.
NPM WARNINGS
pi5@raspberrypi:~/.node-red $ npm install node-red-contrib-googlehome
npm warn deprecated [email protected]: this library is no longer supported
npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm warn deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm audit 3 moderate severity vulnerabilities
Some issues need review, and may require choosing a different dependency.
Run npm audit for details.
pi5@raspberrypi:~/.node-red $ npm audit
# npm audit report
request *
Severity: moderate
Server-Side Request Forgery in Request - https://github.com/advisories/GHSA-p8p7-x288-28g6
Depends on vulnerable versions of tough-cookie
No fix available
node_modules/request
node-red-contrib-googlehome *
Depends on vulnerable versions of request
node_modules/node-red-contrib-googlehome
tough-cookie <4.1.3
Severity: moderate
tough-cookie Prototype Pollution vulnerability - https://github.com/advisories/GHSA-72xf-g2v4-qvf3
No fix available
node_modules/tough-cookie
3 moderate severity vulnerabilities
Provide both usernames you have tried.
Also please run nslookup googlehome.hardill.me.uk on the Pi and show me the results
And anything from the Node-RED logs when it is trying to connect
Also if you look in ./node-red/node_modules/node-red-contrib-googlehome and edit the googlehome.js
remove the // from the start of line 96
node.client.on('error', function (err) {
//console.log(err);
node.setStatus({text: 'disconnected', shape: 'dot', fill:'red'});
node.error(err);
});
so it looks like
node.client.on('error', function (err) {
console.log(err);
node.setStatus({text: 'disconnected', shape: 'dot', fill:'red'});
node.error(err);
});
Then restart node-red, this will output more log information about why it is failing to connect
Thanks for getting back so fast. Here is the information you requested. I will email you the usernames.
NSlookup results Server: 192.168.1.107 Address: 192.168.1.107#53
Non-authoritative answer: Name: googlehome.hardill.me.uk Address: 34.241.226.122 Name: googlehome.hardill.me.uk Address: 2a05:d018:8c4:3201:2a72:eccf:e8a:2b76
Here is the log file 12 Apr 09:52:00 - [error] [google-home-conf:3a8702b4140733a6] AggregateError AggregateError [ETIMEDOUT]: at internalConnectMultiple (node:net:1122:18) at internalConnectMultiple (node:net:1190:5) at Timeout.internalConnectMultipleTimeout (node:net:1716:5) at listOnTimeout (node:internal/timers:583:11) at process.processTimers (node:internal/timers:519:7) { code: 'ETIMEDOUT', [errors]: [ Error: connect ETIMEDOUT 34.241.226.122:8883 at createConnectionError (node:net:1652:14) at Timeout.internalConnectMultipleTimeout (node:net:1711:38) at listOnTimeout (node:internal/timers:583:11) at process.processTimers (node:internal/timers:519:7) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '34.241.226.122', port: 8883 }, Error: connect ENETUNREACH 2a05:d018:8c4:3201:2a72:eccf:e8a:2b76:8883 - Local (:::0) at internalConnectMultiple (node:net:1186:16) at Timeout.internalConnectMultipleTimeout (node:net:1716:5) at listOnTimeout (node:internal/timers:583:11) at process.processTimers (node:internal/timers:519:7) { errno: -101, code: 'ENETUNREACH', syscall: 'connect', address: '2a05:d018:8c4:3201:2a72:eccf:e8a:2b76', port: 8883 } ] }
Hi Ben
The usernames are:
Xia
Xia2 (I deleted this one)
I tested a new user just to make certain that your server was limited to one connected device per user. It made no difference.
Regards
Andrew
From: Ben Hardill @.*** Sent: Friday, 11 April 2025 5:10 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
Provide both usernames you have tried.
Also please run nslookup googlehome.hardill.me.uk on the Pi and show me the results
And anything from the Node-RED logs when it is trying to connect
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2796044918 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3B7VHJ7FSXP5IXQDQ32Y5TEFAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGA2DIOJRHA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3FWEVQ5I75MKW2ORFD2Y5TEFA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVGVBBHM.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2796044918
Provide both usernames you have tried.
Also please run nslookup googlehome.hardill.me.uk on the Pi and show me the results
And anything from the Node-RED logs when it is trying to connect
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2796044918 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3B7VHJ7FSXP5IXQDQ32Y5TEFAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGA2DIOJRHA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3FWEVQ5I75MKW2ORFD2Y5TEFA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVGVBBHM.gif Message ID: @.***>
The logged errors imply you might have a network problem, it would be useful to see a longer section of logs, because the node is setup to try and connect on port 8883 and then 1883 and the entries you've shared show it trying on IPv4 and then IPv6 to connect to 8883 but nothing about trying 1883.
The MQTT broker that is the node uses to does listen on both ports, but the timeout errors implies that you may have a firewall dropping packets to those ports (If you are getting the list of devices in the node and can reach the website, then port 443 is still open)
The unreachable error implies that you do not have IPv6 setup on your local network.
Hi Ben
In the diagnostic log, it try’s twice on 8883, the once on 1883 and then just keeps looping.
I set up HiveMQ today which also uses port 8883 and that worked without issue. So I think that port is not blocked.
I rebooted my old PI4 to test that my router and gateway were not blocking, and it connected to your server immediately without any issue.
Maybe something has changed in the latest version of Debian that is preventing it connection.
As far as I know, Port 8883 is TLS so perhaps it is some sort of certificate issue, considering I can use NSlookup with no issue.
I am a bit stuck as to what to try next. If we come up with a solution I will post it on the git hub page as I am sure you will get more inquiries about this problem.
Cheers
Andrew
From: Ben Hardill @.*** Sent: Saturday, 12 April 2025 5:13 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
The logged errors imply you might have a network problem, it would be useful to see a longer section of logs, because the node is setup to try and connect on port 8883 and then 1883 and the entries you've shared show it trying on IPv4 and then IPv6 to connect to 8883 but nothing about trying 1883.
The MQTT broker that is the node uses to does listen on both ports, but the timeout errors implies that you may have a firewall dropping packets to those ports (If you are getting the list of devices in the node and can reach the website, then port 443 is still open)
The unreachable error implies that you do not have IPv6 setup on your local network.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2798696552 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3A5XA3AUEZERUJ5EU32ZC4JFAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYGY4TMNJVGI . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3CQYMJELSXKCXMHJH32ZC4JFA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVG2C4GQ.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2798696552
The logged errors imply you might have a network problem, it would be useful to see a longer section of logs, because the node is setup to try and connect on port 8883 and then 1883 and the entries you've shared show it trying on IPv4 and then IPv6 to connect to 8883 but nothing about trying 1883.
The MQTT broker that is the node uses to does listen on both ports, but the timeout errors implies that you may have a firewall dropping packets to those ports (If you are getting the list of devices in the node and can reach the website, then port 443 is still open)
The unreachable error implies that you do not have IPv6 setup on your local network.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2798696552 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3A5XA3AUEZERUJ5EU32ZC4JFAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYGY4TMNJVGI . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3CQYMJELSXKCXMHJH32ZC4JFA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVG2C4GQ.gif Message ID: @.***>
It wouldn't be a timeout error if there was a certificate problem (the certs are issued by letsencrypt so should be trusted by pretty much everywhere) and are the same certs as used for the website.
The nslookup is just checking that the pi can convert the hostname to the respective IP addresses.
The next step would be to run the following from the Pi
ping googlehome.hardill.me.uk
curl -4 https://googlehome.hardill.me.uk
The ping proves there is actually a route to the AWS machine it's all hosted on. Curl double checks the pi can actually reach it via https.
But I've not has any other reports of something similar that haven't ended up being DNS problems (which is not the case here as the pi is definitely resolving the hostname)
Hi Ben
Here are the results of the ping and curl commands. See what you think.
PING googlehome.hardill.me.uk (34.241.226.122) 56(84) bytes of data.
64 bytes from ec2-34-241-226-122.eu-west-1.compute.amazonaws.com (34.241.226.122): icmp_seq=1 ttl=36 time=353 ms
64 bytes from ec2-34-241-226-122.eu-west-1.compute.amazonaws.com (34.241.226.122): icmp_seq=2 ttl=36 time=356 ms
curl -4 https://googlehome.hardill.me.uk
<title>Node-RED Google Assistant Bridge</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- <meta name="monetization" content="$coil.xrptipbot.com/KZutpQmJRyqRZAK5KGKfug"> -->
<meta name="monetization" content="$ilp.uphold.com/MmrdQJQiKgNX">
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">
<!-- Optional theme -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap-theme.min.css" integrity="sha384-rHyoN1iRsVXV4nD0JutlnGaslCJuC7uwjduW9SVrLvRYooPp2bWYgmgJQIXwl/Sp" crossorigin="anonymous">
<link rel="stylesheet" href="https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/themes/smoothness/jquery-ui.css">
<link rel="stylesheet" href="/css/basic.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script>
<script src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.12.1/jquery-ui.min.js"></script>
<a href="/login">Login</a> or <a href="/register">Register</a>
New and Existing users, please take a moment to read the following blog post
This site is the entry point for using the node-red-contrib-googlehome
to allow Node-RED as a collection of smart home devices
Please make sure you read the docs carefully
<img style="width: 80%" src="/images/flow.png">
From: Ben Hardill @.*** Sent: Sunday, 13 April 2025 6:05 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
It wouldn't be a timeout error if there was a certificate problem (the certs are issued by letsencrypt so should be trusted by pretty much everywhere) and are the same certs as used for the website.
The nslookup is just checking that the pi can convert the hostname to the respective IP addresses.
The next step would be to run the following from the Pi
ping googlehome.hardill.me.uk curl -4 https://googlehome.hardill.me.uk
The ping proves there is actually a route to the AWS machine it's all hosted on. Curl double checks the pi can actually reach it via https.
But I've not has any other reports of something similar that haven't ended up being DNS problems (which is not the case here as the pi is definitely resolving the hostname)
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2799850384 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3D6Q5OKPNZIBEQBPHD2ZILDTAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJZHA2TAMZYGQ . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3EJJYWZ2IQURLS2TT32ZILDTA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVG4JJZA.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2799850384
It wouldn't be a timeout error if there was a certificate problem (the certs are issued by letsencrypt so should be trusted by pretty much everywhere) and are the same certs as used for the website.
The nslookup is just checking that the pi can convert the hostname to the respective IP addresses.
The next step would be to run the following from the Pi
ping googlehome.hardill.me.uk curl -4 https://googlehome.hardill.me.uk
The ping proves there is actually a route to the AWS machine it's all hosted on. Curl double checks the pi can actually reach it via https.
But I've not has any other reports of something similar that haven't ended up being DNS problems (which is not the case here as the pi is definitely resolving the hostname)
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2799850384 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3D6Q5OKPNZIBEQBPHD2ZILDTAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJZHA2TAMZYGQ . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3EJJYWZ2IQURLS2TT32ZILDTA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVG4JJZA.gif Message ID: @.***>
OK, so there is nothing stopping connections to the server on ports other that 8883 or 1883 by the look of things.
Can you share the exact versions of the following:
There is a small possibility that there is a problem with the MQTT library in the node and the NodeJS version
Here are the versions:
NodeJs 20.19.0
NPM 10.8.2
Node Red 4.0.9
Googlehome 0.0.15
Cheers
From: Ben Hardill @.*** Sent: Monday, 14 April 2025 8:43 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
OK, so there is nothing stopping connections to the server on ports other that 8883 or 1883 by the look of things.
Can you share the exact versions of the following:
There is a small possibility that there is a problem with the MQTT library in the node and the NodeJS version
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2801286315 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3F6YY346U7FYIGFXQD2ZOGJ3AVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBRGI4DMMZRGU . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3EWE4LANIK4TTXLRSL2ZOGJ3A5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVG7A6KW.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2801286315
OK, so there is nothing stopping connections to the server on ports other that 8883 or 1883 by the look of things.
Can you share the exact versions of the following:
There is a small possibility that there is a problem with the MQTT library in the node and the NodeJS version
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2801286315 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3F6YY346U7FYIGFXQD2ZOGJ3AVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMBRGI4DMMZRGU . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3EWE4LANIK4TTXLRSL2ZOGJ3A5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVG7A6KW.gif Message ID: @.***>
OK,I've just created a new test user and spun this all up on the latest docker container (which matches the nodejs/npm/node-red version)
And it all connects properly.
The host is a Intel Ubuntu 22.04 machine at the moment, I'll try a debian VM when I get a moment.
Do you have anything like Pi Hole on your network? Are the old/new system connected differently e.g. wifi vs wired?
I'm at a loss at the moment, this feels like it has to be something in your environment as I've not had any other reports and the same versions are running normally for me.
I have been testing.
I do have pi hole on my network, but it is not blocking, my old system connects to your server just fine.
I have tried wired and Wi-Fi connections with no difference. Old system connects on both. New one does not connect.
I setup a MQTT OUT node to test the connection on Port 1883. Old system connects, New one does not.
I setup the same MQTT OUT node to connect to Hive Mq (no user or password) and it connects on the new system. So I don’t think it is a port blocking issue.
I will leave the node trying to connect to the server. Please check the server log to see if you can see it trying to connect.
Cheers
From: Ben Hardill @.*** Sent: Friday, 18 April 2025 6:23 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
OK,I've just created a new test user and spun this all up on the latest docker container (which matches the nodejs/npm/node-red version)
And it all connects properly.
The host is a Intel Ubuntu 22.04 machine at the moment, I'll try a debian VM when I get a moment.
Do you have anything like Pi Hole on your network? Are the old/new system connected differently e.g. wifi vs wired?
I'm at a loss at the moment, this feels like it has to be something in your environment as I've not had any other reports and the same versions are running normally for me.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2814904829 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3D4OC35XHUYBGEROED22CY6PAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJUHEYDIOBSHE . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3CWMNLNVDFYRG6RVML22CY6PA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVHZAE72.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2814904829
OK,I've just created a new test user and spun this all up on the latest docker container (which matches the nodejs/npm/node-red version)
And it all connects properly.
The host is a Intel Ubuntu 22.04 machine at the moment, I'll try a debian VM when I get a moment.
Do you have anything like Pi Hole on your network? Are the old/new system connected differently e.g. wifi vs wired?
I'm at a loss at the moment, this feels like it has to be something in your environment as I've not had any other reports and the same versions are running normally for me.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2814904829 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3D4OC35XHUYBGEROED22CY6PAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJUHEYDIOBSHE . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3CWMNLNVDFYRG6RVML22CY6PA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVHZAE72.gif Message ID: @.***>
I setup a MQTT OUT node to test the connection on Port 1883. Old system connects, New one does not.
This is with the service username/password and googlehome.hardill.me.uk?
Also just double checking you have totally stopped Node-RED on the old device while testing all this? You can not have 2 instances of Node-RED connected at the same time as the Google Home nodes force using the username as the client id to ensure only a single instance can be online at a time.
I will leave the node trying to connect to the server. Please check the server log to see if you can see it trying to connect.
I don't see anything in the broker logs for today (since midnight UTC) but I do see connections for yesterday (I assume from the old machine and from MQTTExplorer and basic Node-RED). If it was 2 instance running at once I would expect to see them both kicking each other off the broker every 30 seconds.
I've installed a fresh Debian 12 VM and a fresh Node-RED install with a test account and all is connecting fine, so it doesn't appear to be a software versions thing (the VM was on AMD64)
I just tested one system at a time. I have left the new pi with it trying to connect to googlehome.hardill.me.uk With my user name and password. It will be on for the next 8 hours. Then I will disable it.
I also tested a new user name and paw just incase it was something to do with it being tied to the Mac address of my old pi.
If you can't see the logon requests, Then somehow my system is not allowing access to your server. I am not certain what to do next.
On Mon, 21 Apr 2025, 9:15 pm Ben Hardill, @.***> wrote:
I setup a MQTT OUT node to test the connection on Port 1883. Old system connects, New one does not.
This is with the service username/password and googlehome.hardill.me.uk?
Also just double checking you have totally stopped Node-RED on the old device while testing all this? You can not have 2 instances of Node-RED connected at the same time as the Google Home nodes force using the username as the client id to ensure only a single instance can be online at a time.
I will leave the node trying to connect to the server. Please check the server log to see if you can see it trying to connect.
I don't see anything in the broker logs for today (since midnight UTC) but I do see connections for yesterday (I assume from the old machine and from MQTTExplorer and basic Node-RED). If it was 2 instance running at once I would expect to see them both kicking each other off the broker every 30 seconds.
I've installed a fresh Debian 12 VM and a fresh Node-RED install with a test account and all is connecting fine, so it doesn't appear to be a software versions thing (the VM was on AMD64)
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818204571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3AP23VXJHOMDDURLJL22THNDAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGIYDINJXGE . You are receiving this because you authored the thread.Message ID: @.***> hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818204571
I setup a MQTT OUT node to test the connection on Port 1883. Old system connects, New one does not.
This is with the service username/password and googlehome.hardill.me.uk?
Also just double checking you have totally stopped Node-RED on the old device while testing all this? You can not have 2 instances of Node-RED connected at the same time as the Google Home nodes force using the username as the client id to ensure only a single instance can be online at a time.
I will leave the node trying to connect to the server. Please check the server log to see if you can see it trying to connect.
I don't see anything in the broker logs for today (since midnight UTC) but I do see connections for yesterday (I assume from the old machine and from MQTTExplorer and basic Node-RED). If it was 2 instance running at once I would expect to see them both kicking each other off the broker every 30 seconds.
I've installed a fresh Debian 12 VM and a fresh Node-RED install with a test account and all is connecting fine, so it doesn't appear to be a software versions thing (the VM was on AMD64)
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818204571, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3AP23VXJHOMDDURLJL22THNDAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGIYDINJXGE . You are receiving this because you authored the thread.Message ID: @.***>
Just double checking, both Pi's are on a RFC1918 (private IP range) behind the same NAT gateway (so requests should show up as coming from the same external public IP address).
I'm just trying to rule out anything else.
But I am also at a loss here, the timeout implies something along the route between the 2 machines is dropping the packets, but I can't see where.
My only off the wall suggestion is assuming your router is handing out the same IP address to the new Pi, try seeing if you can force it to hand out a different address.
I tried changing ip addresses, switched between wired and wifi. Rebooted all modems and Pi none of this made a difference.
Then I thought maybe the old pi did not log out of your server. So I powered it up, It connected right up. I then deleted the password. This prevented it connecting to your server. Hopefully forcing a disconnect. After shutting down the old pi I setup the connection on the new pi and it still would not connect.
The only thing I can think of now is to setup the old pi to run the google home bit and send its on/off requests to the new pi on the local server. It is a bit messy if I have to use this method.
The only other Idea I had, is perhaps your server has something stored that relates to the old pi. Possibly if you reboot the server it may resolve the issue, by clearing the memory.
From: Ben Hardill @.*** Sent: Monday, 21 April 2025 11:44 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
Just double checking, both Pi's are on a RFC1918 (private IP range) behind the same NAT gateway (so requests should show up as coming from the same external public IP address).
I'm just trying to rule out anything else.
But I am also at a loss here, the timeout implies something along the route between the 2 machines is dropping the packets, but I can't see where.
My only off the wall suggestion is assuming your router is handing out the same IP address to the new Pi, try seeing if you can force it to hand out a different address.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818437570 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3BA5VVDGMRYPF4EY7T22TY2JAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGQZTONJXGA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3HEYIDXNOHKCYSWV5L22TY2JA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVH7XY4E.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818437570
Just double checking, both Pi's are on a RFC1918 (private IP range) behind the same NAT gateway (so requests should show up as coming from the same external public IP address).
I'm just trying to rule out anything else.
But I am also at a loss here, the timeout implies something along the route between the 2 machines is dropping the packets, but I can't see where.
My only off the wall suggestion is assuming your router is handing out the same IP address to the new Pi, try seeing if you can force it to hand out a different address.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818437570 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3BA5VVDGMRYPF4EY7T22TY2JAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGQZTONJXGA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3HEYIDXNOHKCYSWV5L22TY2JA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVH7XY4E.gif Message ID: @.***>
I have had a moment to look at this again.
I think the issue is that I am running Bookworm OS on the PI and that the current release of Node Red only supports Bullseye OS
Surfing the net I have found some other users with the odd Node Red item that won’t work on Bookworm.
I will just have to wait for an update to Node Red that supports Bookworm.
I will let you know if it resolves when there is an update.
Cheers
Andrew
From: Ben Hardill @.*** Sent: Monday, 21 April 2025 11:44 PM To: hardillb/node-red-contrib-googlehome Cc: Cruzxia; Author Subject: Re: [hardillb/node-red-contrib-googlehome] Cannot connect to server. (Issue #32)
Just double checking, both Pi's are on a RFC1918 (private IP range) behind the same NAT gateway (so requests should show up as coming from the same external public IP address).
I'm just trying to rule out anything else.
But I am also at a loss here, the timeout implies something along the route between the 2 machines is dropping the packets, but I can't see where.
My only off the wall suggestion is assuming your router is handing out the same IP address to the new Pi, try seeing if you can force it to hand out a different address.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818437570 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3BA5VVDGMRYPF4EY7T22TY2JAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGQZTONJXGA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3HEYIDXNOHKCYSWV5L22TY2JA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVH7XY4E.gif Message ID: @.***>
https://avatars.githubusercontent.com/u/1800845?s=20&v=4 hardillb left a comment (hardillb/node-red-contrib-googlehome#32) https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818437570
Just double checking, both Pi's are on a RFC1918 (private IP range) behind the same NAT gateway (so requests should show up as coming from the same external public IP address).
I'm just trying to rule out anything else.
But I am also at a loss here, the timeout implies something along the route between the 2 machines is dropping the packets, but I can't see where.
My only off the wall suggestion is assuming your router is handing out the same IP address to the new Pi, try seeing if you can force it to hand out a different address.
— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-contrib-googlehome/issues/32#issuecomment-2818437570 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AXOUB3BA5VVDGMRYPF4EY7T22TY2JAVCNFSM6AAAAAB245Z3BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGQZTONJXGA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AXOUB3HEYIDXNOHKCYSWV5L22TY2JA5CNFSM6AAAAAB245Z3BGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVH7XY4E.gif Message ID: @.***>