Other way for Google assistant

Configuration
1

Hello, I would like to use duckdns to make this work but my router won’t let me forward the 443 and 80 port. So I can’t set let’s encrypt. Is there any way or method to make Google assistant work? Beside paying.
(Sorry for broke English)

2

Are you using hassio?

Can you forward another port?

If so use the duckdns add on, it does not required 80 or 443 to be open.

If you are on hassbian or a virtual enviroment based install take a look at the link below. It also works without 80 or 443 open.

3

I’ve installed hassio.io on Ubuntu 17.10 desktop.
I think I can forward other port, but 443 and 80 it’s reserved on my isp.
I tried duckdns add one but I get connection time out

4

Can you post the log from the DuckDNS add-on?

5

sure, but give me an hour, i’m not home yet :+1:

6

sorry I’m late

INFO: Using main config file /data/workdir/config

  • Generating account key…
  • Registering account key with ACME server…
  • Done!
    Wed Dec 19 13:40:08 UTC 2018:

INFO: Using main config file /data/workdir/config

  • Creating chain cache directory /data/workdir/chains
    Processing MYHOME.duckdns.org
  • Creating new directory /data/letsencrypt/MYHOUSE.duckdns.org …
  • Signing domains…
  • Generating private key…
  • Generating signing request…
  • Requesting new certificate order from CA…
  • Received 1 authorizations URLs from the CA
  • Handling authorization for MYHOUSE.duckdns.org
  • 1 pending challenge(s)
  • Deploying challenge tokens…
    OK + Responding to challenge for MYHOUSE.duckdns.org authorization…
  • Challenge is valid!
  • Cleaning challenge tokens…
    OK + Requesting certificate…
  • Checking certificate…
  • Done!
  • Creating fullchain.pem…
  • Done!
    Wed Dec 19 13:46:05 UTC 2018: OK
    51.179.115.212
    i’ve only installede the addon of duck, I didden’t configurated nothing in the confguratorn.yaml
    i had to reinstall everything.
    Am i missing something?
7

Your certificate appears to have generated just fine. What’s the problem here?

8

when i try to enter via duckdns url i get connection timed out
i can’t use google assistant, and i can’t open the port 443 and 80

9

So configure home assistant for your duckdns and certificate…

You will need to use port 8123, and forward that in your router if you cannot use 443/80.

Did you think DuckDNS was going to magically allow connections into your network without a forward of some sort?

10

I’ve already forwarded the 8123 on my hassio internal ip, the problem is when i try to forward the 443 on the 8123 like most of guide say when i have the ssl certificate, beacuse i can’t use the 443 port.
I don’t know if I’m explain myself correctly

11

If you are using port 8123, you don’t NEED 443…

The port is nothing but an entry point, it doesn’t matter which one you use, as long as it is forwarded. SSL works just fine on alternative ports.

12

i see. so i just have to figure out how to make my duckdns working

13

??

If your duckdns address resolves to your external IP, duckdns is working.

Just follow the official home assistant documentation to get your certs working.

14

I’m following this: https://www.home-assistant.io/docs/ecosystem/certificates/lets_encrypt/
I’ve setted my ip static.
I forwarded the port 8123 on my hassio ip,

added this on the configuration.yaml

Summary

duckdns:
domain: examplehome
access_token: abcdefgh-1234-abcd-1234-abcdefgh

this is the config of duckdns addon

Summary

{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “abcdefgh-1234-abcd-1234-abcdefgh”,
“domains”: [
“examplehome.duckdns.org”
],
“seconds”: 300
}

the log of the add on

Summary

INFO: Using main config file /data/workdir/config

  • Generating account key…
  • Registering account key with ACME server…
  • Done!
    Wed Dec 19 13:40:08 UTC 2018:

