Or, for a data-driven interface direct from Node-RED, uibuilder can create mobile-friendly UI's without all of the overheads of Dashboard & similar. Not sure how good Grafana is on mobile, my limited experiments didn't work out that well though it was quite some time ago, I've not tried recently.
That is true, however, there are button extensions. So depends what you want to do.
One day, I'll get time in between being creative on uibuilder to write some uibuilder-based mobile friendly pages that can be installed as apps. Probably about the same time that I work out how to use webworkers with the uibuilder front-end library. At the moment though, I'm writing a new version of the front-end library that is pure es module. Not as easy as I thought it would be once I got to the detail of what is really allowed to happen in browsers of different ages.
Anyway, to answer the original question, I'd likely build my own web interface using uibuilder and allow it to be taken as a mobile app. Since uibuilder is very robust at re-engaging the websocket interface, especially with the new es module version of the library (not yet quite published). So having the mobile disconnect from the network regularly shouldn't be too much of an issue. Though thinking about it, since the reconnect logic extends its retry time, perhaps a pop-over button to manually reconnect would be sensible - :sigh: another thing to add to the backlog!
I seem to remember that at least one of them simply creates a web request. This would work nicely with Node-RED where you have multiple ways of creating endpoints. I've not really tried them much though since I've never really needed them. I do have some links set up though on some of my Grafana dashboards that reach back to Node-RED.
That is true, and have used Grafana previously, but got out of it. The reason I like Blynk linked to Node-Red is the data from Node-Red is 'pushed' to Blynk, so I dont need to open up firewall ports or use a VPN.
Ideally I'd like to continue the 'push' approach, but doesn't seem to be many around that will do that. I am, not against Blynk, and had paid for some previous functionality. Only issue I have with Blynk 2.0 is the per month charge... mind you I guess they need to get money from somewhere.
Really not many options for that. I'm guessing that Blynk needs to run an intermediate service somewhere in order to achieve the link which is why they are looking for more money.
Your best bet is going to be setting up a reverse proxy to provide edge security and then using web services from a device on your network (probably the device running Node-RED). I bit of a pain to set up properly but once done it should be stable.
Hello, I totally agree with your opinion. I'm looking for an alternative method to the old version of Blynk. A platform where I can push information through node-red. But I still haven't found a method.
...not myself, yet.
But as already said earlier, above, others over in the blynk forum did move to either kodular or M.I.T App Inventor. Also, you can find lots of examples and code libraries to integrate the App via mqtt pub/sub.
I really like the concept of a public MQTT broker. Like I said, the reason I chose Blynk is because it avoided me fooling around with firewall rules, and opening my network to the world.
What is interesting is the Kodular approach i.e. app development. But who has the time to develop an app. And Grafana is ok, but again I dont have time to develop a mobile oriented dashboard, or learn about interfacing Node-Red and Grafana.