Two Tasmota sockets accidentally joined in Home Assistant. Help!

Configuration
1

I bought two sockets today and flashed Tasmota onto them. They’re actually a socket and a night light combined. When I added them into Home Assistant everything seemed to go okay but they’ve somehow become joined. When I turn on one then the other turns on too. Same with the lights.

Does anyone know how I can resolve this, please?

name: NETVIP-Socket1
command_topic: tasmota/cmnd/POWER1
state_topic: tasmota/tele/STATE
value_template: '{{value_json.POWER1}}'
payload_off: 'OFF'
payload_on: 'ON'
availability_topic: tasmota/tele/LWT
payload_available: Online
payload_not_available: Offline
unique_id: 633436_RL_1
device:
  identifiers:
    - '633436'
  connections:
    - - mac
      - 'DC:4F:22:63:34:36'
platform: mqtt

name: NETVIP-Socket2
command_topic: tasmota/cmnd/POWER1
state_topic: tasmota/tele/STATE
value_template: '{{value_json.POWER1}}'
payload_off: 'OFF'
payload_on: 'ON'
availability_topic: tasmota/tele/LWT
payload_available: Online
payload_not_available: Offline
unique_id: 3404C4_RL_1
device:
  identifiers:
    - 3404C4
  connections:
    - - mac
      - 'CC:50:E3:34:04:C4'
platform: mqtt

two_sockets
two_sockets1758×1782 580 KB

2

This is just a guess, but your configuration for socket2 is using command topic & value_json parameters for POWER1.

1 Like
3

Ah yes. They shared the same topic name and I think that was the source of the problem. Thank you.

Edit; actually, despite being fixed the payload still has the same command_topic and value_template so that wasn’t the problem. But regardless, deleting the devices, rebooting, resetting discovery seems to have worked.