No Longer Works With Hassio Version 0.66.0 about hue-sensors-hass

[JuliusLedoux]

Mine is working on version 0.66.1. I made sure to remove the previous version installed on my custom_componenets folder and also modified the hue.py file to have my key (provided by hue) on the line:
URL = "http://192.168.1.111/api/xxxxxxxxxxxxxxxxxKeyxxxxxxxxxxxx/sensors"
Hope this helps!

[ben2011laptops]

It says that this information is in the previous HUE file. Where is this obtained from?

[Mariusthvdb]

finally having all goodies from this CC working, I am a bit reluctant to upgrade Hassio because of this breaking change:

Due to the internal changes of how the Hue integration works, any Hue custom component will no longer work

Is this really so? If yes, can we do anything about that? Other than not upgrade ;-))

see https://www.home-assistant.io/blog/2018/03/30/release-66/#release-0661---april-1 under breaking changes.

[raoulteeuwen]

@ben2011laptops in the HA configuration folder, so where also you configuration.yaml etc resides.

[raoulteeuwen]

@hvbhome : not change anything as long as you think is o.k. is the best way not to break anything. But than again, that probably only postpones problems, as you might encounter extra problems when you want to go from version x to version x+5. @robmarkcole has already updated his code so it works with 0.66 (thank you!). Just check the update readme of his code, which states what you need to do (read carefully ;-)).

[Mariusthvdb]

yes, really appreciate @robmarkcole s work! I have already upgrade the hue.py in custom_components to see what gives, a lo and behold, it really works fine, even got my Geofence phone to showup ;-)

So, i don't need the upgrade for Hue. Do need it for other issues, but i fear it would break this, given @balloob's remarks I quoted above.

So, I would really appreciate some feedback from someone having upgraded to Hassio 66.1 and using hue.py CC with good results...

Cheers,
Marius

[raoulteeuwen]

I'm running 0.66.0 with @robmarkcole s updated work without a problem...

[jongdesteven]

I had some issues too, after "upgrading".
found out i had
platform: hue_sensor
in my configuration

[Mariusthvdb]

thanks @raoulteeuwen and what about the hue.py in the /config/custom_components folder? Did you take that out?

had that a long time ago too @jongdesteven , and talked to @robmarkcole about that, it isnt necessary any longer, at least it wasn't with the previous versions of hue.py. It was there for legacy's purposes, maybe best to take it out of the documentation altogether now..

thanks for feedback!

[thundergreen]

Short feedback as this becomes very unclear here ..u made a mistake in description.. hue.py must be in:

/hassconfigfolder/custom_components/sensor/hue.py

[Mariusthvdb]

nope, i didnt make a mistake.

there's admittedly been a lot of confusion about this: 2 (!) files being necessary with the same name. before it was Hue_sensor and _sensors, later it became twice hue.py.

the CC file by the author here had to go in /config/custom_components/sensor, the other file which was apparently needed for Hassio's support for Hue in the first place had to go in /config/custom_component.

hence my question whether this is still needed now Hassio has built-in support....

[thundergreen]

OK..can't say for hassio but venv install needs mentioned path . thanks for clearing this

[robmarkcole]

I believe this issue is stale so closing