1 hour ago, bubbl3 said:

You have a trailing comma there:

"plugins": {
    "unraidclaw": {
      "serverUrl": "http://192.168.50.122:9876",
      "apiKey": "7f3fa56ce...",   ← trailing comma
    },

It should be:

"plugins": {
    "unraidclaw": {
      "serverUrl": "http://192.168.50.122:9876",
      "apiKey": "7f3fa56ce..."
    },

In general you seems a bit inexperienced here, would suggest reading docs and asking for help in the OpenClaw subreddit, having an LLM writing your config means you won't really know how it works. Also not sure what LLM you're using, it should have catched the trailing comma, it's basic JSON.

Thank you for taking a look at the .json file for me. seems like after making the correction you suggested, I still get the "Invalid openclaw.json unriadclaw api key error". Which will refuse to let openclaw start. I will continue to read around and build up my knowledge.

Thanks for your help

Im back, lol...

I made some progress that openclaw can now see the plugin, and the plugin is communicating back with me, but I am now getting a 401 error.

Im sure this has something to do with api. But I have attempted to re-create the unraid and openclaw api multiple times. Can anyone point me in the right direction?

log

edit: I think this could be a new bug not dealing with unraidclaw

https://github.com/openclaw/openclaw/issues/77800

Edited May 27May 27 by Mrtj18

19 hours ago, Mrtj18 said:

Im back, lol...

I made some progress that openclaw can now see the plugin, and the plugin is communicating back with me, but I am now getting a 401 error.

Im sure this has something to do with api. But I have attempted to re-create the unraid and openclaw api multiple times. Can anyone point me in the right direction?

log

edit: I think this could be a new bug not dealing with unraidclaw

https://github.com/openclaw/openclaw/issues/77800

From the screenshot you can see the calls are not API calls but just http requests for the index page and it's favicon. Basically your OpenClaw instance is trying to open a webpage, not making API calls.

19 hours ago, bubbl3 said:

From the screenshot you can see the calls are not API calls but just http requests for the index page and it's favicon. Basically your OpenClaw instance is trying to open a webpage, not making API calls.

That's odd, I don't have any websites I'm attempting to visit. Plus when I type in any command listed from your GitHub page ( like unraid_list_disk) I receive unraid not connected responses from openclaw.

I also receive the same error others have from your GitHub page when I click on the link that the logs provide when attempting to connect to your plug-in. Attached in the screenshot. Your instructions from the GitHub page says just to double check the openclaw.json file and restart the service along with creating a new key. But I still receive the same error.

On 5/29/2026 at 5:25 AM, Mrtj18 said:

That's odd, I don't have any websites I'm attempting to visit. Plus when I type in any command listed from your GitHub page ( like unraid_list_disk) I receive unraid not connected responses from openclaw.

I also receive the same error others have from your GitHub page when I click on the link that the logs provide when attempting to connect to your plug-in. Attached in the screenshot. Your instructions from the GitHub page says just to double check the openclaw.json file and restart the service along with creating a new key. But I still receive the same error.

What I mean is that the calls in the logs are not API calls, they are simple http calls like the ones you just showed in the screenshot from your phone. This is not how the service is supposed to be accessed so the error is expected.

Edited May 30May 30 by bubbl3

Mmmm.... Maybe there's something I don't understand here, if I typed into openclaw, " what's my Unraid drive health" it should be about to see my unraid drives and provide feedback correct?

Because when I do that, the following results is what I get , in my previous posts.

But thanks for the assistance!

Hey @bubbl3!

I just wanted to thank you for the plugin, it's really useful. I've opened an issue today in Github because the /api/array/parity/status endpoint is just giving the info from the GraphQL API, which is not useful, while you could use the output from mdcmd status.

I'm using a read-only API Key from Hermes Agent and I don't want to give it SSH access, leave alone root.

Thanks a lot!

On 6/3/2026 at 4:11 AM, Mrtj18 said:

Mmmm.... Maybe there's something I don't understand here, if I typed into openclaw, " what's my Unraid drive health" it should be about to see my unraid drives and provide feedback correct?

Because when I do that, the following results is what I get , in my previous posts.

But thanks for the assistance!

Ask Openclaw about the unraid tools available, this is the kind of answer you should be getting:



If it says can't find the tools, ask to look in its configuration file and build a reference for itself so it can easily find them. If it really can't find them then there's an issue with your config.

16 hours ago, adriagarcia said:

Hey @bubbl3!

I just wanted to thank you for the plugin, it's really useful. I've opened an issue today in Github because the /api/array/parity/status endpoint is just giving the info from the GraphQL API, which is not useful, while you could use the output from mdcmd status.

I'm using a read-only API Key from Hermes Agent and I don't want to give it SSH access, leave alone root.

Thanks a lot!

That was actually a very good suggestion, I never considered it, made the change and released v0.1.31: https://github.com/emaspa/unraidclaw/releases/tag/v0.1.31

@Mrtj18 you may want to update the OpenClaw plugin (assuming you are on a June build of OpenClaw), the new version of the NPM package takes advantage of the new features to better declare the tools available: https://github.com/emaspa/unraidclaw/issues/15#issuecomment-4698083784

On 6/13/2026 at 4:11 AM, bubbl3 said:

@Mrtj18 you may want to update the OpenClaw plugin (assuming you are on a June build of OpenClaw), the new version of the NPM package takes advantage of the new features to better declare the tools available: https://github.com/emaspa/unraidclaw/issues/15#issuecomment-4698083784

Wow, after giving this a break for a while, from being frustrated, because i was obviously something I was doing wrong. I did what you suggested, by updating both openclaw and using the command you just provided of "npm i [email protected]" within the Openclaw console, then asking the basic question of " what unraid tools do I have available?". Then boom, I finally got responses from my server.

Thank you so much fort your patience!