Cookies attach to a mother device after being "installed" on the SEN.SE website.
There are 3 sensors in each cookie:
1. Batterie charge level in mV, updated send by mother to SEN.SE every 15 minutes
2. Temperature (value is in Fahrenheit!!), updates send by Mother to SEN.SE every 15 minutes
3. Motion detection with 3 properties, # of moves, intensity and how many seconds activity took updated send by mother to SEN.SE every 10 seconds .. 15 minutes depending on Motion-mode
The "Present/Absent" state is derived from being in Mothers reach or not.
Each time Mother sends info about the states of the cookie sensors to the SEN.SE website it also sends the Signal strength in db/m of the Cookie-Mother communication. (larger negative numbers are lower signal, below -94 connection is lost)
With the help of "Wire Shark" and a Shark Trap Network sniffer hub http://www.amazon.com/gp/product/B00DY7 ... UTF8&psc=1
I did some low level analysts on timing and data formats:
1. structure of data send from Mother to SEN.SE is a http PUT
{"resource" : "events", "method" : "post", "body" : [{"node" : “8d HEX", "timestamp" : "2015-04-25 20:44:43", "feed_type" : "3", "signal" : "-41", "value" : "176,300,95"}]}
(date is in UTC)
2. at startup after UID exchanges ... several basic communications are send like:
{"body": {"stateFrequency": 180, "smileLed": "255,0,0", "serverUrl": "in.sen.se", "rightLed": "200,200,0", "leftLed": "200,200,0", "serverPort": 80, "soundLevel": 50}, "type": "gateway", "resource": "state", "method": "post", "auth": “16 digit hex”} Info of state of Mother etc.
3. once in a while packages like these
{"resource" : "events", "method" : "post", "body" : [{"node" : “8d HEX", "timestamp" : "2015-04-25 20:44:43", "feed_type" : "3", "signal" : "-41", "value" : "176,300,95"}]}
{"resource" : "events", "method" : "post", "body" : [{"timestamp" : "2015-04-25 19:46:42", "feed_type" : "1", "value" : "1"}]}
{"resource" : "events", "method" : "post", "body" : [{"timestamp" : "2015-04-25 19:52:42", "feed_type" : "99", "value" : "Nb Cookie : 5"}]} <== looks like how many cookies near by
are send. They are not linked to specific cookies..
Timings:
general cookie data packages:
Code: Select all
"feed_type" "value" updated every
1 = alive package 0/1/2 58 seconds values: 0=Absent; 1=Present not linked; 2=Present
2 = battery 4 digits 4 digit #=3123mV 15 minutes
3 = motion 1,2,3 3 number a,b,c 15 minutes for "Walk-mode". --10 seconds for "Door-mode" if movement detected
4 = only for type “door” 4 digit # don't know what this is, the data is not available on SEN.SE
5 = temp 4 digits 9101=91.01F 15 minutes To answer the question, how fast does Mother recognize a cookie coming home:
MM:SS action
15:13 put cookie into aluminum foil = out of reach
18:09 value =0 @ 3 minutes until state goes from "Present" to = "Absent" Value =1
18:48 unwrap cookie
18:57 send value =1 @9 seconds until state goes from "Absent" to "Present not Linked", looks like just connected , weak signal..
18:59 send value =2 @11 seconds until state= "Present"
Similar after removing the battery and waiting until "Absent" status reached, it takes about 20+ seconds to send the "Present" status (value=1 or 2). The cookies not to boot up before they talk to Mother
So it looks as if it should be possible to connect directly to a mother device in your home and not depend on the SEN.SE web server outside to get the data.
BUT I would need to help how to do that. .. beyond my capabilties right now, But I would like to change that.
Any advice fro the "top" experts?
Karl
ps Simon in Switzerland did some cool application of a cookie determining when at sleep..
it's just a trigger to set my variable "Night" true|false. (I use this variable to dim the lights during the night, set a shorter time to turnOff the lights after no movement was detected, hold the roller blinds closed ...)
