Error log reports that input_select value is invalid, but it isn't

Configuration
1

For my custom input_select, the HA log shows this error occurring regularly:

Log Details (WARNING)

Invalid option:

Home

(possible options: Home, Away, Sleep)

From the configuration.yaml file:

input_select:
  home_away:
    name: Alarm Mode
    options:
      - Home
      - Away
      - Sleep

Aside from the warning, everything works fine. Any thoughts?

2

I believe ā€˜Homeā€™ is a constant in Home Assistant (i.e. it holds special meaning). Iā€™m not certain this will make the warning message go away but try delimiting Home with single-quotes.

    options:
      - 'Home'
      - Away
      - Sleep
3

Doesnā€™t appear to be - all the constants in that list are properly prefixe with category_variablename. Some have the value ā€œhomeā€, but non are named Home. But hey, worth a try!

4

Is that all that is reported in the warning message or is there more?

5

Thatā€™s all that it shows me on the information page, under the software version numbers etc. where it lists the log message.

6

If you click the error message, a popup appears that shows the message and, sometimes, more information (typically if there was a software execution error).

7

That was the detailed popup that I copied in my original post. No further detail available.

8

I just added your input_select (exactly as youā€™ve shown it) to my test server (running version 0.94.2). I restarted it and I donā€™t get a warning message complaining about an ā€˜Invalid option: Homeā€™.

Do you have an automation or a Template Sensor of some kind that refers to this input_select?

9

Nope, at the moment this input_select is a placeholder not connected to anything. I was planning to use it later.

10

Well, like I said, I added your input_select to my system and it produces no warnings. :man_shrugging:

11

Ok, so maybe itā€™s connected to something else in my setup? As I said, this is a new input_select that I havenā€™t used in any automation or node-red flow.

Maybe the time-stamp on the error log entries is a clue? The only thing I can see that happened at the same time in HA is that my iHome motion sensor triggered. Itā€™s an auto-discovered Homekit device that gets triggered a lot and really fills up the history logbook. But it is not connected to the input_select in any way. The iHome motion sensor is connected only to one node-red flow, and that flow is deactivated.

Oh, there is one other thing - I put this input select in a Lovelace UI group panel together with some input_boolean entities connected to sensors. None of the sensors triggered at the same time as the warning, but itā€™s the only other place the input_select is used.

12

The reason why I had asked if the input_select was referenced by an automation or Template Sensor was because this warning message canā€™t happen for an input_select in isolation (as Iā€™ve demonstrated using my system). Wherever else it is used in your system may hold a clue as to why the warning is issued.

13

Ok, now Iā€™ve pinned the error down better. Going by the exact times the error was logged, I noted that it was happening each time I reloaded my HA Lovelace UI page in the browser. Changing the value of the input_select did not cause an error after the page was loaded. I further noted that if I left the value set as Away or Sleep, the same error was logged on page reload, but citing Away and Sleep as invalid values, so obviously nothing to do with the word Home.

I then had another thought, and tried the same operation in Chrome instead of Firefox. Sure enough, thatā€™s it! No error logged on reloading the page in Chrome. Itā€™s a bug between HA and Firefox.

14

Iā€™m using Firefox and Iā€™m not getting the warning message on reloading the page.

configuration.yaml:

Screenshot%20from%202019-07-15%2012-28-58

ui-lovelace.yaml (Iā€™m using YAML mode):

Screenshot%20from%202019-07-15%2012-34-17

Appearance in UI:
Screenshot%20from%202019-07-15%2012-31-30

Use UIā€™s ā€˜Refreshā€™ command, or Firefoxā€™s F5 key, to refresh the page and no warning message is generated.

Home Assistant: 0.94.2
Firefox: 68.0

1 Like
15

Iā€™m using FIrefox 59.0

16

Perform an upgrade and see if that eliminates the warning message.

17

Iā€™ll take your word for it that itā€™s fixed in Firefox 68. :slightly_smiling_face:

I donā€™t particularly want to update Firefox and deal with all the hassles of broken extensions and plugins just for this, since I already know that it works with Chrome, and thereā€™s no important consequence to the bug now that I know what causes it.

Thanks for the help.