davemds / node-red-contrib-tasmota Goto Github PK

The Tasmota MQTT spec says that sending a blank payload gives the current status of the device. This works using the standard Node Red MQTT nodes but when I try it with this node it gives "Invalid payload received on input" error. I find being able to query a device's current status useful in some logic so miss this facility. Would it be possible to add this feature?

I've got the Sonoff ZB Bridge setup and using Tasmota. I can add devices to this from Tasmota and controlled them manually from MQTT, but it's a pain. I'd really like to use your Tasmota script to make this simpler via NodeRED.
The problem is that I cannot get your nodes to work properly with this setup. Here's a couple of examples of info being received from the bridge in msg.payload:

{"ZbReceived":{"0x11FE":{"Device":"0x11FE","Name":"DoorContact","Power":0,"Endpoint":1,"LinkQuality":179}}}
{"ZbReceived":{"0x0E3A":{"Device":"0x0E3A","Name":"Cabin_Button_2","MultiInValue":1,"Endpoint":1,"LinkQuality":129}}}

The first is a contact switch, and the second is a button. As you can see, the key differentiator is the device ID object at the very start. How would I code this in the Output Channels payload so I can distinguish and detect them correctly?

Similarly, how would I do the reverse to control a switch?

Thanks

Please add ability of set/forward msg.topic on the output of nodes. It make easier the process the outputs of sensor nodes (e.g. create charts to display and comapre data from more sensors etc.).

Node-RED Dashboard buttons, switches etc can be enabled or disabled. For this you need to output "msg.enabled" to true or false when LWT changes. The dasboard button will inactive when the device is powered off or lost wifi. Can you add this functionality please?

I am trying to use your Tasmota Sensor node with a sensor that has an hyphen in its name.
Mqqt In:

{"topic":"tele/tasmota_45FABD/SENSOR","payload":"{\"Time\":\"2020-10-21T17:39:26\",\"SHT3X-0x44\":{\"Temperature\":17.1,\"Humidity\":71.6,\"DewPoint\":11.9},\"TempUnit\":\"C\"}","qos":0,"retain":false,"_topic":"tele/tasmota_45FABD/SENSOR","_msgid":"2799aa79.f26426"}

Unfortunately, using
SHT3X-0x44.Temperature as an output-channel definition cause this error:

{"code":"S0201","position":10,"token":"x44","stack":"Error\n at handleError (/usr/lib/node_modules/node-red/node_modules/jsonata/jsonata.js:5925:30)\n at parser (/usr/lib/node_modules/node-red/node_modules/jsonata/jsonata.js:6886:13)\n at jsonata (/usr/lib/node_modules/node-red/node_modules/jsonata/jsonata.js:5420:19)\n at Object.prepareJSONataExpression (/usr/lib/node_modules/node-red/node_modules/@node-red/util/lib/util.js:571:16)\n at TasmotaSensorNode.sendToOutputs (/home/nodered/.node-red/node_modules/node-red-contrib-tasmota/nodes/sensor.js:46:31)\n at TasmotaSensorNode.onSensorStatus (/home/nodered/.node-red/node_modules/node-red-contrib-tasmota/nodes/sensor.js:67:14)\n at Object.callback (/home/nodered/.node-red/node_modules/node-red-contrib-tasmota/nodes/sensor.js:20:14)\n at MqttClient.<anonymous> (/home/nodered/.node-red/node_modules/node-red-contrib-tasmota/nodes/tasmota_mqtt_client.js:91:33)\n at MqttClient.emit (events.js:327:22)\n at MqttClient._handlePublish (/home/nodered/.node-red/node_modules/mqtt/l...","message":"Syntax error: \"x44\""}
The error disappears only when I remove the hyphen from the output-channel definition.

Sensor node with one payload output works as before,
but when splitting the output data by some Jasonata expressions, it still works,
but produces the warning (with debug dump of stack) : "Jasonata without callback no longer valid at Node-red 4.0".
The exact warning text is:
"Deprecated API warning: Calls to RED.util.evaluateJSONataExpression must include a callback. This will not be optional in Node-RED 4.0. Please identify the node from the following stack and check for an update on npm. If none is available, please notify the node author."
So the sensor node should be updated in time.

