Hardly anything working on hassio

Configuration
1

Dear members,
For the third time in two days I have had a hassio installation performed on a brand new Raspi 3B and ditto samsung sdhc-card.
The first time I think I met some sort of wizard that guided me. Later times not.
I see no way to get the Configurator (what is in a name) on to the overview left side of my screen.
Apart from that my Main problem is mqtt:
Testing configuration at /config ERROR:homeassistant.util.yaml:while parsing a block collection in “/config/configuration.yaml”, line 43, column 3 expected , but found ‘?’ in “/config/configuration.yaml”, line 44, column 3 Failed config General Errors: - Error loading /config/configuration.yaml: while parsing a block collection in “/config/configuration.yaml”, line 43, column 3 expected , but found ‘?’ in “/config/configuration.yaml”, line 44, column 3 Successful config (partial)
16:42 components/hassio/init.py (ERROR)
Unable to prepare setup for platform mqtt.light: Could not set up all dependencies.
16:38 setup.py (ERROR)
Unable to set up dependencies of mqtt.light. Setup failed for dependencies: mqtt
16:38 setup.py (ERROR)
Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml
16:38 components/device_tracker/init.py (ERROR)
Setup failed for mqtt: Component failed to initialize.
16:38 setup.py (ERROR)
Unable to start embedded MQTT broker
16:38 components/mqtt/init.py (ERROR)
Error initializing MQTT server
16:38 components/mqtt/server.py (ERROR)
Broker startup failed: [Errno 98] error while attempting to bind on address (‘0.0.0.0’, 1883): address in use
16:38 components/mqtt/server.py (ERROR)

This error keeps coming up.

Can someone please shed some light on these problems.

pablok

2

The Configurator is an addon

Hass.io -> Add-on Store

I believe the documentation tells you how to have it appear in the menu.

I do not use mqtt.

3

Dear Bosborne, I know. I have it added-on from the store. But thanks for your reply.

4

I was wrong, This page tells you how to get it in the menu.

panel_iframe:
  configurator:
    title: Configurator
    icon: mdi:wrench
    url: http://hassio.local:3218
5

There the errors are coming from is in the error messages themselves. You can some invalid lines in your config, your MQTT broker’s IP is set to 0.0.0.0, and you are missing known_devices.yaml.
Without seeing your config I can’t tell you what’s wrong with the config file, only to read the errors closely and fix what it’s saying is broken.

6

Thank you so much @anon34565116

7

The lines 43 and 44 look like this in the Configurator:
43 script: !include scripts.yaml
44

8

Does scripts.yaml refer to known_devices.yaml ?

9

It is empty. It exists, but empty.

10

I don’t see a known_devices.yaml file.

11

Made a file: known_devices.yaml.
What should go in there?

12

your error lies in line 44, 3rd character. Fix that the rest will follow.

Testing configuration at /config ERROR:homeassistant.util.yaml:while parsing a block collection in “/config/configuration.yaml”, line 43, column 3 expected , but found ‘?’ in “/config/configuration.yaml”, line 44, column 3 Failed config General Errors: - Error loading /config/configuration.yaml: while parsing a block collection in “/config/configuration.yaml”, line 43, column 3 expected , but found ‘?’ in “/config/configuration.yaml”, line 44, column 3 Successful config (partial)

FYI everyone thinks these errors are useless. 9 times out of 10 they tell you exactly what is wrong. You just have to actually read the error instead of glancing at it and assuming it’s jibberish.

First part tells you what python file the error is in:

Testing configuration at /config ERROR:homeassistant.util.yaml

Second part tells the error in python after the colon.

whileparsing a block collection in “/config/configuration.yaml” line 43, column 3 expected , but found ‘?’ in “/config/configuration.yaml”

So lets break that down:

First part tells you some crap, this changes alot. But typically the errors have good info. This error tells you that it had issues parsing the configuration.yaml file. YAY we know where are issue is!

whileparsing a block collection in “/config/configuration.yaml”

The second part tells you EXACTLY where in the file the issue is, the 43rd line 3rd character. According to this section, it was looking for nothing but found something something.

line 43, column 3 expected , but found ‘?’
                          ^
                          |
           here is the nothing

The rest of the error is useless. Not all errors are the same, but this error tells you what your problem is.

1 Like
13

mqtt is already running on that port

14

As I showed earlier, line 43 in the configuration.yaml file looks like this:
43 script: !include scripts.yaml
There is no ‘?’ there.

15

Then the error lies in scripts.yaml. The question mark means it couldn’t find what was wrong. It doesn’t mean that the question mark is the problem.

16

Then why do I get no response from mqtt?

17

Because you have 2 conflicting MQTT instances apparently.

I would fix your errors in your config and restart before troubleshooting other stuff.

18

Should there be anything in the scripts.yaml on a freshly installed system? Scripts.yaml is empty now.

19

From the configuration.yaml file:
tts:
- platform: google

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

mqtt:
  discovery: true
  
light:
  - platform: mqtt
    name: Lamp1 Serre
    command_topic: "cmnd/sonoff1/POWER1"
    state_topic: "stat/sonoff1/RESULT"
    value_template: "{{ value_json.POWER1 }}"
    availability_topic: "tele/sonoff1/LWT"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: true

I cannot make out two conflicting mqtt instances.
Please advise.

20

It would appear Home Assistant is trying to start its own built in MQTT broker, which could be caused by your configuration yaml being broken.

scripts.yaml doesn’t even exist on a fresh install. You had to have created that. If the file is empty that’s why the config doesn’t load! Comment out the line that is trying to load an empty file.