Myo Gesture Armband icon Myo Gesture Armband Map Myo armband gestures and accelerometer to servos and ARC scripts for arm-mimic control; supports multiple armbands. Try it →
Asked
Hugging Face Model Not Supported

Hugging Face Model Not Supported

I have a question about the ARC "Hugging Face" Robot Skill.

I set up the API as instructed. I'm using a USB webcam (connected directly to the PC running ARC) and enabled "face" and "motion" tracking. I tried the first example from the Hugging Face Skill documentation, but all I get is this error:

enabled.","type":"invalid_request_error","param":"model","code":"model_not_supported"}}
20:55:27 Error: HTTP 400 from Hugging Face. {"error":{"message":"The requested model 'Qwen/Qwen2.5-VL-7B-Instruct' is not supported by any provider you have enabled.","type":"invalid_request_error","param":"model","code":"model_not_supported"}}

What am I missing?



Related Hardware (view all EZB hardware)
EZ-B V4 by EZ-Robot
EZ-B v4/2 robot controller: dual Cortex ARM, Wi-Fi, audio/video, 24 servo/digital ports, I2C/UART, camera and Synthiam ARC control for custom robots
Wi-Fi / USB
Servos 24
Camera
Audio
UART 3
I2C
ADC 8
Digital 24

Related Robot Skills (view all robot skills)
Camera Device by Synthiam
Use PC or robot cameras for vision tracking: color, QR, glyph, face, object, motion; record video/data, control servos and movement, run scripts
Hugging Face by Hugging Face Inc
Connects your robot camera to Hugging Face AI models for vision chat, object tracking, classification, captioning, and autonomous movement.

ARC Pro

Upgrade to ARC Pro

ARC Pro is more than a tool; it's a creative playground for robot enthusiasts, where you can turn your wildest ideas into reality.

Author Avatar
PRO
Canada
Twitter YouTube GitHub
#1  

That error is coming from Hugging Face’s provider routing, not from ARC itself.

What it means

Qwen/Qwen2.5-VL-7B-Instruct is a vision-language model, and Hugging Face is saying:

"You don’t currently have any enabled provider that can serve this model."

So ARC is successfully sending the request, but Hugging Face is rejecting the model because your account/token/provider setup doesn’t have access to a backend that can run it.

What to check

1) Verify the model supports the task you chose

In the Hugging Face skill configuration, make sure you’re using the correct task:

  • Vision Chat for asking the model to see and respond
  • Object Detection for finding faces/objects in the image
  • Image Classification for labeling the whole image
  • Image Captioning for describing the scene

If you enabled face and motion tracking, that sounds more like Object Detection, not Vision Chat.

2) Try a known-good default model for the selected task

In the skill’s kebab/gear menu configuration, switch to Default for that task and test again.

For example:

  • Object Detection: facebook/detr-resnet-50
  • Image Captioning: Salesforce/blip-image-captioning-large

These are generally easier to get working than a large vision-chat model.

3) Check Hugging Face model access / provider availability

That specific error usually means one of these:

  • Your token is valid, but the model is not available on the enabled provider
  • The model may require a different provider than the one currently enabled in your Hugging Face account
  • You may need to select a different model that is supported by serverless inference

Hugging Face has a support article for model-based robot use in ARC here:

Important note about your webcam

Your USB webcam on the PC is fine. ARC can use that with the Camera Device skill. The webcam is not the issue here.

Make sure you have:

  1. Camera Device skill added
  2. Webcam selected in that skill
  3. Camera skill started
  4. Hugging Face skill configured to use that camera feed

If the camera is not running, Hugging Face would usually complain about no active camera, not model support.

Best next step

Try this:

  1. Open the Hugging Face skill settings
  2. Switch to Object Detection
  3. Use the default detection model
  4. Press Save
  5. Run Query Now

If that works, then the issue is specifically the Qwen vision-chat model/provider combo.

If you want Vision Chat

If your goal is the "robot sees and talks" behavior, you may need to:

  • choose a different vision model that your enabled provider supports, or
  • use a Hugging Face Inference Endpoint / compatible provider that supports that model

Quick question

Are you trying to do:

  • face detection / tracking, or
  • vision chat where the model describes the scene and answers questions?

If you tell me which task mode you selected in the skill, I can point you to the exact model/settings to use in ARC.

I am a customer support AI and still learning. Please verify important answers in our support documentation. For advanced AI features, use the AI Script Agent built into ARC.
#2  

image.png The image above shows my settings, This is the default setting according to the provided info about this skill. As shown I see a HTTP 400 error showing up, which I am guessing is an issue with connecting to the Huggyface site?

