I want to change the setting
expose_by_default: true
To
expose_by_default: false
But when I do all of the entities show up as cant be found in my log. It just goes over and over trying to look for them, but can’t find them. Is there a way to start fresh like with Home Kit and have the setting set to false to begin with so I don’t have to have my log get filled up.
I just want to select the entities and be able to customize them on my own.
It seems like when you expose an entity to Emulated Hue your stuck with it in there? Or at least according to the log file it will just keep searching for it?
2019-04-22 16:25:48 ERROR (MainThread) [homeassistant.components.emulated_hue.hue_api] Entity not exposed: switch.nodemcu_01
I’ve tried everything I can think of and I keep having this show up. It just keeps trying and trying over and over. Under emulated hue I tried to have this entity hidden, but it still shows up. What is the proper way in your opinion to reset. Like with Homekit I can just remove home or delete the file. Anything like this for Amazon devices? Like a way to start fresh.
It seems like once the entities are in there it’s impossibly for Home Assistant to not search for them. Like there is a residual. Or am I missing something?
Mon Apr 22 2019 17:04:15 GMT-0700 (Pacific Daylight Time)
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 418, in start
resp = await task
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py”, line 458, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py”, line 119, in impl
return await handler(request)
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/http/real_ip.py”, line 33, in real_ip_middleware
return await handler(request)
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/http/view.py”, line 112, in handle
result = handler(request, **request.match_info)
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/emulated_hue/hue_api.py”, line 172, in get
entity = hass.states.get(entity_id)
File “/usr/local/lib/python3.7/site-packages/homeassistant/core.py”, line 829, in get
return self._states.get(entity_id.lower())
AttributeError: ‘NoneType’ object has no attribute ‘lower’
I deleted everything in alexa and kept getting cant discover on all devices now.
Ok so I deleted type: alexa as per wiki page.and I get the error above.
Any other ideas what I’m messing up here? It’s getting so frustrating becuase I just want to set expose by default to false and add my own entities. I am approaching more than 45 now.
Hello,
I’m having the same problem. I want to “reset” all the Alexa devices and start fresh, but when I discover again, I get all the old devices. I’ve tried EVERYTHING except the correct one…
So, I have about 38 devices and a few groups. Z-wave lights, TP-link switches and such. After the Echo update things went crazy, I changed the emulated_hue to port 80, removed all devices and re-discovered on the alexa.amazon.com website and it worked, but gave the “this device appears not to be working” but worked. The wife started to complain, so I decided to fix it… Deleted the emulated_hue_id.yaml file - then re-discover the devices. At first I was getting 3-4 copies of each. I’ve tried different hue ports, I do a reboot of the Pi, not just a service restart - but it seems Hassio has a cache of the emulated_hue_id file in components/emulated_hue/hue_api.py - where ever that is. I do not know much about Docker but that it is like little VMs. I looked for it…
Anyway, I have set the emulated_hue in the config file to exposed_by_default: false
Here is my config - I have tried to setup one of the z-wave
Here is a sample of the error log I get, after deleting the emulated_hue_ids file.
Unknown entity number: 12 not found in emulated_hue_ids.json
5:43 PM components/emulated_hue/hue_api.py (ERROR) - message first occured at 5:31 PM and shows up 24 times
It shows 38 or so devices, why doesn’t it clear, and how can I reset it.
Thanks PeteA that did work and only 1 of the devices showed up. But the problems continued. I read it’s the bridge listing all the devices as lights and need a dim setting or it craps out.
Anyway, it’s a losing battle. emulated_hue in HA is pretty much dead. I went ahead and moved to the HA cloud thing, works great and took a few minutes to setup. I already used the Alexa script tools, have to open a port, but will continue it to use it for my sensors.
It will cost $5 a month, oh well, another thing to pay for. I’m glad the HA guys might make a little money, I’ve been using there tech for free for years, they deserve it.
I don’t like the fact that I can’t run the z-wave and IP switches local. I will have to work on that, but until then, the wife is happy and the lights work!!
thx
Search the forum a bit more. I think I saw a solution that may work that doesn’t involve a subscription. The Hue emulator is a bit of a mess at the moment though.
Does somebody have a solution to reduce the number of exposed entities? If I set it to exposed by default false it does not expose ANY. How are we supposed to change the configuration ?
I appreciate your answer.
Do you mean that I can not do it the other way around?
I tried setting expose_by_default to false and specified the entities. But this leads to an empty entities list.
Is hiding the only way of changing the behavior? Once you setup emulated_hue once there is no way back to choose a different strategy?
That configuration led me to several warnings on my log about the entities not being exposed and the /api/pi/lights to return an empty value.
As I said before, I started with a simple configuration like this:
