Recognizing I'm home using Wifi connection

[PhanTomiZ]

I would like for the ISY to recognize that my son is home by verifying if his phone is connected to the house's WiFi.  Is this possible?

 

Here is the problem...

 

I have a TStat in his room activated by a MS.  Every time there is motion, the TStat goes up to 70 and after 1 hour it goes down to 60.  This works great night and day.  The MS is close enough to catch him turn in his bed while sleeping.  When he's gone, which is most of the time, the TStat is set to 60.

 

Here is the problem.  When someone walks by his room if the door is open or if the wife drops off some clean clothes on his bed, the MS gets triggered and the TStat ups the temp for no reason.  I like the idea of the Wifi connection because that is really the only time I want heat in his room.

 

Thanks

 

[Xathros]

Many of us use WiFi proximity in ways like this.

 

This long thread describes how I and some others do it: http://forum.universal-devices.com/topic/9172-howto-proximity-notification-wifi-phone-ipad-laptop/?hl=%2Bwifi+%2Bproximity

 

Enjoy!  It's a long read.

 

-Xathros

[oberkc]

What kind of phone? Does he use mobilinc or, if not, are you willing to add it?

 

I have not tried xathros suggested method, but it looks pretty interesting. I may have to try it. Until then, I use a method based upon mobilinc and tasker apps on an android phone. Ios has geolocation, but not sure if connection to wifi is a possible condition.

[PhanTomiZ]

He has Android phone.  I will give Xathros' link a read...

[oberkc]

Yes, give it a shot.  Let me know how difficult you find it.

 

My problem is that I want to base arrival to home and departure from home based on two conditions, one of which is the wifi connection.  Tasker handles this well.  I am not sure that the other solution does.  Besides, I already had tasker and mobilinc.  My experience, also, is that (like plumbing) projects with routers are always more complicated than they should be, fraught with unintended and painful consequences.

[smokegrub]

Would this be a good fit for a door sensor? A program which first noted the door open, then closed then followed by MS a couple of minutes later.

[Xathros]

Would this be a good fit for a door sensor? A program which first noted the door open, then closed then followed by MS a couple of minutes later.

Don't think that solution works here unfortunately.

 

 

 

-Xathros

 

Sent from my iPhone using Tapatalk

[smokegrub]

Don't think that solution works here unfortunately.

 

 

 

-Xathros

 

Sent from my iPhone using Tapatalk

I am curious why. The wife can come in and drop things off and close the door with no problem. The son can come home, open and close the door and, if stays, and moves about the desired action will take place.

[Xathros]

Actually, now you've got me thinking about this, maybe all the OP needs is to insert a short delay between motion detection and ISY action preventing the need for proximity detection.

 

 

-Xathros

 

Sent from my iPhone using Tapatalk

[smokegrub]

Xathros: I see that as a potential option as well.

[PhanTomiZ]

Yes, give it a shot.  Let me know how difficult you find it.

 

My problem is that I want to base arrival to home and departure from home based on two conditions, one of which is the wifi connection.  Tasker handles this well.  I am not sure that the other solution does.  Besides, I already had tasker and mobilinc.  My experience, also, is that (like plumbing) projects with routers are always more complicated than they should be, fraught with unintended and painful consequences.

 

I'm using a 2wire DSL/Router that is rented from my provider.  I also have two wireless routers sitting on my computer desk shelf, one of which has DD-WRT installed.  About a year or so ago, I wanted to use this as a remote client-bridge for my wired media player in order to rid myself of the wired portion.  I didn't have the time to play with it, so I instead ran a dedicated CAT 5 cable to my media player.  Its is a D-Link Dir-615.  I'm certain the router is still functional.  

 

