Hue discovered Light(s) don't go away after exclude hue

petro · January 23, 2019, 2:04pm

That’s pretty much telling us that it’s still discovering hue.

sender · January 23, 2019, 2:04pm

100% sure they come from: https://github.com/bwssytems/ha-bridge

I have that running for alexa. And I have configured the names popping up in hass… but I did and dont want that. I want hass to become the alexa ha bridge (hue bridge)

sender · January 23, 2019, 2:05pm

but how can that be then? I have disabled that in configuration.yaml

petro · January 23, 2019, 2:07pm

That repo is for the emulated hue component. That means home assistant will emulate a hue bridge. It won’t add devices in home assistant. It adds devices in alexa or google home. That’s definitely not the repo that is being used.

Unless you are doing that from some other platform and HA is finding it.

sender · January 23, 2019, 2:08pm

I use that repo to emulate ha bridge for alexa. and that’s what hass is discovering.

petro · January 23, 2019, 2:09pm

What’s running that? Vera?

sender · January 23, 2019, 2:09pm

seperate ubuntu server vm in same subnet as hass ova.

edit: currently thát is the bridge between alexa and vera. And I want hass to be that in the future. but hass is fiding the hue devices from thát bridge and I don’t want that.

petro · January 23, 2019, 2:11pm

Seems like you’re your own worse enemy here. I’d get rid of that VM, connect your vera to HA, then use HA’s built in emulated hue (which uses that repo)… This wouldn’t even be a problem if you went that route.

sender · January 23, 2019, 2:13pm

I know. but why can’t I disable hue discovery in hass? Seems evident I must be able to simply do that. I first want to play around with hass (as you can imagine :-)) before stopping with ha bridge on ubuntu which currently works well enough.

petro · January 23, 2019, 2:15pm

It should be disabling it. I don’t know what to tell you there.

You could just turn off discovery all together and configure everything by hand. Just remove discovery and all of it’s sub-attributes.

sender · January 23, 2019, 2:20pm

did that before but keeps discovering (well discovering… putting back the devices)

sender · January 23, 2019, 2:21pm

hey, I remove the portion from /config/.storage/core.config_entries and after reboot they are now gone…?

petro · January 23, 2019, 2:21pm

That doesn’t make any sense. When discovery is missing, nothing will be discovered on any platform. That means the entities are inside history or your entity registry.

petro · January 23, 2019, 2:22pm

Well thats a step in the right direction. It’s possible that discovery was added to the UI and that means you’d have to turn it off from the UI instead of the config files.

sender · January 23, 2019, 2:23pm

ehm… UI, where?

petro · January 23, 2019, 2:24pm

under configuration -> integrations. I’m running an old version so not 100% on the location.

sender · January 23, 2019, 2:27pm

think i never went there… well thanks for the support!

next thing is to get ssl (https) running… have been trying and googling around for about 2 or 3 hours but this seems not so easy.

petro · January 23, 2019, 2:27pm

are you running hassbian or hassio?

sender · January 23, 2019, 2:30pm

used the ova install, I think hassio (no a pi) but a vm on my synology.

this is the core:

Linux core-ssh 4.14.82 #1 SMP Wed Nov 21 10:50:27 UTC 2018 x86_64 Linux

NAME=“Alpine Linux”
ID=alpine
VERSION_ID=3.8.1
PRETTY_NAME=“Alpine Linux v3.8”
HOME_URL=“http://alpinelinux.org”
BUG_REPORT_URL=“http://bugs.alpinelinux.org”

petro · January 23, 2019, 2:36pm

Hmm, that could still be hassbian. on the ui do you have a hassio tab