Discrete on/off IR commands

prl · Post by **prl** » Sat May 07, 2016 09:58

The "multiple versions" facility also does not appear to be available for older Harmony devices that use the Java Harmony Remote Software rather than the Web-based app to do setup.

peteru · Post by **peteru** » Sat May 07, 2016 16:10

I finally heard back from some first line Logitech support person with a canned response. From what he had to say, they don't have any means to do bulk imports or to perform automated testing. They also don't appear to have any way (or desire) of assisting vendors to perform compatibility testing.

From my point of view, it looks like working with Logitech to improve their products is in the too hard basket. Given that I don't even have a Logitech remote control, it will have to be down to other people to get this sorted with Logitech.

Good luck!

MrQuade · Post by **MrQuade** » Sat May 07, 2016 16:13

peteru wrote: Good luck!

Thanks for your efforts, they can be pains in the proverbial.

Gully · Post by **Gully** » Sat May 07, 2016 16:22

Seems a bizarre response when they have effectively already added the new codes, albeit with some errors.

peteru · Post by **peteru** » Sat May 07, 2016 17:32

Yeah, not much logic in Logitech.

scotty · Post by **scotty** » Tue May 10, 2016 10:54

Just heard back from Logitech data support again:

Logitech wrote:Based on your feedback, we have modified the device profile in our Harmony database and removed the duplicate IR commands. Please delete and re-add the device in your account to get the updated settings.

I haven't yet tested the changes.

Scotty

Gully · Post by **Gully** » Tue May 10, 2016 11:04

scotty wrote:Just heard back from Logitech data support again:
Logitech wrote:Based on your feedback, we have modified the device profile in our Harmony database and removed the duplicate IR commands. Please delete and re-add the device in your account to get the updated settings.
I haven't yet tested the changes.

Wonder if that means they fixed Power2 as well?

scotty · Post by **scotty** » Tue May 10, 2016 11:44

Gully wrote:Wonder if that means they fixed Power2 as well?

Looks like they've completely omitted it. I can only see PowerSuspend, PowerToggle and PowerWakeup

Scotty

scotty · Post by **scotty** » Thu May 12, 2016 01:52

Hopefully sorted now. I haven't tested yet.

Logitech wrote:Based on your request, we have added the "Power2" command also to the devices in our Harmony database. Please delete and re-add the device to your account to get the latest version.

Scotty

Gully · Post by **Gully** » Thu May 12, 2016 11:02

Thanks Scotty.

I'll do an update later today.

MrQuade · Post by **MrQuade** » Thu May 12, 2016 11:12

scotty wrote:Hopefully sorted now. I haven't tested yet.
Logitech wrote:Based on your request, we have added the "Power2" command also to the devices in our Harmony database. Please delete and re-add the device to your account to get the latest version.
Scotty

I just hope they didn't call it "Power2"

prl · Post by **prl** » Thu May 12, 2016 11:24

MrQuade wrote:
scotty wrote:Hopefully sorted now. I haven't tested yet.
Logitech wrote:Based on your request, we have added the "Power2" command also to the devices in our Harmony database. Please delete and re-add the device to your account to get the latest version.
Scotty
I just hope they didn't call it "Power2"

That seems to be their wont.

peteru · Post by **peteru** » Sat Aug 27, 2016 03:34

I've been in touch with Logitech and sent them a detailed explanation of how the Beyonwiz T-series work with multiple remotes as well as a list of remote codes supported. I've heard back from Logitech, advising that they have updated their database and "added multiple IR versions for T-series DVRs". Apparently "Users can change the required IR code versions in their Harmony remotes."

Harmony users may wish to take a closer look at the current state of Beyonwiz remote support to see how well it works. I don't have a Logitech remote, so I'll have to leave the testing to someone else.

I'll add the remote code documentation to the Bitbucket repository in due course.

peteru · Post by **peteru** » Sat Aug 27, 2016 03:43

In the meantime, here is a copy of the documentation.

Code: Select all

Beyonwiz remote control codes

Infra Red (IR) remote control codes for Beyonwiz T-series are sent using
the NEC protocol. This protocol uses 4 bytes of data. The first two bytes
form a 16-bit "vendor" code. The remaining two bytes are used to encode
an 8-bit "key" code by sending the 8-bit value for the key as the first
byte and an inverted bit pattern for the second byte.

The hardware and drivers decode the protocol and translate the raw IR
values into standard Linux input events. enigma2 uses keymap.xml to
convert the Linux events into enigma2 events.

The following tables show the IR code to Linux input event mapping for
various Beyonwiz T-series remote controls. Please consult keymap.xml
and source code to learn how enigma2 handles these codes. 

Notes:

Beyonwiz T3 production models shipped with a remote control that only
supports the 0xABCD vendor code. There was a limited number of T3 remotes
sent to some beta testers and these remotes have a small switch in the
battery compartment that can be used to switch the remote control vendor
code to 0xAE97

Beyonwiz T2 and T4 remotes support switching between 0x02F2, 0x02F3 and
0x02F4 vendor codes, with 0x02F2 being the default setting. The T2 and T4
remotes do not support the T3 vendor codes.

