I tried both wss and ws none worked. I have self generated certificates, does this work?
I will try your suggestions with the singular version of websockets.
The name is generated by the system if I don’t give a name to the connection.
I will report back with the testing of your suggestions.
Thank you
I guess so, but I don’t use SSL on my system at the moment.
Pete.
I confirm it works!!!
With “ws” and without the plural!
Thank you!
Excellent!
Are you an ‘old hand’ at Node-Red, or is this a new adventure?
There aren’t that many of us on here, although that’s not for want of trying to drum-up support myself!
Pete.
Thanks a lot Pete, for your help. The documentation on the node-red plugins always showed the plural “version” and with WSS, so… No clue there for a newbie like me…
I’m starting my Node Red adventure. I only have about 2 months of work into it.
Although it’s a slow “work in progress”, let’s say working effectively on it about 1 month.
I have several “fronts” open in this “war”, I had a lot of SonOff devices and depended 100% on their app/cloud.
I don want that. I bought an rPi4, and am “slowly” transitioning the Sonoff’s to Tasmota, and I have a couple of Wemos D1 Mini made by myself too.
Control is all about Node Red. But although Node Red dashboard in a web enviroment is Ok, in a cellphone/tablet it’s not. So, Blynk to the rescue!! 
I will come here often and try to help on what I know.
Thank you very much for this helping start bump !! 
I’ve dabbled with Tasmota a few times, but I have to say that I’m not a fan of it.
I prefer to write my own code for my Sonoffs etc and it give much more flexibility.
I have a mixture of the WiFi smart socket devices. I live in the UK and there are fewer options available for us, as out sockets are different to the EU style sockets. I also have a holiday home in Spain, which obviously uses EU sockets, so that give me much more flexibility about choice. I also use some Shelly1 devices, as well as home-built Wemos D1 Mini/Pro based devices.
I also have a door entry system, solar charge monitor, weather station, blinds (persianas) controller, aircon controller etc that all interface with Node-Red and that gives me the option to control them via Blynk, Alexa, Nextion touch screen, 433MHz fobs or raw MQTT commands.
Everything is controlled via MQTT messaging and I have two Node-Red servers, one in the UK and the other in Spain. I’ve been using Blynk cloud for my apps for a few years, but I’m probably going to migrate everything to local servers running on the same RPIs that act as Node-Red and MQTT servers.
I’m not a fan of the Node-Red dashboard, although I haven’t re-visited it for some time and it might be worth a look again. I looked at Blynk for exactly the same reasons as you, and I love it, especially when used in the way that we use it.
Not sure if you’ve seen this topic that I wrote a while ago…
It needs updating a little, but the basics are still valid.
Pete.
Wow! That is a lot of experience right there!
I will look in that post of yours for sure!! Thanks!
P.S.: I’m from Portugal, Lisbon.
OMG! Pete, that post is … a gold mine!!!
And I’m just at the beginning!!!
Thank you!
@Zalaban i know you’ve withdrawn the question, but I use Mosquitto as my MQTT broker, it runs on the same Pi as Node-Red and Blynk local server.
Pete.
Hi, just to say that I also have the same setup, Mosquitto, Node Red and Blynk local server. All run in containers except the Blynk local server.
I looked at dockerising my setup, including trying-out IOTStack, but for me it caused more problems than it solved.
Pete.
I have IOTstack. Everything works fine, only the Blynk Local Server, wich exists in IOTstack, did not work, so I opted to make it stand alone.
I may return to that case and try to dockerising the Blynk also, but for now, “it just works”
For me, it was the opposite.
I had a test Blynk server running in IOTstack, but couldn’t figure-out how to successfully enable RAW data storage.
Also, the original developer of IOTstack seems to have disappeared and the project has been forked. The forked version seems incompatible with the original version in some key areas, and the documentation seemed quite poor at the time I did these tests.
TBH, it’s quite a simple task to set-up a Pi from scratch with non-dockerised installs of Node-Red, Mosquitto, Blynk server and Webmin (which I use as a management console for the Pi, and can’t be dockerised). Compared to the amount of time is spent trying to get IOTstack working, the Docker benefits are non-existent for me.
Pete.
Yeah… Local Blynk on IOTstack is quite “green”. So I’ve chosen to “KISS” and make it outside the container, it’s, has you said, quite easy to do.
On the other hand, IOSstack for NodeRed, Mosquitto, TasmoAdmin to manage my Tasmota devides, MariaDB to … be a database where to store everything and Portainer to controle/manage the containers. They all work flawlessly and where a breeze to setup and use.
This with the easy to manage backups? A great setup I think.
Later I will add the Wireguard container and access all this in security from where I want
Have you looked at ZeroTier?
It’s a fantastic tool and makes remote management so simple.
I have a Pi at my holiday home in Spain with ZeroTier client installed. This gives it a unique “global” IP address in my ZeroTier system and I can then simply open a browser on any machine that has the ZeroTier client installed and access my Node-Red control panel. Speed is fantastic, just as if the Pi was part of my home network.
I also have a mini PC in Spain that I can turn on remotely (using a Sonoff type switch) and I was previously using this over TeamViewer as a way to do OTA updates to devices, or to log on to devices that aren’t “ZeroTier aware” such as my router. I now use Windows Remote Desktop over ZeroTier and that’s about 5 times faster than TeamViewer.
It’s also great for MQTT Explorer. I have a connection to the ZeroTier IP for my Spanish Pi, and can view the MQTT traffic there as if I was on the same physical network.
If you install the client on a phone or tablet then you can also do the same stuff, and can even put the global IP of the Blynk server in your custom server settings of the Blynk app. The only slight drawback to this is that some devices will turn the ZeroTier client off after a period of inactivity, so you have to fire-up the app to turn it back on again before launching the Blynk app.
But, for people running a local server on a Double NAT internet connection it’s one of the few ways to access the local server remotely.
Pete.
What a coincidence! I’ve just come by Zerotier yesterday by reading another post here on the forum. Made a quick look to the service, only
Now that you make this exposition of the practicality of it, I will surely look into it.
For what I saw, it is seems simpler than Wireguard.
Thanks!
@PeteKnight I also use Node-Red, Mosquitto as my MQTT broker running on RasPI but I do not have Blynk running on local server. What are the advantages of Blynk local server?
Thanks
Paul
For me, the biggest advantage is that I do not need to rely on the “cloud”.
Even if I loose Internet I can control everything in my house.
Also, I don’t like to give my privacy to clouds.
And for last, you get more control over admin stuff, I think, because I never used the “cloud” version to compare.
I still use Blynk cloud for my home automation, but I’ve been running a local yet server for some time and have cloned all of my cloud projects across to it - I just need to do the last part and point my app and Node-Red connections across to the local server.
I’ve been holding off because I’ve been beta testing the new version of Blynk, so putting quite a bit of time into that, and waiting to see what the new version offered.
I’ve decided that I will make the switch over to my local server soon, as I don’t think the new version is something that I’ll be migrating to in the short to medium term and I’d like to put the server in a place where I have control.
Pete.
@PeteKnight @hmgp Thanks I still am a little confused. How do you connect to your devices with your phone without the cloud. I still want to be able to control devices when away from home with my phone.
Thanks
Paul