A zero stored by an electric-vehicle efficiency sensor could affect far more than its own graph when Home Assistant converted between inverse units such as kilowatt-hours per 100 kilometres and kilometres per kilowatt-hour. One such value could stop the entire five-minute statistics job for every entity and fail again on the next run. A second path could break period-statistics queries and their graphs.
The fix routes both recorder paths through a converter that treats zero as unavailable when the conversion would divide by it. Statistics retrieval returns no value for that point, while compilation skips it as it would a non-numeric state. The change is limited to recorder statistics; the live entity-display path remains outside this fix.