Improve UI for number settings

[pilot51]

Change number settings to use box instead of slider
I find the slider to be annoying to use as it normally doesn't show its value and is often difficult to accurately change it to a desired value, especially when using a touchscreen or when the slider is so short that it skips numbers.

Change display units "PERCENT" to "%" and "VOLT" to "V"
Using full words for units takes up a lot of valuable space, especially when viewed in a narrow column as is common in HA.
Using the unit's symbol allows more space for the entity name or value.

[zakery292]

#101 im assuming you didnt see my reply to your original issue. Im not going to merge this for all as people might not want this change we need to look at making it configurable VIA the config flow other wise we will annoy people. Im also looking at a way for custom configs so you all can have 1000 different const.py files or a config file that is not over written on update

[pilot51]

I'm not exactly convinced a text box would annoy people. I'm already annoyed by the slider and see little benefit to it. On the other hand, xkcd 1172.

The issue you mentioned about HA firing excessive commands may be a problem, but it doesn't appear to be something that would be visible to users. In my testing, I see no difference in the entity activity history. Changing a value causes it to change back to the old value and then back to the new value regardless of the entry type, which I assume is because it takes a few seconds for the setting to actually apply and the dongle publishes the old value shortly after the update request is sent.

[zakery292]

So i have added this in the options flow. should you want to use it just enable it there and it will set for you. this gives the best of both worlds for the people that like the slider and the people that want number instead of a blanket decision im going to close this once you let me know your happy with this solution its ready in release 3.2.0 in pre release for a few days until im happy with dongle FW 3.2.5 at which point ill push both. @pilot51

I also fixed the other issue with poor formatting on my behalf

[pilot51]

Updated. FW 3.2.286 -> 3.2.5 said "OTA update failed" even though it succeeded.

I like what I see. Great work!

However, the battery entities aren't working right. I have 3 batteries, but it only shows "Battery 1" and appears to be using data from Battery_ID_03 (last one in the array). I suspect it's because batIndex on all 3 of them is 0.

Other than that, no obvious issues to report with new features or regressions. I haven't gone over the other issues I mentioned in #101 yet.

[zakery292]

Yeh it will do stupid thing it might miss the last payload but as long as version number bumped its up to date.

Yes i did notice the battery issue (i dont have access to those in the UK so it was a wild punt) ill get that fixed before release but im glad the other bits have not effected anything there might be some weirdness with temperature entities or duplication, these were duplicated in const.py so they have been removed....

Ill work on the batteries thing and then i think its finally ready for a new release! Dongle should be stable on 3.2.5 heap memory has been stable on all users so far with limited fragmentation. Apologies its taken so long i wanted the firmware to be right on the dongle plus the binary size got a little out of hand so had to make some reductions