Use a finer grained filter for charging level (power) about evplugfinderpublic HOT 8 CLOSED

even with settings set to "Schuko (Type F) OFF" the APP offers the loading point "Kulinario" in Schweinfurter Straße 7, 97525 Schwebheim, Germany.
Data base shows 2x 3kW Schuko and 0x several other plugs for this location, so this might be a problem with the database - maybe you are able to sort them out anyway.

from evplugfinderpublic.

@secuder the "0x" is definitely a bug in the OCM data, yes, the "count" property being optional it should have been null in the JSON having the semantic "number of connections unknown". Unfortunately the "0" means the same for the OCM logic, for that reason the filtered query also lists this entries.

from evplugfinderpublic.

understood - it will be hard to improve the database at this point :-) but any possibility to filter that in the APP?
Not good, I know, but better than false readings

from evplugfinderpublic.

@secuder I can't workaround this issue, this has to be done in the OCM database layer.. I will try to open a bug request there..

from evplugfinderpublic.

Hm, workaround does not work on build 12: Loading point "Kulinario" in Schweinfurter Straße 7, 97525 Schwebheim, Germany is still on display even with Schuko OFF.
(Data base shows 2x 3kW Schuko and 0x several other plugs for this location)

from evplugfinderpublic.

@secuder this is an issue with the OCM database. 0x means there often "we simply don't know how many plugs are available". So I can't just filter them out, this will be just wrong. It would have been better to save a null instead of the int 0, but ..

from evplugfinderpublic.

I see, but what kind of workaround have you implemented then?

from evplugfinderpublic.

my comment is just wrong, I will delete it

from evplugfinderpublic.