Home Assistant : Q&A, Tips & Tricks, Your Configs

[riscbroker]

I thought letsencrypt was part of the duckdns setup, so I did not look any further.

 

[chickenbeef]

I thought letsencrypt was part of the duckdns setup, so I did not look any further.

You do not need to setup letsencrypt separately.

The docs are quite good and list the valid parameters.

addons/duckdns/DOCS.md at master · home-assistant/addons

:heavy_plus_sign: Docker add-ons for Home Assistant - home-assistant/addons

github.com

IMHO, you should be trying to access it via the public IP to make sure your router config is correct then worry about duckdns.

 

[SauRoNZA]

Yup get the pure IP networking up first and confirm that works.

Then worry about the next level with DNS.

You are chasing too many variables at once.

http://{PUBLIC-IP}:8123

With a port forward rule to 8123.

Then once that works worry about DuckDNS and Letsencrypt.

https://{duckdnsdomain}

With a port forward rule to 443 externally to whatever port Letsencrypt is internally.

Then go remove the 8123 port forward.

 

[SauRoNZA]

Connection times out

I set up the port forward, put this in configuration.yaml and restarted HA:

http:
base_url: http://xxxxxxxx.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: True
login_attempts_threshold: 3

Do I need to restart the router?

Doesn’t make sense that you have http with certificates that apply to https.

I’ve not done this setup myself but those two things don’t correlate on any configuration.

It should either all be https as it stands there, or if it’s going to be http (pointless) the certificates would need to come out.

Also makes no sense that it would point to 8123. You want it all to go to 443 surely?

Granted I don’t use it like this and have separate Dockers for all these things but the above Is the “proper” way to do it.

I have a Raspberry Pi on loan and just shipped off the kids so will be doing exactly all this today.

First fighting with how to write a Micro SD card without a full size adaptor....

 

[riscbroker]

Doesn’t make sense that you have http with certificates that apply to https.

I’ve not done this setup myself but those two things don’t correlate on any configuration.

It should either all be https as it stands there, or if it’s going to be http (pointless) the certificates would need to come out.

Also makes no sense that it would point to 8123. You want it all to go to 443 surely?

Granted I don’t use it like this and have separate Dockers for all these things but the above Is the “proper” way to do it.

I have a Raspberry Pi on loan and just shipped off the kids so will be doing exactly all this today.

First fighting with how to write a Micro SD card without a full size adaptor....

You're quite correct - that line now reads:

base_url: xxxxxxxx.duckdns.org:8123

so no more confusion between http and https

Its working fine now, just tested over 3G

 

[riscbroker]

You do not need to setup letsencrypt separately.

The docs are quite good and list the valid parameters.

addons/duckdns/DOCS.md at master · home-assistant/addons

:heavy_plus_sign: Docker add-ons for Home Assistant - home-assistant/addons

github.com

IMHO, you should be trying to access it via the public IP to make sure your router config is correct then worry about duckdns.

Thanks for this, so I can conclude that letsencrypt etc is all set up properly and I don't need to take any furthers steps to secure my network/machine?

 

[chickenbeef]

Thanks for this, so I can conclude that letsencrypt etc is all set up properly and I don't need to take any furthers steps to secure my network/machine?

Yes, an easy way to check is if you can see the lock icon next to the URL in your browser.

If the certs are applied, it will say the connection is secure.

Example:

 

[alqassam]

Next problem my router doesn't want to accept more reserved IP addresses.

I have a usg3 lying around but with hat my blink cameras refuse to connect to the cloud.

 

[chickenbeef]

Next problem my router doesn't want to accept more reserved IP addresses.

I have a usg3 lying around but with hat my blink cameras refuse to connect to the cloud.

If you use AdGuard/PiHole you can use that for DHCP.

I think there's also a dedicated DHCP add on for home assistant. I just use PiHole (need to switch to AdGuard in the near future).

 

[alqassam]

If you use AdGuard/PiHole you can use that for DHCP.

I think there's also a dedicated DHCP add on for home assistant. I just use PiHole (need to switch to AdGuard in the near future).

What I'm worried about is if my pi is down for whatever reason how will DHCP work?

 

[riscbroker]

Yes, an easy way to check is if you can see the lock icon next to the URL in your browser.

If the certs are applied, it will say the connection is secure.

Example:

View attachment 854325

Hmmmm. The HA instance running on the laptop with the virtual machine is not secure, but when I access HA remotely with my phone it seems to be a secure connection...

 

[alqassam]

I also want to implement something like this

My OCD kicking in


'm a network administrator so I may have gone over board but this is mine. 192.168.0.1 - 10 is network infrastructure 11 - 29 is servers 30 - 39 is laptops 40 - 49 is cellphones and tablets
100 - 119 is media devices 120 - 139 is light bulbs 140 - 149 is ip cameras 150 - 159 is iR blasters 160 - 180 is other devices
200 - 250 is DHCP pool
250 up is for testing
Everything has a place and I have a table with ip's and Mac addresses. Now here is where it gets interesting, because everything has already been assigned an IP there is no real need for DHCP except for when mates come over. So I have Hassio scan 200 - 250 every 10 mins and it sends a notification to me if it finds a device. Early warning if someone is on my network that shouldn't be there

 

[chickenbeef]

What I'm worried about is if my pi is down for whatever reason how will DHCP work?

