WTH does a scene have to contain ALL the entities in a device?

Month of "What the heck?!"
1

As one of many examples, I have a TP-Link Kasa 2 outlet outdoor switch. I use one outlet to control holiday lights. I use the other outlet to control a small pond pump.

I have scenes for various holidays that need to include the holiday light outlet about. However, I do not want to change the state of the pond pump outlet as it is controlled by a separate automation. However, adding the TP-Link Kasa device to the scene requires me to set the state of both entities.

For now I’m setting all of the holiday scenes to turn the pump on because running it too often is better than not running it enough. But it seems like this should be avoidable. If I create the scene YAML manually, it, of course, can handle this, since scenes are entity based. But if I use the scene editor, I have to include both.

2

No you don’t… Just add the entity, not the device. Scroll down on the page.

image
image751×654 21.5 KB

3

Well now I feel stupid. LOL

I’ve been an HASS user for many many years, but I just recently (6 months or so) decided that scenes would be easier than automations doing the same basic thing, mostly because the scene editor is really handy and more accessible to non-technical users (so other people in my house can edit their own scenes and the automations just apply them).

Some how, in that whole 6 months I never noticed the second half of this page (to add entities). And I generally work on a PC with a big monitor, so it’s not even that I didn’t scroll enough. It’s just right there. Has it always been there? Was it added more recently?

Either way, thank you. This WTH is now an ID10T error. :slight_smile:

4

:rofl: I think it’s always been there. I haven’t used the UI for this though

1 Like