_______________________
Beyonwiz T3
=======================
Vendor	Key	Event
------	---	-----
0xABCD	0x0A	KEY_POWER
0xABCD	0x11	KEY_1
0xABCD	0x12	KEY_2
0xABCD	0x13	KEY_3
0xABCD	0x14	KEY_4
0xABCD	0x15	KEY_5
0xABCD	0x16	KEY_6
0xABCD	0x17	KEY_7
0xABCD	0x18	KEY_8
0xABCD	0x19	KEY_9
0xABCD	0x10	KEY_0
0xABCD	0x44	KEY_PREVIOUS
0xABCD	0x43	KEY_NEXT
0xABCD	0x00	KEY_UP
0xABCD	0x01	KEY_DOWN
0xABCD	0x03	KEY_LEFT
0xABCD	0x02	KEY_RIGHT
0xABCD	0x1F	KEY_OK
0xABCD	0x08	KEY_EPG
0xABCD	0x41	KEY_FAVORITES
0xABCD	0x04	KEY_MENU
0xABCD	0x1C	KEY_EXIT
0xABCD	0x06	KEY_INFO
0xABCD	0x40	KEY_MEDIA
0xABCD	0x09	KEY_LAST
0xABCD	0x4E	KEY_VOLUMEUP
0xABCD	0x4F	KEY_VOLUMEDOWN
0xABCD	0x0C	KEY_MUTE
0xABCD	0x5E	KEY_CHANNELUP
0xABCD	0x5F	KEY_CHANNELDOWN
0xABCD	0x4B	KEY_RED
0xABCD	0x4A	KEY_GREEN
0xABCD	0x49	KEY_YELLOW
0xABCD	0x48	KEY_BLUE
0xABCD	0x58	KEY_REWIND
0xABCD	0x55	KEY_PLAYPAUSE
0xABCD	0x54	KEY_STOP
0xABCD	0x5C	KEY_FASTFORWARD
0xABCD	0x56	KEY_RECORD
0xABCD	0x07	KEY_PROGRAM
0xABCD	0x65	KEY_SEARCH
0xABCD	0x42	KEY_BOOKMARKS
0xABCD	0x45	KEY_AUDIO
0xABCD	0x51	KEY_SCREEN
0xABCD	0x0B	KEY_SUBTITLE
0xABCD	0x1E	KEY_SLEEP
0xABCD	0x0D	KEY_TEXT
0xABCD	0x0F	KEY_TV
0xABCD	0x1A	KEY_RADIO
0xABCD	0x64	KEY_HELP
0xABCD	0xFA	KEY_SUSPEND
0xABCD	0xFB	KEY_WAKEUP
0xABCD	0xFC	KEY_POWER2

_______________________
Beyonwiz T3 (alternate)
=======================
Vendor	Key	Event
------	---	-----
0xAE97	0x0A	KEY_POWER
0xAE97	0x11	KEY_1
0xAE97	0x12	KEY_2
0xAE97	0x13	KEY_3
0xAE97	0x14	KEY_4
0xAE97	0x15	KEY_5
0xAE97	0x16	KEY_6
0xAE97	0x17	KEY_7
0xAE97	0x18	KEY_8
0xAE97	0x19	KEY_9
0xAE97	0x10	KEY_0
0xAE97	0x44	KEY_PREVIOUS
0xAE97	0x43	KEY_NEXT
0xAE97	0x00	KEY_UP
0xAE97	0x01	KEY_DOWN
0xAE97	0x03	KEY_LEFT
0xAE97	0x02	KEY_RIGHT
0xAE97	0x1F	KEY_OK
0xAE97	0x08	KEY_EPG
0xAE97	0x41	KEY_FAVORITES
0xAE97	0x04	KEY_MENU
0xAE97	0x1C	KEY_EXIT
0xAE97	0x06	KEY_INFO
0xAE97	0x40	KEY_MEDIA
0xAE97	0x09	KEY_LAST
0xAE97	0x4E	KEY_VOLUMEUP
0xAE97	0x4F	KEY_VOLUMEDOWN
0xAE97	0x0C	KEY_MUTE
0xAE97	0x5E	KEY_CHANNELUP
0xAE97	0x5F	KEY_CHANNELDOWN
0xAE97	0x4B	KEY_RED
0xAE97	0x4A	KEY_GREEN
0xAE97	0x49	KEY_YELLOW
0xAE97	0x48	KEY_BLUE
0xAE97	0x58	KEY_REWIND
0xAE97	0x55	KEY_PLAYPAUSE
0xAE97	0x54	KEY_STOP
0xAE97	0x5C	KEY_FASTFORWARD
0xAE97	0x56	KEY_RECORD
0xAE97	0x07	KEY_PROGRAM
0xAE97	0x65	KEY_SEARCH
0xAE97	0x42	KEY_BOOKMARKS
0xAE97	0x45	KEY_AUDIO
0xAE97	0x51	KEY_SCREEN
0xAE97	0x0B	KEY_SUBTITLE
0xAE97	0x1E	KEY_SLEEP
0xAE97	0x0D	KEY_TEXT
0xAE97	0x0F	KEY_TV
0xAE97	0x1A	KEY_RADIO
0xAE97	0x64	KEY_HELP
0xAE97	0xFA	KEY_SUSPEND
0xAE97	0xFB	KEY_WAKEUP
0xAE97	0xFC	KEY_POWER2

