What can you use the dumbest wifi motion sensor for? NEO Coolcam (includes Tasker instructions in Post 10)

Hello,

I have been trying for quite some time to figure out how best to use this NEO Coolcam wifi Motion Sensor model number NAS-PD01W but I haven’t had any success whatsoever.

This sensor can’t connect to Smartthings(which I’m not surprised) but what surprised me was that you can’t even connect it to Alexa, which is weird because it uses Smart Life or Tuya app and almost every device that uses those app are compatible with Alexa.

So what I’m asking here is, IS THERE ANY WAY TO CONNECT THIS DEVICE TO SMARTTHINGS OR ALEXA? some virtual motion sensor device handler that mirror the behavior of this device? Any suggestions are very welcomed

Thank you

As you noted, it doesn’t natively integrate with anything. That leaves you with two options.

  1. It does send push notifications. :calling: So if you have an android phone, you might be able to capture those notifications with a combination of Tasker and sharptools. I know people have done that with some other push notification apps. @joshua_lyon might be able to say more. If you have an iPhone, though, you’re out of luck on this one.

  2. Depending on the exact model, it can create three different changes in the physical environment: a bright red LED, a vibration, or tone. :rotating_light: You might be able to pick this up with a different sensor.

However, in this case I can’t see any reason for doing that since you likely could just use another sensor to begin with.

But I suppose it’s possible that one of the third-party sensors could be placed in such a location that it could pick up physical alerts from a whole room full of the Coolcam sensors. It would require a lot of trial and error testing, though.

So I list this as a possibility just because I think the physics would work, but in terms of practical home automation I don’t think very many people would choose this option.

Meanwhile, just curious: what kind of battery life do you get from it?

1 Like

I really like that first option that you suggested. Thank you! I have an Iphone but I have an android tablet that I use as a control board for my smart house so that will be perfect for this project.

As for battery life, I bought it in September last year and now its at 85%.

One more question off the topic here. I have connected some smart plugs to Global Suite but I dont know how to be able to see them in ST? Any directions would be greatly appreciated.

I’d honestly go with their zwave plus version of this device and eliminate any latency brought on my man-in-the-middle ways of doing it. It may be a bit more expensive, but you will have a lot less issues and you won’t wonder why motion events take longer than you’d like to show up in SmartThings.

1 Like

I can confirm that zwave version is working fine with ST. I have couple of them.

2 Likes

Yes I’m familiar with their Zwave plus version. As a matter of facts I have a Contact Sensor that is also NEO Coolcam product but this one uses Zwave plus protocol and not wifi like this motion sensor.
I just want to make some use from this motion sensor since I already have it. I don’t want it to go to waist.

Thank you for you reply!

1 Like

Yup, make sense. It drives me crazy having unused devices sitting around doing nothing.

2 Likes

In the initial beta version of the global suite integration, it did recognize devices of other brands. But now that it is out officially, it can only be used with devices of the actual Global Suite brand. So if it’s a different brand, you’re out of luck. :disappointed_relieved:

2 Likes

Oh man that sucks. Thank you for the helpful reply!

2 Likes

@Spaka reached out via PM, but I wanted to post the discussion here publicly in case it helps anyone else who finds this thread.

As @JDRoberts alluded to, you can use Tasker to capture notifications on Android and can use the SharpTools Tasker plugins to integrate with SmartThings.

Tasker is developed by a different developer, João Dias, and is really is a powerful tool that allows you to build custom automations. Each persons automations might be slightly different, but I can provide some high-level pointers to get you going in the right direction. If you have any specific questions about the SharpTools side of things, I’d be happy to answer those.

For Tasker specific questions, the /r/tasker subreddit is a very helpful community.

:warning: One thing I would note is that Tasker is definitely more of a Tinkerer’s paradise and will likely require reading the documentation.

Summary

Tasker breaks things down into two components:

  • Profile - which includes the events or states that trigger Tasker to start doing something
  • Task - the actions that occur when a profile is triggered

Profile

Tasker has the ability to react to received notifications using the Event > UI > Notification feature. You can use the filters in the event configuration screen to filter down to just the notifications you want:

Many people prefer to use one of the many third-party Tasker plugins which have more features and control for capturing notifications though. The two most popular are probably AutoNotification and Notification Listener. Each of these plugins provide deeper control over capturing notifications and getting details from these notifications in the form of Variables. For example, you could capture the title or message as a variable and then use that later in your action.

Task

Once you capture your notification, you’ll have to decide what you want to do with it. This is done in the Task that you’ll create for the profile. Tasks can have any number of actions and logic within them.

In your case, you’ll likely want to create a Simulated Motion Sensor within the SmartThings IDE:

Then you can use the Plugin > SharpTools > A Thing action to control that simulated motion sensor sending the relevant active() or inactive() command based on the notification that you receive from your app:

3 Likes

Perfect! I tried it and it took me some time to figure out the notification part but after couple tries it worked! Good part was that I already had one virtual motion sensor in my ST so the Task part was very easy. I just need to make it on Tasker or WebCore another task/piston to revers the virtual motion sensor to “no motion” after couple seconds so that I can get a motion on my virtual sensor again when something happens. Thank you Joshua!

2 Likes

Thanks for the update - glad to hear you got it working!

There’s a ‘wait’ action in Tasker that you could use. A simple approach would be something like:

  1. Thing: Motion → active()
  2. wait: 3000ms
  3. Thing: Motion → inactive()
2 Likes

Oh that’s good… then I don’t need another task/piston for this project.
Thanks!

1 Like