Input_select unavailable

Configuration
1

Hi,
i recognized some (not all) of my input_selects are unavailable since a few days. Also a restart does not help. It also makes no difference if i set a initial value or not. Any ideas how to fix that?

2

What changed a few days ago?

3

ā€¦ And how/where do you define them ?
Please post a representative sample

4

My guess is that, several days ago, you edited the configuration file and accidentally introduced a new, empty input_select: section (located after the original, non-empty, input_select: section).

1 Like
6

Sorry again, you are right (it was late yesterday :sleeping: ). That would help. Here is my code:

input_select:

  temperature_states:
    name: AuƟentemperatur in fĆ¼nf Temperaturstufen diskretisiert
    options:
      - "0"
      - "1"
      - "2"
      - "3"
      - "4"
      - "5"
    icon: mdi:oil-temperature

  alarm_states:
    name: Alarm Status bzgl. Fenster offen und Licht an
    options:
      - "0"
      - "1"
      - "2"
      - "3"
    icon: mdi:sign-caution

  mercedesme_choosen_day:
    name: Auswahl des Tages zur Anpassung der Aktivierungszeit fĆ¼r die Standheizung
    options:
      - "Montag"
      - "Dienstag"
      - "Mittwoch"
      - "Donnerstag"
      - "Freitag"
      - "Samstag"
      - "Sonntag"
    initial: "Montag"

input_select:
  alexa_message_target:
    name: Type Of Broadcast
    options:
      - "media_player.echo_alexa"
      - "media_player.echo_computer"
      - "media_player.echo_echo"
      - "group.alexa_all"
    initial: "media_player.echo_alexa"
    icon: mdi:speaker-wireless
7

Sorry that i have not explained this. I did a lot of work the last days (no work and exit lock due to corona at the moment). For this reason i could not define what was the change which created the problem. Thatā€™s a part of my problem :wink:

But you are awesome. Yout expectation was correct. I introduced a second ā€œinput_select:ā€ - line (as you see above). After a test it is now again working as intended.

Thank you very much :grinning:

1 Like
8

That was either a ā€˜hellovanā€™ insightful guess, you have done some very weird stress testing or you have a very good memory as someone has done this before.
Any which way, kudos to you :+1:

Iā€™ll have to try to do that as I donā€™t see how it would even pass a config check :man_shrugging:

9

Iā€™ll have to try to do that as I donā€™t see how it would even pass a config check :man_shrugging:

Thatā€™s exactly what surprised me the most. But it did pass the config check. :thinking:

10

I did a quick check of how my system is configured and I have 43 packages (so a potential to have 43 separate and valid instances of ā€œinput_select:ā€ but I actually only have 5 of them).
So I can see why putting a check for that would be a ā€˜a little more involvedā€™ for the config checker.
Ah well, itā€™s one those to be filed away and try to ensure it doesnā€™t happen again.
Good luck with your config updates.