It won't. My Pi is on backup power so it's not an issue for me.

 

[alqassam]

I also want to implement something like this

My OCD kicking in


'm a network administrator so I may have gone over board but this is mine. 192.168.0.1 - 10 is network infrastructure 11 - 29 is servers 30 - 39 is laptops 40 - 49 is cellphones and tablets
100 - 119 is media devices 120 - 139 is light bulbs 140 - 149 is ip cameras 150 - 159 is iR blasters 160 - 180 is other devices
200 - 250 is DHCP pool
250 up is for testing
Everything has a place and I have a table with ip's and Mac addresses. Now here is where it gets interesting, because everything has already been assigned an IP there is no real need for DHCP except for when mates come over. So I have Hassio scan 200 - 250 every 10 mins and it sends a notification to me if it finds a device. Early warning if someone is on my network that shouldn't be there

It won't. My Pi is on backup power so it's not an issue for me.

That's an issue for.

Eg yesterday I changed to a new sd card as the old one was on the brink. Took me like half a day as the snapshot etc was wrong.

 

[chickenbeef]

Hmmmm. The HA instance running on the laptop with the virtual machine is not secure, but when I access HA remotely with my phone it seems to be a secure connection...

Are you accessing it via the domain name or IP address on the local network?

If you access it via the domain name it will be secure.

If you access it via the IP it will not be secure as the address you're using doesn't match the certificate. That's expected.

 

[riscbroker]

Are you accessing it via the domain name or IP address on the local network?

If you access it via the domain name it will be secure.

If you access it via the IP it will not be secure as the address you're using doesn't match the certificate. That's expected.

Makes sense. The problem is that I cannot access HA on the laptop where it is installed if I try the domain name - the connection just times out.

When I use the IP address I have to bypass/ignore the security warning.

 

[Stuey74]

My OCD kicking in

'm a network administrator so I may have gone over board but this is mine. 192.168.0.1 - 10 is network infrastructure 11 - 29 is servers 30 - 39 is laptops 40 - 49 is cellphones and tablets
100 - 119 is media devices 120 - 139 is light bulbs 140 - 149 is ip cameras 150 - 159 is iR blasters 160 - 180 is other devices
200 - 250 is DHCP pool
250 up is for testing
Everything has a place and I have a table with ip's and Mac addresses. Now here is where it gets interesting, because everything has already been assigned an IP there is no real need for DHCP except for when mates come over.

Lol, I am exactly the same, run an Untangle GW and do similar. OCD for the win - or CDO as it should be, alphabetically correct.

 

[TedLasso]

I also want to implement something like this

My OCD kicking in


'm a network administrator so I may have gone over board but this is mine. 192.168.0.1 - 10 is network infrastructure 11 - 29 is servers 30 - 39 is laptops 40 - 49 is cellphones and tablets
100 - 119 is media devices 120 - 139 is light bulbs 140 - 149 is ip cameras 150 - 159 is iR blasters 160 - 180 is other devices
200 - 250 is DHCP pool
250 up is for testing
Everything has a place and I have a table with ip's and Mac addresses. Now here is where it gets interesting, because everything has already been assigned an IP there is no real need for DHCP except for when mates come over. So I have Hassio scan 200 - 250 every 10 mins and it sends a notification to me if it finds a device. Early warning if someone is on my network that shouldn't be there

I do something similar but have DHCP hand out ips based on Macs. I have three vlans. Lots of fun!

 

[riscbroker]

So now that the Home Assistant bug has bitten properly, I'd like to set up an install on a Samsung NC10 that is unused. This is a 32 bit machine, 2GB RAM, 1.60 GHz Atom processor. I currently have it dual booting Windows 7 and Ubuntu 16.04.

I've tried a few methods of installation: in a VM on Windows, in a VM on Ubuntu, and with a script install, but I'm getting nowhere.

I understand that the 32 bit processor may impose a limitation (Docker??) but I'm battling to find an install method that will work on this particular architecture. Am I wasting my time or is there a build/image of Home Assistant/HassOS/Hass.io that I can successfully install on this machine?

 

[Tinuva]

So now that the Home Assistant bug has bitten properly, I'd like to set up an install on a Samsung NC10 that is unused. This is a 32 bit machine, 2GB RAM, 1.60 GHz Atom processor. I currently have it dual booting Windows 7 and Ubuntu 16.04.

I've tried a few methods of installation: in a VM on Windows, in a VM on Ubuntu, and with a script install, but I'm getting nowhere.

I understand that the 32 bit processor may impose a limitation (Docker??) but I'm battling to find an install method that will work on this particular architecture. Am I wasting my time or is there a build/image of Home Assistant/HassOS/Hass.io that I can successfully install on this machine?

Why Ubuntu 16.04? Why not 18.04 at the very least.

That said, there is a 386 docker image.
https://hub.docker.com/r/homeassistant/home-assistant/tags

So when you say, installation using a script, which script is this?

I would recommend the supervised installer at https://github.com/home-assistant/supervised-installer

If you run 32bit linux, you need to pass that flag on:

• qemux86

Ignore the warning at the top that says the install method is deprecated.
See: https://www.home-assistant.io/blog/2020/05/26/installation-methods-and-community-guides-wiki/

Edit: Actually I see the guide is now at https://community.home-assistant.io/t/installing-home-assistant-supervised-on-ubuntu-18-04-04/200020