Hello

I have been trying to configure the sensor node to connect to an online Broker and whilst the Node Red MQTT nodes configure and run there is no way I or the Broker support can figure how to connect.

I presume the connection fails on the topic as the same security is used as with the Node Red MQTT node there is also a connection from my mobile on the Tasmota platform in operation.

I have tried with three separate Node red terminals on differing machines 2 on differing RPI and one on windows to no avail.

Error: Connection refused: Server unavailable
at MqttClient._handleConnack (C:\Users\Ian.node-red\node_modules\mqtt\lib\client.js:920:15)
at MqttClient._handlePacket (C:\Users\Ian.node-red\node_modules\mqtt\lib\client.js:350:12)
at work (C:\Users\Ian.node-red\node_modules\mqtt\lib\client.js:292:12)
at Writable.writable._write (C:\Users\Ian.node-red\node_modules\mqtt\lib\client.js:302:5)
at doWrite (C:\Users\Ian.node-red\node_modules\readable-stream\lib_stream_writable.js:428:64)
at writeOrBuffer (C:\Users\Ian.node-red\node_modules\readable-stream\lib_stream_writable.js:417:5)
at Writable.write (C:\Users\Ian.node-red\node_modules\readable-stream\lib_stream_writable.js:334:11)
at Socket.ondata (node:internal/streams/readable:750:22)
at Socket.emit (node:events:369:20)
at addChunk (node:internal/streams/readable:313:12) {
code: 3

Any help, advice or assistance greatly appreciated.

Regards

Ian

If multiple switch node outputs are enabled, a topic containing a switch id is still included in the message. This appears to be incompatible with the light node which expects no topic for mode 1 (simple) and a predefined set of topics for the other modes. I get an Invalid message error. I had to insert a function to remove the topic from the message to use mode 1.

Steve

Hi, I noticed the Tasmota nodes send a message with their current status when you press deploy in node red.
However this triggers (at least in my case) logic in other nodes to start doing things. Resulting in flashing lights in the house whenever I press deploy.
Can we have an option to "silence" this behaviour?

I'm not sure if this is fixable, but when multiple tasmota nodes reference the same device name (disclaimer: only tried with lights) only one of them shows the correct state. The others (somewhat random order, assume it's based on a race condition) show "Offline" or occasionally "Wrong Config" (only until a message is sent, then it switches to "offline").

To illustrate, these are in two separate flows:

It would be preferred that all references were able to show the status correctly.

When setting i.e. brightness (25) and color (blue) at the same time, it looks as if the brightness will be sent but directly overwritten by the color command, which sets brightness to 100%.

Node-red screenshot (test setup):

Tasmota console output (setting brightness and color together):

14:00:33 MQT: tasmota/lightcat/stat/RESULT = {"POWER":"ON","Dimmer":25,"Color":"000040","HSBColor":"240,100,25","Channel":[0,0,25]}
14:00:33 MQT: tasmota/lightcat/stat/RESULT = {"POWER":"ON","Dimmer":100,"Color":"0000FF","HSBColor":"240,100,100","Channel":[0,0,100]}

Tasmota console output (setting color, then brightness):

14:02:17 MQT: tasmota/lightcat/stat/RESULT = {"POWER":"ON","Dimmer":100,"Color":"0000FF","HSBColor":"240,100,100","Channel":[0,0,100]}
14:02:20 MQT: tasmota/lightcat/stat/RESULT = {"POWER":"ON","Dimmer":25,"Color":"000040","HSBColor":"240,100,25","Channel":[0,0,25]}

In the source (/nodes/light.js, line 126ff.) the single attributes are handled sequentially, with brightness before color.

I would think that handling brightness after color would fix the issue. As I am not that into JS I did not test modifications to the JS code.

NodeRED version: v3.1.3
Tasmota nodes version: 0.9.13

When you place a node (tested with Switch) some settings like QoS and Retain will default to 1 (integer) and false (boolean) as defined in the switch.html line 182 and in the base_tasmota.js line 15

When you modify the QoS to zero, internally it will save the QoS setting (in the NodeRED flows.json file) as "0", as a string and not an integer anymore, this prevents the node from connecting to the MQTT broker and remains offline indefinitely. (maybe there is an internal crash when parsing the setting and the offline is a false message as I received many timeout messages)

