so the 08-10-2017 hue_sensorS.py needs to be replaced with the newer hue.py ?
i ask because on your github it mentions hue_sensor.py…(no trailing S), which makes it all a bit confusing I am afraid. Sorry.
Hi ,you will see that the component has a dependency REQUIREMENTS = ['hue-sensors==1.2']. This can be manually imported by placing hue_sensors.py from here into the sensors custom component folder.
What you have highlighted is the renaming of the main file in an earlier change.
Cheers
HI Rob,
Thanks,
Just to be precise:
in the latest versionology, we still need both
- the new hue.py https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/hue.py
and
- your hue_sensors.py https://github.com/robmarkcole/Hue-sensors ?
your file has been updated and hue_sensor.py has been updated and renamed to hue.py…
That it?
Hi you shouldn’t need both, only if HA kicks up an error about being unable to install the requirement.
Cheers
If you have updated to the latest version of home assistant (0.61) you need to download (and place within your custom_components folder) the files called custom_components/hue.py and custom_components/sensor/hue.py that can be found here here
The first one is simply an edited version of the hue.py that is supplied with homeassistant 0.61
The second one is what allows the sensors to work
1 Like
funny,
different versions if what to do…
it would be very convenient if the naming of the python scripts wouldn’t be so confusing. It was like that in the hue_sensor(s).py situation, and gets even more so in the 2x hue.py situation we have now…
too bad really, because unique file names are real prerequisites in debugging and correct installing.
As it stands, there are at least 3 different versions of what to do… 
Cheers,
Marius
Hi there @Mariusthvdb , all components follow the convention of keeping the same filename for hub and then for ‘component files’. E.g. blink, check out the HA repo.
If you feel the docs are lacking please submit a PR.
Cheers
Not really different versions of what to do, it’s just that home assistant itself was updated several times recently with breaking changes to the hue component, which in turn meant that this custom component had to be refactored each time, so the instructions have had to keep changing.
I think you got confused with what to download from where - it’s just the files from the one repo that are needed, not the things that you linked to in your earlier thread. Just go to this repo download the custom_components files and follow the instructions for adding to your config
Good luck!
OK I just released a version (v0.3) which removes the requirement for HA to install and import the dependency that has caused so much grief.
Please note I only created this dependency to satisfy the HA code review when I submitted this as a full HA component originally. It was never accepted as they requested the use of phue which caused other problems (performance issues updating multiple sensors as phue makes a request for every individual sensor, whilst my approach polled all sensors in a single request).
HI Mark,
Wonderful! Thanks a bunch.
Please allow me this (feeling insecure…) really not trying to be a pain, it just isn’t very clear to me and id rather like to be sure before changing setup than have to repair afterwards…
on your page there are
/custom_components/hue.py and
/custom_components/sensor/hue.py
we need both? and only these?
no more
/custom_components/sensor/hue_sensor.py and
/custom_components/sensor/hue_sensors.py
thanks for your patience …
Marius
You only need what’s in the repo. Hue_sensors.py has been rolled into the component so no more installing or importing this dependency.
Cheers
cool, is see (finally…)
maybe its the terminology Repo im not familiar with, but that implies the use of both
custom_components/hue.py and
custom_components/sensor/hue.py ?
Cool, I should have added the 
you’re quite good at not answering a very simple question though…
You now only need what’s in the repo.
If that’s not a clear answer then I don’t know what is.
Cheers
no worries, i think it is a typical situation of (mis)communication between a specialist and a newcomer like me.
I believe wat your saying is:
yes,
you need the (updated and renamed) Hue hub component hue.py in the /custom_components folder, and your (updated) hue.py in the custom_components/sensor/ folder.
Cause they’re both in your repo…
Correcto 
2 Likes
Hello - thanks for the package. It’s working, but I can’t seem to get the template portion to display. Here is what my configuration.yaml looks like
Hue-sensors
hue:
bridges:
- host: 10.1.30.162
#Sensors
sensor:
- platform: hue
- platform: template
sensors:
sensor.basement_hallway_garage_motion_sensor_temperature:
friendly_name: ‘Living room temperature’
value_template: ‘{{states.sensor.basement_hallway_garage_motion_sensor.attributes.temperature}}’
unit_of_measurement: °F
But when I perform configuration validation, I get the following message:
Testing configuration at /config
2018-01-22 23:18:51 ERROR (SyncWorker_0) [homeassistant.util.yaml] mapping values are not allowed here
in “/config/configuration.yaml”, line 93, column 14
2018-01-22 23:18:51 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: mapping values are not allowed here
in “/config/configuration.yaml”, line 93, column 14
I added it to groups.yaml this way:
Hue:
entities:
- sensor.basement_hallway_garage_motion_sensor
- sensor.basement_hallway_garage_motion_sensor_temperature
I see the sensor. It shows as off. If I click it, I can see the temperature, last presence, etc. So something is working, But I can’t get temp or other attributes to show anywhere.
Any ideas?
Hi, Is there a limit on how many motion sensors you can get in to hass? I have 8 motion sensors but I can only ever get 7 to show up in hass. Running hass 0.61 and your latest component. I also have 7 dimmer switches all showing up in hass. By deleting motion sensors in hue I can controll wich 7 motion sensors show up in hass beacuse its the last one added to hue thats not showing up. So for example if sensor 1-7 is showing up in hass but not number 8 I can delete sensor 7 and 8 and then add them in the other order in hue and then sensor 8 is showing but not 7 if you understand what I mean.