Hey guys, so I spent some time the last few days starting over from the beginning, and
trying to be very thorough and document my entire process. I have not succeeded yet, but
I believe I am getting closer and now have a much narrower view of the problem. Here are a
list of the steps I’ve taken (planning to post them at some point if I ever succeed).
- Restore modem to default
- Restore Pi3 SD to hio 0.69.1
- Verify hassio.local:8123 works
- Snapshot
- Assign Pi3 static IP address in router/reboot router
- Install SSH server
- Setup and verify SSH connection with laptop
- Snapshot
- Setup basic “homeassistant” info and http pw in configuration.yaml
- Enable port forwarding of 8123:8123 to Pi3, restart router
- Verify internet works, SSH works, hassio.local:8123 works
- Find IP address via https://whatismyipaddress.com/
- Navigate to http://...:8123 with the IP address found in previous step
- If you can’t access via your home network, loopback may not be supported. Try from
a completely external network, such as your cellphone without WiFi on. - Use hassio.local:8123 on local network if loopback is not supported
- Make sure to attempt to login with your http password set previously
- Snapshot
- Create DuckDNS account
- Create subdomain of your choosing, we will use mydomain.duckdns.org
- ping mydomain.duckdns.org
- I used the PingTools Android app because my network does not support loopback
- ping terminal command will work fine if you have a home network with loopback
- Navigate to http://mydomain.duckdns.org:8123 and verify it loads and you can sign in
- Install DuckDNS add-on on hassio
- Setup and save DuckDNS config file with info from DuckDNS account. Mine looks like:
{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "x-x-x-x-x",
"domains": [
"mydomain.duckdns.org"
],
"seconds": 300
}
- Restart hassio (Hamburger button->Configuration->General->Restart)
- Make sure everything went OK in the duckDNS log (Hamburger->Hass.io->Dashboard->DuckDNS)
- One time Duck DNS did not start for me, and no log was present - not sure what happened
- Another time the challenge failed for some reason
- Getting everything setup can take a few minutes, maybe a good time for a break
- Keep trying until you see a succesful log, such as this one:
starting version 3.2.4
# INFO: Using main config file /data/workdir/config
+ Generating account key...
+ Registering account key with ACME server...
+ Done!
# INFO: Using main config file /data/workdir/config
+ Creating chain cache directory /data/workdir/chains
Processing mydomain.duckdns.org
+ Creating new directory /data/letsencrypt/mydomain.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 mydomain.duckdns.org
+ 1 pending challenge(s)
+ Deploying challenge tokens...
OK + Responding to challenge for mydomain.duckdns.org authorization...
OK + Challenge is valid!
+ Requesting certificate...
+ Checking certificate...
+ Done!
+ Creating fullchain.pem...
+ Walking chain...
+ Done!
- Verify http://mydomain.duckdns.org:8123 still works
- Snapshot
- Modify configuration.yaml by adding in http info. I’ve tried both supplying https://
and leaving it out and have had similar results.
http:
# Secrets are defined in the file secrets.yaml
api_password: !secret http_password
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: https://mydomain.duckdns.org
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
- Restart hassio
- Check local access first for sanity (https://hassio.local:8123 and https://hassio.local - I know, the correct URL at this point should be the first one, but tried both just for fun I guess).
- DOES NOT WORK. homeassistant frontend never loads all the way.
See weird log file, note that https://hassio.local:8123 does not work! If I comment
out the SSL parameters, I can access the local front end over http just fine. - I’m not able to get Duck DNS log, either I’m using hassio cli wrong or some other issue:
core-ssh:~# hassio ad list |grep Duck
"name": "Duck DNS",
core-ssh:~# hassio -d ad logs -name "Duck DNS"
DEBUG [addons]: action->'logs', endpoint='Duck DNS/logs', serverOverride->'', GET->'true', options->'', rawjson->'false', filter->''
DEBUG [ExecCommand]: basepath->'addons', endpoint->'Duck DNS/logs', serverOverride->'', get->'true', Options->'', Filter->'', RawJSON->'false'
DEBUG [GenerateURI]: basepath->'addons', endpoint->'Duck DNS/logs', serverOverride->''
DEBUG [RestCall]: data->'http://hassio/addons/Duck DNS/logs', GET->'true', payload->''
DEBUG [RestCall]: ResponseBody->'Addon not exists'
Error decoding json invalid character 'A' looking for beginning of value: Addon not existscore-ssh:~#
- “weird” log:
2018-05-22 23:33:42 ERROR (SyncWorker_8) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-22 23:43:58 ERROR (zeroconf-ServiceBrowser__tivo-remote._tcp.local.) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
So I definitely think my issue is somewhere along the lines of SSL cert’s and Duck DNS
breaking. I’m beginning to wonder if this issue is related at all:
I may post this topic to the GitHub as well to see if anyone there knows what to do.
. Thank you all for your support…