GoControl Motion/Temperature Sensor

Configuration
1

I’ve been using HA for 6 months or so now. Maybe longer. It’s been working great with my limited number of devices and whatnot. One device I’ve had since day 1 has been the GoControl Motion Sensor that came as a part of a kit from Wink. It has always worked ok as a motion sensor. A little slow to react but still worked without issues. I think it was supposed to also do temperature but it never seemed to do that.

Until today. Today I was messing around with HA, trying to get my views and groups set up how I liked them when I noticed my motion sensor was no longer there. I went to check the “States” page and see what sensors it saw thinking it had maybe changed names from binary_sensor.living_room_motion.

Turns out I was right, but not in the way I thought I would be. The sensor is now reporting as sensor.living_room_motion_temperature all of a sudden. I verified within the Wink app and it is now reporting temperature and motion to Wink.

My first reaction was happy, since I now had another temperature sensor I could use. But then I realized it didn’t split the sensor into the 2 different ones. My motion sensor is now completely gone, replaced with only the temperature sensor.

Now I don’t think that this is caused by something I did. But I’ve been very wrong before. I haven’t done any manual firmware/software updates on my Wink hub and I’m unsure if there are ever updates on the devices in the background but I suppose that could have happened as well.

Has anyone had this happen to them? Is this an ID10T error? Is there something I can do to see both motion and temp? I’ll be glad to share my config, logs, or anything else.

Thanks for any help.

2

I just saw something in a Google Wink community that Go Control Temperature readings were now showing up following some update. https://plus.google.com/+JasonReuter/posts/FJP9uLEeAF1

3

Still waiting for confirmation (https://github.com/home-assistant/home-assistant/issues/3381), but I think it is a bug.

Issue has been logged, so check back there.

4

Confirming the same here and added my confirmation to your issue report on Github.

Honestly didn’t even know they had temp sensors in them! I was just using the motion detection.

5

Well this may sound odd, but I’m glad to see that it may be a bug. That means I might not be an idiot after all!

I’ll keep an eye on that issue tracker.

Thanks folks.

6

Same here. Possible to get both sensors in HA? Right now I only have temp. In Wink I both.

7

JWL posted the link to an issue tracker on the subject that they opened. Best bet would be to follow along there.

1 Like
8

@w1ll1am23 confirmed there was a change in the API that caused this. Sounds like he is working on it.

2 Likes
9

Maybe this is a sign that they are fleshing out more of the ZWave attributes the hub sees; that would be good news for things like Schlage locks!

10

PR for the python-wink changes has been open. https://github.com/python-wink/python-wink/pull/52

Once this gets pulled in, I will have to make a change in Home-Assistant as well to get this working. The sensors will change a bit, will end up with a sensor.whatever_temperature and a binary_sensor.whatever_motion

3 Likes
11

Has this been pulled in to HA? Any way I can help? I see the PR on the python-wink side was merged.

12

As far as I know it has not been pulled into the production version of HA yet. If you have a dev instance set up I’m sure they wouldn’t hate having someone else test it.

13

This is officially pulled into HA. Updated this morning and I now have both motion and temperature sensors.

Nice work everyone!