ChargerSync

Bluetooth connectivity fails due to poor BLE management. Writing code in Android (which doesn’t have stringent BLE management) then running through an iOS emulator to transcode without validation, beta testing is inexcusable. This may also include the charger’s firmware. For a company so well established, how can anything like this continue to happen?

Improved a lot compared to previous iteration, but I need to use the old one still sometimes to be able to connect. I am disappointed that I cannot have multiple schedules to accommodate different off peak periods (noon, night, full weekends). I would like to be able to both schedule and also define prices for those periods. Most annoyingly, the application started yesterday to produce a popup “the charge point has been booted” every hour or so…