Prevent flow tigger on node-red startup

General
1

I have a zigbee doorbell, its default action is "single" click. And it is the default state. So when I restart node-red it triggers the doorbell. This is annoying as I don't want this to happen when im updating the server etc.

Any suggestions on disabling the doorbell update on the start? Maybe using a startup timer?

2

I don't understand exactly what is happening. Do you mean that on startup something is sending a message? Add debug nodes to work out exactly what is happening. If it is a contrib node that is sending a message then tell us what it is.
Also please export and post just the nodes in your flow that are causing the problem. That should not need to be more than about five nodes.

3

Ok ive found my issue was that mosquitto persistence setting was enabled. Whenever a mqtt connection was established, all the signals would be sent to the client. In my case triggering the doorbell through node-red.

Is there an option to ignore all the initial messages when node-red connects to an mqtt server?

4

Yes, change the topic to non-persistent. That does not sound like a topic that should be set as persistent.

5

The topic I am using on the mqtt node is "zigbee2mqtt/Front Door/action".

Ive just notice that if i change to mqtt v5 i have the options for retained message handling. This should solve the issue :slight_smile:

6

In the web UI for zigbee2mqtt you can configure whether you want it retained or not.

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.