Config error, expected dictionary value

[nvschilleman]

Problem/Motivation

Keep getting config errors, while my config comparable to examples

Expected behavior

Including only the set entities to my database

Actual behavior

Keeps getting errors

I've configured the addon following the steps given in the readme. When trying to configure the component in Hass I keep getting the following errors:

Invalid config for [influxdb]: expected a dictionary for dictionary value @ data['influxdb']['include']. Got [OrderedDict([('entities', [OrderedDict([('entity', 'binary_sensor.koelsignaal')]), OrderedDict([('entity', 'binary_sensor.compressor')]), OrderedDict([('entity', 'binary_sensor.verdamperventilator')]), OrderedDict([('entity', 'sensor.ontdooiing')]), OrderedDict([('entity', 'binary_sensor.celdeur')]), OrderedDict([('entity', 'binary_sensor.algemene_koelstoring')])])])]. (See /config/configuration.yaml, line 54). Please check the docs at https://home-assistant.io/integrations/influxdb/

I don't see anything wrong in my config, this is my config:

 influxdb:
   host: a0d7b954-influxdb
   port: 8086
   database: pfio_mon
   username: xxx
   password: xxx
   max_retries: 3
   include:
       entities:
         - binary_sensor.koelsignaal
         - binary_sensor.compressor
         - binary_sensor.verdamperventilator
         - sensor.ontdooiing
         - binary_sensor.celdeur
         - binary_sensor.algemene_koelstoring
   default_measurement: state
   tags: 
     source: hass

[addons-assistant]

👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

[sinclairpaul]

As this isn't an issue with the addon I will close this.

Details of how to get help with the configuration of Home Assistant can be found at https://www.home-assistant.io/help/

Home Assistant

Help

If you need help or have a question...

[addons-assistant]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.