To be honest, I'm slightly intimidated about trying to get this setup as I had very little luck setting it up as a client-bridge.  I think the real problem is that I didn't have the time (how can you have the time if you don't make the time???) to figure it out even with the help of multiple Youtube videos and How To links.  So I see this project as a time consuming one and will probably get put on the back burner for a while, even if the interest is very very very strong.

 

When I do get time, I will dust it off and wire it up to the router and try re configuring it as a router again...I just thought that their may be an easier, less time consuming way of doing this. 

[PhanTomiZ]

Would this be a good fit for a door sensor? A program which first noted the door open, then closed then followed by MS a couple of minutes later.

 

This would work great for two people, but I really don't want that heater on unless the son is in that room...

[Xathros]

This would work great for two people, but I really don't want that heater on unless the son is in that room...

In that case, you don't want the WiFi proximity solution either as that will tell you when his phone/device is on your network, not when he is in that room specifically.  I think using your motion detector with a smart delays makes more sense.

 

I do something very similar-ish in my basement laundry area which also leads to my basement exit.  I want the light to come on when motion is detected in the area but turn off in 30 secs if no additional motion.  This way if I just walk in the door to head upstairs, the light will shut off after 30 secs.  If i'm working at the laundry in the evening, I can be still enough to be in the dark after the initial 30 seconds.  If there is enough initial motion detected, it bumps the timeout up to 5 min with a reset the counter with continued motion.  Very hard to stay in that location and not trigger motion at least once every 5 mins.

 

In the below example, you will have to trigger motion in the boy's room 8 times within a 2 minute period for the stat to turn up.  Once that happens it will stay up as long as there continues to be motion at least once in a 20 minute period.  Thermostat will set back again 20 min after last motion detected.  This way, as long as you don't have more than 7 random triggers in a 2 min period, the stat won't turn up.  This example assumes that the motion sensor is using sensing mode.

Define a state variable: s.BoyRmMotionCnt.  Init value: -1

Program: BoyRmCntMotion
If 
   Control 'BoyRmMS_Sensor' is Switched On
   And $s.BoyRmMotionCnt < 8 (Will need to experiment for this value.  Depends on MS sensing more and timeout config)

Then
   $s.BoyRmMotionCnt += 1
   Wait 2 minutes
   $s.BoyRmMotionCnt = 0


Ese


Program: BoyRmTurnUpHeat

If
   $s.BoyRmMotionCnt >=8  (Will need to experiment for this value.  Depends on MS sensing more and timeout config)

Then
   Set 'BoyRmTS_Heat Setpoint' to 70
   s.BoyRmMotionCnt = 29 (This will be the number of minutes the heat will stay on without additional motion detected plus the Off count value in the last program.  20 min in this example.)
   
Else


Program: BoyRmHeatRun

If 
   $s.BoyRmMotionCnt > 9  (This value should be one greater than the minimum motion count used in the above 2 programs.)

Then
   Wait 1 Minute
   $s.BoyRmMotionCnt -= 1

Else
   $s.BoyRmMotionCnt = 0
   Set 'BoyRmTS_Heat_Setpoint' to 60


NOTE:  You should place the following line in the then section of a program that runs at ISY startup. This will ensure that the heat does not stay turned up if the ISY were to restart during a heat run.

$s.BoyRmMotionCnt = 0 

This will change the value from the init value of -1 and force the last program to set back the heat.
   

I hope this proves useful.

 

-Xathros

[PhanTomiZ]

In that case, you don't want the WiFi proximity solution either as that will tell you when his phone/device is on your network, not when he is in that room specifically.  I think using your motion detector with a smart delays makes more sense.

 

I do something very similar-ish in my basement laundry area which also leads to my basement exit.  I want the light to come on when motion is detected in the area but turn off in 30 secs if no additional motion.  This way if I just walk in the door to head upstairs, the light will shut off after 30 secs.  If i'm working at the laundry in the evening, I can be still enough to be in the dark after the initial 30 seconds.  If there is enough initial motion detected, it bumps the timeout up to 5 min with a reset the counter with continued motion.  Very hard to stay in that location and not trigger motion at least once every 5 mins.

 

In the below example, you will have to trigger motion in the boy's room 8 times within a 2 minute period for the stat to turn up.  Once that happens it will stay up as long as there continues to be motion at least once in a 20 minute period.  Thermostat will set back again 20 min after last motion detected.  This way, as long as you don't have more than 7 random triggers in a 2 min period, the stat won't turn up.  This example assumes that the motion sensor is using sensing mode.

Define a state variable: s.BoyRmMotionCnt.  Init value: -1

Program: BoyRmCntMotion
If 
   Control 'BoyRmMS_Sensor' is Switched On
   And $s.BoyRmMotionCnt < 8 (Will need to experiment for this value.  Depends on MS sensing more and timeout config)

Then
   $s.BoyRmMotionCnt += 1
   Wait 2 minutes
   $s.BoyRmMotionCnt = 0


Ese


Program: BoyRmTurnUpHeat

If
   $s.BoyRmMotionCnt >=8  (Will need to experiment for this value.  Depends on MS sensing more and timeout config)

Then
   Set 'BoyRmTS_Heat Setpoint' to 70
   s.BoyRmMotionCnt = 29 (This will be the number of minutes the heat will stay on without additional motion detected plus the Off count value in the last program.  20 min in this example.)
   
Else


Program: BoyRmHeatRun

If 
   $s.BoyRmMotionCnt > 9  (This value should be one greater than the minimum motion count used in the above 2 programs.)

Then
   Wait 1 Minute
   $s.BoyRmMotionCnt -= 1

Else
   $s.BoyRmMotionCnt = 0
   Set 'BoyRmTS_Heat_Setpoint' to 60


NOTE:  You should place the following line in the then section of a program that runs at ISY startup. This will ensure that the heat does not stay turned up if the ISY were to restart during a heat run.

$s.BoyRmMotionCnt = 0 

This will change the value from the init value of -1 and force the last program to set back the heat.
   

I hope this proves useful.

 

-Xathros

 

Your explanation proves very useful.  The program will take a little while to decipher, but nonetheless much easier and faster than the other options.  I don't mind doing the homework, but this solution will take me there for the time being.  When I have time, I will try the other options.

 

Many thanks to you for this solution...

 

I will let you know when I've entered the program and is fully functional...

 

PhanTomiZ