How to change remote code sets for STB on U4 remote? (solved)

[sub3R]

Does anyone know how to correctly change the code sets on the U4 remote?

The U4 remote apparently comes factory set to the remote primary code 0xAE97. But it can be changed to the 0x02F3 alternate. See here.

The U4 User Manual (which can be viewed here) doesn’t specifically say how to do this.
On page 47 it only shows the following (see image at the end of this post).

Reading that, I assume I would use the following steps:

1. Press and hold the STB component key until the LED on the remote control turns on.
2. Enter 3-digit code.
3. Press and release the OK key, then the LED blinks 3 times.

If this is correct, what are the 3 digit codes for 0xAE97 & 0x02F3? I’m guessing it could be [003] for 0x02F3, & [007] for 0xAE97, but I don’t want to make a change from 0xAE97 to 0x02F3 & find I can’t get back to 0xAE97 because of the wrong 3 digit code.

The T2 & T4 User Manuals are much clearer. They have the following wording (exactly the same for the T2 & T4).

From page 47 of the T2 User Manual:

“Program the Remote to control other Beyonwiz PVRs.
The T4 remote can be programed to work on any of the Beyonwiz T-Series
PVRs. Additionally the T4 IR software can be set to work in any of those
modes (see page 49). STB mode has 3 custom codes as follows and T4
(02F4) is the factory default for STB.
1. Custom code "02F2" for T2.
2. Custom code "02F3" for T3.
3. Custom code "02F4" for T4.
If you want to change custom code to T2 or T3, please program the remote control for
STB following these steps.
1) Press and hold the [STB] key and [OK] key at the same time until the red LED on [STB] key turns on and then release both keys.
2) Enter the three (3) digit code, "003" or "004"
[002] = Custom Code "02F2"
[003] = Custom Code "02F3"
[004] = Custom Code "02F4"
3) Press [OK] key.
4) When the [OK] key is released, if the code is valid, red LED on [STB] key blinks 3 times.
The LED doesn't blink if the entered code is invalid.”

Do I use the above T2/T4 steps on the U4 remote (this includes OK in step 1)? And if so, what are the 3 digit codes for 0xAE97 & 0x02F3?

From page 47 of the U4 User Manual:

[prl]

After looking back at an old U4 beta forum post, you need to:

1. In MENU>Setup>System>Remote control code settings, scroll to the code set corresponding to the remote code you want to set to the remote to, and press OK. You have 30 seconds before the popup times out and reverts to the previous code.
2. Press and hold the STB key on the remote until both the STB and TV buttons blink 3 times and then STB button stays on.
3. Enter the 3-digit code (see below) for the STB code set. The STB button flashes off once for each button press.
4. Press OK. The STB button flashes on 3 times and then goes off.
5. Navigate down to "yes" and press OK. If you've messed up, the popup will time out and revert to the old code.

The only 3-digit codes that appear to work are:
800 - Beyonwiz U4 (0xAE97)
801 - Beyonwiz U4/T4/T2 (0x02F3)

I tried a few other 80x codes and none of them seemed to work.

[sub3R]

Excellent. Thanks very much Peter, I wouldn’t have guessed that in a million years.

The only 3-digit codes that appear to work are:
800 - Beyonwiz U4 (0xAE97)
801 - Beyonwiz U4/T4/T2 (0x02F3)

I tried a few other 80x codes and none of them seemed to work.

That lines up with what peterU mentioned in the bitbucket.org info I linked to; ‘Beyonwiz U4 remote can be switched between 0xAE97 and 0x02F3 ...’.

For completeness, on f/w 17.5 20180901 on our T2 & U4 under ‘MENU>Setup>System>Remote control code settings’, the following options are listed:

T2:
All supported – (default option)
Beyonwiz T3 (0xABCD)
Beyonwiz (0x02F2)
Beyonwiz (0x02F3)
Beyonwiz (0x02F4)
Beyonwiz U4 (0xAE97)
HDx (0x0933)

