Last time I got low battery warning I went either 37 or 47 days before I actually had to swap it out. Remote remained fully functional till close to the bitter end. As of today, I’m 13 days getting that warning; waiting to see if I can break previous record
Depends on usage. It’s not a record to be beaten but a sign that you need to change the battery over.
A battery will last a long time with normal usage and 40 days really is the bottom of the tank. The idea is to advise users that a replacement is needed and give them plenty of time to do so.
Obviously unlike a car running it to empty won’t stir the bottom of the tank, so we could consider a way of suppressing the warning in the future. But the question is how to re-activate that warning when the user replaces the battery.
A user can do it themselves whenever they wish…
<?xml version="1.0" encoding="UTF-8"?>
<!-- disables low battery warning on OSMC remotes -->
<keymap>
<global>
<keyboard>
<f2>noop</f2>
</keyboard>
</global>
</keymap>
I even put this very thing as an example in the keymap guide…
https://osmc.tv/wiki/general/osmc-remote---long-press-keymap-guide/
Aware of that – but I’m thinking of a setting in Kodi.
The problem is that we introduced this nagging for a reason – because before we became a battery replacement service…
I suppose someone could do this to limit how often they see the warning…
<?xml version="1.0" encoding="UTF-8"?>
<keymap>
<global>
<keyboard>
<f2>noop</f2>
</keyboard>
</global>
<home>
<keyboard>
<f2>Notification(OSMC Remote Controller, Low battery please replace,5000)</f2>
</keyboard>
</home>
</keymap>
Not a bad idea; maybe we should consider that.
Do you mean end-users requested or required you to replace batteries?
I read that a while back, but probably not the whole thing since I just noticed the low battery notice part.
Don’t feel bad. I am the one who wrote that guide and had forgotten I had put that in there until after I had retyped that keymap and written most of that post. 
Changing the keymap is going to help the annoyance factor if that warning is popping up sooner than it should. If the battery really is getting drained that fast though (remote starts missing keypresses’ or just stops working altogether including the warning) you might look to see if you have any devices using 2.4ghz radio signals particularly close to the receiver as that has been known to potentially cause the battery to drain much faster.
Users were sending back the remote as faulty and insisting they had changed the battery. They hadn’t… it was expensive to ship the remote back and forth just to replace a battery…
This is the first time I am reading about such a warning. During all the years of using OSMC remotes and having to replace the batteries multiple times after they were not responding to any inputs anymore, I have never seen this notification.
Is there a way to check for the setting or manually enable the notification?
The low battery notification has not been on all of the Vero remotes. The 2252:1037 and 2017:1688 remotes (this is a vendor and product id that shows in your logs) did not have this notice. The 2017:1689 and the current 2017:1690 remotes will send out a F2 key press when you push a button and the voltage in the remote is reading below a certain threshold. This key press was keymapped to a notification around three years ago on all OSMC systems, and for all other linux installs if Kodi sees an OSMC remote around two years ago IIRC.
That sucks. I wonder if that’s a common scam.
I don’t think so. Our customers aren’t scammers. I think a lot just didn’t believe their battery could’ve died / needed replacing and thought something must be wrong.
Voltmeters are common and cheap…
This is a very old thread.
The warning can be suppressed, but until we have further reports of the warnings being ‘too early’, we’re reluctant to adjust anything yet.
So it is! Not sure why it popped up then.
I just meant that people ought to be able to check a button cell state for themselves.
Had to chime in here, sorry for adding to the necro threading Sam.
So as you know mate I upgraded to the V5 and I had never seen this warning before, guess I had an older non supporting remote with my V4.
Saw my first warning a couple of months in V5 ownership and was a little baffled having not seeing it before.
Were it my business, which it is not, I’d have manufacturing ship the battery uninstalled. The time that battery is sitting in the remote is draining the factory battery somewhat between installing and end user delivery. This causes a less than normal battery life and the ‘false positive’ fault diagnosis from users that jump to wrong conclusions. For reference I have changed out my factory battery since getting the warning and have already exceeded its life by far with a fresh battery.
One final question, the warning is based on an internal voltage reading of the battery or did I misread that and it’s just X days?
Not at all.
There’s a thin insulating layer between the remote and battery to stop unnecessary drain in transit. You might have just been unlucky and had a faulty or poorly performing cell.
Voltage.
From memory, if there’s a low voltage (2.2V), then each time a button is pressed, we will send the F2 keycode, which will trigger a low battery notification. It’s a bit spammy, but solves us becoming a battery replacement service.
I must have been unlucky as you said and hadn’t got one of the insulation strips on mine. Glad it’s a normal thing though.
The voltage thing is really cool, not seen it on the OG V4 remote (assuming it was one of the aforementioned models that didn’t do it). I kinda ignored it for a week and thought I’d msg you one day and ask, then saw the thread. The V5 (even as a V4 owner) has been a constant improvement and joy to use.
Can’t wait for French comms to pull their fingers out and get fibre to my house (which should have been here first quarter 2023 but has had delays on delays) and I can use the V5 at ‘maximum warp speed’ 
Stunning product mate.