If we can't read data from your Sparky, you cannot charge. Follow these steps to fix the issue.
Need to charge urgently? Your installer can remotely re-configure your charger without sparky. This temporary solution will disable dynamic load management.
They must use the Volt Time Installer app.
Alternatively, Sparky can also be disconnected from your charger via the Web Portal. Go to Location>Load Management and remove the Meter. The charger should probably be set to charge at a lower speed, as load balancing will no longer work.
How to check if there is a problem with your Sparky
Chargee App
Via the Chargee app on your phone. If there is no Live data, then there is a problem with Sparky.
Note that Volt Time only supports P1 smart meters with (D)SMR4.0 or higher. If you have a lower version, your installer must use a different metering solution.
Web Portal
Start a charging session.
Go to Location>Load Management
Scroll down to Technical Details
If the Meter only shows "- A", and no actual values, there is a problem.
Note: If you do not start a charging session, all values in this screen will be "- A", which does not indicate a problem. You must start a charging session to know if there's an issue.
How to fix issues with Sparky
Most common fixes:
Sparky must be connected to your P1 via the grey IN port, not the black OUT port.
Sparky must connect to a dedicated 2.4GHz WiFi network. Combined 5GHz/2.4GHz may result in Sparky getting stuck in the final step "Connecting to Chargee server".
Try using the USB-C power adapter for Sparky.
Try resetting Sparky.
For a complete guide, see Chargee's support article.
More common issues
Mesh/WiFI extenders must be put into Bridge mode. If Sparky blinks but remains stuck in "reading smart meter", it could be that the extenders are in DHCP mode.
Sparky can take 15 minutes to finish "reading smart meter", or in rare cases even 24 hours. Sparky will not blink. You can finish the installation and Sparky should come online later.
Make sure the firewall settings allow for outbound traffic for internal devices. This is often a problem for company networks.