decimal pointless that is
Iâve just tested the new build vs. my node red implementation. I updated the Android app and removed my float-converting node. It doesnât seem to be working.
To me, it still looks like the button widget is sending a float.
On:
{ "payload": "1.0", "arrayOfValues": [ "1.0" ], "_msgid": "7a6b2e2b.8594d" }
and Off:
{ "payload": "0.0", "arrayOfValues": [ "0.0" ], "_msgid": "5458966d.aba768" }
I may be missing something, of courseâŚ
Is your button on virtual or digital/analog pin? Such behavior is possible on virtual pins.
Itâs a virtual pin. But if the build was meant to fix this issue, itâs not fixing it.
I donât know why the button needs to send a float instead of a fixed 1/0 binary result (inheritance?), but in that case Iâd suggest making available the same option the slider has to turn floats off.
@pathway today 2.19.2 appâs version would be available, it should fix your issue with floats on a virtual pin of the button
@Gunner @tulo 2.19.2 release would allow you to add max to 5 decimals after the point to min/max fields of the slider, âset propertyâ should use maximumFractionDigits
field and values from 0 to 5.
âFractionâ isnât really the right way to describe the number of decimal places. âResolutionâ is the correct term.
Pete.
In the UI the text is already changed, but the name for âset propertyâ command would not be changed.
@Pete, resolution reminds me of the amount of significant digits. I thing fraction or decimal places fits better here.
Resoloution can be used to refer to both the number of significant digits and the number of decimal places.
Pete.
resolution is an abhorrent term.
Why ?
Because itâs not used by the mainstream.
Breaking news: Blynk announces latest app update - now with slider resolution of 0.03125 (1/32) or the new (1/2 ^ 5) resolution slider.
Great news!!
Just donât know why⌠yet
I confirm that the latest build fixes the problem with the button and the virtual pins. I just tested it and it works just like it used to.
Thank you!
I didnât get if this is running or notâŚbecause it doesnât seem to work.
What exactly doesnât work? @Dmitriy is the server ready for âset property maximumFractionDigitsâ calls?
Yeah I was wondering if the server can already handle thatâŚ
Server is ready but not deployed yet :).
Seems this property update should work now, as the server has been updated and also we have a new app release.