dash widget not working
I am trying today to have dash working with homarr.
dash is running on the same docker network as homarr so basically same gateway, dash is not configure with nginx because i do not want it exposed to the internet.
when i go to the integration page on homarr with the docker ip of dash i save it and success.
then i go to create the system resources widget then select dash but i get an error on the widget that says
TRPCClientError: Failed to parse integration data

14 Replies
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?
browser console log
Can you post the docker / server log? There should be the reason in it why it got a parse error for the integration
not sure if the same but i spent ages trying to resolve this - turned off having "storage" disabled in the dashdot widget was the issue. i think homarr was failing when the storage array was empty (even if the widget had storage disabled). @MasterDingo
When I run
curl -v http://192.168.2.4:3001/info
on Windows, I get the system information in valid JSON format.@superht can you post your
http://192.168.2.4:3001/info
?
Is there anything like storage: []
For me it seems more like the response we get is not json, so is there a proxy or something in between? Can you set
LOG_LEVEL
to debug
so it lists all requests like Dispatching request xyz
. Then we can check the urlThere is no "storage". I tried turning storage on and off in the dashdot, but "storage" still doesn't appear.
Okay I think I now understand, you get a json parse error because of the storage which probably either returns 404 or at least html instead of json, I would suggest you to upvote https://github.com/homarr-labs/homarr/issues/2933
GitHub
bug: System Health Monitoring app Errors when dashdot's storage wid...
Describe the bug Having Dash-dot's storage widget disabled breaks system health monitoring app. Steps to reproduce Have a working dash dot integration connected to a System Health Monitoring ap...
I recently ran into the same issue, where it was working then stopped.
I had changed Dash in the docker compose file. I removed storage and it broke with error "Failed to parse json"
DASHDOT_WIDGET_LIST: 'os,storage,cpu,ram,network' # default 'os,cpu,storage,ram,network'
So if he sets it to the default it should work again, unless he's running into a different issue.
If he never had it working he may need to add this to his dash configuration:
DASHDOT_ROUTING_PATH: '/dashdot'
remember to save the config then "compose up" again and it should recreate Dash. you can also stop and rm it to make sure you're starting a fresh Dash. then click retry in Homarr
So is my understanding correct:
The dashdot running on unRAID is not outputting
storage
information, causing homarr to fail to display properly. (On my Synology, dashdot outputs storage information normally and homarr displays correctly.)
Moreover, the issue isn't just with homarr - the main problem lies with dashdot running on unraid. Regardless of whether DASHDOT_WIDGET_LIST
has storage
enabled or not, dashdot doesn't output storage
information properly.
Therefore, I suggest having homarr ignore the storage information.agree that it looks like a json parsing error on homarr's end. when my storage was empty it would not work in homarr with the parse errors. I have managed to getmy dashdot storage working on unraid (latest versions of unraid/dashdot/homarr). my relevant dashdot environmental variables:
-
DASHDOT_WIDGET_LIST
os,cpu,ram,storage,gpu
- DASHDOT_STORAGE_LABEL_LIST
brand,size,type
- DASHDOT_FS_VIRTUAL_MOUNTS
shfs,/dev/nvme1n1p1
- DASHDOT_FS_DEVICE_FILTER
nvme0n1,nvme1n1,sba,sdb,sdc...etc
- DASHDOT_STORAGE_POLL_INTERVAL
30000
- DASHDOT_OVERRIDE_STORAGE_BRANDS
shfs=Array,/dev/nvme1n1p1=Cache
(there is a bug renaming virtual mounts in dashdot not working properly)
