Hue motion sensors + remotes: custom component

bryantp · February 25, 2019, 12:46am

Hi All,

I updated Home Assistant to 0.88.1, had the same errors that others had in this thread, and applied the fix. However, my Hue Switch seems to have disappeared.

I have a Entity not available: sensor.switch warning when I try to use the component.

Diginorse · February 26, 2019, 2:11pm

can not for the love of the network gods get the temp sensor working … i mean I see it in the hue app… but can not get it working on my hassio…
this gonna give me grey hairs

yottatsa · February 26, 2019, 6:34pm

Which error did you get? What’s your config?

bryantp · February 26, 2019, 9:22pm

Looks like I had the naming incorrect.

I had a duplicate sensor top level field and had the wrong filename for one of the files.

Thanks anyway though.

Jeppe_Lutzhoft · February 27, 2019, 2:37pm

Does the outdoor sensor work?

Ragnar_Bull-Nielsen · February 28, 2019, 6:08pm

Yes, just like the indoor one, no difference as far as I can see.

Ragnar_Bull-Nielsen · February 28, 2019, 6:14pm

Anybody else have trouble getting this component to work in HA 0.89b?
I’m aware of the new component file structure, and the latest version of this custom component that I cloned just before upgrading seems to reflect the updated structure, but it still doesn’t work.

claytonjn · February 28, 2019, 8:43pm

My guess would be that this is the issue:

github.com/home-assistant/core

Prevent partial custom component overlays

home-assistant:dev ← home-assistant:prevent-partial-custom-overlays

opened 07:38PM - 14 Feb 19 UTC

balloob

+44 -16

## Description: This will force platforms to be resolved based off the componen…t path, if it exists. Today, if you want, you can override the Hue light platform, but not the other parts of the Hue integration. If a future update evolves the Hue component, removing or changing internal methods that the custom platform relied upon, the custom platform will start failing (like [this report](https://github.com/home-assistant/home-assistant/issues/17943#issuecomment-462014778)). To avoid this, we're going to no longer allow custom components to be partial overlays (just a platform). Instead, if you want to override a built-in platform, you will need to override the whole component. This is enforced by first resolving the platform as a component, and if it exists, limiting the lookup path to the component path. Example: if I look up the `hue` component, and it is provided by a custom component, then all platform lookups will also be looked up in the custom component dir. The same works the other way around, if a user would only try to override `hue/light.py` but not `hue/__init__.py`, the custom platform will be ignored. **Breaking change:** Custom platforms that override a built-in platform that has a component, should now also include the component in the `custom_components/` folder. So if you want to override `hue/light.py` with a custom version, you will also need to provide/copy over `hue/__init__.py`. **Related issue (if applicable):** fixes https://github.com/home-assistant/architecture/issues/141 ## Checklist: - [x] The code change is tested and works locally. - [x] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass** - [x] There is no commented out code in this PR. If the code does not interact with devices: - [x] Tests have been added to verify that the new code works. [ex-requir]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard/__init__.py#L14 [ex-import]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard/__init__.py#L23

TravelinMax · March 1, 2019, 12:28pm

These components stopped showing in the custom updater for me a few days ago. I don’t know if that was intentional or not.

Jonde · March 2, 2019, 5:02pm

Just updated to the latest version of this CC, 1.0.4. Everything seem to be working fine with 0.87.1. But I also wanted to use the device_tracker and my phone seem fine in HA but the status does not change at all. It is always “home”.
Is there some trick to get this working?

bturrie · March 5, 2019, 6:06pm

I’ve decided to stay with 0.88.2 (which is working) until this package is officially added to HA. To me the Hue stuff is more important than staying up to date. So I cannot help with 0.89b. I just wanted to record somewhere how important this component is to my system.

markbajaj · March 6, 2019, 10:31am

Just put my dev HA onto 0.89b3 and can confirm that it does break this CC.

It seems that it is the changes mentioned by @claytonjn a few posts up.

@robmarkcole - any chance of an update to it? From reading the breaking change it does seem quite a major rewrite though?

If i understand correctly (I am an IT geek and enterprise infrastructure engineer, not a programmer), the breaking change means that a custom component has to be ‘all in’ or not. So this one will take control of the whole Hue integration, not just the sensors?

markbajaj · March 6, 2019, 11:03am

As a total bodge (lol I am definitely not a programmer) I copied all the /config/custom_components/hue/ files to /homeassistant/components/hue folder and it now works

I suppose that is because HA now thinks it is the official component? I have only done this in my development instance and definitely dont recommend doing on a live one…it will get rewritten with each release as well.

Is a solution to have the CC called hue_sensors or similar?

Excuse my lack of understanding in all things programming.

cicero222 · March 6, 2019, 11:21am

Perhaps you should do it the other way round: Copy all files from homeassistant/components/hue to /custom_components/hue/

That way you override the entire Hue platform as requested with Prevent partial custom component overlays by balloob · Pull Request #21070 · home-assistant/core · GitHub

markbajaj · March 6, 2019, 11:45am

i tried that first and it didn’t seem to work. The error in the log was:

Unable to find platform hue. Search path was limited to path of component: homeassistant.components

However, a couple of reboots and my bodge has stopped working too. Files are still in the components section.

markbajaj · March 6, 2019, 5:06pm

Actually just looked at the GitHub issues, and this has been addressed by @Mariusthvdb here:

Just did what is suggested - rename custom component folder to hue_custom and also in configuration.yaml (or sensors.yaml etc if used) to hue_custom: and it all works fine

gr4z · March 7, 2019, 8:49am

Mmm I tried this but it still doesn’t work. I am on 88.2. None of my sensors now appear

I renamed the hue folder hue_custom in custom components and changed the references in configuration.yaml from hue to hue_custom.

markbajaj · March 7, 2019, 9:17am

My ‘production’ HA is on 88.2 and it works and my development HA is on 89b3 and it works too?

Below is the file structure:

And my sensors.yaml (note this version is an older version of the CC that didn’t split into binary & sensor - though the dev one is the newer version and it works fine)

# Sensors.yaml
#Hue custom componenent motion sensors 
  - platform: hue_custom

Hope this helps.

gr4z · March 7, 2019, 9:23am

Thanks! Very odd this was my setup. I did a restore to a previous snapshot from 2 days ago and it now works. I haven’t changed anything in the last 2 days at all so no idea what was wrong.

Anyway working now.

Phoenix · March 7, 2019, 3:17pm

Hey i have updated in 0.89.0 i have done all the changes and the error before are gone.

But i can‘t see any Sensor in my home Assistant.

Has anyone some good advices please.

Thx