Logs? Crystal ball crashed.
3 Likes
Where can I found the logs for it? I have enabled debugging log for it, but don’t know where it is located.
It’s called home-assistant.log it is in the same directory as configuration.yaml. Configuration.yaml - Home Assistant
Thank you! This is what appears in the log:
2024-02-27 10:46:34.717 DEBUG (MainThread) [homeassistant.components.fronius] Finished fetching fronius_logger_192.168.50.218 data in 3.273 seconds (success: False)
Fronius is still working for me. Was fine the whole way through the 2024.2.x versions.
Can you ping 192.168.50.218?
Since this release i am facing an issue with database corruption and log.fault.
It happens when i try to purge the DB.
You can see more details here: Database Corrupted - #14 by michaelkrtikos
I came home late from yesterday and the inverter became unavailable naturally since the sun was no longer up. I will check today, but through my energy supplier’s app I can still track it.
new warning logged starting with 2024.2.4:
Logger: zigpy.ota.provider
Source: runner.py:188
First occurred: 7:50:13 AM (2 occurrences)
Last logged: 7:50:30 AM
Salus: Couldn’t download ‘https://eu.salusconnect.io/demo/default/status/firmware’: 500/Internal Server Error
check the url in your browser
Beside it’s 500 http(s) error, to external source, so nothing to do with HA
1 Like
the warning is originating from the zigbee integration and did not exist prior to v2024.2.4 so it has something to do with HA
500 error is when trying to conenct to something external. It’s telling you that there’s an issue with what HA is trying to connect to. I.e. https://eu.salusconnect.io/demo/default/status/firmware, so no, it’s not a home assistant issue.
1 Like
this is an issue with zha integration and ota.
i will submit an issue on the integration.
Ok, but the error is an internal server error and the server is https://eu.salusconnect.io/demo/default/status/firmware
Done 100% outside HA, just in a browser. Try it yourself, use edge or any other browser.
EDIT: Puddly mentions that the server provider (I.e. the endpoint above) was shut down.
2 Likes
When pinging I get nothing, it is not responding. It has worked for almost a year with no issues and it works with Tibber. I can’t figure out what might be the issue.
If you try as i suggested, and even Petro(with T) showed you, It Is an error in the Browser !
Even, if you remove “firmware” , same error, and if you remove “/status”, same, and if you remove/default, you get an Access-Denied (not an error actually)
500 is thrown when a Browser, don’t know what else to “say” because the error most likely is at OS level (hint-Server-error)
The Web-server has no idea, why the “resource” is unavailable , this could be i.e a mount-error at os level ( which above path-search could indicate ) /default is not to be found, allthou the web-server, works with all links/path etc ( It’s not aware of i.e certain mount-issues on OS level )
500 from webserver, is basically “Unknown Error at OS/Hardware Level” Or deep in the Webserver, beyond front-end
1 Like
HA has a PR to switch the provider. So something is being done about the shutdown of the previous provider.
1 Like
I don’t have ZHA ota enabled. I’m also getting the could not download error. I’d rather not be downloading files from https://eu.salusconnect.io/demo/default/status/firmware at all. Is there a way to disable ZHA ota downloads completely?
Well there’s nothing to worry about because the server isn’t running or serving up files.
EDIT: From the sounds of it, it’s not getting turned back on either.
1 Like
But the question remains, why is ha checking for updates when is zha is not enabled. This is effectively phoning home to salusconnect for no reason. What happened to privacy?
Yes, it concerned me to see Home assistant attempting to contact and download from a server I didn’t recognize.