Update 6/23/26: This seems to be fixed now with UNRAID Connect v4.35.1. 4.35.1 (2026-06-18)
Bug Fixes:
api: isUpdateAvailable returns null for all containers when cache has an undef entry (#2030) (b166407) Original Post: I've been having an issue with apps like nzb360 and the UNRAID integration for Home Assistant to report available updates for my Docker containers. I've tried creating new API keys with ADMIN permissions and restarting the API service. I’m currently on UNRAID 7.3.1 stable with the latest UNRAID Connect API (2026.06.01.1911 ), and Docker updates show correctly in the UNRAID WebUI. I've enabled the Developer Sandbox to test responses from the /graphql and have noticed that isUpdateAvailable is returning null. Should this not be returning a boolean? curl -k https://MY_UNRAID:PORT/graphql \
-H "x-api-key: MY_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"query { docker { containers { names isUpdateAvailable } } }"}'
{"data":{"docker":{"containers":[{"names":["/SearXNG"],"isUpdateAvailable":null},{"names":["/mariadb"],"isUpdateAvailable":null},{"names":["/Nextcloud"],"isUpdateAvailable":null}, ... Other responses like isRebuildReady are returning boolean values: curl -k https://MY_UNRAID:PORT/graphql \
-H "x-api-key: MY_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"query { docker { containers { isUpdateAvailable } } }"}'
{"data":{"docker":{"containers":[{"isRebuildReady":false},{"isRebuildReady":false}, ... I'm guessing that this is probably confirming why these 3rd party apps aren't reporting any Docker updates? I've attached a diagnostics zip. Any help is greatly appreciated. Thanks! nas-diagnostics-20260616-1123.zip