_______________________
Beyonwiz T2/T4 - mode 1
=======================
Vendor	Key	Event
------	---	-----
0x02F2	0x3C	KEY_POWER
0x02F2	0x11	KEY_1
0x02F2	0x12	KEY_2
0x02F2	0x13	KEY_3
0x02F2	0x14	KEY_4
0x02F2	0x15	KEY_5
0x02F2	0x16	KEY_6
0x02F2	0x17	KEY_7
0x02F2	0x18	KEY_8
0x02F2	0x19	KEY_9
0x02F2	0x0B	KEY_PREVIOUS
0x02F2	0x10	KEY_0
0x02F2	0x0D	KEY_NEXT
0x02F2	0x00	KEY_UP
0x02F2	0x01	KEY_DOWN
0x02F2	0x03	KEY_LEFT
0x02F2	0x02	KEY_RIGHT
0x02F2	0x1F	KEY_OK
0x02F2	0x06	KEY_EXIT
0x02F2	0x09	KEY_MENU
0x02F2	0x04	KEY_LAST
0x02F2	0x1C	KEY_INFO
0x02F2	0x4B	KEY_RED
0x02F2	0x4A	KEY_GREEN
0x02F2	0x49	KEY_YELLOW
0x02F2	0x48	KEY_BLUE
0x02F2	0x4E	KEY_VOLUMEUP
0x02F2	0x4F	KEY_VOLUMEDOWN
0x02F2	0x0C	KEY_MUTE
0x02F2	0x5E	KEY_CHANNELUP
0x02F2	0x5F	KEY_CHANNELDOWN
0x02F2	0x41	KEY_PROGRAM
0x02F2	0x40	KEY_MEDIA
0x02F2	0x08	KEY_EPG
0x02F2	0x58	KEY_REWIND
0x02F2	0x55	KEY_STOP
0x02F2	0x07	KEY_PLAYPAUSE
0x02F2	0x5C	KEY_FASTFORWARD
0x02F2	0x50	KEY_RECORD
0x02F2	0x54	KEY_FAVORITES
0x02F2	0x56	KEY_SEARCH
0x02F2	0x4C	KEY_BOOKMARKS
0x02F2	0x43	KEY_AUDIO
0x02F2	0x44	KEY_SCREEN
0x02F2	0x1A	KEY_SUBTITLE
0x02F2	0x1E	KEY_SLEEP
0x02F2	0x42	KEY_TEXT
0x02F2	0x51	KEY_TV
0x02F2	0x52	KEY_RADIO
0x02F2	0x53	KEY_HELP
0x02F2	0xFA	KEY_SUSPEND
0x02F2	0xFB	KEY_WAKEUP
0x02F2	0xFC	KEY_POWER2

_______________________
Beyonwiz T2/T4 - mode 2
=======================
Vendor	Key	Event
------	---	-----
0x02F3	0x3C	KEY_POWER
0x02F3	0x11	KEY_1
0x02F3	0x12	KEY_2
0x02F3	0x13	KEY_3
0x02F3	0x14	KEY_4
0x02F3	0x15	KEY_5
0x02F3	0x16	KEY_6
0x02F3	0x17	KEY_7
0x02F3	0x18	KEY_8
0x02F3	0x19	KEY_9
0x02F3	0x0B	KEY_PREVIOUS
0x02F3	0x10	KEY_0
0x02F3	0x0D	KEY_NEXT
0x02F3	0x00	KEY_UP
0x02F3	0x01	KEY_DOWN
0x02F3	0x03	KEY_LEFT
0x02F3	0x02	KEY_RIGHT
0x02F3	0x1F	KEY_OK
0x02F3	0x06	KEY_EXIT
0x02F3	0x09	KEY_MENU
0x02F3	0x04	KEY_LAST
0x02F3	0x1C	KEY_INFO
0x02F3	0x4B	KEY_RED
0x02F3	0x4A	KEY_GREEN
0x02F3	0x49	KEY_YELLOW
0x02F3	0x48	KEY_BLUE
0x02F3	0x4E	KEY_VOLUMEUP
0x02F3	0x4F	KEY_VOLUMEDOWN
0x02F3	0x0C	KEY_MUTE
0x02F3	0x5E	KEY_CHANNELUP
0x02F3	0x5F	KEY_CHANNELDOWN
0x02F3	0x41	KEY_PROGRAM
0x02F3	0x40	KEY_MEDIA
0x02F3	0x08	KEY_EPG
0x02F3	0x58	KEY_REWIND
0x02F3	0x55	KEY_STOP
0x02F3	0x07	KEY_PLAYPAUSE
0x02F3	0x5C	KEY_FASTFORWARD
0x02F3	0x50	KEY_RECORD
0x02F3	0x54	KEY_FAVORITES
0x02F3	0x56	KEY_SEARCH
0x02F3	0x4C	KEY_BOOKMARKS
0x02F3	0x43	KEY_AUDIO
0x02F3	0x44	KEY_SCREEN
0x02F3	0x1A	KEY_SUBTITLE
0x02F3	0x1E	KEY_SLEEP
0x02F3	0x42	KEY_TEXT
0x02F3	0x51	KEY_TV
0x02F3	0x52	KEY_RADIO
0x02F3	0x53	KEY_HELP
0x02F3	0xFA	KEY_SUSPEND
0x02F3	0xFB	KEY_WAKEUP
0x02F3	0xFC	KEY_POWER2