When you change the Retain to true or false, it will save the setting as "true" or "false" both as string and not boolean anymore.
This does not prevents the node from connecting to the MQTT broker but every message is sent as retained even with the "false" setting as "false" string is interpreted as true boolean

Not tested with other nodes or settings

Thank you for node-red-contrib-tasmota. I have a single relay module flashed with Tasmota. The single relay is successfully being controlled by your switch node and is reporting status fine via this node.

I have a reed switch sensor connected to GPIO14 and it is configured as Switch2 in Tasmota. SetOption14 has been set to detach switches from relays. When I add your sensor node for the reed switch it only reports the switch's status from periodic telemetry:

tele/tasmota_3DD57B/SENSOR = {"Time":"2020-12-09T14:12:09","Switch2":"OFF"}

However, when the sensor closes and sends an immediate MQTT status update:

stat/tasmota_3DD57B/RESULT = {"Switch2":{"Action":"ON"}})

I can't get the sensor node to report this update in real-time. If I use your button node instead of a sensor node, then the node does report the immediate status update (albeit showing it as 'button2' in debug messages) but then doesn't report periodic telemetry.

Is there something I am missing? I have left the nodes' advanced MQTT settings blank (i.e., default). Ive checked incoming MQTT payloads via a network mqtt in node and all looks correct. Thanks.

How can I get LWT Status from your module without using other nodes

it is also possible to use variable values in the node settings field !!!

Have Sonoff Tasmota device. When I unplugged in from power outlet, there will be state in Nodered "Neaktivni" (Not active) with warn red square. But the node don't send this information. Is it possible to add this feature?

Hello .. since 3 day's I got the "close timed out" error when performing full deploy or modifying broker node
the MQTT Server seems to run in a timeout .. there is a similar problem
here:
node-red/node-red#2934 (comment)
I've been told that i report it here.
cmd: 9 Jun 11:54:48 - [error] [tasmota-mqtt-broker:MyTas-MQTT] Error stopping node: Close timed out
Mark_Muc

Hi,

is it possible to set qos and, more important to me, retain? My sonoff / tasmota wifi plugs are not always powered so I have to send out commands periodically. Having the retain function of mqtt, that should take care of that.

Thanks!

Hello ... first of all, thank you for the nice and good working tasmota nodes.
I do now have a relay board supporting 16 channels .. Tasmota
New versions of Tasmota support more then 8 relays now ..
Is it possible that the switch node supports more than 8 channels?
The device will show correctly and working but output channels work only up to 8 channels ..
I can split myself using a function (1 channel or all merged) node .. but will be much easiest if the switch node
will support it by default!!
THX & Regards
Mark_Muc

Thanks very much for the node. It is great.

Alas I am not getting it all on how to use it.

"Out of the box" the node shows an "online" signal - which is good.
But when I set it for 3 switches and the like, the node condition changes to "offline", and I don't get why.

I am also having a lot of trouble getting the output/s working.

I have 3 debug nodes on the 3 outputs, but turning the outputs on/off nothing is seen in the debug nodes. (They are set to display all)

After upgrade to Node-Red 2.0.5 all tasmota nodes lost their MQTT-Broker relationship.
If I open the config of the node there is no dropdown list to choose broker from.

Hi @DaveMDS,
Thank you for your great work on Tasmota node.
I have a question.
I'm able to successfully execute single commands such as "POWER ON" using "command" topic but when I send multiple commands such as "Backlog POWER ON; Dimmer 20" the message that reaches Tasmota device is changed to "POWER OFF".
Can you confirm if Backlog command is supported in this node or not?

Many thanks in advance

Node-RED version: v1.2.9 , docker version
Node.js version: v12.20.1
Linux 5.10.17-v7l+ arm LE

After update plugin node-red-contrib-tasmota to newest version 0.9.8 have problem with rebooting/cycling Nodered with this log:

