MQTT triggers two switches instead of just one

So I am almost done setting up my own house. Touch sensors, and voice control via Alexa all work perfect. However I have an issue with two relays when controlling them via Hassio web interface. Stairs and Backyard seem to be attached. If I turn either of them on, both turn on, if I turn either of them off, both turn off.

I went ahead and uninstalled mqtt, re started, and re installed mqtt again, and did a new mqtt integration. I am gong the auto discovery route. After the new integration I have the same issue with the same two relays.

At the moment I mostly use Alexa voice commands and the physical sensors to control the lights, so not a huge deal right now, but eventually I do want to get into automation so that is when I will have issues with it.

Any ideas of what it can be? How I can trouble shoot?

I did try qith mqtt explorer, but can’t say I understand much of what is going on. However I think I know where the problem is, just not sure how to fix it.

There is a tree, on top my mqtt server IP,
then lists out “sonoff” “MannyBedroom”, “Mirswtich”, “MiriamSwitch”.

When I turn either stairs or backyard with Alexa or with web interface, I see the “sonoff” area blink. MannyBedroom is correct, but for example “mirswitch” was friendly name i used in previous build, have changed friendly name to “bathroom”, but still lists old name. Again when I trigger bathroom lights I can see “mirswitch” blink. Finally “MiriamSwitch” is tha name of a swtich no longer in the network.

How can I change those names? I did a quick look throughout tasmota options, and didn’t find anything. Figured deleting mqtt and re installing it would clear old info.

Solved! I have to update my mqtt settings on Tasmota!

There’s a 1 minute difference between your two posts. I think it took me longer to read your first post than it took you to solve the problem. :wink:

Glad to hear you fixed it.

Well I was at it for about an hour. After I posted I took another look at tasmota settings, and found “mirswitch” on the MQTT topic, so I knew that is where my problem was :slight_smile:

That’s why am in the habit of recommending to people that they should use both MQTT Explorer and MQTTFx (or equivalent). They are both very good programs for what they are intended but they both have their strengths and weaknesses. And readability is a definite weakness in MQTT Explorer.