Error while adding a led device in the configuration file

Configuration
1

Hello,

I tried to add a simple light in the yaml conf file, but the system console says that something is wrong. Below is the content of the conf file.
In addition: which utility can I use to check the configuration error?
The documentation says:

hass --script check_config . On Hass.io you can use the hassio command: hassio homeassistant check

but I don’t have nor “hassio” program, nor “hass” (I installed hassio on raspbian with

“curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | sudo bash -s – -m raspberrypi3”

and I only have “hassio-supervisor” executable.

Thanks for your help

######################################

homeassistant:

Name of the location where Home Assistant is running

name: Home

Location required to calculate the time the sun rises and sets

latitude: 41.9569
longitude: 15.0355

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

elevation: 0

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: Europe/Rome

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:

Allow diagnosing system problems

system_health:

Sensors

sensor:

Weather prediction

  • platform: yr

Text to speech

tts:

  • platform: google

Cloud

cloud:

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

light:

  • platform: mqtt
    view: yes
    name: “Brightness light”
    state_topic: “office/light/status”
    command_topic: “office/light/switch”
    payload_off: “OFF”
    brightness_state_topic: ‘office/light/brightness’
    brightness_command_topic: ‘office/light/brightness/set’
    on_command_type: ‘brightness’
2

I’m sorry, something went bad while formatting the text.
Here is the complete conf file:

http://paste.ubuntu.com/p/4rnqhDVJCP/

3

Paste all your code in the box.

Highlight all the code.

Click the code button </>

4

What would be helpful here is the ACTUAL error message.

5

view: yes shouldn’t be in your light configuration for a start.

6

Here’s the content of home-assistant.log

2019-02-04 21:51:30 ERROR (MainThread) [homeassistant.setup] Setup failed for mqtt: Component failed to initialize.
2019-02-04 21:51:30 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of light.mqtt. Setup failed for dependencies: mqtt
2019-02-04 21:51:30 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform light.mqtt: Could not set up all dependencies.

The device is not phisically connected… does it cause the error above and then it’s not displayed in the GUI ?

7

Just solved.
I had to add the mosquitto entry in the yaml file.

But I wonder… given that I used the mosquitto addon, this should be done automatically… or at least the addon page must give a warning

8

Seems to me like you should have enabled it in the INTEGRATIONS page in the GUI instead. The add-on merely pulls and runs a docker image, it doesn’t necessarily tell HOME ASSISTANT that you want to use the application right away.