_______________________
Beyonwiz T2/T4 - mode 3
=======================
Vendor	Key	Event
------	---	-----
0x02F4	0x3C	KEY_POWER
0x02F4	0x11	KEY_1
0x02F4	0x12	KEY_2
0x02F4	0x13	KEY_3
0x02F4	0x14	KEY_4
0x02F4	0x15	KEY_5
0x02F4	0x16	KEY_6
0x02F4	0x17	KEY_7
0x02F4	0x18	KEY_8
0x02F4	0x19	KEY_9
0x02F4	0x0B	KEY_PREVIOUS
0x02F4	0x10	KEY_0
0x02F4	0x0D	KEY_NEXT
0x02F4	0x00	KEY_UP
0x02F4	0x01	KEY_DOWN
0x02F4	0x03	KEY_LEFT
0x02F4	0x02	KEY_RIGHT
0x02F4	0x1F	KEY_OK
0x02F4	0x06	KEY_EXIT
0x02F4	0x09	KEY_MENU
0x02F4	0x04	KEY_LAST
0x02F4	0x1C	KEY_INFO
0x02F4	0x4B	KEY_RED
0x02F4	0x4A	KEY_GREEN
0x02F4	0x49	KEY_YELLOW
0x02F4	0x48	KEY_BLUE
0x02F4	0x4E	KEY_VOLUMEUP
0x02F4	0x4F	KEY_VOLUMEDOWN
0x02F4	0x0C	KEY_MUTE
0x02F4	0x5E	KEY_CHANNELUP
0x02F4	0x5F	KEY_CHANNELDOWN
0x02F4	0x41	KEY_PROGRAM
0x02F4	0x40	KEY_MEDIA
0x02F4	0x08	KEY_EPG
0x02F4	0x58	KEY_REWIND
0x02F4	0x55	KEY_STOP
0x02F4	0x07	KEY_PLAYPAUSE
0x02F4	0x5C	KEY_FASTFORWARD
0x02F4	0x50	KEY_RECORD
0x02F4	0x54	KEY_FAVORITES
0x02F4	0x56	KEY_SEARCH
0x02F4	0x4C	KEY_BOOKMARKS
0x02F4	0x43	KEY_AUDIO
0x02F4	0x44	KEY_SCREEN
0x02F4	0x1A	KEY_SUBTITLE
0x02F4	0x1E	KEY_SLEEP
0x02F4	0x42	KEY_TEXT
0x02F4	0x51	KEY_TV
0x02F4	0x52	KEY_RADIO
0x02F4	0x53	KEY_HELP
0x02F4	0xFA	KEY_SUSPEND
0x02F4	0xFB	KEY_WAKEUP
0x02F4	0xFC	KEY_POWER2

prl · Post by **prl** » Sat Aug 27, 2016 10:00

peteru wrote:... Apparently "Users can change the required IR code versions in their Harmony remotes." ...

I think that may only apply to newer remotes that use the Web page setup rather than the old Java setup program.

prl · Post by **prl** » Sat Aug 27, 2016 11:29

I just checked in Logitech Harmony Remote Software v7.8.1 (the Java Harmony setup program), and if there's a way to switch code sets for a device, I can't find it.

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 12:54

prl wrote:I just checked in Logitech Harmony Remote Software v7.8.1 (the Java Harmony setup program), and if there's a way to switch code sets for a device, I can't find it.

When you first add the device to your account, it says that it can't find an exact match and prompts you for the remote. I presume this is so that you can teach it which code set to use.

I just had a look and there is an option called "Confirm Infrared Commands" that also looks like it runs through the command set learning wizard. It allows one option to choose the command set, but the numbers they provide are strange decimal numbers that don't correspond to the 0x02f2 etc... sets. The screen does say that they don't match, so the command set numbers listed must be some Logitech database key of some sort.

The prompts are very similar to the "Device Version" feature that is included in the "MyHarmony" software, which also asks if you have the original remote.

I have given this a test on my Harmony Elite, and it did successfully learn the correct code set, but it seems that the additional power commands don't do anything. I'll have to experiment some more to figure out what commands are actually being sent.

prl · Post by **prl** » Sat Aug 27, 2016 14:51

MrQuade wrote:
prl wrote:I just checked in Logitech Harmony Remote Software v7.8.1 (the Java Harmony setup program), and if there's a way to switch code sets for a device, I can't find it.
When you first add the device to your account, it says that it can't find an exact match and prompts you for the remote. I presume this is so that you can teach it which code set to use.
...

If I ask to add a T2 device, it asks whether I have a remote for the device. If I say no, it just uses some code set, presumably the default. If I say yes, it goes into the mode to learn all the codes. There doesn't seem to be any way to tell it to use an alternative code set.

If I just search for a "T" as the device name, it offers T2, T3 and T4 as the possible choices. If I pick one of them, it just goes ahead with setup as above.

Being able to learn an alternative code set in that has always been possible. I'm talking about a way to tell it that I want to use, say, the 0xAE97 code set from the Logitech database for the new device entry on the Logitech, I can't see how to to access that.

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 15:48

Well so far, it is a bloody mess.

Set up a new T2 in MyHarmony:
1) The inital code set is 0x02f2, which is all good.
2) Change command set to 0x02f3 and it asks you to send it a POWER command to verify the new code set. Once, set, it changes all commands to 0x02f3, except the new power commands, which get set to 0x02f4 for some reason. Broken!
3) Change the command set to 0x02f4, and it asks you to press POWER, 1, and CH+. It looks like going to 0x02f4 doesn't change the code set at all. If initially set to 0x02f2, it stays there. If it was previously set to 0x02f3, it also stays there. (with power codes still on 0x02f4). Broken!
4) Change the command set to 0xABCD, and it asks you to press POWER, 1, and CH+. Likewise, It looks like going to 0xabcd doesn't change the code set at all. If initially set to 0x02f2, it stays there. If it was previously set to 0x02f3, it also stays there (with power codes still on 0x02f4). Broken!
5) If already set to 0x02f3 (with 0x02f4 power codes), then you attempt to set it back to 0x02f2, then it asks you to press POWER, 1, and CH+, and once done that all seems to work properly.

