mishamyrt / dohome_rgb

💡 DoHome lights Home Assistant integration
MIT License
1 stars 1 forks source link

Invalid config for 'dohome_rgb' at configuration.yaml #2

Closed MarcoLeongDev closed 5 months ago

MarcoLeongDev commented 5 months ago

I am aware of the issue and ensure that the syntax is latest for the yaml. Invalid config is still being encountered.

The main error log:

Screenshot 2024-01-15 at 11 55 45

Followed by another two log entries:

Screenshot 2024-01-15 at 11 57 10 Screenshot 2024-01-15 at 11 57 16

Other info:

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

light living_room:
  - platform: dohome_rgb
    sids:
      - 7ED0

Questions:

  1. The device is connected but not in pairing model, is that a requirement?
  2. From the error point of view looks like it is not because of variable/argument but rather some function/component calls isn't working? Any experience on this type of issue?
  3. Let me know which direction I should be looking at to troubleshoot the issue?

I am quite new to custom components, especially the troubleshooting, thank you for your understand and help in advance

mishamyrt commented 5 months ago

Hi! Regarding your first question, the device must be connected to wifi and configured. For the others, the configuration seems to be in a broken format:

light living_room:
  - platform: dohome_rgb
    sids:
      - 7ED0

should be

# remove living_room
light:
  - platform: dohome_rgb
    sids:
      - '7ed0' # lowercase is better

At the moment I haven't implemented entity naming through the configuration, I'll probably add it later. For now I can only recommend to configure without naming, and then set what via UI.

mishamyrt commented 5 months ago

Checked it again and yes, you're right. There is an error in the code, I will fix it

mishamyrt commented 5 months ago

Problem fixed in version v0.5.2, update the integration please