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.
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!
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).
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?
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.
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.
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.
Iāll take your word for it that itās fixed in Firefox 68.
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.