Set up a new T3 in MyHarmony:
1) The inital code set is 0xabcd, which is all good.
2) Change the command set to 0x02f2, and it asks you to press POWER, 1, and CH+. It stays configured as 0xabcd. Broken!
3) Change the command set to 0x02f3, and it asks you to press POWER, 1, and CH+. It stays configured as 0xabcd. Broken!
4) Change the command set to 0x02f4, and it asks you to press POWER, 1, and CH+. It stays configured as 0xabcd. Broken!

Set up a new T4 in MyHarmony:
1) The initial code set is 0x02f4, which is ok. It doesn't match the default code set of the T4 remote, but it does match the manual, so be it.
2) Change the command set to 0x02f2, and it asks you to press POWER. Everything works including the new power codes.
3) Change the command set to 0x02f3, and it asks you to press POWER. All the regular codes work, but the new power codes are all set to 0x02f4. Broken!
4) Change back to 0x02f4, and it asks you to press POWER. Everything back to normal and working.
5) Change the command set to 0xabcd, and it asks you to press POWER, 1, and CH+. It stays configured as whatever it was previously configured as (including the broken power codes when set to 0x02f3).

I really can't tell if this is a database error or a software error, but it really doesn't work at all well. The default command sets are working fine, but the alternates are all over the shop.

I don't have a working 785 remote to test the old software with, so prl will have to do that if he has time.

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 15:51

prl wrote: If I ask to add a T2 device, it asks whether I have a remote for the device. If I say no, it just uses some code set, presumably the default. If I say yes, it goes into the mode to learn all the codes. There doesn't seem to be any way to tell it to use an alternative code set.

Does it actually ask for all of them, or just a sample of 2 or 3 buttons so it can identify the code set from thyem? On the MyHarmony app, it asks for POWER, 1 and CH+. (sometimes only POWER).

prl wrote: Being able to learn an alternative code set in that has always been possible. I'm talking about a way to tell it that I want to use, say, the 0xAE97 code set from the Logitech database for the new device entry on the Logitech, I can't see how to to access that.

How about the "Confirm Infrared Codes" feature that I mentioned for an existing device? It allows for the learning mode, as well as allowing you to select a set (from a choice of three available.....not sure what sets they were though.)

prl · Post by **prl** » Sat Aug 27, 2016 16:52

MrQuade wrote:
prl wrote: If I ask to add a T2 device, it asks whether I have a remote for the device. If I say no, it just uses some code set, presumably the default. If I say yes, it goes into the mode to learn all the codes. There doesn't seem to be any way to tell it to use an alternative code set.
Does it actually ask for all of them, or just a sample of 2 or 3 buttons so it can identify the code set from thyem? On the MyHarmony app, it asks for POWER, 1 and CH+. (sometimes only POWER).

It does in fact try to identify the remote code set. But when it has, it just says "Based on the commands you just entered we have found a set of commands that may match your device." No information about what the codes are, but If I use a T3 remote for the identification, the codes include the new power codes. This also works for the (non-production) T3-style remote in 0xAE97 code mode.

MrQuade wrote:
prl wrote: Being able to learn an alternative code set in that has always been possible. I'm talking about a way to tell it that I want to use, say, the 0xAE97 code set from the Logitech database for the new device entry on the Logitech, I can't see how to to access that.
How about the "Confirm Infrared Codes" feature that I mentioned for an existing device? It allows for the learning mode, as well as allowing you to select a set (from a choice of three available.....not sure what sets they were though.)

Yes, I can get to the choice of three code sets, too, but it seems a bit of a mess. First, there's an alarming-looking message in bold red at the top of the screen that says "The numbers assigned to each command set listed do not correspond to remote addresses for your device". It then lists three code sets, named "Set78884(most popular)", "Set80598" and "Set80599". They look decimal, but I can't find any obvious connection between those numbers and the code set device codes (0xABCD, 0xAE97, 0x02F2, 0x02F3, 0x02F4). I'd guess that they probably are 0xABCD, 0x02F2 and 0x02F3, but I haven't tested whether that's correct.

So there is a choice available, but even in the generally user-hostile Harmony setup program, this is particularly unfriendly. I haven't tested whether any of them actually work in a sensible fashion.

peteru · Post by **peteru** » Sat Aug 27, 2016 20:47

As far as I can see, the Beyonwiz side is well documented and not all that complicated. All I can suggest is that you contact the Logitech Harmony support people and work with them through this. One would hope that since providing universal remotes is their business, they should be able to get their heads around this and come up with a solution.

prl · Post by **prl** » Sat Aug 27, 2016 21:06

The Harmony Java setup program hasn't been updated for a long time and I don't expect it ever will be.

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 21:19

prl wrote:The Harmony Java setup program hasn't been updated for a long time and I don't expect it ever will be.

From what you are saying, the Java application seems to work properly in that it sets the appropriate code set when hinted with a few commands with an original remote.

The lack of a coherent manual selection mechanism is another mate though and incredibly unlikely to get any love from them.

Did you end up trying any of the broken combinations from my post to see if the Java app shared any of the strangeness of the MyHarmony app?

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 21:22

peteru wrote:As far as I can see, the Beyonwiz side is well documented and not all that complicated. All I can suggest is that you contact the Logitech Harmony support people and work with them through this. One would hope that since providing universal remotes is their business, they should be able to get their heads around this and come up with a solution.

If you have recently been talking to them, are you able to just contact them back to tell them that contrary to their claims, their database is not actually correct? I would be more than happy to do it, but you sound like you have their ear already and can speak with some authority when it comes to representing the Beyonwiz company.

They simply appear to, simply, have not done what you have asked them to do.

