Emulated Hue entities?

Configuration
1

According to the docs the “emulated_hue_hidden:” option under the “customize” section is supposed to be going away sometime in the near future.

According to the docs it will be replaced by “hidden: true” or “hidden: false” in the new “entities:” section directly under “emulated_hue:” in the configuration.yaml file.

I tried to update my configuration with the new set up and I get an error in the log:

2018-02-19 05:06:02 ERROR (MainThread) [homeassistant.config] Invalid config for [emulated_hue]: [entities] is an invalid option for [emulated_hue]. Check: emulated_hue->emulated_hue->entities. (See /home/homeassistant/.homeassistant/configuration.yaml, line 208). Please check the docs at https://home-assistant.io/components/emulated_hue/

my new emulated_hue section looks like the following:

emulated_hue:
  host_ip: 192.168.1.125
  listen_port: 8300
  off_maps_to_on_domains:
    - script
    - scene
  expose_by_default: true
  exposed_domains:
    - script
  entities:
    script.turn_off_mbr_fan:
      hidden: false
    script.turn_off_sunroom_fan:
      hidden: false
    script.close_gdn:
      hidden: true
    script.open_gdn:
      hidden: true
    script.garage_lights_timer:
     hidden: true
    script.garage_timer_control:
      hidden: true
    script.turn_off_all_lights:
      hidden: true

Line 208 is the line that starts “emulated_hue:”

Are the docs wrong (again…) or am I?

2

What version of homeassistant are you running? Entities is working fine here.

Also, the hidden line under garage lights timer needs indenting one more space.

3

0.60.1

and that was a typo in the post, not in the actual config.

When did the entities: get implemented?

4

Always read the change log for the version you are using. Nothing there about the emulated hue changes.

5

Yeah, well…I’m not seeing the breaking change in any of the releases.

I only see a vague blog post about it between 61 and 62.

Is that when the change took effect?

I generally look at the breaking changes and forum posts before I decide to do an update. Which is why I’m still on 60 because of issues I’ve seen others are having with the recent releases.

6

I’m running 63 and I’m using the old hidden method. I’ll update to the new style later today and post my results. It’s about time they made this change! I’ll let you know if I get a config issue.

7

Where did you see that blog? Technically, it is not a breaking change (yet), as the old customization option has NOT been removed. AFAICT, the change took effect in 63. So >=63, both emulated_hue customization and normal customization work, <63 only the normal customization works.

8

What’s this then?

41
41857×193 32.1 KB

Taken from here which is linked from the homepage…

2 Likes
9

Yeah, well…again…

Honestly, I don’t ever read the ENTIRE list of changes as the vast majority don’t affect me. It’s usually a big waste of time. if it’s not a new platform or a breaking change I assume it’s not important.

And that one was buried so far down in that list I’m not surprised I didn’t see it.

the only reason I knew about it in the first place was I was looking at some examples from others configs and saw a reference to it. From the timing of the changes in their configs I assumed (wrongly…) that it was already implemented in an earlier release.

I think there ought to be some reference in the docs on when a change was introduced, especially if you are going to the trouble to explicitly annotate that IS a change in the first place.

JMHO…

thanks for the help tho. :grin:

10

The docs are always relevant to the current version of the software.

11

Yes, i know that but if they are going to the extent of annotating that a change was made in the docs then it would be as simple and informative to annotate when the change was implemented.

just simply add “in version 0.63.0” to

hue

12

Hello, I thought I’d post here before starting a new thread.

I want to expose only certain entities (zwave devices, groups) to emulated hue, as most of my lights for example are Hue so they are already discovered by Alexa and don’t want to double up.

As I understand, I should set expose_by_default: false to avoid all entities being exposed by default. I can then indicate which domains are exposed, so lights and groups, and then indicate which entities are exposed. Would this only expose the entities I indicate in those domains?

I currently have it set to true by default, then I list all the entities in the lights category, and go through each one and set hidden to true or false, but this is very tedious.

Something like this:

# Example configuration.yaml entry
emulated_hue:
  host_ip: 192.168.1.186
  listen_port: 8300
  advertise_ip: 10.0.0.10
  advertise_port: 8080
  expose_by_default: false
  exposed_domains:
    - light
    - group
  entities:
    light.bedroom_light:
      name: "Bedside Lamp"
    light.potlights
13

I haven’t used emulated hue in a really long time but my understanding from reading the docs is that if you have “expose_by_default: false” you have to list every entity you want to expose explicitly in the “entities:” section.

If you have it set to true then you will list only the domains you want to expose by default in the "exposed_domains: " section. Then you can also list any entities outside of those domains to add explicitly or any entities within those domains that you want to hide explicitly.

I think… it’s really kind of confusing…

I realized the strict limitations of the emulated_hue component pretty quickly and stopped using it so for a long time I used the haaska custom component. It was more flexible and IMHO easier to use once you got thru the more complex initial set up. In my understanding even the initial set up is a little more straight forward now compared to back then.

I just use the HA cloud now. It seems to be at least a little easier.

14

I use this simple way to expose each entity:

emulated_hue:
  expose_by_default: false
  entities:
    light.bedroom_light:
      name: "Bedside Lamp"
      hidden: false
    light.potlights:
      name: "Pot Lamp"
      hidden: false