Mysensors related nodes, for decoding / encoding mysensors serial protocol and MQTT topic, and wrapping arbitrary messages into mysensors compatible messages
A node-RED mysensors protocol decoder / encoder / wrapper package. Contains a node to decode / encode mysensors serial protocol to / from node-red messages, and a node for adding mysensors specific data like sensor type, nodeid etc. which can then be sent to mysensors network
In an upcomming release the node mysdecenc will be removed, it is only left here for legacy purpose, and to not break current flows.
Within your local installation of Node-RED run:
npm install node-red-contrib-mysensors
Once installed, you will have two new nodes available : mysdecenc, and mysencap.
This decodes the mysensors serial protocol packages or a MQTT topic from a mysensors MQTT gateway, and enriches the Node-RED msg object with the following extra data:
msg.payload // Payload data from sensor network msg.nodeId // node of the origin msg.childSensorId msg.messageType msg.ack msg.subType
see mysensors API v2.x for more info on the different parts
The following nodes will be able to use these properties to interact with the messages from the mysensors network
This encodes a message into either mysensors serial, or a mysensors mqtt topic. If using MQTT, then set topicRoot on the message, before sending it into this node, in order to set your own root topic
This will add the message properties mention under mysdecenc to the message object of an existing Node-RED message. By sending the output through mysdecenc, you can create a message that can be sent to the sensor network.
This will decode the mysensors serial protocol payload, and enrich it with descriptions of sensor types etc. Meant as a debugging tool. Data will be sent out of the node, and can be used in a debug node, or dumped to disk, for file logging