2021-04-06T08:40:34.808416873Z 6 Apr 10:40:34 - [info] [mqtt-broker:c31e24e2.791568] Connected to broker: mqtt://10.0.0.1:1883
2021-04-06T08:40:34.890535879Z 6 Apr 10:40:34 - [red] Uncaught Exception:
2021-04-06T08:40:34.891029779Z 6 Apr 10:40:34 - TypeError: ts.startsWith is not a function
2021-04-06T08:40:34.891092463Z     at matchTopic (/usr/src/node-red/node_modules/@node-red/nodes/core/network/10-mqtt.js:38:20)
2021-04-06T08:40:34.891120259Z     at MqttClient.handler (/usr/src/node-red/node_modules/@node-red/nodes/core/network/10-mqtt.js:319:25)
2021-04-06T08:40:34.891145259Z     at MqttClient.emit (events.js:326:22)
2021-04-06T08:40:34.891170018Z     at MqttClient._handlePublish (/usr/src/node-red/node_modules/mqtt/lib/client.js:1277:12)
2021-04-06T08:40:34.891193981Z     at MqttClient._handlePacket (/usr/src/node-red/node_modules/mqtt/lib/client.js:410:12)
2021-04-06T08:40:34.891217462Z     at work (/usr/src/node-red/node_modules/mqtt/lib/client.js:321:12)
2021-04-06T08:40:34.891377256Z     at processTicksAndRejections (internal/process/task_queues.js:79:11)
2021-04-06T08:40:34.936478783Z npm ERR! code ELIFECYCLE
2021-04-06T08:40:34.937217068Z npm ERR! errno 1
2021-04-06T08:40:34.950677039Z npm ERR! [email protected] start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
2021-04-06T08:40:34.950860462Z npm ERR! Exit status 1
2021-04-06T08:40:34.951248956Z npm ERR! 
2021-04-06T08:40:34.952061074Z npm ERR! Failed at the [email protected] start script.
2021-04-06T08:40:34.952132925Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-04-06T08:40:34.969871981Z 
2021-04-06T08:40:34.970310086Z npm ERR! A complete log of this run can be found in:
2021-04-06T08:40:34.970806004Z npm ERR!     /data/.npm/_logs/2021-04-06T08_40_34_953Z-debug.log
2021-04-06T08:40:36.174071677Z 
2021-04-06T08:40:36.174150250Z > [email protected] start /usr/src/node-red
2021-04-06T08:40:36.174178879Z > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
2021-04-06T08:40:36.174205712Z 

When node is connected to broker but the device is offline (and never been online) the node status shows "connected" it is not clear that the device is offline as it is reporting the broker connection status.

If the device subsequently comes online and then goes offline the LWT is received and the status "Offline" and show correctly.

An additional status for when the broker is online but the device is offline would be beneficial.
e.g.

Red - Broker Unavailable
Yellow - Broker Connected, Device Offline
Green - Online

Hi there,
Today I had upgraded to the latest version of node red (1.3.3 from maybe 1.3.1 or so). I had 38 instances of tasmota working which included sensors, buttons, etc.
However, when updating to the latest tasmota node version, all hell broke lose on my mqtt server (mosquito). It took me about 2 hours to pinpoint the problem to tasmota. Only once I pointed the tasmota mqtt settings to a non existing mqtt server, the rest of my home automation went back to normal. Every couple of seconds I had "burst" of over 200 mqtt msg/ sec, completely parallising my entire home automation system.
Experimenting with a single tasmota node and the correct mqtt settings did not yield any working results any longer either while all other nodes using mqtt work fine.
Not sure what exactly happend but all of my 38 node-red-contrib-tasmota nodes are down (while e.g. node-red-contrib-sonoff-tasmota-enhanced or mqtt receive work perfectly fine).
As my tasmota node configurations are partially complex, deleting and replacing them all would be a very bad option for me.

Here a screenshot showing the debug output when I "freshly" create a new node-red-contrib-tasmota node and new MQTT settings, while node-red-contrib-sonoff-tasmota-enhanced works perfectly fine.

Not sure what it is but something seems "incompatible" with MQTT now!

Is there anything I can do to provide additional information for further troubleshooting or any other (manual) tricks to restore normal operation? So far I was really happy with this tasmota node and it would be a shame if I had to replace it all.

THANKS
Robert

