Get the name and/or alias of a datastream in JSON via HTTP request

Need Help With My Project
1

Hello
After some research in the doc and in the forum remain without answer, I would like to know if there is a way to get the name and/or the alias of a datastream in JSON by a http command like :

https://blynk.cloud/external/api/data/get?token=myToken&v33.....

Because in one of my projects, I want to display this data and the value of the virtual pin on a MagicMirror in HTML, CSS (the data retrieval and html display code is in javascript)

Thanks

2

I don’t believe that it’s possible.

In the Legacy API there was a somewhat clunky way to obtain that using the /project API query, but that’s not supported in Blynk IoT.

@Dmitriy there was a topic recently about whether it was programmatically possible to determine whether the result from a datastream should be an integer, float or string, which is in some ways of related to this question.

Also, in Node-Red when you add a Blynk input or output node you choose the virtual pin number, but of course there is no way to retrieve the corresponding datastream description or properties and there is no method to query this from the server.

Have you considered a REST API and/or C++ API method to query this data?

Pete.

3

it’s a pity, in the old version of blynk it was possible to recover all the data related to a project, all the widgets, etc… like :

  • the type : button, led, etc…
  • the value : 0, 1 …
  • the widget id
  • the name
  • etc…

their treatment in JSON became very easy afterwards

there are more than 40 virtual pins and this possibility would have allowed me to write in my loop of recovery of the answer (stored in a javascript table) only one IF and for each pin of which I wanted to display to have directly its name or its alias and not to make an IF by vpin.

so if for x reason the function of the virtual pin changes or i have to add one, i wouldn’t have to modify all my IF but just change the name or the alias of the vpin in the datastream

I can’t use the node-red for this

thank you for your answer

4

I wasn’t suggesting that you do, simply pointing-out that the feature you requested wold be useful in that environment too, if it were to be implemented.

Pete.

5

yes, absolutely

developers, it’s up to you :rofl: