JP1 Remotes

[JHBrandt]

This is a very simple remote: only 13 buttons. I listed two functions twice in the .RMDU because they work slightly differently depending on whether the PIP is active, so there are 15 total functions in the file.

I didn't assign any functions to remote buttons in the .rmdu; I figured since there are so few, and since they don't necessarily map intuitively to most universal remotes, it was best to let each user assign the functions to their remote's buttons as they see fit.

A note to those considering purchasing this device: this remote uses the very common NEC protocol with the very common device code of 0/255; an unfortunate choice which often results in conflicts with other remotes, such as those for the HomeWorx HW-180STB and the Terk TUNVR1 set-top box/DVRs. So make sure to check the protocol for your other device remotes before purchasing

[JHBrandt]

Turns out this HDMI switch doesn't care what sub-device code is sent; the remote that comes with it sends 255, but you can send, say, 251, and the switch will still respond.

This is bad in one way, because it means lots of remotes will inadvertently control this switch. For example, a remote for a StarTech HDMI switch, or a remote for an HW-130, HW-180, or HW-220 STB, will cause unwanted actions on the DotStone switch.

I haven't found a way around that yet, but on the plus side, at least the upgrade file can be changed so that a remote using the upgrade is less likely to inadvertently control another device. So, i changed the upgrade file to send sub-device 250 vs. 255; my upgrade file still works, but now using it no longer causes unintended actions on my HW-220.