Author Avatar
PRO
Canada
Twitter YouTube GitHub
#3  

Thanks for the screenshot - that helps.

What I see is that you’re on Vision Chat with the default Qwen/Qwen2.5-VL-7B-Instruct model, and ARC is successfully reaching Hugging Face. So this is not a webcam problem and not a general "can’t connect to Hugging Face" problem.

What the error means

The key part is:

model_not_supported
The requested model 'Qwen/Qwen2.5-VL-7B-Instruct' is not supported by any provider you have enabled.

That means:

  • ARC is sending the request correctly
  • Hugging Face received it
  • Hugging Face does not have an enabled provider on your account/session that can run that model

So the issue is model/provider availability, not ARC connectivity.

Why the default model can fail

Even if the skill documentation lists a default model, Hugging Face serverless inference may not currently serve that model for your account/provider setup. Model availability can change, and some models require:

  • a different provider
  • an inference endpoint
  • accepted model terms
  • or a smaller/more common vision model

What to try next

1) Test with a simpler model

In the Hugging Face skill:

  • open the kebab/gear menu
  • go to the Hugging Face tab
  • change the model to something more commonly supported

If you want to test Vision Chat, try another vision model that is known to work with your provider setup.

If you want to test face/motion tracking, that should usually be done with Object Detection, not Vision Chat.

2) Make sure you selected the right task

From your description, you mentioned face and motion tracking. That sounds like:

  • Object Detection mode for detecting a face/person
  • then Camera Tracking to move servos

For that, the default object detection model is a much better test than Qwen vision chat.

3) If you want the exact default docs behavior

The docs may assume a provider setup that isn’t available in every Hugging Face account. If the default model doesn’t run, the fix is usually to pick a different supported model, not to change ARC networking.

In short

This is not a connection failure to Hugging Face.

It is Hugging Face saying:

"I received your request, but I can’t run that model with any provider currently enabled for your account."

Try this in ARC:

  1. Switch the Hugging Face skill to Object Detection
  2. Leave the model at the default detection model
  3. Make sure your Camera Device skill is started
  4. Press Query Now

If that works, then your ARC setup and webcam are fine, and the issue is only the Vision Chat model choice.

Helpful reference

If you want, I can help you pick a working Vision Chat model or walk you through setting up object/face tracking correctly in ARC step by step.

I am a customer support AI and still learning. Please verify important answers in our support documentation. For advanced AI features, use the AI Script Agent built into ARC.
#4  

Yes, I would like some help on picking a working vision chat model since I have no idea on what to look for or setup. This is my first time doing this.

Author Avatar
PRO
Canada
Twitter YouTube GitHub
#5  

Absolutely - for a first-time setup, the safest path is to use a smaller, commonly supported vision model rather than the big default one.

What to look for

In Hugging Face Vision Chat mode, you want a model that:

  • supports vision-language / image-to-text / image-text-to-text
  • is available through the provider enabled on your Hugging Face account
  • is not a huge model that requires special access or an inference endpoint

The default Qwen/Qwen2.5-VL-7B-Instruct is a good example of a modern model, but it may not be available through your current provider setup, which is why you got the model_not_supported error.


Good first models to try

Try one of these in ARC one at a time:

  • HuggingFaceTB/SmolVLM-2B-Instruct
  • HuggingFaceTB/SmolVLM-Instruct
  • microsoft/Phi-3.5-vision-instruct
  • llava-hf/llava-1.5-7b-hf

If one fails with provider/model support, try the next one.

My recommendation for a beginner

Start with:

HuggingFaceTB/SmolVLM-2B-Instruct

It’s smaller and often easier to get working than larger vision models.


How to change it in ARC

  1. Open the Hugging Face robot skill.
  2. Press the kebab/gear menu for the skill settings.
  3. Go to the Hugging Face tab.
  4. Leave Task set to Vision Chat.
  5. Replace the model name with one of the models above.
  6. Press Save.
  7. Press Query Now.

If it works, you should see a response in the log and $HfSpeak / $HfResponse should populate.


If it still errors

If you get another model_not_supported error, that means the selected model is still not available from your enabled Hugging Face provider.

In that case, the quickest way forward is:

  • try the next model in the list above
  • or use Object Detection mode first, which is much more likely to work out of the box for tracking a face/person

Important note about your goal

You mentioned face and motion tracking. For that, you may actually want:

  • Object Detection mode
  • Track label: person
  • Pan/Tilt servos assigned on the Camera Tracking tab

That is the correct setup if you want the camera to follow a person’s face/body. Vision Chat is better for "look at the camera and describe what you see."


Helpful ARC docs


Quick question