Edit: actually, on second thought, since the base code sets work properly and it is only the alternates that are buggered, it may be the alternate function is broken rather than the database. I'll probably just contact them anyway. You've already gone above and beyond (wiz?).

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 22:12

I have started a post on the forums to begin with rather than emailing them directly.

Hopefully I get a response from someone helpful rather than a canned response.

Post is here:
https://community.logitech.com/s/questi ... 05Mxh3oCAB

A bit hard to read, as it removed all of my additional newlines *sigh*.

Their new support forum is the WORST!

peteru · Post by **peteru** » Sat Aug 27, 2016 22:18

I have not been doing anything too special with Logitech. Just a bunch of email exchanges with datasupport@logitech.com as was suggested earlier. I think it's best if you take it up with them directly, since at least you have the means to test.

It takes a few days or even weeks to get a response from that email address. It's clearly not staffed by native English speakers. Most of the time it seems like only about 20% of what you write is read/comprehended and most of the responses seem to be canned. The overall impression I got with dealing with Logitech regarding their Harmony remotes is that their back end and database maintenance is complete chaos and they have no means to do bulk imports, automated testing or any other quality control.

peteru · Post by **peteru** » Sat Aug 27, 2016 22:24

MrQuade wrote:Post is here:
https://community.logitech.com/s/questi ... 05Mxh3oCAB

Your post says that the code for T4 is 0x02F4, but that is not correct. All T4 remotes shipped with 0x02F2 and the drivers expect the default code for the T4 to be 0x02F2.

This also contradicts with the information I supplied them with.

Never mind what the Beyonwiz manual claims - it's important to actually get Logitech to follow the real world.

MrQuade · Post by **MrQuade** » Sat Aug 27, 2016 22:49

peteru wrote: Your post says that the code for T4 is 0x02F4, but that is not correct. All T4 remotes shipped with 0x02F2 and the drivers expect the default code for the T4 to be 0x02F2.

This also contradicts with the information I supplied them with.

Never mind what the Beyonwiz manual claims - it's important to actually get Logitech to follow the real world.

Entirely true. I would prefer them to be using 0x02f2 as well, but figured it wouldn't matter as long as it was currently working properly when set to 0x02f4. I didn't want to make things more confusing.

But thinking about it now though, the wake-with-no-keypress behaviour is going to be slightly broken if the T4 is set to all-codes. Damn.

I'll amend the post at the risk of confusing that matter even further.

prl · Post by **prl** » Sun Aug 28, 2016 14:31

OK, I've enumerated the "Command Set" numbers that I see in the Java "Logitech Harmony Remote Software (7.8.1)". YMMV.

T2:
78884 -> 0x02F2 (default)
80598 -> 0x02F2
80599 -> 0x02F3*

T3:
68043 -> 0xABCD (default)
80589 -> 0xAE97

T4:
78892 -> 0x02F2
78893 -> 0x02F4 (default)
78597 -> 0x02F3*

* When using "Command Sets" that should emit the 0x02F3 code set, they actually emit 0x02F4 codes for the new power codes (POWER2/SUSPEND/WAKEUP).

It doesn't seem possible to select code set 0x02F4 on Logitech's T2 remote. Only the 0x02Fx codesets are available on the Logitech T2/T4 remotes and only the 0xAxxx codesets are available on the Logitech T3 remote.

The mapping of Beyonwiz codes to codenames in the Logitech setup is also strange:
PwrToggle -> POWER (as before)
PwrOff -> SUSPEND
PwrOn -> WAKEUP
PwrSuspend -> SUSPEND
PwrWakeup -> WAKEUP
Pwr2 -> POWER2

I'd give the effort about a C+.

MrQuade · Post by **MrQuade** » Wed Aug 31, 2016 19:29

Ok, some very small progress on the Logitech forums.

They have now fixed the 0x02f3 code set for the T4 so that the correct power codes are sent.

It is still configured to send 0x02f4 codes by default, and the 0x02f2, and 0xabcd code sets do not work.

If they can get the broken sets working, and make 0x02f2 default, then I will ask them to make the T2 IDENTICAL! to that

Then work on T3. *sigh*

MrQuade · Post by **MrQuade** » Wed Sep 07, 2016 00:40

Received my first reply from their device support crew, and there has been some small progress.

I have tested the T2, T3, and T4 devices and there are a few outstanding issues.

On the T2 device:
0x02f2 Codes are working
0x02f3 All codes are working except commands 0xfa, 0xfb and 0xfc. Those commands have the incorrect device code of 0x02f4.
0x02f4 This code set does not work at all.
0xabcd Codes are working.
0xae97 Not able to test. (I lack that remote)

On the T3 device:
0xabcd Codes are working.
0x02f2 Codes are working.
0x02f3 Codes are working.
0x02f4 Codes are working.
0xae97 Not able to test. (I lack that remote)

On the T4 device:
0x02f2 This code set is not working at all. This code set should be the default code set, but it currently is not.
0x02f3 Codes are working.
0x02f4 Codes are working, but are set as the default code set. This is not correct default set should be 0x02f2.
0xabcd Codes are working.
0xae97 Not able to test. (I lack that remote)

So probably as good as could be hoped for as a first round attempt. I have replied and asked them to fix the remaining issues with the T2 and T4.

If prl can spare some time, can you please have a look at the Harmony Remote software and check the T3.
Can you now see 5 devices in the list of alternate codes now?

Are you able to test the 0xae97 code set on the T3 (and T2 + T4 if you have the patience).

MrQuade · Post by **MrQuade** » Thu Sep 08, 2016 17:35

Looks like it only took two rounds

