Node status unclear about node-red-contrib-tasmota HOT 9 CLOSED

I'll see if I can fix this and make a pull request

from node-red-contrib-tasmota.

I checked the node-red git hub, the broker connection is setting the status, this also means the setting the status on broker connections is redundant and can be removed, tested.

from node-red-contrib-tasmota.

Indeed this is a know issue: the tasmota-node and the broker-node are fighting for the status-label.
The first "connected" status is setted by the broker-node and I did not found a solution to fix this,
did you found one?

from node-red-contrib-tasmota.

Still working on it, it's hard because it's not instant so you need an asyn function to wait for the connection, bit the .register function doesn't return anything so no way to know it's complete.

from node-red-contrib-tasmota.

This should be fixed now, can you please give it a try?

from node-red-contrib-tasmota.

from node-red-contrib-tasmota.

Any news on this?

from node-red-contrib-tasmota.

from node-red-contrib-tasmota.

Ok, no problem, I tested this quite well, it works well IMO.
I'm closing the issue, feel free to reopen if needed

from node-red-contrib-tasmota.