Closed Shinigami777 closed 1 year ago
error 504 is Gateway Timeout. that means omv backend didnt reply in time and its web server cut the session. I dont thing this has anything to do with integration, but you may try to capture the issue with debug on for more details.
I already have a debug file but I don't know how to send or share it?
just upload it here
that is not debug, but HA diagnostic report.
I need to see what was before that error too. That will be the lead.
you forgot to enable debug. otherwise yea, I need to see what is before "[custom_components.openmediavault.omv_api] OpenMediaVault 192.168.1.66:66 unable to fetch data (504)" in debug. we will see what was requested and failed and what happened before that.
no, debug is not turned on
I don't know what I'm doing wrong anymore 😑. I go to Settings -> Devices -> Integrations ->I click 3 dots enable debugging on opemnediavault integration. I re-load integration and stop debugging when integration stopped working. What else or what should I do differently?
hmm, I didnt even knew they added such option. I will have to check how it works later. Normally you add entry to configuration and restart HA: https://github.com/tomaae/homeassistant-openmediavault#enabling-debug
Thank you for the instructions, I will do it and send it. 😁👍 Sorry for the trouble but I'm new to Home Assistant.
I know it's probably a stupid question, but where will I find these logs later?
same place as before, there will just be more info
Will that be enough? Or should I share even earlier logs? error_log 03.txt
Edit. Is something wrong? If you can please help my fix this issue.
Sorry, I missed the reply. You error is error 504 on smart query. Assuming that OMV responds with correct code, it would mean OMV backend is having some kind of trouble. Check smart interface in OMV, if that is working reliably. also check OMV logs at time of failure, maybe you can get more info there.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue was closed because it has been stalled for 5 days with no activity.
Describe the issue
Soon after configurated integration, all entities become inaccessible until the next re-loading of integration
How to reproduce the issue
Steps to reproduce the behavior:
Software versions