Mqtt config in Yaml

Configuration
1

I need help with my mqtt setup on Home Assistant running on Raspberry Pi 3. I am missing something really simple I apologise for the long and probably incorrectly formatted post. Any tips would be appreciated.:grimacing:

I have a series of NodeMCU’s with DHT22 sensors that, at the moment, point to a RPi running NodeRed. This gives a nice result, but for a more integrated dashboard I’d like to point the outputs to Home Assistant. I have also set up a stand alone NodeMCU that points directly at Home Assistant

I have loaded the mqtt broker(v1.0) to Home Assistant and the log shows the following:

starting version 3.2.2
1514676267: mosquitto version 1.4.12 (build date 2017-06-01 13:03:48+0000) starting
1514676267: Config loaded from /etc/mosquitto.conf.
1514676267: Opening ipv4 listen socket on port 1883.
1514676267: Opening ipv6 listen socket on port 1883.
1514676267: Warning: Mosquitto should not be run as root/administrator.
1514676278: New connection from 10.1.1.189 on port 1883.
1514676278: New client connected from 10.1.1.189 as mqtt_7f095960.80f6a8 (c1, k60).
1514676294: New connection from 10.1.1.77 on port 1883.
1514676294: New client connected from 10.1.1.77 as Bedroom_3 (c1, k120).

The connection from 10.1.1.189 is from the NodeRed setup, 10.1.1.77 is direct from the NodeMCU (ESP8266)

So I know that Home Assistant is seeing the two feeds, but my overview shows an invalid config message
“The following components and platforms could not be set up:

  • mqtt
  • sensor.mqtt
    Please check your config.”

My Yaml file looks like this.

homeassistant:
`# Name of the location where Home Assistant is running
name: MYSYSTEM

Location required to calculate the time the sun rises and sets

latitude: -37.0000000
longitude: 144.0000000

Impacts weather/sunrise data (altitude above sea level in meters)

elevation: 25

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: Australia/Melbourne

Customization file

customize: !include customize.yaml

Show links to resources in log and frontend

introduction:

Enables the frontend

frontend:

Enables configuration UI

config:

http:

Secrets are defined in the file secrets.yaml

api_password: my secret

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

base_url: mydns

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:

Weather prediction

sensor:

  • platform: yr

Text to speech

tts:

  • platform: google

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

weather:

  • platform: bom
    sensor:

  • platform: bom
    station: IDV60901.95866
    name: Home
    monitored_conditions:

    • apparent_t
    • wind_dir
    • wind_spd_kmh

  • platform: bom
    station: IDV60901.95936
    name: City
    monitored_conditions:

    • apparent_t
    • wind_dir
    • wind_spd_kmh

  • platform: scrape
    resource: http://www.bom.gov.au/vic/forecasts/melbourne.shtml
    name: Melbourne maximum
    select: ‘.max’
    unit_of_measurement: ‘Max °C’

  • platform: scrape
    resource: http://www.bom.gov.au/vic/forecasts/melbourne.shtml
    name: Melbourne minimum
    select: ‘.min’
    unit_of_measurement: ‘Min °C’

  • platform: scrape
    resource: http://www.bom.gov.au/vic/forecasts/melbourne.shtml
    name: Melbourne summary
    select: ‘p:nth-of-type(4)’

    unit_of_measurement: ‘Nil’

  • platform: mqtt
    state_topic: Bedroom_3
    name: Temperature
    unit_of_measurement: ’ C’

camera:

2

For future use, you need to post your configuration.yaml file using the instructions in the big blue box at the top of the page.

But a quick glance shows that you don’t have an mqtt: section. See