U4:
Beyonwiz U4 (0xAE97) – (default option)
Beyonwiz U4/T4/T2 (0x02F3)
Beyonwiz T2/T4 (0x02F2)
Beyonwiz T2/T4 (0x02F4)
Beyonwiz T3 (0xABCD)

[sub3R]

The above steps worked successfully on the T2 quite a few times back & forth, & the popup timing out & reverting to the old code if not completed within 30 seconds was confirmed.

However, once when changing from 0xAE97 to 0x02F3 the T2 ended up not responding to any of the remotes (U4 remote, T2 remote & Harmony 650 set for the T2) after completing the steps Peter posted. I don’t know if I made a mistake or the communication between the remote & T2 wasn’t successful with one or more of the steps, but the T2 just displayed 0x02F3 without the popup being displayed. It hadn’t hung up because the clock was still updating.

Trying to the get the U4’s remote working with the T2 again using steps 2 to 4 inclusive & the 3-digit code for 0x02F3 didn’t work. But using steps 2 to 4 inclusive & the 3-digit code for 0xAE97 did work & the T2 displayed 0xAE97 & responded to the U4’s remote. The next time I tried changing from 0xAE97 to 0x02F3 worked as it should.

[prl]

... the T2 just displayed 0x02F3 ... the T2 displayed 0xAE97 ...

The process of changing the code set on the remote shouldn't change the code set displayed on the PVR. It's only the actions done (or failed to do) when the remote is sending codes, first in the old code set to start the process (step 1 above), and then in the new code set to confirm that the buttons work as intended (step 5 above). If the "Is this remote OK?" popup times out, the PVR should revert to the previous code set.

Sometimes when I change codes on the U4 remote and on a U4 PVR, pressing the remote buttons that change the remote codes sometimes pops up the volume control bar, though. I don't know why.

I've definitely sometimes had "finger trouble" changing code sets and ended up with the PVR and the remote set to different code sets from each other. The 30 seconds allowed can still be a bit rushed (but better that the original 15 sec when I tried it in beta testing).

[MrQuade]

Better if you do all the UI navigating via the OpenWebIf, and you can change the codes on the remote at your leisure either before or after setting the code on the T2/U4.

[sub3R]

I've definitely sometimes had "finger trouble" changing code sets and ended up with the PVR and the remote set to different code sets from each other. The 30 seconds allowed can still be a bit rushed (but better that the original 15 sec when I tried it in beta testing).

I’m not sure what happened in my case. I definitely got the code set change from 0xAE97 to 0x02F3 displayed on the T2 at item 1, but it appears that I may not have got the 30sec timeout popup (too busy concentrating on the remote).

BTW, this was all in front of the T2. I hadn't tried any changes on the U4 remote in front of the U4 prior to this.

I just tried to replicate what happened in front of the U4 with the U4 remote but couldn’t. It worked as it should.

With a 15sec timeout it would have been a pretty tall order to achieve, except maybe for kids that are used to texting on smart phones.

I also randomly got the volume control bar popping up on the T2 & on the U4.

Better if you do all the UI navigating via the OpenWebIf, and you can change the codes on the remote at your leisure either before or after setting the code on the T2/U4.

Ahh yes, that’s a better way, I didn't think of that. And it would have been an easier way to get the T2 working again with the U4 remote after the out of sync that happened.

[Star6key]

So I have bitten the bullet and ordered a barebones U4 (and splitter).
As I will be using the T4 to record FTA & hdmi, and the U4 purely for hdmi, I have some questions.

Do the 2 machines have same/different IR codesets?
Will there be issues with the U4 if I don't connect an aerial?
Is the IR receiver on the U4 as dodgy as the T4 (have to aim pretty much directly at the unit)?

[MrQuade]

Do the 2 machines have same/different IR codesets?

