Delete menu item and device?

Hi there,

can someone please answer a couple of very basic questions please?

In the attached screenshot, how do I remove the MQTT entry from the menu on the left? I had configured the link in the panel_iframe config section, but have since deleted it, as I no longer need it, but the menu entry persists (yes I’ve done multiple restarts.

Similarly, I no longer have “Tree” section on the switch section of the config, but I can’t delete the entry on the card.

Finally, is this the “Lovelace” interface? I’ve found some articles that say Lovelace isn’t “yet” the default interface, but this is the only one I ever see, even after using the “Lovelace Migration” Add-In.

Shift+F5 on your browser just incase its cached. Failing that maybe post your panel_iframe config?

Maybe a little more info on what the device is. How it was setup in the first place etc?

I would guess not but look at your address bar if its lovelace your address will be http://hassio:8123/**lovelace**

Thanks for the speedy reply.

Shift+F5 makes no difference, the MQTT item persists.

“Tree” was a Sonoff S20 smartplug, running Tasmota firmware. It has since been re-flashed and reused. All the other devices on that card are similar devices ( 4 x S20 and 1 x POW R2) and all work properly.

My config is as follows:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: !secret latitude
  longitude: !secret longitude
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 230
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: of_tz_database_time_zones
  time_zone: UTC
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
# introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: 

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Sensors
sensor:
  # Weather prediction
  - platform: yr

  - platform: mqtt
    name: POW Current
    state_topic: "stat/sonoff-p1/STATUS10"
    value_template: "{{ value_json.StatusSNS.ENERGY.Current }}"
    unit_of_measurement: 'amps'
  - platform: mqtt
    name: POW Power
    state_topic: "stat/sonoff-p1/STATUS10"
    value_template: "{{ value_json.StatusSNS.ENERGY.Power }}"
    unit_of_measurement: 'watts'
  - platform: mqtt
    name: POW Voltage
    state_topic: "stat/sonoff-p1/STATUS10"
    value_template: "{{ value_json.StatusSNS.ENERGY.Voltage }}"
    unit_of_measurement: 'volts'  
 

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

mqtt:
  broker: !secret MQTTBroker
  username: !secret MQTTUsername
  password: !secret MQTTpwd
  #client_id: home-assistant
  discovery: true
  discovery_prefix: homeassistant
  
# Switches

switch:
  - platform: mqtt
    name: "sonoff-s1"
    state_topic: "stat/sonoff-s1/POWER1"
    command_topic: "cmnd/sonoff-s1/POWER1"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: true

  - platform: mqtt
    name: "sonoff-s2"
    state_topic: "stat/sonoff-s2/POWER1"
    command_topic: "cmnd/sonoff-s2/POWER1"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
  
  - platform: mqtt
    name: "sonoff-s3"
    state_topic: "stat/sonoff-s3/POWER1"
    command_topic: "cmnd/sonoff-s3/POWER1"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
    
  - platform: mqtt
    name: "sonoff-s4"
    state_topic: "stat/sonoff-s4/POWER1"
    command_topic: "cmnd/sonoff-s4/POWER1"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: true    
  
  - platform: mqtt
    name: "sonoff-p1"
    state_topic: "stat/sonoff-p1/POWER1"
    command_topic: "cmnd/sonoff-p1/POWER1"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
  
  - platform: mqtt
    name: "sonoff-p2"
    state_topic: "stat/sonoff-p2/POWER1"
    command_topic: "cmnd/sonoff-p2/POWER1"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: true


panel_iframe:
    configurator:
      title: 'Configurator'
      icon: mdi:wrench
      url: http://192.168.150.116:3218

did you enable discovery (setOption19 1) the tree S20 if so that is why you are still seeing it in HA. The quickest way to remove it would have been to turn it off again first.
I guess now you will need to remove the entry from MQTT manually.
It will be “homeassistant\switch\something” This explains how the discovery works and should help you find the exact topic you need to remove.

Having said that if you are manually defining your tasmota devices why not just turn off MQTT discovery in your HA config? This should also remove the MQTT menu option.

Your switches may be configured wrong… Ive took the first one from your config
Im not really sure why you are using POWER1 over just POWER in the topics

platform: mqtt
name: "sonoff-s1"
state_topic: "stat/sonoff-s1/POWER1"
command_topic: "cmnd/sonoff-s1/POWER1"
qos: 1
payload_on: "ON"
payload_off: "OFF"
# Should be false not true
retain: false
# add availability e.g. sonoff is not plugged in
availability_topic: "tele/sonoff-s1/LWT"
payload_available: "Online"
payload_not_available: "Offline"

Then so HA gets the correct state on reboot set “PowerRetain 1” on the sonoff devices

Do you use packages? Is the MQTT iFrame perhaps in a package somewhere?

1 Like

Sorry for the delayed reply - been a busy week.

AFAIK, I don’t have any “packages” running, I do have some HASS Add-ons though (do they count as “packages”?) - Configurator, Mosquitto, Pi-Hole and Tasmo Admin.

I’m still getting precisely nowhere with fixing the GUI.

I’ve stripped all of the “switch” details out of my configuration file and physically unplugged all of the Sonoff switches, except one (Sonoff-p1) but they are all still showing up on the front page.

As is the MQTT link in the menu, even though it’s no longer in the config file, and has been replaced, in theory by a link to the PiHole admin tool, which itself is not showing up.

It’s almost as if the home screen is ignoring the information in the config file. Except that some things do work and update - the sensor data from Sonoff-p1 is displaying and updating as it should.

I’m completely out of ideas.

Current config looks like this:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: !secret latitude
  longitude: !secret longitude
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 230
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: UTC
  # Customization file
  customize: !include customize.yaml

# Show links to resources in log and frontend
# introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Sensors
sensor:
  # Weather prediction
  - platform: yr

  - platform: mqtt
    name: POW Current
    state_topic: "stat/sonoff-p1/STATUS10"
    value_template: "{{ value_json.StatusSNS.ENERGY.Current }}"
    unit_of_measurement: 'amps'
  - platform: mqtt
    name: POW Power
    state_topic: "stat/sonoff-p1/STATUS10"
    value_template: "{{ value_json.StatusSNS.ENERGY.Power }}"
    unit_of_measurement: 'watts'
  - platform: mqtt
    name: POW Voltage
    state_topic: "stat/sonoff-p1/STATUS10"
    value_template: "{{ value_json.StatusSNS.ENERGY.Voltage }}"
    unit_of_measurement: 'volts'
    
  - platform: pi_hole
    host: localhost:4865
    monitored_conditions:
      - ads_blocked_today
      - dns_queries_today
      - unique_clients
 

# Text to speech
tts:
  - platform: google

# Cloud
cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

mqtt:
  broker: !secret MQTTBroker
  username: !secret MQTTUsername
  password: !secret MQTTpwd
  #client_id: home-assistant
  #discovery: true
  discovery_prefix: homeassistant
  

panel_iframe:
   - configurator:
      title: 'Configurator'
      icon: mdi:wrench
      url: http://192.168.150.116:3218
 
   - pihole:
      title: 'Pi-hole'
      icon: mdi:block-helper
      url: http://192.168.150.116:4865

Resulting in homescreen that looks like this:

your iframe items are too far to the right… indent should only be 2 spaces…
also clear cache and delete data… in chrome, press F12 and then right click on the refresh button and do a hard reload and clear cache

Hi David,

Thanks for spotting the excess indent. I’ve fixed that now. But still the zombie MQTT link and switch configs are showing up.

The screenshot is from a cleanly installed VM, the first time I connected it to the HA interface.

I’m wondering if I should just trash the whole thing and start again. I can’t help thinking the HASS incarnation, with it’s reliance on Docker is over complicating things. Maybe I should just go with a native deployment. Although the Hass “Add-On” store is a nice feature.