Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing HA server port from 8123 results in tts.cloud error with Google Cast #45695

Closed
Morphy99 opened this issue Jan 29, 2021 · 2 comments
Closed
Assignees

Comments

@Morphy99
Copy link

Morphy99 commented Jan 29, 2021

The problem

After changing my HA instance port away from 8123 tts.cloud seems to be broken. If I change back this works OK again.
Casting local media works as before. Just tts.cloud isn't working.

- service: tts.cloud_say
  data:
    message: any random message
    entity_id: media_player.bedroom_nest

Environment

  • Home Assistant Core release with the issue: 2021.1.5
  • Last working Home Assistant Core release (if known): -
  • Operating environment (OS/Container/Supervised/Core): Container
  • Integration causing this issue: tts /google cast
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/tts/

Problem-relevant configuration.yaml

This is how I changed the HA port:

http:
  server_port: 8089

I have tried this in configuration.yaml:

  - platform: cloud
    service_name: cloud
    base_url: https://myURL.ui.nabu.casa/

Still the same error below with the local IP

Traceback/Error logs

Source: components/cast/media_player.py:348
Integration: Google Cast (documentation, issues)
First occurred: 9:31:03 (5 occurrences)
Last logged: 9:32:49

Failed to cast media http://192.168.x.x:8123/api/tts_proxy/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx_en-us_a9c18110b0_cloud.mp3 from internal_url (http://192.168.x.x:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address

Additional information

@probot-home-assistant
Copy link

Hey there @pvizeli, mind taking a look at this issue as its been labeled with an integration (tts) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@Morphy99
Copy link
Author

Morphy99 commented Feb 8, 2021

Never mind. I forgot all about the internal_url which is in general settings in lovelace. I've now put it in configuration.yaml just to remind my future self 😄

@Morphy99 Morphy99 closed this as completed Feb 8, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Mar 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants