core: Spotify Integration stops to work with 0.115 HA

The problem

After update to 0.115 version in integration page the spotify integration ask to be riconfigured. I’ve pushed the button and the system say “operation aborted”. Then I’ve tried to reinstall integration by ui interface and the system says “operation aborted”. Now my spotify integration and entities desappered

Environment

HassOS installation HassOS 4.13 Supervisor 245 stable HA 0.115 Hardware Rasperry PI4 4GB

Previusos HA 0.114.4 spotify working correctly

Problem-relevant configuration.yaml


Traceback/Error logs

NO logs was detected


Additional information

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 8
  • Comments: 32 (13 by maintainers)

Most upvoted comments

@Sholofly he got the answer, just put this in your configuration.yaml, it worked for me.

homeassistant: external_url: “https://www.example.com” internal_url: “http://homeassistant.local:8123

@Sholofly I’am experiencing the same problem, when updating to the new version (0.115) it asked to reconfigure spotify. When I did that from the integration menu after pressing reconfigure it popped a message “aborted” without an error, So I deleted the integration completely and reconfigured it, but if I try to add the integration and configure it, it immediately pops up a message “aborted”, it doesn’t show any errors in the logs, I also have installed spotcast and the spotify-card. edit: (it is not a custom component error as I disabled them all temporary without succes)

For those still struggling even when they have internal_url and external_url set, be sure to access you HA instance using exactly the domain you have in your URL’s. I have “canonical” URL for my HA which looks like hass.example.com, however I also aliased it as example.com. When I was accessing HA using example.com, I kept getting the Aborted error. But when I accessed it using hass.example.com, everything finally worked.

I had spotcast installed, Uninstalled it and rebooted but same result.

Anything in the logs? As in, I’m not having this issue and there is not much to work with / go on in this issue.

Some additional pointers: