Trying to remove the automatic hue areas, any suggestions?

[dumbdevice]

Not possible. Speech-to-text uses all areas in the system in the templates

edit: it should be Speech-to-Phrase, not Speech-to-text

[petro]

I’m pretty sure the voice page with entities allows you to filter whats provided to voice. Have you tried modifying what’s exposed in settings → voice assistant?

[dumbdevice]

Yes, I have minimum entities exposed. Speech-to-text knows about all areas in HA regardless and uses them in generated templates file.

[petro]

I guess I’m confused by this comment then.

@dumbdevice

Hue areas entities

Because to me, that’s an entity that you can disable, either via voice assistent expose or simply disabling the entity all together.

[NathanCu (Nathan Curtis)]

Show me a screenshot of this page

For. One of those hue entities. And. You may already see what I’m going to point at. You can override a device area. Per entity.

[dumbdevice]

@petro

Because to me, that’s an entity that you can disable, either via voice assistent expose or simply disabling the entity all together.

Hue Integration entities are special. You can’t disable or hide Hue areas in HA. Again, Speech-to-text knows about all areas in HA regardless and uses them in generated templates file. I tested it

[petro]

Show me this “hue area”

[NathanCu (Nathan Curtis)]

At some point this gets exposed as an entity. That’s how HA works.

And if the hue integration is doing that if honestly open a bug against it you should be able to override your entites.

So either it’s a bug on Hue

Or

Go override the entities

(or me get off the hue hub and go 100% zigbee or something else, an integration gets exactly one shot to misbehave and locking you into area names to me is misbehaving. It wouldn’t last long.)

[petro]

Everything I can see in the integration code points to “grouped lights” which can be disabled or suggested areas, which can be ignored and removed. So I’m really curious to know what they are referring to.

[NathanCu (Nathan Curtis)]

And the minute all entities that are assigned to an area are gone the area won’t be pushed into context. Unless you deliberately pull a template to list all areas.

If you do that the list has an extra area. Big deal handle it in procedures and tell the llm to ignore it. I have an entire floor in my setup the llm doesn’t even acknowledge exists.

[dumbdevice]

@NathanCu

For. One of those hue entities. And. You may already see what I’m going to point at. You can override a device area. Per entity.

Oh, I tried many things to override a Hue device area. I know about this option. I also tried to rename Hue areas, but renaming is not permanent, it can be overwritten on HA restart or Hue Integration reload.

BTW at the moment I don’t even have any hue light exposed! Automation that trigger light is exposed.

@petro

Show me this “hue area”

in HA? here some (the current weird area names after my latest tests)

[petro]

Those are regular areas, you can delete them and ignore the suggestion

[dumbdevice]

But I can’t delete them, they will reappear after HA restart or Hue Integration reload. What suggestion?

[petro]

The suggestion is what’s creating the area, if you remove devices from said area, the area won’t be created. And if it is created (I’d argue that’s a bug), you can always just assign those devices to another area created by you. You could name it something you’d never utter to voice, like farfegnugen. Then it won’t create anything. Lastly, if you omit devices from voice, those devices regardless if the areas are exposed will not show up in voice.

[NathanCu (Nathan Curtis)]

That. 100%

If you remove the entities from the areas EVEN if the areas still exist it does not matter.

Even if you make a template that does nothing BUT call that area and inject it directly into teh context… If there’s no entity In it the llm wont give a rat about it unless you ask a direct question.

[dumbdevice]

@petro

The suggestion is what’s creating the area, if you remove devices from said area, the area won’t be created. And if it is created (I’d argue that’s a bug), you can always just assign those devices to another area created by you.

Are you talking about in context of the new experimental area dashboard? I don’t use it. It’s not related to dashboard. And I don’t want to create any other new areas, I want to disable existing ones provided by hue integration.

You could name it something you’d never utter to voice, like farfegnugen. Then it won’t create anything.

that exactly what I tried with areas names like “hl1” and “p4”

Lastly, if you omit devices from voice, those devices regardless if the areas are exposed will not show up in voice.

No, this is not like Speech-to-text works. There is special file sentences.yaml with templates generated by HA entities and all areas that you have in the system will be there.

[petro]

No, I’m not talking about the new dashboards. I’m talking about areas. Just regular old areas.

[dumbdevice]

well, those areas are generated by Hue Integration. I can rename them in Hue app

[petro]

My guy, remove the area from the device in HA. Then delete the area, the area will not be created anymore. And if it does, try the other method mentioned twice now (fake area). It’s getting created because hue is suggesting an area to HA and HA creates it.

[dumbdevice]

I did a test.

So I have “hl1” area and 2 devices in it

1. “hl1” room (created in hue app)
2. “hue lamp” (actual device)

(there are some automations and scenes Targeting this area)

• on Devices page I removed “hl1” area from “hl1” room and “hue lamp”
• “hl1” area is now empty
• I deleted “hl1” area
• restarted HA

After restart I see the same area “hl1” and devices “hl1” room and “hue lamp”