I have bought a Vero V recently and very happy with it’s performance so far.
I have have some questions about the power and remote though.
Is there standby/off function? On my other players, there is a power button. When I press that it turns off my tv and AVR etc, and when I turn it on, it turns everything on. That way I only use the media player remote. With the Vero V, I can’t do that, so I have to use the TV remote, which works ok, but it doesn’t have the long press functionality.
With the remote, is there a way to get the long press functionality? I use that a lot. I understand there is a menu button, but there is no such button on my TV remote.
The default keymapping of the OSMC remotes allow for CEC power on/off. First you have to have cec enabled on your TV and then in Kodi you would need to go to settings>system>input>peripherals>CEC adapter and set the settings for devices to power on and off. Make sure you click OK to exit this screen as hitting the back button might not save them. I don’t remember if you need to reboot to have these settings take effect. Once you have that set then from the home screen you should be able to long-press the home button on the OSMC remote to power off. To power on you would press the home button somewhere between 1-3 times, depending. If Kodi is in screensaver/sleep mode then the first press will wake it but not register to Kodi as a keypress to process. If you not on the home screen then the home button will take you to the home screen. When your on the home screen the home button short press will send a CEC wake signal to your TV and/or AVR/sound bar depending on what you had configured.
If one wanted to make the home button dedicated to that function, I have a keymap to do this in my long-press keymap guide…
As for getting long-press working with a TV remote, you can’t with just some simple settings change. Basically anything that goes through LIRC doesn’t support this. This means anything using the built-in Vero IR or CEC input. If your TV remote has the ability to act as a universal remote then my recommendation would be to pick up a FLIRC USB IR receiver and a USB extension to plug it into. You would then with a PC program the FLIRC with your TV remote programed to something like a media center remote, or an xBox so you have full selection of buttons to work with. You will probably want to program the flirc to match up with standard Kodi keymapping layouts so you don’t have to mess around with a bunch of Kodi keymapping. You can reference the most common ones [here] in a user friendly format. Just don’t have whatever you use for the FLIRC also set in the My OSMC add-on’s remote section as you don’t want two different receivers responding to the same signal. You can program the FLIRC to long-press commands. I suggest to not do this and just set any custom long-press actions in a Kodi keymap. Kodi will pick up long-press from this device so don’t complicate things by having the FLIRC send out two different for a short and long.
The other option for long-press is if your TV remote will do Bluetooth to a secondary device. You could pair such a thing in My OSMC and if it works, it will also have long-press support.
As for a menu button on your TV remote, I’m going to assume you mean controlling Kodi via CEC. Most TV’s only forward a limited number of buttons via CEC and which ones vary from TV to TV. To overcome this one generally would need to find a button that is forwarded that isn’t essential for other functions, and then program that to act as a menu button. On some remotes this may be programming one of the colored buttons, on another this may mean programming to a rw, ff, or chapter +/-. This is easiest accomplished with the Keymap Editor add-on that can be found in Kodi’s repository.
Thanks for the reply. Unfortunately it’s not helped in either case.
Holding the home button does nothing on my Vero.
CEC is enabled and working. This is how I am able to use my TV remote to control Vero. I can also use the Vero remote to control the volume of the AVR. The CEC parts works well out of the box. But as a precaution, I have gone into the settings and have put the CEC back to default.
Holding the home button on the Vero remote does nothing for me. The home button itself works, when I press it, it takes me to the home screen. But holding it does nothing.
The long press issues is both on the Vero remote and my TV remote. On the Vero, long press of the middle/OK button does something, but doesn’t bring up the menu as you would expect. It takes you to back to the first item on the list. On the TV remote, it seems to be pressing the OK button constantly rather than a long press.
I have a few other remotes from other media players. I will try to pair those up and see if I can get different results.
To be clear, the “home button” only sends power commands when in the “home” screen. The home screen is the main landing page that the system boot up into. You could turn on debug logging and try it from the home screen and then upload a Kodi log and paste the url and I could check it to make sure it is sending the command. It may be possible that your TV and/or AVR isn’t able to, or isn’t configured for responding to CEC power requests I suppose. If that is the case there is nothing that can be done about it from the Kodi side that I’m aware of.
As for the menu not coming up when long-pressing the select/OK/enter button, that is expected as that function was intestinally removed from the default keymapping with the OSMC keymap. It makes sense when using something like an old apple remote that lacked a menu button, but is redundant on a remote that has a dedicated button for the function. As for what the long-press are programed to it depends on what screen your in and I listed most of them in the long-press guide I linked to above.
As for the other remotes, the issue is not the remote itself. There is a software layer (LIRC) that sits between the built-in IR sensor and CEC input and Kodi, and that software is what doesn’t support passing through the long-press. The OSMC remotes and the hardware I previously mentioned don’t take that same route as they present themselves as generic keyboards and go directly into Kodi.
The ‘home’ button does work. I press it, and it takes me to the ‘home’ screen. I will do a debug log tonight.
As for my TV and AVR, the CEC power on and off definitely works. I’ve had many media players connected to it, and all of them have been able to turn the TV/AVR on and off. That’s not the problem here. The problem here is turning the Vero on and off. In this case, holding the ‘home’ button when in the home screen does nothing.
OK. I now understand the long press is disabled by design on the OSMC remote.
Is there a language barrier going on here? This comment very much sounds like your not fully understanding my responses to you.
If you have other devices plugged into the same setup that will power the TV on/off then you should be able to do this with the Vero as well. Since the TV also isn’t going to sleep when you tell Kodi to power off as well then it seems most likely you have not gotten your CEC setting configured as mentioned earlier. Go back to your Kodi CEC settings and make sure you have the following…
Switch source to this device on startup - ENABLED
Put devices in standby mode when activating screensaver - ENABLED
Wake devices when deactivating the screensaver - ENABLED
Enabled - ENABLED
Devices to also put in standby mode - ENABLED
For these two option how they should be set depends on one’s particular setup. They might need to be set to just “TV” if the TV and/or AVR is configured to power on/off together. Otherwise it may need to be set to TV and AVR. If there is still an issue it may need to be set as forced.
Devices to power off during shutdown
Devices to power on during startup
These settings may need to be enabled or disabled depending on a person’s particular setup.
Force AVR to wake up when Kodi is activated
Send “inactive source” command on shutdown
This thread should cover all the info you need to overcome your issues. Perhaps you can give it another read through in the future and maybe it won’t seem as intimadating.