hmm, this seems odd. Has anyone updated to 0.94 without this issue? I wonder why some of us see the error or warning before updating, and the rest of the community doesnt raise the issue… And in the latter case, what was done to mitigate the issue. really like to update too…
1 Like
Just confirming that I also get an error since 0.94:
Configuration invalid
Platform not found: device_tracker.huesensor
Wow - to this topic with the bad reaction time on the motion sensor i changed the sensor from hue V2 network to my zigbee2mqtt (CC2531) network because of this post by @Burningstone
and hey the reaction is nearby originally hue <<< 2sec
BUT
now i’m not able to detect NO MOTION reliable 
after minutes with no motion my hue sensor is on
#superbad
Any ideas someone???!?
I’m using Deconz and I have no issue with Hue Motion and the detection is fast. Now, related to your issue, maybe you have a zigbee network issue (e.g. interference with WiFi, meshing and range issue…), or the sensor delay setting is wrong. I’m not sure how you can verify it with zigbee2mqtt though.
hmmmm… i guess not, my z2m network is about 38 devices and really reliable.
Also two xiaomi body sensors are going well its all about this hue motion thing
but thanks for the hint at the moment i’m thinking about updating cc2531 firmware but this is a courageous project 
For what it’s worth: The custom component was at least 2-3 seconds faster at detecting motion than the native component. I’ll be sticking with the custom component until the issue is resolved. FYI: I am on the v2 hue bridge. I am not blaming anyone for the issue but the response time for the native component is slow enough to be nearly useless for me.
Note: I only compared the response times once. Since the issue is sample frequency related I should have tested multiple times to get a good estimate of the actual difference because the result I got depends upon where in the sampling interval I happened to trigger the motion.
.
How do I change the components?! 
I’m on .94 and I’ve not seen any errors that’s been reported recently
that good to hear. Could you please share your settings, so we can confirm all is fine?
thanks!
I use Deconz. I used a hue motion in the past but switched to Aeotec Multisensor because of the temp and humidity sensor, but the hue motion sensors worked perfectly fine for me.
Maybe it’s the best if you post your question in the ZigBee2MQTT thread
1 Like
I confirm that the patch works on home-assistant 0.94.3
Thanks for fixing it!
What does the device_tracker part of this do? I’m still getting an error from this, so wondering if I can just remove that part.
I have Hue lights, dimmers & motion sensors. Would removing the device_tracker line from my config stop anything working??
you guys should seriously consider getting a conbee: https://phoscon.de/en/conbee
I have now got rid of all my 3rd party hubs, and now have clear skies (no cloud) setup is a sinch and no flaky work arounds…
Not to say that I don’t love and admire @robmarkcole work, but with the constant change to the Home Assistant environment, it is good to have something that just works and is not reliant on a big companies cloud API which they may or may not continue to support…
2 Likes
You are right in Many ways, but I don‘t want to miss some features my Hue Bridge has!
First is Hue Entertainment! I Love it and I also use it 
Second is to control my lights with Alexa, for free! My wife and son love this Feature!
Third, my hue Dimmer has less features with deconz than with my Hue hub!
For my sensors or rooms where I don’t Need this Features I use deconz as well.
Just ordered one!
yes, but essentially, the hue hub and software thereon is largely under the control of Philips, they can change or whatever they want to this platform as it is an extension of their cloud.
If for example, they found a security issue, they would then force an update to the hub which could potentially break the api access (I had this happen to me about 3 times, to the point where philips just started reponding to my tickets by sending me a new hub…I have actually become quite friendly with some senior technicians at hue now through this. I have about 4 of them (hubs not engineers now lying around at home. ) I also had an incident whereby the hub would keep renaming and mixing up the names of my bulbs, causing endless headaches downstream (I have about 30 bulbs)
So whilst I know that there are loads of features (like the entertainment and switch functions) built into the hub, for me, it is much better talking to the zigbee network directly as opposed to via the hub, but each to the own… I thought I would simply share my humble opinion… 
Like I said, I used the custom component from @robmarkcole and it worked brilliantly, my house just started getting very busy when I started to add the xiaomi kit, and reliability started failing to my bulbs… all my bulbs now work much better since I use conbee with xiaomi and hue and all other zigbee on the same network…
Interesting, I’ve had the exact opposite experience. I have 36 lights, a motion sensor, and 6 FOH switches on my Hue bridge and it has been absolutely rock solid. In 4 years I’ve never once had an issue controlling lights or anything of that nature.
I also have 5 sets of Lightify Gardenspots which were absolute crap when connected to the Lightify hub. I have 7 Keen Home vents which were absolute crap when connected to the Keen Home hub. I’ve since connected those 12 devices directly to Home Assistant with an Xbee and they’re much better, but still nowhere near as reliable as my Hue system. Heck, Home Assistant in general isn’t as stable, and I’m running it on an enterprise server with dual 16-core CPUs, 52GB of RAM, dual PSUs, etc.
As this point I’ve basically decided that I’m replacing all non-Hue Zigbee devices with Hue products or Z-Wave.