Logitech have responded to my last report, and have updated the T2, T3, and T4 remotes in their database accordingly.

Everything that I am able to test appears to be working.

0x02f2, 0x02f3, 0x02f4, and 0xabcd code sets are all working for the T2, T3, and T4, and default code sets are 0x02f2, 0xabcd, and 0x02f2 respectively.

I'll update the Howto thread appropriately, and include a link that points to Logitech's instructions on how to change code sets.

prl, if you can verify the codes are working in the old Harmony application, and try the 0xae97 code sets, that would be great. (how many remotes exist for that set anyway......half a dozen?)

If you are really keen, and can identify which of the Harmony "Command Sets" correspond to which NEC device ID code, I can include that information in the Howto as well. (The manual "Command Set" option is not available in the new app for me to test).

prl · Post by **prl** » Thu Sep 08, 2016 17:49

MrQuade wrote:... prl, if you can verify the codes are working in the old Harmony application, and try the 0xae97 code sets, that would be great. (how many remotes exist for that set anyway......half a dozen?) ...

I'm pretty sure that there are at least two...

I'm not sure what Jai's plans are for this. For two devices in the same room, a T3 and a "T3+" remote set to 0xae97 would be a good way to go IMO.

MrQuade · Post by **MrQuade** » Thu Sep 08, 2016 18:08

Whoops. One little problem with the default settings.

The T2, T3, and T4 currently default to use "Wake" for power on and "Suspend" for power off.

I have requested Logitech to change their database so that "Power Toggle" is used for both power on and power off as default.

prl · Post by **prl** » Thu Sep 08, 2016 18:16

MrQuade wrote:Whoops. One little problem with the default settings.

The T2, T3, and T4 currently default to use "Wake" for power on and "Suspend" for power off.

I have requested Logitech to change their database so that "Power Toggle" is used for both power on and power off as default.

I posted about that before:

prl wrote:The mapping of Beyonwiz codes to codenames in the Logitech setup is also strange:
PwrToggle -> POWER (as before)
PwrOff -> SUSPEND
PwrOn -> WAKEUP
PwrSuspend -> SUSPEND
PwrWakeup -> WAKEUP
Pwr2 -> POWER2

IMO, PwrOn shouldn't exist, and PwrOff should map to POWER2.

MrQuade · Post by **MrQuade** » Thu Sep 08, 2016 18:27

prl wrote: I posted about that before:
prl wrote:The mapping of Beyonwiz codes to codenames in the Logitech setup is also strange:
PwrToggle -> POWER (as before)
PwrOff -> SUSPEND
PwrOn -> WAKEUP
PwrSuspend -> SUSPEND
PwrWakeup -> WAKEUP
Pwr2 -> POWER2
IMO, PwrOn shouldn't exist, and PwrOff should map to POWER2.

Ahh sorry, I missed that when you posted it.
The new software doesn't have the equivalent "PwrOn" or "PwrOff" codes in the database (it only has the toggle, suspend, wake and power2 ones and no other aliases), so I didn't see them in my testing.

I am going to have a crack at testing the 0xae97 codes myself using my Pronto, but I still have no way of telling which "Command Set" maps with which device ID for the older software.

prl · Post by **prl** » Thu Sep 08, 2016 18:34

I may have time to look at that tomorrow, Friday.

Gully · Post by **Gully** » Thu Sep 08, 2016 18:41

prl wrote:
MrQuade wrote:Whoops. One little problem with the default settings.

The T2, T3, and T4 currently default to use "Wake" for power on and "Suspend" for power off.

I have requested Logitech to change their database so that "Power Toggle" is used for both power on and power off as default.
I posted about that before:
prl wrote:The mapping of Beyonwiz codes to codenames in the Logitech setup is also strange:
PwrToggle -> POWER (as before)
PwrOff -> SUSPEND
PwrOn -> WAKEUP
PwrSuspend -> SUSPEND
PwrWakeup -> WAKEUP
Pwr2 -> POWER2
IMO, PwrOn shouldn't exist, and PwrOff should map to POWER2.

Power Toggle as default sounds reasonable but what would be the effect of not having PwrOn and PwrOff mapping to POWER2?

I have used those 2 in my current Harmony config as I didn't see PwrSuspend and PwrWakeup when I first set it up.

MrQuade · Post by **MrQuade** » Thu Sep 08, 2016 19:04

Gully wrote: Power Toggle as default sounds reasonable but what would be the effect of not having PwrOn and PwrOff mapping to POWER2?

I have used those 2 in my current Harmony config as I didn't see PwrSuspend and PwrWakeup when I first set it up.

I don't think it should matter.

If the Harmony defaults to using Power Toggle, then they will work with a Wiz with a factory configuration.

As long as POWER2, PwrSuspend and PwrWakeup exist in the database, you can configure your Harmony to use them. If PwrOff is just an alias for POWER2, then there shouldn't be any confusion if someone wants to customise their power settings.

MrQuade · Post by **MrQuade** » Thu Sep 08, 2016 19:28

Bugger, code set 0xae97 works for the T2 and T4, but not the T3. Another email

Edit:
*facepalm*
I just found a more insidious problem with the Harmony codes

.
My T2 device, when set to Device ID 0x02f3, correctly sends Devide ID 0x02f3, but is using the set of command codes for the 0xabcd/0xae97 remotes. ie. When I send a Power Toggle, it is sending command code 0x0a, instead of 0x3c.

This is going to take a while to untangle

.
I really don't know how they got this wrong. PeterU's original set of codes was pretty unambiguous!!!

prl · Post by **prl** » Fri Sep 09, 2016 13:53

