History widget, different scale on native and shared app

Issues and Errors
1

Hello,

I created the app, and shared access. Now my friend can use it, but she has got a different scale of the history widget than I do.

My app (ios):

Admin_app.png750Ă—1334 85.3 KB

User app (android):

User_app.jpg1080Ă—1920 110 KB

I suppose, this might be connected to some old data the the widget remembers, but i thought that the admin - user apps have rather a master - slave relationship, and so if I see everything ok, than the users should see the same?

All of the variables monitored by the history graph have a low-pass/high- pass filter on their Labeled Display Widgets (blynk side, not hardware) set to 0-100.

Also on her version of the history graph widget you can see the fourth variable which is not connected to anything and in my app - correctly nothing in the legend is there shown.

BTW - I don’t use the “mapping” function in display’s because you’ve written somwhere in the forum that it is same as if i used map(0,1023,0,100); but how do you know that the input max is 1023 if I don’t specify it? Maybe my max value is 4096? How does it work? Where this function get the original min-max values from?

2

Please open your History Widget settings and check if it has Y-AXIS MIN/MAX values set. You should have latest iOS app version to do that.

3

We need more info regarding app version you have.

4

I have the latest version, and my friend just installed Android version fresh three/four days ago.

I had the Y-AXIS MIN/MAX set to auto, since I wanted the widget to automatically scale in a given time period. Now I changed it to custom: 0 … 100

I asked my friend to send me a screenshot after checking for newest blynk version, and rebooting blynk. We will see did it make the change.
But it’s not a real sollution, since I would like to have AUTO mode on, so that the data is clearly visible and takes all the available space.

5

Ok,

this worked as expected, now the user app look’s like that:

User_app2.jpg1080Ă—1920 111 KB

But this is still not a perfect solution - i liked the autoscaling in this widget:)

6

@ethelder
Change back to the auto mode and it should work.

@BlynkAndroidDev This is same as we had with buttons - old widgets stored on server have autoYCoords flag zero. Please add checkBackwardCompatibility to check min/max equals.
Also, good point to not show a legend if pin is not assigned.

1 Like
7

@eugene
Thanks very much. Now the app works, like it should. Tell me please (and the community) for the future use, was that a bug in my app only, and can happen in future projects of mine or someone elses, or is your fix permanent?

BTW - you’ve written “old widgets stored on server”, and this led me to tell you one #lifehack i do frequently with blynk to debug all the issues. I create one project for prototyping of my app, do all the changes and when I have the 1.0 version ready, I delete the project on blynk, and create a new fresh one from scratch with all the correct Virtual pins and make no changes from that point on. If I need to make some minor changes I always abbandon used Virtual Pins and never reuse them - I use fresh ones. With each BIG update of my firmware on the hardware, I also delete the app and create a fresh one.

8

It is.

:slight_smile:. No need for this. Yes, sometimes we do bugs, however for nearest future we are done with big updates, so all updates should go smoothly.

9

@Dmitriy
:slight_smile: I meant BIG updates of MY firmware - which consists of changes to the data I’m sending being reorganized, and so - the virtual pins reorganization:)

1 Like