Do you want your robot to:

  1. talk about what it sees with Vision Chat, or
  2. track a person’s face with the camera?

If you tell me which one, I can give you the exact ARC settings to use next.

I am a customer support AI and still learning. Please verify important answers in our support documentation. For advanced AI features, use the AI Script Agent built into ARC.
#6  

Not successful. I have tried all four of the models you recommended, none of them worked. I have tried different tracking settings in the camera,face or motion, or object. Again nothing is working.

Each time., I still get this message....

 20:38:08 Error: Attempting to read GetCurrentBitmapManaged while locked.
20:39:02 Error: Attempting to read GetCurrentBitmapManaged while locked.
20:39:42 Error: HTTP 400 from Hugging Face. {"error":{"message":"The requested model 'microsoft/Phi-3.5-vision-instruct' is not supported by any provider you have enabled.","type":"invalid\_request\_error","param":"model","code":"model\_not\_supported"}}
20:40:17 Error: Attempting to read GetCurrentBitmapManaged while locked.
20:41:00 Error: Attempting to read GetCurrentBitmapManaged while locked.

While I created the API thru the HuggyFace website, are there other settings on the website I need to set/choose, thats not mentioned in the original information of this skill?

Author Avatar
PRO
Canada
Twitter YouTube GitHub
#7  

Yes - there are two separate issues in your log, and the Hugging Face website setup is likely part of one of them.

1) model_not_supported = Hugging Face provider issue

This one is still the same root problem:

The requested model ... is not supported by any provider you have enabled.

That means your token is valid enough for ARC to reach Hugging Face, but your Hugging Face account is not enabled for a provider that can serve that model.

What to check on Hugging Face

Please log into Hugging Face and check:

  • Settings Access Tokens
    • Confirm the token is correct and not expired
  • Any billing / provider / inference settings
    • Some models require a provider that isn’t enabled by default
  • Model page access
    • Some models are gated and need you to accept terms on the model’s page

The exact wording in the error is the giveaway: this is not ARC failing to connect; it’s Hugging Face rejecting the model because no enabled backend can run it.

2) Attempting to read GetCurrentBitmapManaged while locked

This is a separate ARC camera-image contention problem.

It usually means more than one skill is trying to read the camera frame at the same time, or the camera feed is being accessed while another process is holding the bitmap.

Common causes

  • Camera Device is open in one skill, while Hugging Face is also trying to pull frames
  • Another vision skill is active at the same time
  • The camera stream is paused/starting/stopping repeatedly
  • Tracking is enabled in multiple places at once

What to do

Try this clean test setup:

  1. New empty project
  2. Add Camera Device
  3. Select your USB webcam
  4. Press Start on Camera Device
  5. Add Hugging Face
  6. In Hugging Face, use only one mode at a time:
    • either Vision Chat
    • or Object Detection
    • not multiple tracking modes in the Camera skill while testing
  7. Press Query Now

Also make sure no other robot skills are trying to use the camera.

Important: for face tracking, don’t use Vision Chat

If your goal is to track a face/person, use:

  • Camera Device for the webcam
  • Hugging Face Object Detection
  • target label: person
  • then use Camera Tracking tab for pan/tilt servos if you have them

That is much more reliable than trying to use Vision Chat for tracking.

Most likely answer to your question

No, there usually isn’t a special hidden setting on Hugging Face that ARC forgot to mention. The big issue is:

  • the model/provider combination you’re trying is not enabled on Hugging Face, and
  • ARC is also seeing a camera frame lock conflict

Next best step

Please try this exact diagnostic:

Clean camera test

  • Create a brand-new ARC project
  • Add only Camera Device
  • Start the webcam

Then add Hugging Face

  • Use Object Detection
  • Try the default model
  • Do not enable other camera/vision skills

If that works, then we know the camera lock issue was caused by another skill or setup.

If you want, I can help you with either of these next:

  1. a known-good ARC camera + Hugging Face test setup
  2. a face-tracking setup using the Camera Device skill with pan/tilt
  3. checking your Hugging Face token / provider settings step-by-step

If you’d like, send a screenshot of:

  • the Hugging Face skill settings
  • the Camera Device skill
  • and your Hugging Face token/settings page with sensitive info hidden

and I’ll help you narrow it down.

I am a customer support AI and still learning. Please verify important answers in our support documentation. For advanced AI features, use the AI Script Agent built into ARC.
#8  
  1. a known-good ARC camera + Hugging Face test setup
  2. a face-tracking setup using the Camera Device skill with pan/tilt
  3. checking your Hugging Face token / provider settings step-by-step

Yes, I would like a step by step of these three items......