tldr: the device has a sleep mode, which will inevitably enter after 10-15 seconds of inactivity, where it delays any wireless requests to arm/disarm INDEFINITELY until you open/close the door (see why below). All wireless communication notifications to and from your...See more
tldr: the device has a sleep mode, which will inevitably enter after 10-15 seconds of inactivity, where it delays any wireless requests to arm/disarm INDEFINITELY until you open/close the door (see why below). All wireless communication notifications to and from your product and phone will delayed by 5-6 seconds after the door is opened. However, during active mode, all wireless communication is instant, as well as the request to arm/disarm. The problem? You can''t control when it''s active or sleeping. So without going into too much technical detail, the product is good in the sense that it does what it advertises, but it''s potential for greatness is limited by its hardware -- I''ll explain what I mean. The device has two components: a magnet, and a sensor. When the magnet is connected to the sensor by very close proximity (less than ~10.0mm apart), the device will enter a power-saving mode, called "sleep" on the mobile application. Technically, the device is still on, but just on standby mode. If you push a button/number/lock or disconnect the sensors by opening the door/window, it''ll wake itself back up, because it''s not completely off. Similarly, if you poke your sleeping friend hard enough, they''ll wake up, because sleeping doesn''t mean they''re dead -- just inactive. With this in mind, when the user tries to log any INPUT activity by wireless connection, as in Arm or Disarm the alarm during the device''s sleep mode (i.e. when the door/window is shut; the sensor and magnets are super close), nothing will happen. Why? Every time you click on "Arm" or "Disarm" on the mobile app, you are sending a request to the Braumm''s server, and then their server to your device that has an onboard wifi connection. The request will be considered "pending" because the device is still sleeping (i.e. the door/window is still shut). Here''s how it looks like pictorially: You ---> *click* ---> Phone ---> Braumm Server ---> Request to Arm/Disarm ---> Wifi Door Sensor (SLEEPING: Please leave a voicemail..) Because your device is sleeping, it will not answer any requests until you wake it up, much like our previous analogy about poking your friend hard enough to wake them up. Instead of poking, you would open the door/window to REACTIVATE the sensors via the disconnection of magnet and sensor. Now that the device is awake, it will receive the signal to arm or disarm. Here''s how it will look like when it''s awoken: You ---> *click* ---> Phone ---> Braumm Server ---> Request to Arm/Disarm ---> Wifi Door Sensor (ACTIVE: Oh my lord, I slept through all these requests!! OK, I''ll arm/disarm myself right away!) So what does this mean in the end? It means that there is a delay in input and output signals. From the input signal, if you arm the device via the mobile app WHILE IT IS IN SLEEP MODE, you have to wait until someone opens the door to disconnect the sensor and the magnet to wake up the device. Once the device wakes up, the "ARM THE ALARM!!" request will finally go through, and the alarm will sound. ...However, there is a time lag of 5 seconds before this happens, as opposed to arming the device when it is already awake, and having an immediate trigger response; this explains how the output signals get delayed. As a fun experiment, listen closely to your device in a quiet environment when you connect and disconnect the magnet from the sensor. You''ll notice that every time you do so, you can HEAR the sensor in the device starting to "wake up" the device by running its components on and off -- this is the time period where your input signals from the mobile app are live and active...and the only time it will ever be. Let''s recap with a few case scenarios to understand how the product behaves: 1) Sally disarms the device and closes the door; she expects no alarm noise to activate. After 15 seconds, the device shows "sleeping" on her mobile phone. Her brother opens her door, then the notifications appear on her phone, but only after 5 seconds -- no alarm noise was sounded. 1.1) ...After 15 seconds, the device shows "sleeping" on her mobile phone. She arms the device through her mobile phone (instead of pressing physically on the device). Her brother opens her door, then the notifications AND alarm noise appear, but only after 5 seconds. 1.2) Sally disarms the device and closes the door, but this time, she arms the device right away on her mobile application while the phone was still "ACTIVE" as displayed on the app. After 15 seconds, the device enters sleep mode. Her brother opens the door, and the alarm is immediately triggered, but the notifications appear 5 seconds after. 1.3) Sally disarms the device and closes the door, but this time, she arms the device right away. Her brother opens the room immediately after she closes the door (less than 15 seconds when she armed the device). The device immediately triggers the alarm noise, and the notifications immediately appear on her phone -- all because her device was still "ACTIVE" and not asleep. In conclusion, your input and output signals to and from your phone/device will be delayed by 5 seconds when the device inevitably enters sleep mode. Yet, it still does what it does, which is sending push notifications, and sounding alarms -- just not immediately.