Support beyond Climate?

[ndrwrbgs]

This came up when I was trying to work around features which are planned anyway now[0]. But I figure I should mention it!

I was looking for the ability to control an arbitrary input_number, in case the value I was controlling wasn’t hooked up to a climate entity.

In the end, lacking this ability encouraged me down a route that had me properly configure multiple rooms as separate schedules, which I think was a better match for reality and the mental model anyway. This may be a YAGNI then, because while it could support more advanced workflows, it could also have enabled me to proverbially shoot myself in the foot with complexity.

[0] “boost”, my work around would’ve added a layer of indirection, but would’ve been less nice than true integration as the history on the views would have matched my indirection and not reality

[ndrwrbgs]

This would start to overlap with the https://github.com/nielsfaber/scheduler-component

I tried that plugin first for climate automation: it had more functionality but this had more usability for my needs.

It may be that keeping the scope narrow is exactly what gives this the usability benefits and protects them for the future.

[kneave]

There's some support for this already in there, you can create a group without any climate entities and if you add nodes to the graph and click on them you should see text fields labelled A, B, and C. When a node is triggered it fires a climate_scheduler_node_activated event which includes these values, you should be able to create generic automations based on this.