Intelligent charge target sensor now requires multiples of 5

[ianfriend]

A recent change to the integration has added a validation to the Intelligent Charge Target sensor to only allow multiples of 5. This has caused my automations to now fail.

Was there a specific reason that this was introduced as it seems inconsistent with the octopus app which allows target charged in increments of 1.

[BottlecapDave]

Hello. When the feature was originally added, the app only supported multiples of 5. The restriction was already there in the sensor, but ha only seemed to enforce it when using the up/down arrows, not when applying the value. This matched the enforcenents in other integrations. This apparently caused errors when sending to the OE APIs and attempting to view in the app (#1079 (comment)). Someone else stated that the app then updated to support increments of one, but I could not confirm. I'm not on intelligent so can't confirm myself.

If this is wrong, please raise an issue with proof that you can change the value to an increment of one in the app, and I'll try and fix the issue in the next release.

[ianfriend]

Thanks for the reply Dave,

Issue created: #1157