-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
[Errno 104] Connection reset by peer from Spotcast #511
Comments
@mfabiani53, this look like a connection issue with Spotify.
Is it a constant issue or only momentarily? You say tons of errors, how many? Can you provide a debug log so we get more information on the situation? |
It happens constantly... i see those errors everyday. How to have a debug log? This is from today log:
|
@mfabiani53 that one would be a different issue. I'll open a new ticket for that one.
By going into the Integration dashboard in Home Assistant, clicking on Spotcast and then You can go through that link to go directly to your server's Spotcast Integration screen Please provide a debug log, so we can look further into the 104 error. |
Ok, done. How much i must wait to send you the log? |
@mfabiani53 you let it run for a while, making sure the error you want is triggered and then deactivate. It will download the file directly in your browser |
Here it is, but cannot find the errors we are discussing about... Logs
|
This while playing some music on one of my devices... logs
|
It seems all ok.... |
@mfabiani53 I don't see any errors in the logs you sent. Good news is that, the 104 error is not a constant one. That would have mean your network stack would have been at fault probably. I can see you are able to get tokens and all sensors seem to be able to load. My best guess currently for the 104 might have been the Spotify Proxy you tried to reach was being overloaded, so it wasn't even able to respond with a 503 error which would mean its unable to serve you at the moment, it simply declined the new connection, so the TCP relay replied back with a 104 error. I'll make 104 error a warning instead of a traceback error, that still means they will register. Its not something that can be fixed at the integration level. |
@mfabiani53 quick tip, you can drag and drop a file in Github, it will upload it and create a permalink. Its much easier to parse through |
Ok, glad to help you... |
The problem
I am getting ton of these errors and really don't know the meaning of them and the reasons...
Any hints?
Hope this helps....
System Health details
System Information
Home Assistant Community Store
AccuWeather
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Spotcast
Spotify
What type of installation are you running?
Home Assistant OS
Diagnostics information
ersione | core-2025.1.4 -- | -- Installation type | Home Assistant OS Sviluppo | false Supervisor | true Docker | true Utente | root Virtual environment | false Python version | 3.13.1 Operating system family | Linux Operating system version | 6.6.62-haos-raspi CPU architecture | aarch64 Fuso orario | Europe/Rome Configuration directory | /configExample YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: