Emulated Hue Depreciated? (solved)

Third party integrations
1

Hi,

EDIT 2: Looked up on the github issues tracker and it appears this refers to the “customize” section only that has changed.

I just upgraded to 0.55 to get the owntracks HTTP component working but I see my logs are now full of…

2017-10-08 16:29:40 WARNING (MainThread) [homeassistant.components.emulated_hue] ‘emulated_hue’ is deprecated. Please rename ‘emulated_hue’ to ‘emulated_hue_hidden’ in your configuration file.

Renaming to emulated_hue_hidden results in not found in the logs.

Please tell me this is just an error on my end. I just spent the last week moving all my alexa commands over from ha-bridge to emulated hue.

I tried to look for answers on here and the blog but don’t find mention of it.

EDIT: Running Hassbian 1.3 on a Pi3.

Any ideas?

Thanks

Simon

2

This is a nonsensical change.

Before this change the config was emulated_hue: false to not add to emulated hue. Now you mark hidden as false to hide it, whereas logic dictates that if hidden is false, it is not hidden.

3

emulated_hue_hidden makes it explicit and consistent with homebridge_hidden.

All you need to do is replace emulated_hue: true with emulated_hue_hidden: false and vice versa.

4

That makes it clearer. I found the documentation confusing as the comment in the code snippet doesn’t make it clear what the given example defines.

5

Lot of that going on at the moment :slight_smile: people are probably thinking ahead of what they’re writing and leaving important bits out. Easily done but not often picked up as few people reread what they write nowadays.

1 Like
6

It is a open source project, feel free to create PRs to update the docs.

7

I did look at doing it for some other major omissions but didn’t understand how it worked, is there an idiot’s guide to creating PRs to do that?

This is a classic that must really confuse any newcomers to emulated_hue…

A physical Hue Bridge is required for the lights to function - this virtual bridge will not replace a physical bridge.
2 Likes
8

I would be happy to submit the PR or point you to the right location if you want to provide me with better documentation.

9

Every page has a Edit this page on Github that you can use to edit the page.

10

Yes, I don’t think any of us are blind, but you then get…

You’re editing a file in a project you don’t have write access to. Submitting a change to this file will write it to a new branch in your fork xxxxxx/home-assistant.github.io, so you can send a pull request.

We want to help but need some ourselves first rather than an assumption it’s obvious. I’m sure this is quite normal in github land but if you don’t know how it works, you don’t know.

11

Demonstrated here: https://youtu.be/dRfk9JAlPJk?t=1h16m17s

1 Like
12

Perfect, thanks Daniel :+1:

13

(Never mind) I figured it out
Necessary missing piece was
hidden: false

I’m sure I’m missing something simple. I’ve been using emulated hue for a long time and got tired of the depreciated messages in the logs so I’m trying to do it right now.

When I use the entities section to publish and comment out the customize emulated_hue, nothing shows up on harmony hub as hue lights. But if I do it the old way in customize it works fine.

in customize.yaml (this works but with log warnings of depreciation)

switch.entertainment_center_power:
  icon: mdi:power
  emulated_hue: true
  emulated_hue_name: Entertainment Center Power

in configuration.yaml

emulated_hue:
  expose_by_default: false
  entities:
    switch.entertainment_center_power:
      name: "Entertainment Center Power"