Hue motion sensors + remotes: custom component

robmarkcole · January 26, 2018, 8:53am

Can you check what is being returned by the Hue API? Perhaps with many sensors the data is returned in separate calls or something. The custom component just iterates over every sensor it finds to no limit there

sevenofnine · January 26, 2018, 8:54am

How can I check that? I am connected to the api now but what should I test?

robmarkcole · January 26, 2018, 9:18am

There’s instructions in this thread. Il also add them on GitHub when I get a chance.
Cheers

commandcontrolit · January 26, 2018, 2:01pm

Thank you! By way of another thread I got this sorted. It was how I was formatting it.

Thank you.

quackpack · January 26, 2018, 10:37pm

@robmarkcole, you mention that a 4 button remote can have 2 states. Short press and long press. But when using the Hue TAP I can only get short press working? Is the 4 button remote you mention not the Philips Tap remote?

robmarkcole · January 26, 2018, 11:00pm

Tap and remote are different I’m afraid

sevenofnine · January 28, 2018, 7:58pm

Hi, I have now checked the hue api and the motion sensor not showing up in ha is showing under api/sensors.

Here is the complete responce from the api showing all 8 motion sensors. https://pastebin.com/nRTJDRUM

The strange thing is that it is sensor number 6 that is not showing up.

robmarkcole · January 29, 2018, 7:07am

Hi all, I’ve added instructions on reporting and debugging issues here. Please let me know if these instructions require any clarification.
Cheers

robmarkcole · January 29, 2018, 7:10am

Please see here. Please clarify the device id not showing up, and comment if anything looks strange about its data.
Cheers

sevenofnine · January 29, 2018, 7:17am

Hmm the sensor not showing up is named hobbyrummet sensor. Its not showing in your link? But it is showing in my pastebin.

Hmm I was blind. I found it. will look for anything strange and report back.

robmarkcole · January 29, 2018, 7:22am

Lets continue this thread on Github

Andrew_Lozoya · January 31, 2018, 7:28pm

@robmarkcole Does this custom component work with out a physical Hue Hub?

robmarkcole · January 31, 2018, 8:07pm

Sorry but extremely confident Hub is required

Andrew_Lozoya · January 31, 2018, 8:26pm

figured… i am trying to not get into z wave tech but am looking for a proper motion sensor

robmarkcole · January 31, 2018, 8:32pm

The hue system is incredibly simple to use and the API is very good, only downside is slightly high price. The Ikea Tradfi may be worth a look.

Mariusthvdb · February 1, 2018, 2:46pm

reread the entire thread, but has anyone ever found the solution to this log-spamming?

not sure if it is custom_component related, but since you are the Hue experts, id dare to repost this question:

cheers,
Marius

robmarkcole · February 1, 2018, 3:15pm

Those warnings aren’t generated by the component, but by HA. Any suggestions on how to fix appreciated.
Cheers

Mariusthvdb · February 1, 2018, 3:50pm

ok thanks, just a polite nudge here, maybe others have solved it.

btw, those errors aren’t generated by the component, but maybe the component causes them? Just trying to find a way to solve this.

Cheers,
Marius

robmarkcole · February 1, 2018, 4:03pm

You can change your log level to not see them.
I believe these warnings are due to the phue dependency. Solving these issues can be a lot of work so always grateful for collaborators

anderstbl · February 1, 2018, 4:06pm

I got rid of the warning by changing the update interval from 0.1 to 0.5 in the component code, although it still appears occasionally