I cannot use the three tasmota nodes anymore. Even after removing and reinstalling I'm getting these errors:

16 May 14:20:00 - [info] Installiertes Modul: node-red-contrib-tasmota
16 May 14:20:00 - [info] Hinzugefügte Node-Typen:
16 May 14:20:00 - [info] - node-red-contrib-tasmota:Tasmota Switch : SyntaxError: Invalid or unexpected token (line:3)
16 May 14:20:00 - [info] - node-red-contrib-tasmota:Tasmota Sensor : SyntaxError: Invalid or unexpected token (line:3)
16 May 14:20:00 - [info] - node-red-contrib-tasmota:Tasmota Light : SyntaxError: Invalid or unexpected token (line:3)

Thanks for this node red contribution!
I'm especially looking forward to using the raw commands.
I'm trying to make a sonoff switch blink the number of hours on the hour to create a time signal

Reading the readme.md, however, I failed to understand how the new raw command works.
Maybe the description can be made a bit more clear?

I read in the readme.md that the structure has 3 possible formats:
1. string payload: 'CMD <param>'
2. string list payload: ['CMD <param>', 'CMD <param>', ...]
3. object payload: {'CMD': 'param', 'CMD': 'param', ...}

But how is param formated? I need a command and a variable, like BlinkCount 12 or BlinkTime 3
Or is 'CMD' the command as used by Tasmota? i.e. BlinkCount: 12
Perhaps you can add a few examples to clarify the text?

Also I found a small typo on line 75: sand-> send

Regards,

Bert

I have a sensor node, with just device id set.

I expect to see tele/X/sensor/

I see all topics instead ( at least on the first payload channel )

My Tasmota nodes are sending messages on the output when I control them via the input.

The last line in the help text says they won't do this, but they do.

It's making my flows loop all over the place because they feed their output back to my source.

Was this changed at some point by accident?

node-red-contrib-tasmota 0.9.12
node red v2.2.2

The SensorNode thows the following Error on each MQTT-Message:

Error:
at Object.evaluateJSONataExpression (/usr/lib/node_modules/node-red/node_modules/@node-red/util/lib/util.js:775:18)
at TasmotaSensorNode.sendToOutputs (/root/.node-red/node_modules/node-red-contrib-tasmota/nodes/sensor.js:50:35)
at TasmotaSensorNode.onSensorTelemetry (/root/.node-red/node_modules/node-red-contrib-tasmota/nodes/sensor.js:60:14)
at /root/.node-red/node_modules/node-red-contrib-tasmota/nodes/sensor.js:16:14
at MqttClient. (/root/.node-red/node_modules/node-red-contrib-tasmota/nodes/mqtt_broker.js:113:21)
at MqttClient.emit (events.js:400:28)
at MqttClient._handlePublish (/root/.node-red/node_modules/mqtt/lib/client.js:1277:12)
at MqttClient._handlePacket (/root/.node-red/node_modules/mqtt/lib/client.js:410:12)
at work (/root/.node-red/node_modules/mqtt/lib/client.js:321:12)
at Writable.writable._write (/root/.node-red/node_modules/mqtt/lib/client.js:335:5)
at doWrite (/root/.node-red/node_modules/mqtt/node_mod...

Hello all,

I have Tasmota on my D1 mini to receive MQTT messages from a switch to my NodeRed. In NodeRed I just see the message from /SENSOR but not from /RESULT and /POWER.

18:29:30.415 MQT: tele/tasmota_1/SENSOR = {"Time":"2022-09-26T18:29:30","Switch1":"ON"}
18:31:39.371 MQT: stat/tasmota_1/RESULT = {"POWER":"ON"}
18:31:39.374 MQT: stat/tasmota_1/POWER = ON
18:31:45.179 MQT: stat/tasmota_1/RESULT = {"POWER":"OFF"}
18:31:45.182 MQT: stat/tasmota_1/POWER = OFF

What can I change to receive also the other messages? Can anyone help me?

Am I not sure how the setup needs to be? do I point MQTT on the tasmota to the node-red server and if so what ports. I am new to Node-red and I have an MQTT broker taking between an esp8266/ dht11 and node-red server working. I wanted to try your software but can't find the details to get it working. Any help would be useful

The Tasmota firmware/documentation allow us to create full topics such as:

• FullTopic %prefix%/%topic%/ default
• FullTopic tasmota/%topic%/%prefix%/
• FullTopic tasmota/bedroom/%topic%/%prefix%/
• FullTopic penthouse/bedroom1/bathroom2/%topic%/%prefix%/
• FullTopic %prefix%/home/cellar/%topic%/

Unfortunately this node has only 2 predefined templates %prefix%/%topic%/ %topic%/%prefix%/.

May you please allow us to define our custom FullTopic in advanced configuration?

Thanks :)

