Blynk mobile buttons

[FCS]

Hi Blynk team

Can we please have an option to be able to send nothing on a button release within mobile apps? (Button, styled button)

Currently sends a 0 on release

This would be fantastic. It will cut down on
Data usage (cellular)
Data processing
Program interruption
Interruptions to bit banging

[PeteKnight]

I don’t understand how this would work in practice.

If the app doesn’t update the widget status on the server then the server will still believe that the current widget value is On, and the web dashboard will also show the widget as being On.

Pete.

[hms11]

Would you not be better off using a switch instead of a button in this case?

I don’t understand how your button would ever turn “off” if it never sends the 0.

With a switch it will just stay “on” or 1 for as long as the switch is on, which in your use-case is apparently forever?

[FCS]

@hms11

I am using styled buttons. They look much nicer than standard buttons and have a lot more functionality IMO much better for dynamic keypads and most importantly can be sized down much more that regular buttons

@PeteKnight
You are right if you are using a switch in “switch mode”
I am using “Push” mode. There is currently no web dash board that supports styled or push buttons yet.

If people were concerned about always being on you do have the “invalidate after x” in data stream setups.

On the message side you only receive a 1 once per update and with code this is not an issue.

I basically use it as a messaging service from app to device.

@PeteKnight
You are a Gem . You do fantastic work on this forum!!

[VIGHNESHNS2008]

@FCS

There is currently no web dash board that supports styled or push buttons yet

Yes I agree but you can do as @Blynk_Coeur MentionS

@Blynk_Coeur

Waiting for a real push button, you can turn the switch into a push button by coding like this :

BLYNK_WRITE(V1) {//reset maxmin button
  int sw = param.asInt();
  // do reset maxmin
  if (sw == 1) {
    Blynk.virtualWrite(V1, 0);
  } else {
    Blynk.virtualWrite(V1, 1);
  }
}

’
ThankS

[PeteKnight]

I still can’t see the sense in this to be honest, but I guess it depends on what the Blynk developers think.

Pete.

[Dmitriy]

I think you need to use the menu widget or text input in that case. Button always has 2 states on/off. It should work in that way. Also, according to our data - the main issue for the “low data” devices is sensor data (data send from the device), not actions over the device.