I want to report non-optimal behavior of super chart:
Using public server, esp12, blynk lib example sketch.
App:
One button digital output D1
Superchart with datastream boolean value of D1
superchart live doesn’t update, if there is no action with D1 - it is not “live”
Workaround: adding value display widget for the same pin
I haven’t checked it, but logically thinking (?) it shouldn’t need other widget with the same pin, but only for VirtualPins, and ONLY if the device is pushing the data with virtualWrite In other words it will not work for physical pins, as they are read by the app (data is pulled) and SuperChart cannot pull data
To clarify this: If device uses VPins AND is pushing data to server with virtualWrite it will work.
If device uses only physical pins (as in @marissv project) IT WILL NOT WORK without other widget, which will “pull” data from device…
And if the device uses VPins but NOT pushing any data, and there is no widget to pull it, it will not work either
Correct me if my thinking is wrong…
I’ve noticed, that the vertical level widget do not have ANY label visible, despite being set in properties. I do not remember if it was there and disappeared at some point or it wasn’t there for some reason (Only tried this widget once, after introduction).
I know the space is very limited in vertical mode, but it would be great if at least 4-5 characters were visible below (or above) the bar.
Vertical Level and Slider have no enough space to label, that’s why it is hidden from their first introduce. But yep, that’s strange that we have a setting for that label in the settings, and have this setting for LED widget with same width.
@Pavlo maybe we could introduce a title somewhere in this vertical widgets? And also make LED title optional?
The new styled buttons were disappearing from the android app so I had to update my Raspberry Pi local Blynk server to the latest version (also updated the client) and that seemed to fix it. The only headache I got from upgrading was that my client would not log in to my server until I changed the port to 8080. Use to be 9443 but I’m not sure why it changed.
Did I do something wrong?
Of course, you use the IP of your Local Server… not mine
And the key point… Blynk is in constant development, so always read the Announcement Topics and try to keep ALL aspects of Blynk (App, Library & Local Server, if used) up to date on a regular basis… they all tie together.
Thank you for clearing that up Gunner. I’m glad it was nothing I did. In the future, to avoid headaches I’ll try to keep up with the changes specially for new updates.