All the T and U series support the same 5 code sets.
The U4's remote only supports a single code set and can't be set to an alternate (0xae97). The T4's remote can be set to use any one of three sets (0x02f2, 0x02f3, 0x02f4), but is set to 0x02f2 by default.

The simplest solution is to make sure that your T4 is configured to respond to 0x02f2 only (instead of "All supported codes") and the U4 is configured to respond to 0xae97. That way, the remotes wont clash.

Will there be issues with the U4 if I don't connect an aerial?

Nope. Just make sure it has a network connection, and it has access to a NTP time server, otherwise it won't have any way of accurately maintaining the time.
You can even configure the U4 to stream live TV or recordings from the T4 over the network if you wanted to. (I do this with my T2 and T3).

Is the IR receiver on the U4 as dodgy as the T4 (have to aim pretty much directly at the unit)?

It's a bit better in my limited experience. But I use a Harmony day to day, so its a non-issue most of the time.

[Star6key]

Do the 2 machines have same/different IR codesets?

All the T and U series support the same 5 code sets.
The U4's remote only supports a single code set and can't be set to an alternate (0xae97). The T4's remote can be set to use any one of three sets (0x02f2, 0x02f3, 0x02f4), but is set to 0x02f2 by default.

The simplest solution is to make sure that your T4 is configured to respond to 0x02f2 only (instead of "All supported codes") and the U4 is configured to respond to 0xae97. That way, the remotes wont clash.

Will there be issues with the U4 if I don't connect an aerial?

Nope. Just make sure it has a network connection, and it has access to a NTP time server, otherwise it won't have any way of accurately maintaining the time.
You can even configure the U4 to stream live TV or recordings from the T4 over the network if you wanted to. (I do this with my T2 and T3).

Is the IR receiver on the U4 as dodgy as the T4 (have to aim pretty much directly at the unit)?

It's a bit better in my limited experience. But I use a Harmony day to day, so its a non-issue most of the time.

Currently running - beyonwiz 17.5.20190206 (17.5-819-gdd3f1fa) fw.

The T4 was set to 'All supported'. Changed it to (0x02f2), pressed Save, and the Harmony remote no longer responds. Let the 'Is the remote OK' message time out, and the remote is ok. Changing it to (0x02f3) and (0x02f4), is no better. Changed it to T3 (0xABCD), and now the Harmony responds. Not sure of what the long term consequences will be (maybe different actions for certain buttons/options), so I've left it at 'All supported' for now.
edit - I wonder if maybe I've set it up as a T3 on the Harmony... If I remember correctly, there was no T4 in the Logitech database when the T4 first came out, and we had to set it up as a T3. Don't know how to confirm that.

The U4 will be ethernet connected.

Obviously (from the above), I use a Harmony (650), but I still find the IR range isn't great (usable, but not great).

Thanks for the info MrQuade.

[prl]

edit - I wonder if maybe I've set it up as a T3 on the Harmony... If I remember correctly, there was no T4 in the Logitech database when the T4 first came out, and we had to set it up as a T3. Don't know how to confirm that.

You try adding a new device: search for the model, and then cancel before creating it. In that way I have confirmed that the Harmony database has code sets for T2 0x02f2, T3 0xabcd, T4 0x02f4 and U4 native mode 0xae97.

The T3 remote can send only 0x02f3.
The T2 and T4 remotes can send 0x02f2, 0x02f3 and 0x02f4 and factory default to 0x02f2.
The U4 remote can send 0xae97 and 0x02f3.

A very small number of pre-release T3-format remotes exist that have a mechanical switch that can switch them between 0xabcd. These remotes never went into production.

[MrQuade]

The T3 remote can send only 0x02f3.

The production T3 remote can only send 0xABCD.

A very small number of pre-release T3-format remotes exist that have a mechanical switch that can switch them between 0x02f3 and 0xabcd. These remotes never went into production.

