For a while now I’ve been frustrated that the highly capable ‘smart’ electric car charging point installed as part of the Electric Nation research project reverted to ‘dumb’ mode at the end of the trial period. It’s not been too bad because the car has some of its own intelligent charging logic but since moving from the Octopus Agile tariff to Octopus Go (with a rate of 5p per kWh between 00:30 and 04:30 every night) it’s become more important to do all the charging between those times – and I’ve got enough of the API to the charge point working to exercise the control I need.
There’s a separate Technical Article on the details of the Circontrol EVSE API but the following high-level logic is currently working well:
- The car is configured to charge immediately and at the maximum rate of 32A / 7kW
- The charge point is normally configured as ‘Disabled’; this state is automatically set at 12:00 (noon) every day
- This means that the car can be plugged in at any time after that and it doesn’t start charging
- At the start of the Octopus Go low-tariff period (00:30), there’s a script which runs to:
- Check there is a car connected to the charge point
- Change the charge point to the ‘Enabled’ state
- Run the ‘Remote Start’ transaction to prompt the car to start charging
The result is that – whenever the car needs charging overnight – it can be plugged in at any time of day and it will be fully charged by the morning, using cheap-rate electricity. The charge point is also available to power pre-conditioning of the car and the battery for a morning departure, if that has been configured in the car.
(If the car battery is really low (like less than 10 miles of range) it can take 4.5 hours to fully charge at 7kW, so it’s not quite fully charged by 04:30 when the cheap-rate period ends. The least-bad thing to do is to leave it charging until it finishes, which is probably no later than 05:00.)
5 years after installation I’ve just encountered the first significant failure of the home automation system. The KNX module that monitors the momentary-action ‘light’ switches in the bedrooms stopped responding. Upon checking the unit all of its LEDs were flashing on about a 1-second cycle, so it wasn’t completely dead, but it clearly wasn’t happy. Turning it off and on again didn’t help.
The module is a 16-Channel Binary Input Module for Potential-Free Contacts, made by MDT in Germany. Searching for reports of similar problems turned up a couple of posts (in German) on https://knx-user-forum.de/ that hinted at a firmware bug. These devices come with a generous 3-year warranty, but I confirmed the purchase date and it was May 2016. A new replacement unit would be about 200 GBP.
I contacted MDT Support who confirmed there was nothing further I could do as an end-user and suggested I send the unit back to them for repair. They expected it would just need new firmware loading.
Sadly, thanks to Brexit, sending devices for repair in the EU is much more complex than when the UK was in the Single Market. The principal consideration is avoiding the imposition of either Import Duty or VAT – either when the package is going to Germany or coming back to the UK. (These would apply to the initial purchase, but because all applicable taxes had been paid in 2016 they do not need to be paid again, since nobody is making a new purchase.) I found little useful guidance on the Royal Mail or HMRC websites but stumbled across this very useful post from Mura Car Accessories, based in Romania and followed those instructions carefully – with good results. (A key step seems to be declaring a Temporary Export for Repair Purposes on the C22 form.)
The delivery of the repaired item was delayed because of an issue recording the UK (alphanumeric) postal code in one of the German systems (some mix-up between MDT and UPS, by the look of things), but it was delivered today and simply needed re-installing and re-programming. I am grateful to MDT for not charging for either the repair or the return shipment, so I got a good-as-new device for just the 7.50 GBP outward postal charge.
While the unit was away for repair, none of the wall switches were working, which was slightly annoying but actually highlighted a strength of KNX’s modular architecture. All of the rest of the home automation system continued to work perfectly and a simple workaround was to control the bedroom lights with the openHAB iPhone app instead – which still triggered the openHAB rule that sets ‘Night Mode’ when the bedside lights are turned off.