OpenMediaVault Integration Errors on CPU Temp

Hello, I set up a fresh Docker install using latest (v1.2.0) on OMV 7.5.2-1, then configured the integration for Homarr to get System Health statistics. After figuring out which groups the user I created for the connection, I am now getting an error in the logs, which are in a codeblock down below. Based on what I saw in Homarr repository, it seems as the RPC response isn't returning CPU statistics. I could be missing one of the default groups OMV provides, but I couldn't find the needed groups for the API user to have. Thanks!
21 Replies
Cakey Bot
Cakey Bot2mo ago
Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
latenightwreck
latenightwreckOP2mo ago
Logs:
2025-01-27T13:50:07.059Z info The callback of 'healthMonitoring' cron job succeeded (before callback took 3 ms, callback took 5 minutes)
2025-01-27T13:50:10.358Z info The callback of 'mediaServer' cron job succeeded (before callback took 2 ms, callback took 5 ms)
2025-01-27T13:50:10.358Z info The callback of 'downloads' cron job succeeded (before callback took 2 ms, callback took 5 ms)
2025-01-27T13:50:10.358Z info The callback of 'dnsHole' cron job succeeded (before callback took 2 ms, callback took 5 ms)
2025-01-27T13:50:10.360Z info Dispatching request http://192.168.1.25/rpc.php (7 headers)
2025-01-27T13:50:10.455Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:11.491Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:11.647Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:12.002Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:12.024Z error Failed to run integration job integration=isc6uxta490q7h6ypcc52gc8 inputHash='W3t9XQ==' error=Error: Invalid CPU temperature response
at _OpenMediaVaultIntegration.getSystemInfoAsync (/app/apps/tasks/tasks.cjs:448993:13)
at async Object.requestAsync (/app/apps/tasks/tasks.cjs:451665:12)
at async Object.requestAsync (/app/apps/tasks/tasks.cjs:450499:16)
at async requestNewDataAsync (/app/apps/tasks/tasks.cjs:450453:26)
at async Object.getCachedOrUpdatedDataAsync (/app/apps/tasks/tasks.cjs:450464:20)
at async /app/apps/tasks/tasks.cjs:451615:9
at async catchingCallbackAsync (/app/apps/tasks/tasks.cjs:437700:9)
2025-01-27T13:50:07.059Z info The callback of 'healthMonitoring' cron job succeeded (before callback took 3 ms, callback took 5 minutes)
2025-01-27T13:50:10.358Z info The callback of 'mediaServer' cron job succeeded (before callback took 2 ms, callback took 5 ms)
2025-01-27T13:50:10.358Z info The callback of 'downloads' cron job succeeded (before callback took 2 ms, callback took 5 ms)
2025-01-27T13:50:10.358Z info The callback of 'dnsHole' cron job succeeded (before callback took 2 ms, callback took 5 ms)
2025-01-27T13:50:10.360Z info Dispatching request http://192.168.1.25/rpc.php (7 headers)
2025-01-27T13:50:10.455Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:11.491Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:11.647Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:12.002Z info Dispatching request http://192.168.1.25/rpc.php (8 headers)
2025-01-27T13:50:12.024Z error Failed to run integration job integration=isc6uxta490q7h6ypcc52gc8 inputHash='W3t9XQ==' error=Error: Invalid CPU temperature response
at _OpenMediaVaultIntegration.getSystemInfoAsync (/app/apps/tasks/tasks.cjs:448993:13)
at async Object.requestAsync (/app/apps/tasks/tasks.cjs:451665:12)
at async Object.requestAsync (/app/apps/tasks/tasks.cjs:450499:16)
at async requestNewDataAsync (/app/apps/tasks/tasks.cjs:450453:26)
at async Object.getCachedOrUpdatedDataAsync (/app/apps/tasks/tasks.cjs:450464:20)
at async /app/apps/tasks/tasks.cjs:451615:9
at async catchingCallbackAsync (/app/apps/tasks/tasks.cjs:437700:9)
Docker file:
services:
homarr:
image: ghcr.io/homarr-labs/homarr:latest
container_name: homarr
restart: unless-stopped
environment:
- PUID=${DOCKERUSER_UID}
- PGID=${DOCKERUSER_GID}
- TZ=${TIME_ZONE}
- SECRET_ENCRYPTION_KEY=<KEY>
volumes:
- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- $BASE_PATH/homarr/config:/appdata
ports:
- '7575:7575'
services:
homarr:
image: ghcr.io/homarr-labs/homarr:latest
container_name: homarr
restart: unless-stopped
environment:
- PUID=${DOCKERUSER_UID}
- PGID=${DOCKERUSER_GID}
- TZ=${TIME_ZONE}
- SECRET_ENCRYPTION_KEY=<KEY>
volumes:
- /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
- $BASE_PATH/homarr/config:/appdata
ports:
- '7575:7575'
latenightwreck
latenightwreckOP2mo ago
Homarr Widget setup:
No description
Manicraft1001
Manicraft10012mo ago
Hi, thanks for the request. We already answered this here: https://www.answeroverflow.com/m/1332443358940889118 I will mark this as solved. Thank you
OMV and Proxmox integration, 1.2.0 - Homarr
Having issues after the migration
latenightwreck
latenightwreckOP2mo ago
now just the OMV sensor reading problem is the one to solve
The last comment from Alea says that this still hasn't been solved. Am I missing the solution for the OMV problem?
Manicraft1001
Manicraft10012mo ago
No, but we are working on the fix.
latenightwreck
latenightwreckOP2mo ago
OH so i did miss the solution, its called code 😄
Manicraft1001
Manicraft10012mo ago
So just wait and update your Homarr frequently. It will magically "fix itself" as soon as we release the fix
latenightwreck
latenightwreckOP2mo ago
tysm. Is there a GH issue I could track? OH yes it is
Manicraft1001
Manicraft10012mo ago
At this time, not for the problem you are experiencing. The linked thread also found another issue that we already have a fix for. Can you submit a ticket on GitHub and then we'll put it into the backlog
latenightwreck
latenightwreckOP2mo ago
will do! sorry i was still reading issue #2094 thinking it was this one
latenightwreck
latenightwreckOP2mo ago
https://github.com/homarr-labs/homarr/issues/2145 just threw something up quickly, but at least attached logs 🙂
GitHub
bug: OpenMediaVault Integration Errors on CPU Temp · Issue #2145 · ...
Describe the bug I set up a fresh Docker install of Homarr using v1.2.0 on OMV 7.5.2-1, then configured the integration for Homarr to get System Health statistics. After figuring out which groups t...
Yossi
Yossi2mo ago
No description
Yossi
Yossi2mo ago
Work’s for me
Manicraft1001
Manicraft10012mo ago
That's likely because your system has access to the sensor and OP's has not I think the temp sensor is optional in OMV, no?
Yossi
Yossi2mo ago
Did you install CPU temp plugin?
Solution
Yossi
Yossi2mo ago
No description
Yossi
Yossi2mo ago
Yes
latenightwreck
latenightwreckOP2mo ago
im OP. let me check. IS that said in documentation for the integration? did not have it installed. rebooting after install. will let you know @Manicraft1001 Installing the above plugin (openmediavault-cputemp) resolved the issue. For the created ticket, would you prefer a delete and then add one for documentation to mention this needed cpu-temp?
Manicraft1001
Manicraft10012mo ago
No, the integration should be able to cope when the addon is not installed. But you can add this hint to the documentation yourself.
latenightwreck
latenightwreckOP2mo ago
Will do. Thank you for your help, and thank you @Yossi for the insight to point out the plugin!

Did you find this page helpful?