You could copy the attachted file to /usr/lib/enigma2/python/Plugins/SystemPlugins/InputDeviceManager (please make a backup of the original) - restart enigma2 - e.g. using the console command dreamboxctl restart - and try the JVC TV.
Feedback would be VERY welcome!
Note: The JVC protocol is already there. But as we have nothing to test it on and I honestly didn't expect any JVC TV to still be around, I didn't add it to the device database (until now).
Thanks!
The "TV" entry didn't work, unfortunately. But with a bit of toying around, I found that the "LCD TV" had at least the power button working. Reading the .json it then became clear that the "device": 3 entries are candidates in my case, and they did indeed all work for me. I ended up using one of the RM-... entries that had this device ID to get the most important functionality.
So you solved my problem - thank you!!!
Where do these entries actually come from? There is a lot of redundancy; some of the RM-xxx entries are essentially identical apart from the name, and some have only one or two more buttons defined compared to another. Many are incomplete; I found one ("Monitor") that defines the "Menu" button, but lacks the definition of right/left/up/down that would be needed to move around in the menu after it has come up. In principle, is it possible to combine entries for different buttons from various entries for the same device? Having a somewhat consistent naming scheme would also be helpful. Sorry, that's not a critique, just an observation - it must be a nightmare to maintain this, especially without access to the actual hardware. And for old and outdated hardware like mine... So thanks for your work on this - and it would be really nice to keep the JVC entries.