INFO: Using main config file /data/workdir/config

  • Creating chain cache directory /data/workdir/chains
    Processing examplehome.duckdns.org
  • Creating new directory /data/letsencrypt/examplehome.duckdns.org …
  • Signing domains…
  • Generating private key…
  • Generating signing request…
  • Requesting new certificate order from CA…
  • Received 1 authorizations URLs from the CA
  • Handling authorization for examplehome.duckdns.org
  • 1 pending challenge(s)
  • Deploying challenge tokens…
    OK + Responding to challenge for examplehome.duckdns.org authorization…
  • Challenge is valid!
  • Cleaning challenge tokens…
    OK + Requesting certificate…
  • Checking certificate…
  • Done!
  • Creating fullchain.pem…
  • Done!
    Wed Dec 19 13:46:05 UTC 2018: OK
    51.179.115.212

INFO: Using main config file /data/workdir/config

  • Account already registered!
    Wed Dec 19 15:02:18 UTC 2018: OK
    51.179.115.212

NOCHANGE
INFO: Using main config file /data/workdir/config
Processing examplehome.duckdns.org

  • Checking domain name(s) of existing cert… unchanged.
  • Checking expire date of existing cert…
  • Valid till Mar 19 12:41:00 2019 GMT (Longer than 30 days). Skipping renew!
    Wed Dec 19 15:07:21 UTC 2018: OK
    51.179.115.212

NOCHANGE
Wed Dec 19 15:12:23 UTC 2018: OK
51.179.115.212

NOCHANGE
Wed Dec 19 15:17:27 UTC 2018: OK
51.179.115.212

NOCHANGE
Wed Dec 19 15:22:29 UTC 2018: OK
51.179.115.212

NOCHANGE
Wed Dec 19 15:27:30 UTC 2018: OK
51.179.115.212

NOCHANGE
Wed Dec 19 15:32:35 UTC 2018: OK
51.179.115.212

NOCHANGE
Wed Dec 19 15:37:36 UTC 2018: OK
51.179.115.212

NOCHANGE

but i still cannot acces from outside or from duck dns
It’s the first time whit Hassio so i don’t know if i’m doing something wrong or if i’m missing something.

15

I see nowhere where you configured home assistant to do anything with your certs.

16

can you explain better?
I relly don’t have any idea of what i have to do, every guide say something different

17

Right on the page for the addon is the configuration instruction.

18

so i followed what this say

Summary

now to enter home assistant i have to type http://192…
but i still can’t connect from my duck domain.

i tryed to install let’s encrypt but he give me back this

Summary

starting version 3.2.4
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for MyDomain.duckdns.org
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. MyDomain.duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://MyDomain.duckdns.org/.well-known/acme-challenge/6NhPwpenbHKoRRf_c9CfwLH1uhR72GjPwku_TTd00Fs: Timeout during connect (likely firewall problem)
IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: MyDomain.duckdns.org
    Type: connection
    Detail: Fetching
    http://MyDomain.duckdns.org/.well-known/acme-challenge/6NhPwpenbHKoRRf_c9CfwLH1uhR72GjPwku_TTd00Fs:
    Timeout during connect (likely firewall problem)

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

At this point i think that is a problem of my router or my isp

19

You said you were running hassio.

Why are you installing anything else? Why aren’t you just following the instructions I sent? Just use the duckdns add-on. Then set your configuration yaml in home assistant…this isn’t hard.

20

my confuguration yaml

Summary

homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: 0
longitude: 0
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 0
# metric for Metric, imperial for Imperial
unit_system: metric
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: UTC
# Customization file
` customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.

http:
base_url: mydomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
# Optional, allows Home Assistant developers to focus on popular components.
# include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Sensors
sensor:
# Weather prediction
- platform: yr

# Text to speech
tts:
- platform: google

# Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

Duckdns addon

Summary

{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “abcdefgh-1234-abcd-1234-abcdefgh”,
“domains”: [
“[examplehome.duckdns.org](http://examplehome.duckdns.org/)”
],
“seconds”: 300
}

unistalled let’s encrypt addon (sorry)
still don’t work
I’ve istalled hassio from this guide the alternative section

Edit. I have to wait 2 hour to post a reply.

Sorry I’m new in the forum. I’ve edited the script. And thanks for your help, pls don’t be mad with me.
No, I’ve tested from my own network and from my cellphone network.
I can’t enter from both network