Node-red version 1.1 is now available. There are a couple of interesting features that popped out when I took a look.
Inject node can now inject and property into the msg object and not just the payload and topic.
The function node now can contain setup code that runs when the flow is deployed. This is a new way of initialisation that I covered in Node-Red Flow Initialisation
The debug node can be activated and deactivated in lots on nodes in one go.
Node grouping is a new feature that lets you combine nodes into a group.
You can find more details here as well as upgrade instructions.
The node-red team have also published a road map so you can see the planned development cycle here.
This was pointed out to me by a reader and is an HTTP to MQTT gateway.
It uses an API similar to Paho, The following is taken from the web page here.
The library exposes an Eclipse Paho-like API. Any HTML page can easily become an MQTT client, able to publish and subscribe to/from MQTT topics, irrespective of which MQTT broker you are using. This way, web pages can exchange messages with IoT devices and existing MQTT applications as well as interact with other web pages in real time.
Similarly, any Node.js application will be able to access any MQTT broker and produce/consume messages.
I mentioned in my newsletter at the beginning of the year that I believe MQTT-SN will grow in importance this year, and I actually expect it to become more popular than MQTT in the years to come, but we shall have to wait and see.
In the meantime there is an upcoming webinar that may be of interest that will discuss the importance of MQTT-SN in the future and the current time plan for standardisation You can register here.
As you may be aware there are plans to standardise MQTT-SN in much the same way as MQTT.
Ian Craggs who is chairman of the committee responsible has an update on his website which is worth a read as it talks about MQTT-SN as well as MQTT v5.
Interested article in Electronic design about configuring IOT devices with security credentials.
The first part gives a good overview of the problem on using certificates in the hardware and then goes on to cover a software based approach.
Although I still find the solution too complex it is certainly going to be an important topic in the future. Read it here
Following several questions regarding IP address assignment On the raspberry PI I did some research and testing which I turned into a tutorial you can read here.
A while ago a published a tutorial on using CloudMQTT and in that tutorial I used their free hosting plan.
Recently CloudMQTT have stopped this plan and I was asked for an alternative.
A that time I had just helped someone with a connection problem to Beebotte and so I needed to sign up using their free plan which you may want to look at as an alternative.
Some data currently being published as web pages and sent over http is far more suited for being sent over MQTT.
So what happens to existing applications that publish over http.
Well IMO nothing as it is relatively easy to take this existing data and republish it over MQTT without having to modify the existing application.
Doing it this way would greatly reduce the load on the application server and reduce costs.
A while ago I developed both a python script and a node-red flow to do this if you haven’t seen the tutorial then here it is.
A- It can be revoked. There are a number of ways that a client(browser) can check if a certificate is revoked see here
I have received several questions regarding raspberry pi and Mosquitto . They are mainly concerned about the pi being able to handle the number of connections.
I ran my broker connection tester on my pi and got 1016 before being denied.
I was curios about this limit as it was mosquitto but the tcp daemon.
It seems that users are only allowed 1024 connections by default and so the user running mosquitto was limited you can change this see here