Dock 3 error “This device does not support IR learning.”

General
1

When I select Dock 3 in the web configurator and press “Learn code” to record an IR code, it returns an error “This device does not support IR learning.”

The Dock 3 specs say it has an IR receiver for IR learning, so how are other people learning IR codes with Remote 3 & Dock 3?

2

You could try using the blaster instead of the dock. Make sure it’s recognised in the dock settings. I assume you’re trying to use the internal IR receiver? Make sure its been activated first under settings/development/preview features.

3

You must select the correct Dock to learn AND the Dock must be connected. I could learn IR with Dock 3.

Ralf

4

Thanks for the response, Ralf.

When you say ‘select the correct dock’, what exactly do you mean? - I only have one dock, which is, as I said on my post, a Dock 3, and it is connected - otherwise I couldn’t access it. Are there different types of Dock 3?

5

So have you added a new device, selected infrared, add name, selected create empty and hit next? You then select a dock to learn and then select + on top right to add a new command. There are 2 types of dock (charging and non-charging) but either should work fine. As you only have one dock just select that one.

6

Thanks, iordish,

Yes, I was trying to use the Dock 3 IR receiver. The development preview features only seem to refer to enabling the remote’s IR blaster, I don’t see an option to enable an IR receiver for the Dock 3.

How would using the blaster help with learning IR codes? I’m confused…

7

You’re right - senior moment - it wont. Dock 3 IR receiver should work though.

8

Yes, that’s what I did - I selected + to add a new IR command, named the command, and pressed the wavy line ‘IR learn’ button. This produced the “This device does not support IR learning” error message.

Update: As a last ditch effort, I factory reset the Dock 3, got it connected again, and retried the IR command learning, and this time it worked!

Now I can turn my projector on and off - result!

Thanks for your confirmation that I was doing the correct steps, it made me think the problem might be a firmware glitch - and it looks like that’s what it was.

When I was a software developer, back in the day (I’m retired now), we used to call this the ‘cardbord guru’ effect - just asking someone to look at the code you were having problems with helped you see the solution, even if they didn’t actually do anything… :wink:

9

Just glad you got it working!