Hi All,
I have a 2016 30kWh Leaf and I'm running Firmware: 3.3.005-869-ga0afe28f0/ota_0/edge (build idf v3.3.4-854-g9063c8662c May 5 2026 15:38:09, product v3.3-5) however I think most of these issues are the same on the previous stable version.
Contrary to information in other issues and elsewhere on the internet the remote door lock/unlock does work on my 2016 Leaf, and does set and disable the alarm correctly as well, which is great. (I specifically tested this after reading reports of the alarm not being disabled on unlock)
However there are a few usability issues with the lock/unlock feature.
-
If you use remote unlock while the remote climate control is running it stops the climate control. Using the normal remote fob to unlock the doors does not cancel remote climate control.
-
If the car is plugged in with the charge timer preventing charging (timerwait state) locking the doors via OVMS overrides the charge timer and starts charging the car. Seems an odd thing to do... and certainly doesn't happen with the key fob.
-
Remote locking via the fob is prevented if the key fob is in the car, or any door is open, however remote locking via OVMS will happily lock the doors even if the key is in the car or a door is open, making it easy to lock the key in the car, or lock the car from a distance not realising a door is not properly closed and can later be opened by someone even though it reports the car is now locked. Since the state of the doors is known it should at least be able to check the doors are closed before sending a lock command ?
Tangentially related to this I've also noticed:
- If the car is plugged in but NOT charging due to the car being in timer wait mode (outside the allowed charging times) starting remote climate with OVMS will start charging the car and will actually charge for the entire remote climate period. This was definitely not the case when remote climate control was started with the TCU and Nissan App/API.
Yes, you would see the charge percentage go up about 2% but then hold there. So for example if the car was at 80% SoC and in timer wait mode, starting climate control from the Nissan app would cause the SoC to creep up to about 82% in the first 10 minutes, then it could run the remainder of the maximum two hours without going any higher and with the only power consumption from the charge point being that to run the heater. (And ECU overheads etc)
When triggered via OVMS it seems to just override the charge timer and charge flat out the whole time. This is also problematic if you're using suffisoc - say that is set to 80%, as soon as the SoC goes over 80% during the remote climate session suffisoc will shut off the charge point, stopping the remote climate control prematurely.
So if you use suffisoc and have the car plugged in you can't really use the remote climate control properly as it will just turn back off again, which is a shame!
- suffisoc doesn't always play nicely with the charge timer. Sometimes - for reasons I haven't been able to find a pattern to, I'll plug the car in after a drive and it will just start charging immediately, ignoring the charge timer. Usually sending a stop charge command via the app will stop the charge and put the car into timer wait mode correctly, however I never sent a start charge command earlier to override the timer...
This has happened a lot less often since I set Allowed SoC drop to 4% - and also fixed another weird problem. I have the charge timer set to 12:30am to 4:30am - on a day when the allowed SoC is set to 100% it would charge in the time window as expected then stop, then some time around 6:20am (why then I'm not sure!) the car would report 98% SoC and start charging again - even though it was outside the configured charge timer window. suffisoc appears to override the timer wait state if the reported SoC drops below the threshold, but IMHO it should respect the timer wait mode ?
Anyone else notice any of these issues ?
Hi All,
I have a 2016 30kWh Leaf and I'm running Firmware: 3.3.005-869-ga0afe28f0/ota_0/edge (build idf v3.3.4-854-g9063c8662c May 5 2026 15:38:09, product v3.3-5) however I think most of these issues are the same on the previous stable version.
Contrary to information in other issues and elsewhere on the internet the remote door lock/unlock does work on my 2016 Leaf, and does set and disable the alarm correctly as well, which is great. (I specifically tested this after reading reports of the alarm not being disabled on unlock)
However there are a few usability issues with the lock/unlock feature.
If you use remote unlock while the remote climate control is running it stops the climate control. Using the normal remote fob to unlock the doors does not cancel remote climate control.
If the car is plugged in with the charge timer preventing charging (timerwait state) locking the doors via OVMS overrides the charge timer and starts charging the car. Seems an odd thing to do... and certainly doesn't happen with the key fob.
Remote locking via the fob is prevented if the key fob is in the car, or any door is open, however remote locking via OVMS will happily lock the doors even if the key is in the car or a door is open, making it easy to lock the key in the car, or lock the car from a distance not realising a door is not properly closed and can later be opened by someone even though it reports the car is now locked. Since the state of the doors is known it should at least be able to check the doors are closed before sending a lock command ?
Tangentially related to this I've also noticed:
Yes, you would see the charge percentage go up about 2% but then hold there. So for example if the car was at 80% SoC and in timer wait mode, starting climate control from the Nissan app would cause the SoC to creep up to about 82% in the first 10 minutes, then it could run the remainder of the maximum two hours without going any higher and with the only power consumption from the charge point being that to run the heater. (And ECU overheads etc)
When triggered via OVMS it seems to just override the charge timer and charge flat out the whole time. This is also problematic if you're using suffisoc - say that is set to 80%, as soon as the SoC goes over 80% during the remote climate session suffisoc will shut off the charge point, stopping the remote climate control prematurely.
So if you use suffisoc and have the car plugged in you can't really use the remote climate control properly as it will just turn back off again, which is a shame!
This has happened a lot less often since I set Allowed SoC drop to 4% - and also fixed another weird problem. I have the charge timer set to 12:30am to 4:30am - on a day when the allowed SoC is set to 100% it would charge in the time window as expected then stop, then some time around 6:20am (why then I'm not sure!) the car would report 98% SoC and start charging again - even though it was outside the configured charge timer window. suffisoc appears to override the timer wait state if the reported SoC drops below the threshold, but IMHO it should respect the timer wait mode ?
Anyone else notice any of these issues ?