Hey, this add on looks like what I need. I’m trying to add the repository to home assistant, but it’s saying invalid repository. Is this a known issue, This is my first attempt at adding a custom add on to home assistant…
hey @baykelper ,
Are you following instructions at ha-addon-dnsmasq-dhcp/DOCS.md at c975ab14ca2f744ceb43aa649e3b35aa78fb899b · f18m/ha-addon-dnsmasq-dhcp · GitHub ?
hi, i had,
looked through the source and saw reference to nginx, so i added that and let’s encrypt addons, and it added fine, i’ll configure now.
i’m not sure if that was the issue, The other thing is that as i recall i probably used the elipses, add repository dialog, directly (i would assume that should work also?)
thanks again!
A couple more questions, Can any configs be exposed via samba share? I.e. I’d like to save etc/ hosts (and edit, manage it). For host to ip mapping ,
I don’t see local host names in the dns portion of the gui.
I’m not sure where the mount of the docker:/etc/hosts to home assistant:/addon_configs/dns_dhcp/etc/hosts. Would be done.
Can any configs be exposed via samba share? I.e. I’d like to save etc/ hosts (and edit, manage it).
In a nutshell: it’s technically feasible but I don’t suggest you to go down that path.
If you have full access to the Linux box running HomeAssistant, you will find the config for the addon under /usr/share/hassio/addons/data/79957c2e_dnsmasq-dhcp in the options.json file.
If you mount via Samba that folder/file, then you have the addon config being read by HomeAssistant from a remote folder.
This might work or might not (home assistant & supervisor are docker containers so I’m not 100% sure it would be able to access files living in a remote samba share transparently).
However are you really sure you want to have the configuration of your DHCP server in a remote location? DHCP is a critical protocol in a network to get connectivity and you should try to make DHCP as resilient as possible. Mounting its config from another network location is probably going to increase the chances of the DHCP addon not being to run.
If the samba server is getting its ip via DHCP… then you have a circular dependency: you need the samba server to have a DHCP server working to get/renew its lease, but your DHCP server needs the samba server already up to work…
I don’t see local host names in the dns portion of the gui.
sorry what do you mean?
You mean to say that in the “Current DHCP clients” tab you only see hostnames without the DNS domain qualifier (e.g. “light1” instead of “light1.lan”) ?
If yes… then maybe havea a look at the “link” property under dhcp_ip_address_reservations (see the docs)
what i ment was that after configuring the add-on, i could copy the configs, possibly edit and copy back. i see you opened in issue in git-hub for config as code, so you are looking at it.
I agree that having the addon read its configs from a remote location is no good.
i did eventually figure out the dns hostnames, thanks,
1 Like
Hey all,
Just wanted to share that I had some time for this project in the last couple of weeks and this led to 5 new releases in 1 week time frame 
I cleaned up a lot of the backlog and I feel like the project has really evolved a lot. Please check out the screenshots and the docs at GitHub - f18m/ha-addon-dnsmasq-dhcp: An Home Assistant app that runs dnsmasq both as DHCP server and DNS server · GitHub if you are interested in refreshing your DHCP/DNS servers.
Any feedback is welcome!