I don't have one of those hen's teeth remotes, but I thought it was switchable between 0xABCD and 0xAE97?

[MrQuade]

The T4 was set to 'All supported'. Changed it to (0x02f2), pressed Save, and the Harmony remote no longer responds. Let the 'Is the remote OK' message time out, and the remote is ok. Changing it to (0x02f3) and (0x02f4), is no better. Changed it to T3 (0xABCD), and now the Harmony responds. Not sure of what the long term consequences will be (maybe different actions for certain buttons/options), so I've left it at 'All supported' for now.

That means that your Harmony is configured to send the 0xABCD commands.

There are no consequences to changing command sets between the T3 and T4, the buttons are identical. You can happily set your T4 to use 0xABCD, and there will be no operational issues. If you leave it as 'All Supported", then the codes sent by your new U4 remote will also act to operate the T4.

edit - I wonder if maybe I've set it up as a T3 on the Harmony... If I remember correctly, there was no T4 in the Logitech database when the T4 first came out, and we had to set it up as a T3. Don't know how to confirm that.

I reckon that's exactly what has happened.

You can also switch the code set that Harmony sends as well. You need to open the My Harmony software and find the option that says "I use an alternate remote" (or something like that). The My Harmony software will ask you to plug in the 650, and then use your original remote to train the new remote (only takes 2 or 3 buttons to train it).

It might be easier to just leave the T4 on 0xABCD though, as you can easily get yourself tied into knots unless you are careful.

Obviously (from the above), I use a Harmony (650), but I still find the IR range isn't great (usable, but not great).

Sorry, I should have been specific too. Mine is a hub-based remote, so aiming is not required in that instance.

[Star6key]

In that case, I will set the T4 to the T3 IR codes. Saves a lot of mucking about.

The hub remote doesn't have enough buttons (for me), as I use my 650 to also issue PC commands (especially the function keys, so the number buttons are essential) through my HP media centre receiver.

[prl]

The T3 remote can send only 0x02f3.

The production T3 remote can only send 0xABCD.

A very small number of pre-release T3-format remotes exist that have a mechanical switch that can switch them between 0x02f3 and 0xabcd. These remotes never went into production.

I don't have one of those hen's teeth remotes, but I thought it was switchable between 0xABCD and 0xAE97?

Quite right. Thanks. Fixed in the original post now.

[Paul_oz53]

In that case, I will set the T4 to the T3 IR codes. Saves a lot of mucking about.

The hub remote doesn't have enough buttons (for me), as I use my 650 to also issue PC commands (especially the function keys, so the number buttons are essential) through my HP media centre receiver.

Interesting choice - its exactly what I have done, more by accident than design!

The T3 was in the lounge and became a T4 and now a U4 but I didn't bother reprogramming the Harmony remotes so they all still use the T3 0xABCD set. Only hassle is I needed the U4 remote to do a full reinstall of the firmware on the U4. Couldn't easily restore settings without it.

When I access the T4/U4 HDMI-IN I just use its channel number, which is 18 on my setup.

[MrQuade]

The T3 was in the lounge and became a T4 and now a U4 but I didn't bother reprogramming the Harmony remotes so they all still use the T3 0xABCD set. Only hassle is I needed the U4 remote to do a full reinstall of the firmware on the U4. Couldn't easily restore settings without it.

That's odd. The U4 should respond to "All supported" codes after a fresh install, so it should have been fine with 0xABCD commands from the Harmony.

[Paul_oz53]

That's odd. The U4 should respond to "All supported" codes after a fresh install, so it should have been fine with 0xABCD commands from the Harmony.

That's what I expected too but it doesn't appear to have "All supported" as an option. The closest thing is U4/T4/T2 (0x2f3). Able to use T3 once settings were restored.

[MrQuade]

That's what I expected too but it doesn't appear to have "All supported" as an option.

Huh, bugger me! I never noticed that this was missing on the U4.