Template select blueprints broken?

Configuration Blueprints
1

Attempting to understand template blueprints in general and select in particular. At this point though I am beyond frustrated, nothing seems to work, error messages makes no sense and documentation is lacking.

I have cut down my blueprint so that there is barely anything left, but it is still throwing an error message that for some reason variables is an invalid option:

Invalid config for ‘template’ at configuration.yaml, line 15: ‘variables’ is an invalid option for ‘template’, check: select->0->variables

There seems to be only one single example of a template blueprint, the included inverted_binary_sensor.yaml, and that one uses variables. Why would variables not work for template select? How am I supposed to pass settings from configuration to the blueprint without it?

blueprint:
  name: "Select Test"
  domain: template
  homeassistant:
    min_version: 2024.10.0
variables:
  test: "Test"
select:
  availability: "{{ true }}"
  state: "{{ 'One' }}"
  select_option:
  - stop:
  options: "{{ ['One', 'Two'] }}"

Also, is it just me or is the Developer Tools > YAML > YAML configuration reloading > Template entities button also broken? While it does seem to reload the relevant portions of configuration.yaml, it does not reload the template blueprints which makes them kind of impossible to debug/develop. Reloading all configuration does not reload template blueprints either, only a full HA restart does. Unlike the buttons for Automations and Scripts on the same page, which does reload the blueprints as well.

2

Outside of state-based sensors and binary sensors, any other template blueprints should really be considered as beta at this point in time.

There is a similar issue regarding variables already open for trigger-based sensors. You should add a comment about template selects there.

3

FWIW, I get the exact same error for a button blueprint template.

4

Yeah, unfortunately that does seem to be the case. Considering how half-baked template blueprints still are, it does not seem like a feature that should’ve made it into general releases yet.

I am working on an automation blueprint that would’ve made sense to be a template select blueprint instead. I have other blueprints that would work nicely as a template switch, but those don’t seem to be blueprintable at all yet.

Hopefully progress is made before this feature is forgotten…