MrQuade wrote:...
My T2 device, when set to Device ID 0x02f3, correctly sends Devide ID 0x02f3, but is using the set of command codes for the 0xabcd/0xae97 remotes. ...

Here's a handy table of the code table differences between the T2/4 remotes (0x02Fx) and the T3 remotes (0xAxxx), extracted from peteru's code tables:

Code: Select all

Code  T2/4 decode       T3 decode
----  -----------       ---------
0x04  KEY_LAST          KEY_MENU
0x06  KEY_EXIT          KEY_INFO
0x07  KEY_PLAYPAUSE     KEY_PROGRAM
0x09  KEY_MENU          KEY_LAST
0x0A  ---               KEY_POWER
0x0B  KEY_PREVIOUS      KEY_SUBTITLE
0x0D  KEY_NEXT          KEY_TEXT
0x0F  ---               KEY_TV
0x1A  KEY_SUBTITLE      KEY_RADIO
0x1C  KEY_INFO          KEY_EXIT
0x3C  KEY_POWER         ---         
0x41  KEY_PROGRAM       KEY_FAVORITES
0x42  KEY_TEXT          KEY_BOOKMARKS
0x43  KEY_AUDIO         KEY_NEXT
0x44  KEY_SCREEN        KEY_PREVIOUS
0x45  ---               KEY_AUDIO
0x4C  KEY_BOOKMARKS     ---
0x50  KEY_RECORD        ---
0x51  KEY_TV            KEY_SCREEN
0x52  KEY_RADIO         ---
0x53  KEY_HELP          ---
0x54  KEY_FAVORITES     KEY_STOP
0x55  KEY_STOP          KEY_PLAYPAUSE
0x56  KEY_SEARCH        KEY_RECORD
0x64  ---               KEY_HELP
0x65  ---               KEY_SEARCH

The three columns are the key code, what it decodes to if the vendor code is 0x02Fx and what it decodes to if the vendor code is 0xAxxx). "---" means that there's no valid decoding of the key code for that vendor code.

The attachment is the same info as a download. Unix style line endings.

MrQuade · Post by **MrQuade** » Fri Sep 09, 2016 15:09

Thanks for that prl.

After some testing last night, their issue seems to be somewhat less tangled than I thought.

It looks like they just used the T3 style command codes for all of the 0x02f<n> vendor codes.

I just told them what the problem was and requested they re-do all of the 0x02f<n> sets as-per the lists that PeterU posted earlier in the thread. I decided last night, not to waste more time dictating the differences code by code.

At least it explains why when learning some code sets, the Harmony only asks you to press POWER and for other sets, it asks for both POWER and 1. (The command code for 1 is the same between the two sets, but POWER is one of the different ones). Also, if the Harmony database doesn't have a code set, it asks you to press POWER, 1, then CH+, then gives up.

prl · Post by **prl** » Fri Sep 09, 2016 16:20

You might want to download it again. The first version had an error.

prl · Post by **prl** » Fri Sep 09, 2016 16:51

I've confirmed (fairly exhaustively) that the Logitech Command Set 80781 has the 0xAxxx key codes sent with the 0x02F2 vendor code.

I haven't enumerated all the Logitech Command Set numbers yet, but it's wort a note that the set for the T2 and T4 devices are the same {80760, 80763, 80780, 80781, 80782} (and 80781 is the broken 0x02F2 code set, so I'd expect it to be broken for both T2 and T4 devices in the Harmony). The default (and "most popular") code set for both the T2 and T4 devices is 80781. None of the T2/4 command set numbers are the same as when I enumerated them when the codes first came out.

The T3 has a different (in fact, disjoint) set of Command Set numbers: {68043, 80589, 80741, 70753, 80755}. The Harmony app notes 68043 as the "most popular" and the default, so it looks like it should be 0xABCD. The command sets 68043 and 80589 were in the previous enumeration I did as the code sets 0xABCD and 0xAE97 respectively.

I would guess that fixing Command Set 80781 may fix the commands for both the T2 and T4. I strongly suspect that fixing 80781 won't fix the 0x02Fx commands for the T3 device, if they are also broken.

I have no idea why the T3 has been given what looks like a different set of copies of the same (or perhaps, even more frustratingly, almost-the-same) code sets. It all looks a bit like "let's do it in the most fragile and hard to check way that we can".

prl · Post by **prl** » Fri Sep 09, 2016 17:06

T3 Command sets 80741 and 80753 are for vendor codes 0x02F2 and 0x02F3 respectively. The 0x02F2 codes appear to be broken in the same way as the 0x02F2 codes for the T2/T3 remotes.

MrQuade · Post by **MrQuade** » Fri Sep 09, 2016 17:35

Ok. Best probably holding off on enumerating those Harmony command sets for now, until we know they have them correct. If they change numbers between updates, then it will just be wasted effort.

And just thinking about it, it might not even be worth documenting them at all if they are subject to change down the track.

prl · Post by **prl** » Fri Sep 09, 2016 17:52

MrQuade wrote:... Best probably holding off on enumerating those Harmony command sets for now, until we know they have them correct. ...

I'm not sure how to do the latter without doing the former.

MrQuade · Post by **MrQuade** » Fri Sep 09, 2016 20:02

prl wrote: I'm not sure how to do the latter without doing the former.

Use your real remotes to teach the one or two commands that are required for it to identify which code set to use rather than selecting them from the list.

I can make sure they get the database sorted out (at least for the new remotes), but once I get that right, I may have to get you to check just to make sure the old app is working off the same database.

About the Forum

Join us