Hi Guys,

I'm using the node-red-contrib-tasmota, works great, but I can't configure a single output in a button node with a topic to distinguish the channel, ever i put the topic i get "offline" status....

Someone can help me explain how can i configure a single output with a distinguished channel by topic ?

In documentation say:
"The node can be configured to send all press actions to a single output (in this case the topic is used to distinguish channels)"

Error: read ECONNRESET

And the weirder thing is that the node is disabled.

Sorry if this is too vague, but that's all I am seeing in the debug window at the side.

This is the best I can offer in the way of a screen shot.

It's my flow. When first time I enable this flow - it's work fine. But after any edit and deploy - any triggered entity start calling tasmota node multiple times. It's happening only with this setup (hass entity > tasmota node). Any another node that I connected for testing purposes still calling only once. That's why I think it's on tasmota plugin side.

It's not happening when triggered by Inject node, for example.
It's not happening when hass node triggering debug node directly.
It's resetting to normal work only when I disable flow/deploy/enable flow again/deploy

Examples:

Reset > Edited name of one tasmota node. Result: One trigger > two executions:

Edited name of same tasmota node. Result: It's multiplied one more time

Interestring moment: edited one node but multiplied for two connected nodes

It's hapenning every time so it's easy to reproduce. Will be nice if anyone will try to reproduce it.

I'm using latest versions of HASS, Node-Red integration and tasmota plugin.

Hi,

I am sending to my tasmota device this command, in order to get the "mem" variables:

cmnd/<topic>/mem

The message is correctly sent to the device, but I have no output from the switch node. How can I get the mem variables in my flow?

Hi, is possible to add code examples to your screenshots?

Have Sonoff Dual R3 with two relays, but don't know, what must be in inject to control Relay 1 and Relay 2, as on this your screenshot:

Thank you for reply.

Hey,

i use the "Light" node in the json output mode, everything seems to work fine. But when i sent a msg.payload with true or false the brightness value are increasing.

Example:
On with 1%
Turn off, value is now 4%
Turn on again, value is now 12%
Turn off again, value is now 32%
etc..

After some turn off and on's the value can go far beyond 100%:

Also the ct values jumps to a wrong value around ~400-500 when the correct ct value are ~5300:

Issue not occur when using the node with splitted outputs.

I recently updated all of my device (40+) to tasmota 12.5 after being on 9.2/9.5 for quite some time. I am still able to control all of my lights and other devices via the nodes, but now they no longer report anything to do with the state/status, they also do not forward ANY flow information to debug nodes.

This means that any of my flows that rely on knowing the current status of a light are no longer able to function.

You can reproduce this by installing tasmota 12.5 onto a device and then configuring the node for that device. Attach a debug node to the output of the node. Send the node any commands. Your device will follow the commands, but the node will not indicate anything has happened, nor will it forward the change, or any incoming flow data out to to the debug node.

Would really appreciate a fix for this as a lot of my home automations are related to elderly care are rely on the status of devices from those nodes to function properly.

If I am able to figure out any further information as to the cause I will report back. This was working exactly as is on 9.2, and 9.5, the only thing that changed in my setup was updating to tasmota 12.5.

Tasmota supports sending a "blink" message to the power cmnd channel of a device. I use this to indicate to my daughter that her light will be turning off for bedtime in 5 minutes.

"blink" should be a valid input for on/state/power and should send the message "blink" to the cmnd channel.

Currently, this can be done as shown in the README by issuing a msg.topic "command" with the msg.payload set to "Power blink". While an acceptable work-around, I do feel the blink option should be directly supported, similar to "toggle."