MQTT BROKER and entity

[123 (Taras)]

@Espen_Overbye

Thanx alot guys.

You’re welcome!

Please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic is resolved. This helps other users find answers to similar questions. For more information, refer to guideline 21 in the FAQ.

---

@Espen_Overbye

I have alot of these sensors I need to separate them

If you have one topic, mqtt/out, that contains information from multiple devices then it’s best to use Strategy #2 in the following post:

Sonoff RF Bridge. Strategies for receiving data

Here are two strategies for receiving payloads published by a Sonoff RF Bridge (flashed with Tasmota firmware). Strategy 1: value_template In this strategy, all sensors are subscribed to the same topic published by the RF Bridge. The topic's structure depends on how you defined it when you configured *your* RF Bridge. This example will use `tele/RF_Bridge/RESULT`. Change that to whatever you have set for your Bridge. Because all sensors are subscribed to the same topic, a sensor will receive pa…

In a nutshell, you create an automation that subscribes to mqtt/out (using an MQTT Trigger) and it examines the received payload. If the payload is from device A (represented by some combination of ID and SWITCH values), the automation publishes it to a different MQTT topic dedicated for the use of device A only. It’s a proven technique that simplifies the process of configuring MQTT entities that share a common MQTT topic.

I can help you implement this method but I would need to know the ID and SWITCH values for each device that publishes information to mqtt/out.