It only changed in this release.
The base_url under tts allowed you to use base_url under http without trying to have the tts routed externally.
So previously I had my base_url set to my external FQDN this would make the google home devices try to use the FQDN which didn’t work (before I changed my router out due to no hairpin NAT).
1 Like
Sorry, missed that it was the tts config you were talking about. I must be blind, you mentioned it more than once.
1 Like
I am using SSL/HTTPS for my local communication, too. I was hoping that I could use TTS without disabling SSL - but there is no way to only use http for tts? I tried usting http://local-ip in the base_url in the TTS setup but that would not work - only the https://mydomain.duckdns.org works flawlessly.
There appear to be a couple of issues:
- The async_get_events method in the Todoist integration (which the Calendar API calls to get the events for a specific date range) can’t handle tasks without a due date and throws an error. (I’ve posted a comment regarding that on this issue)
- If any calendar throws an error, the entire calendar panel will display blank
I found that, with mine, it was my Alexa Shopping List calendar (synced from Alexa to Todoist) which caused the issues and deselecting that calendar allowed the events to appear.
1 Like
Tom are you using secrets for the base URL config in the GUI?
and solved: https://github.com/home-assistant/frontend/issues/6044#event-3371156457
thanks Bram for the immediate action!
1 Like
well, base_url is no longer supported according to the docs for tts: ànd http:
you use it for tts: to keep it talking, and I use it under http: …
tts:
- platform: google_translate
service_name: google_say
cache: false
http:
base_url: !secret base_url
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: true
login_attempts_threshold: 10
isn’t that odd?
Apparently it’s now undocumented, but I assure you base_url works for google_translate, one would assume it would default to use internal_url if present and fallback to external_url. 
maybe, but I had proof it didn’t…
guess we would have to ask Frenck if base_url for either of the options should result in an error, and why tts would function without it.
Happy I got it working right now, will follow the development on this closely 
1 Like
I’m finding that as well but on 0110.1 as well…well described!
No, in configuration.yaml.
Did you solve this? I’m seeing the same behaviour and is having trouble making connection via browser
not sure what caused it, but not seeing the error anymore
I had the same. I fixed it by changing theme from “backend-selected” to “default” (or any other theme).
I now notice this:
stating it uses the internal_url by default if no base_url is set. In my setting internal_url is not set manually, nor is it in .storage/core.config which has:
"internal_url": null,
So I guess (will test shortly) that without either (base_url under tts: or internal_url under homeassistant:) tts won’t know where to speak 
Having said that, I would hope that using the local address, or internal_url, would prevent startup speech issues, since it wont have to go all over the world to speak over my internal intercom
Lets try!
2 Likes
That is not the solution. I’m still using backend selected. This is the solution:
Update HACS. Restart HA and clear your browser cache.
well, I can get any internal_address to work, unless I set it to my external_address, or previous base_url for that matter.
checking the core.config, I still see
"internal_url": null,
even though Ive explicitly set it to:
homeassistant:
name: Ha Rpi4
internal_url: !secret base_url
in the configuration.yaml
what’s even more surprising, that in the .storage/http file, I see this:
{
"data": {
"cors_allowed_origins": [
"https://cast.home-assistant.io"
],
"ip_ban_enabled": true,
"login_attempts_threshold": 10,
"server_host": "0.0.0.0",
"server_port": 8123,
"ssl_certificate": "/ssl/fullchain.pem",
"ssl_key": "/ssl/privkey.pem",
"ssl_profile": "modern"
},
"key": "http",
"version": 1
}
shouldn’t there be an internal server listed? 0.0.0.0 hardly would go anywhere?
I cant seem to use the local ip addresses in a browser window either, only
the https://hassio-3.local:8123 (I’ve checked, host name still is hassio, not homeassistant) and this is 1 of 3 instances on my network. Previously all were hassio systems, with the suffix added automatically.
This bit just means “listen on ALL interfaces (ie: eth0, eth1, eth0-ipv6, eth1-ipv6)”
Is there any way to choose/save a preferred view in the calendar panel? I would like it to default to week view instead of month view. And the week should also start on a monday…