Tasmota switch showing in UI but not in Integrations

Hello,
I have a tuya boiler switch flashed with tasmota (version 6.6.0), with mosquitto MQTT installed on my Rpi as an add-on to hass.io.
the switch shows up on my UI and works perfectly including automations. I can see the commands from HA to the switch via MQTT Explorer and it works well. however it does not show up on Integrations->MQTT or devices or entities. other MQTT devices (such as Aqara temp sensor connected via zigbee2mqtt) do appear there. I’ve searched the community but couldn’t find a solution to this problem.
How can I fix this?
these are my configurations:

SetOption19 is set to On on the switch.
I have acl.conf with “acl_file /share/mosquitto/accesscontrollist” and accesscontrollist with:

user X
topic readwrite #
user homeassistant
topic readwrite #

configuration.yaml:

mqtt:
  broker: 192.168.1.139
  username: X # home assistant user for MQTT
  password: X
  discovery: true
  discovery_prefix: homeassistant

switch:
  - platform: mqtt
    name: "Boiler"
    state_topic: "stat/sonoff/POWER"
    command_topic: "cmnd/sonoff/POWER"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    optimistic: false
    retain: false

MQTT config:

{
  "logins": [
    {
      "username": "X", # home assistant user for MQTT
      "password": "X"
    }
  ],
  "anonymous": false,
  "customize": {
    "active": true,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "require_certificate": false
}

Thanks!

Just guessing. You did setoption19 1, so it should be autodiscovered and showing up in integrations. But then you add it also manually under switch. Maybe the manual defined one is interfering with the autodiscovered one ?

nope, doesnt work. removing the switch configuration from configuration.yaml changes the boiler in the UI to “unavailable” but didn’t add anything to integrations / devices.

Solved - I didn’t know the basic tasmota FW didn’t support discovery. I’ve upgraded from sonoff-basic.bin to sonoff.bin via OTA and it works.