Dash widget "Cannot acquire information from dash"
I can view the dash web UI running fine directly on my host at http://192.168.1.59:80, but the widget doesn't work in homarr. I'm only trying to enable internal http access. I don't need external or https. Why doesn't this work?
- OS: Debian 12
- Homarr version: latest tag?
- Dash version: latest tag?
- Server logs: https://pastebin.com/YPexqBec
Relevant docker-compose.yaml config:
Pastebin
ERROR No valid integrations found for health monitoring in 'defau...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
10 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?
Client logs:
Ok actually from the client logs, that dashdot network request's payload is "{"0":{"json":{"url":""}}}", and the response error is telling me the url is invalid, which makes sense, but is the url not sourced from the Dash integration I configured? Where is the url coming from?
Has me wondering if/how the dash integration works at all.
The iframe embedding approach works fine 🤷♂️
Solution
Widgets -> Dash. -> Edit -> Enter URL -> Save
from your screenshot above, you are just making an "app" and leaving the widget unconfigured
@rando1234 see above
Sorry I'm an idiot lol. Pretty obvious now in retrospect. Thanks, that fixed the issue!
All good, seems more common than I would imagine by looking at the get-help posts. Probably why version 1.0 is moving to configuring these in a backend for every user to add to their dashboards