Do you use an editor such as the Cloud9 IDE add-on? Do a search of all of your HA files for ‘source_entity_id’ and see where it is.
Using Atom the key ‘source_entity_id’ it found it only in the home-assistant.log
Not specifically related to this topic but you really need to remove all of your personal info and keys from your posted config. Specifically the stuff under the Google assistant section.
you have right… I removed all personal info in the configuration file
It show me 57 errors
I have many device sonoff flashed with Tasmota which use the MQTT protocol
Could it be someting about changes in MQTT platform?
Could it be someting about changes in MQTT platform?
Yeah, back in 0.87 they changed unsupported keys to start throwing warning instead of being silently ignored, but nothing more recent than that which im aware of for MQTT_Switch. Have you checked that for all of your MQTT switches, every key you are using is currently supported and shown in the docs?
This is my switches.yaml file:
########################### SWITCHES #############################
- platform: mqtt
name: "Sonoff Corr"
state_topic: "stat/sonoffcorr/POWER"
command_topic: "cmnd/sonoffcorr/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Ing"
state_topic: "stat/sonoffing/POWER"
command_topic: "cmnd/sonoffing/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Cuc"
state_topic: "stat/sonoffcuc/POWER"
command_topic: "cmnd/sonoffcuc/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Sogg"
state_topic: "stat/sonoffsogg/POWER"
command_topic: "cmnd/sonoffsogg/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Bagn1"
state_topic: "stat/sonoffbagn1/POWER"
command_topic: "cmnd/sonoffbagn1/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Studio"
state_topic: "stat/sonoffstu/POWER"
command_topic: "cmnd/sonoffstu/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Cam1"
state_topic: "stat/sonoffcam1/POWER"
command_topic: "cmnd/sonoffcam1/power"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Cam2"
state_topic: "stat/sonoffcam2bagn2/POWER1"
command_topic: "cmnd/sonoffcam2bagn2/power1"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Sonoff Bagn2"
state_topic: "stat/sonoffcam2bagn2/POWER2"
command_topic: "cmnd/sonoffcam2bagn2/power2"
qos: 1
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Blitzwolf1"
state_topic: "stat/blitzwolf1/POWER"
command_topic: "cmnd/blitzwolf1/POWER"
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Blitzwolf2"
state_topic: "stat/blitzwolf2/POWER"
command_topic: "cmnd/blitzwolf2/POWER"
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Blitzwolf3"
state_topic: "stat/blitzwolf3/POWER"
command_topic: "cmnd/blitzwolf3/POWER"
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: mqtt
name: "Blitzwolf4"
state_topic: "stat/blitzwolf4/POWER"
command_topic: "cmnd/blitzwolf4/POWER"
payload_on: "ON"
payload_off: "OFF"
retain: true
- platform: command_line
switches:
#Switch for Foscam Motion Detection
foscam_motion:
command_on: 'curl -k "http://192.168.1.14:88/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig1&isEnable=1&usr=vpomax&pwd=Qashqai16cdi"'
command_off: 'curl -k "http://192.168.1.14:88/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig1&isEnable=0&usr=vpomax&pwd=Qashqai16cdi"'
# command_state: 'curl -k --silent "http://192.168.1.14:88/cgi-bin/CGIProxy.fcgi?cmd=getMotionDetectConfig1&usr=vpomax&pwd=Qashqai16cdi" | grep -oP "(?<=isEnable>).*?(?=</isEnable>)"'
value_template: '{{ value == "1" }}'
- platform: broadlink
host: 192.168.1.148
mac: '1C:87:2C:46:20:BF'
timeout: 15
switches:
tv_lg:
friendly_name: "LG Tv Power"
command_on: 'JgBYAAABIJISExETETcSEhISEhQQFBETETcROBESEjcRNhM1EjcTNRMTERISNxEUERMSExE2EjYSNhM2EhIROBE3ETcREhITEgAFGwABH0oSAAwzAAEfShEADQU='
command_off: 'JgBYAAABIJISExETETcSEhISEhQQFBETETcROBESEjcRNhM1EjcTNRMTERISNxEUERMSExE2EjYSNhM2EhIROBE3ETcREhITEgAFGwABH0oSAAwzAAEfShEADQU='
tv_lg_hdmi1:
friendly_name: "HDMI1"
command_on: 'JgBIAAABIZMRExITEjYSExMRERURExEUEDkRNxEUEjYSNhM3ETcSNxITETgSNhI2ExMQExE4ETYSNxIUERMSExE4ETcRFBETEQANBQ=='
tv_lg_hdmi2:
friendly_name: "HDMI2"
command_on: 'JgBQAAABJJMSEhISETgSEhITEBMSEhMSETcSNxMREjcSNxI3EjcSOBETERITNhM2EhITERM2EzcRNxI3ExISEhI3EjcRExETEgAFLQABJEoRAA0FAAAAAAAAAAA='
tv_lg_hdmi3:
friendly_name: "HDMI3"
command_on: 'JgBIAAABIZMSFBISETgRExEUERQQFBETEjcTNhMSETgRNxE3EjcROBM2ERMSFBE4ERMSNxM2EjUSFBE2ETgRExM2ExITEhATEwANBQ=='
tv_lg_av1_av2:
friendly_name: "LG Tv AV12"
command_on: 'JgBIAAABIpQPFBITETgSEw8UEhQSEhEVDzgSOBAUETgQOQ84EjgRNxITETgSExA5EDgREhI3EhMROBMSEDkQFBETEjYTEhE4EQANBQ=='
command_off: 'JgBIAAABH5YPFBETETgUERAUEBURFBATETgROBEUETcSNxE4ETcSOBISEBUQFREUEjUSFBA5ETcRNxE4ETkQOBAUEjcRFRAUEQANBQ=='
- platform: mqtt
name: "Zigbee2mqtt Main join"
state_topic: "zigbee2mqtt/bridge/config/permit_join"
command_topic: "zigbee2mqtt/bridge/config/permit_join"
payload_on: "true"
payload_off: "false"Those switches look fine. 
How about lights?
Are you using any auto discovered MQTT entities?
this is my code in configuration.yaml
mqtt:
broker: 192.168.1.2
port: 1883
username: vpomax
password: !secret mqtt_password
discovery: true
discovery_prefix: homeassistant
birth_message:
topic: 'hass/status'
payload: 'online'
will_message:
topic: 'hass/status'
payload: 'offline'After updated to v. 0.93.1 I have a better log error file:
Please remove [source_entity_id], [source_attribute].
Configuration source: MQTT (topic: 'homeassistant/sensor/motion_sensor_158d00016dafd8_battery/config').
Offending data: {"device_class": "<redacted>", "name": "Presenza Corridoio Battery", "state_topic": "homeassistant/sensor/motion_sensor_158d00016dafd8_battery/state", "unit_of_measurement": "<redacted>", "unique_id": "<redacted>", "source_entity_id": "binary_sensor.motion_sensor_158d00016dafd8", "source_attribute": "battery_level", "platform": "mqtt"}
2019-05-23 01:35:41 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
Please remove [source_entity_id], [source_attribute].
Configuration source: MQTT (topic: 'homeassistant/sensor/illumination_158d0002234653_battery/config').
Offending data: {"device_class": "<redacted>", "name": "Illumination_158d0002234653 Battery", "state_topic": "homeassistant/sensor/illumination_158d0002234653_battery/state", "unit_of_measurement": "<redacted>", "unique_id": "<redacted>", "source_entity_id": "sensor.illumination_158d0002234653", "source_attribute": "battery_level", "platform": "mqtt"}
2019-05-23 01:35:41 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
Please remove [source_entity_id], [source_attribute].
Configuration source: MQTT (topic: 'homeassistant/sensor/motion_sensor_158d0002234653_battery/config').
Offending data: {"device_class": "<redacted>", "name": "Sensore presenza Studio Battery", "state_topic": "homeassistant/sensor/motion_sensor_158d0002234653_battery/state", "unit_of_measurement": "<redacted>", "unique_id": "<redacted>", "source_entity_id": "binary_sensor.motion_sensor_158d0002234653", "source_attribute": "battery_level", "platform": "mqtt"}
2019-05-23 01:35:41 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
These error are all related to battery level of xiaomi sensors
what is this device and how is it configured (automatically via integration? Manually via yaml? Automatically via MQTT?)
That look like auto-generated Zigbee2MQTT entity name, loaded from discovery.
It also looks like an auto-generated Xiaomi device using their hub.
Actually reading your log again, that doesn’t make sense. The xiaomi integration doesn’t use mqtt, but the log clearly shows an mqtt device. Confused now. @Silicon_Avatar’s suggestion seems more likely.
some xiaomi devices are under zigbee2mqtt, could be them?
but some sensor like this window/door sensor isn’t under zigbee
Please remove [source_entity_id], [source_attribute].
Configuration source: MQTT (topic: 'homeassistant/sensor/door_window_sensor_158d0001b14427_battery/config').
Offending data: {"device_class": "<redacted>", "name": "Porta Ingresso Battery", "state_topic": "homeassistant/sensor/door_window_sensor_158d0001b14427_battery/state", "unit_of_measurement": "<redacted>", "unique_id": "<redacted>", "source_entity_id": "binary_sensor.door_window_sensor_158d0001b14427", "source_attribute": "battery_level", "platform": "mqtt"}
2019-05-23 01:35:42 WARNING (MainThread) [homeassistant.helpers.config_validation] Your configuration contains extra keys that the platform does not support.
it is very strange…
I have only 4 devices under zigbee2mqtt:
‘zigbee2mqtt/0x00158d0001593043’
‘zigbee2mqtt/0x00158d00028e3516’
‘zigbee2mqtt/0x00158d0002234653’
‘zigbee2mqtt/0x00158d0002236904’
Problem solved…
@nickrout you have right
With MQTT discover: true
zigbee2mqtt discovered all xiaomi sensor devices actives… not only the xiaomi devices configured but all devices… it will cause this problem. This is a bug.
in configuration.yaml iI changed discover to false and it do not show me errors.