compatible with home assistant WUD card?

[seebats]

Hi there,

I just came from WUD and I really love Drydock so far. With WUD I used wud-card in Home Assistant to trigger and check updates (https://github.com/angryvoegi/wud-card). However I'm unable to set it up using Drydock, as it cannot reach the server.

I have enabled server_cors , origin and methods.
The url http://hostname:3000 is accessible in the browser and data is visible when entering http://hostname:3000/api/containers.

Are there any changes with regard to WUD that would clarify why this would not work? And what changes would I have to make to make this card work with Drydock?

[scttbnsn]

It won't work as-is, and it's not your setup. Two separate things are going on:

The real blocker is response shape. In v1.4.0 drydock standardized its collection endpoints to return { "data": [...], "total": ... } instead of WUD's bare arrays. wud-card was written against WUD's shape, so it calls .forEach() on our response object, that throws, and the card's own error handler reports it as "cannot reach the server". The red dot is misleading: your server is reachable (your browser test proves that), the card just can't parse what it gets back.

CORS is worth double checking anyway. DD_SERVER_CORS_ORIGIN has to be the exact origin your Home Assistant frontend is served from (e.g. http://homeassistant.local:8123), not drydock's own address. Typing the URL into the address bar never sends an Origin header, so that test doesn't tell you whether CORS is right. But even with CORS perfect, the card still fails on the shape above.

What we're doing about it: v1.6.0 ships an opt-in compatibility flag, DD_COMPAT_WUDCARD=true, that serves WUD-shaped responses on exactly the endpoints the card calls, so wud-card works unmodified. Heads up that v1.6.0 also removes the deprecated unversioned /api/* paths, which the card hardcodes; the compat flag is the supported exception that keeps it working past that.

If you want it working today, you can patch the card locally, it's a couple of lines in wud-card.js: unwrap the data field on the two GET responses (containers.data.forEach(...) instead of containers.forEach(...), and store triggers.data instead of the raw triggers response). Once v1.6 lands, the stock card plus the flag is the supported setup.