I was installed recently a new hassOS 3.13 on a RPI2 board but since I try to configure a few “integrations” without getting there. (I know than RPI2 is not recommended but it’s a test/poc)
I try to configure this “integrations” in the first time
Freebox [work it now]
Enedis
synology_dsm [work it now]
NISSAN Leaf [work it now]
Z-Wave by razberry
SNMP
When I configure it by the user interface, it doesn’t work. I also try by the configuration files (configuration.yaml and secrets.yaml) same result.
configuration.yaml
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
linky:
- username: !secret enedis_username
password: !secret enedis_password
timeout: 30
synology_dsm:
- host: "DISKSTATION"
username: !secret synology_dsm_username
password: !secret synology_dsm_password
port: 443
ssl: true
nissan_leaf:
- username: !secret nissan_leaf_username
password: !secret nissan_leaf_password
region: !secret nissan_leaf_region
# Text to speech
tts:
- platform: google_translate
Here is they logs:
first issue
2020-05-10 22:27:48 ERROR (MainThread) [homeassistant.setup] Setup failed for secrets: Integration not found.
second issue (enedis integration)
2020-05-10 22:27:49 ERROR (MainThread) [homeassistant.components.linky.config_flow] Login error: Please check your username/password.
third issue (NISSAN Leaf integration)
2020-05-10 22:27:51 ERROR (SyncWorker_15) [pycarwings2.pycarwings2] carwings error INVALID PARAMS: -2010
2020-05-10 22:27:51 ERROR (SyncWorker_15) [homeassistant.components.nissan_leaf] An unknown error occurred while connecting to Nissan: <class ‘pycarwings2.pycarwings2.CarwingsError’>
fifth issue (synology_dsm integration)
2020-05-10 22:27:54 ERROR (MainThread) [homeassistant.components.synology_dsm.config_flow] ConnectionError = <urllib3.connection.HTTPSConnection object at 0x6ee98f50>: Failed to establish a new connection: [Errno -3] Try again
Could you help me for the basic configuration, let’s take one issue after other
Next, remove the integrations that don’t work from your Integrations and / or .yaml files, so we can start fresh with one at a time.
Afterwards restart HA or better the whole Pi and let’s see, what error messages come up then. If nothing fancy comes up, start with the next integration, e.g. enedis.
After setting it up, restart HA again, and see, what errors come up. You get the idea. If something happens doing this, come back here and report.
Yeah, it’s a good start, but unfortunately you have choosen one integration, that doesn’t seem to work correctly right now… Take a look here for an answer of the developer:
I’d suggest to take a closer look to the linked Github repository to monitor for the change to happen, so the integration will work again. Sorry.
So, up to the next, synology_dsm. How does this work out?
Configuration is not in yaml. It is in JSON and inside a hidden directory called .storage. You should not attempt to modify this file while the system is running and if you incorrectly modify the file while the system is off, HA will not start properly.
NISSAN leaf
error log:
2020-05-13 22:21:01 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] while parsing a block collection
in “/config/configuration.yaml”, line 16, column 3
expected , but found ‘?’
in “/config/configuration.yaml”, line 19, column 3
2020-05-13 22:21:01 ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: while parsing a block collection
in “/config/configuration.yaml”, line 16, column 3
expected , but found ‘?’
in “/config/configuration.yaml”, line 19, column 3. Activating safe mode
See, as I said, it will take it’s time, but it will work.
Yep, the issue is closed, the underlying library is already fix, but for what I can see in the home assistant repository, it is already in the dev branch, but not in master. So you have to wait for one of the next releases of HA, where this is fixed. But that will not take long, as it is already fixed in the dev branch.
And as @flamingm0e said, in line 16 of your configuration.yaml seems to be an error. If this is a password line, you should put ' around the password, to mask special characters like ?.