2 ms·
Sadly Google Assistant does need to use the DNS setup because I play local media for announcements on it and every time the DNS is broken it stops working and d
by jeena 5y ago
Sadly Google Assistant does need to use the DNS setup because I play local media for announcements on it and every time the DNS is broken it stops working and doesn't play any local media anymore. Basically home assistant media player plays a mp3 which is stored on the raspberry pi on the Google Assistant, for example when someone opens the out door it plays a chime on all Google Assistants in the whole house so that my parents know that someone opened the door downstairs. The url will be https://myparentshouse.duckdns.org/local/open-door.mp3 https://myparentshouse.duckdns.org/local/open-door.mp3 so if the Google Assistant doesn't use the local DNS it can't resolve the domain to the local raspberry pi, and instead resolves it to the public IP address which then without the Loopback NAT doesn't go anywhere.
I understand that I should then instead of using Google Assistant for that to use something else, but I haven't found any free hardware which would have the functionality of good microphones and working speech to text yet.
- jeroenhd 5y agoIn that case I'd find a way to put the file universally accessible on the internet somehow (the proxies I mentioned, or IPv6, through HE Tunnelbroker if necessary, or on a random HTTP host you might control?). Debugging split DNS issues can take hours and luckily there are free and cheap tools to avoid this mess! They require some setup, but in my opinion the lack of maintenance they require is much easier to live with than the split-DNS-mess. I haven't seen much evidence of Google hardware actually using DoH, but they will definitely use 8.8.8.8. If your router has the ability, you could try forcing traffic intended towards 8.8.8.8:53/udp to your router's DNS server.