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

Cant get it to work. Google home app cannot reach (iobroker nodered) #212

Closed
TimoS911 opened this issue Dec 22, 2021 · 6 comments
Closed

Comments

@TimoS911
Copy link

Okay i think i have done everything but it wont work.

I just did everything in the manual and i also get a status 200 (OK) with reqbin.com.
NodeRed is installed as an adapter in iobroker. I forward port 80,443,3001,8084 to my iobroker raspberry.

My settings:
accountlinking
googleactions
noderednode
req
IMG_9008

Is there any way i can check more stuff that can lead me to the point where i have something wrong?
To get to this point just took me way too long (fk ssl certificates + iobroker... just use certbot if you try to get ssl certificates...)

Would be nice if someone got an idea.
I am out of ideas.

@ckhmer1
Copy link
Contributor

ckhmer1 commented Dec 22, 2021

Open the browser to the /check page instead of sending it a rest request.
The page You see in the response is a test page, fill in the form info, and press test.

@TimoS911
Copy link
Author

TimoS911 commented Dec 22, 2021

If i open the website "https://tim............net:3001/check i get an error that this page is not reachable.

website-check

So i need this page to be browsable? It should display something?

@Caprico85
Copy link
Collaborator

You accidentally included your URL on the screenshot. I tried to access it ... and it works.

image

So maybe something on your phone or your network is blocking the connection. Have you tried disabling WiFi to use your mobile internet connection?

@TimoS911
Copy link
Author

Wow really... Thank god i accidentally included the URL :D
I can login with the google home app with wifi off.

Can this lead to any problems in the future?
I will try to add some dummy smart devices today in nodered and check if i can controll it with my phone app.

But thank you so much!

@Caprico85
Copy link
Collaborator

Can this lead to any problems in the future?

During normal operation it shouldn't. The only one talking to your port 3001 are Google servers. As Google is coming from outside your network, it shouldn't hit whatever is blocking port 3001.

You might have to relogin after some months. As long as you remember to turn off your WiFi then, it shouldn't be a problem.

@TimoS911
Copy link
Author

Okay i tested some different nodes and everything works fine.
Finally i can start on voice controll my HSV RGB lights.
I just have to figure out how to use NodeRed :) but thats not for this issue here.

Maybe you should add the little info that you can open the /check page in youre browser and should see that picture you send in the setup guideline. I thought that i can only get and post requests on that port/site.

Info for someone that finds this case because of google iobroker and this nodered.
Try not to hard to get the SSL stuff going directly from iobroker. It didnt work at all for me with letsencrypt on web.0/admin.0.
Just set up a certbot directly in ssh and use the path to the certificates in the main iobroker setup certificates tab.
Make sure that iobroker can read these as certbot maybe create these as root user and iobroker cannot access it. (try to cd there or nano the certificate via ssh and you will see if pi user can access.)
Once this is set up you can go ahead and use the well written instructions on how to set up this nodered node.
I just put the JWT Key json file in the iobroker upload directory and gave it the direct path to that file at the management node config. (/opt/iobroker/iobroker-data/files/0_userdata.0/iobroker-xxxxx-xxxxx-xx.json)

This case can get closed and thank you Caprico.

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