Faq

Please write an e-mail to us with our concern support@puresec.de

Have a look to the Publisher documentation to find an instruction.

The sensor cannot currently detect and report the standing up movement itself. However, it can detect whether a person enters or leaves the "bed area".

The "bed exit" function was introduced with sensor firmware version 0.40. This detects within 15 to 60 seconds whether a person moves out of bed. To implement this, a region must be defined for the bed and the kind "bed" must be set. An event is generated when entering/leaving. We can evaluate and process this using a corresponding rule.

For reliable monitoring and reporting, the manufacturer recommends installing a sensor on the ceiling approx. 150 cm from the corner of the bed area.

Please contact us if you have a specific application.

The permissible maximum room dimensions differ depending on the installation location (wall or ceiling).

Wall: 4 × 4 meters
(2 meters to the left, 2 meters to the right, 4 meters to the opposite wall)

Ceiling: 4 × 5 meters
(2 meters towards the button, 2 meters towards the cable, 2.5 meters to the right, 2.5 meters to the left)

Ceiling 45°: 4 × 5 meters
(2 meters towards the button, 2 meters towards the cable, 2.5 meters to the right, 2.5 meters to the left)

Yes, all the functions that our cloud also provides are available.

We have created a webhook interface to transmit the different events and situations.

There are two ways the webhook interface can be used.

1. Account-Bot

This webhook is defined as a bot. This bot is then used in rules to notify of certain situations or states. This type is the most commonly used.

Here you can specify in which rule for which sensor this webhook should be used. When rules are created for specific situations, only the information for the affected rules is sent via webhook. All other events sent by the sensor are ignored.

1. Customer

No user/bot is used here, instead the webhook is linked to the customer. Only an administrator of the system can make this configuration.

At this level there is no further definition of which sensor the webhook should be used for. When a customer-level webhook is created, all events from all of the customer’s sensors are always sent unfiltered to the webhook. That is about 3000 events per sensor and day.

The frequent change between detected and exit is not a problem for the sensor, nor is it necessarily an indication of a malfunction/incorrect configuration. This change only means that a situation to be examined more closely has occurred (Detected). However, there is no confirmation from the sensor, so the process is ended (Exit). There are installations where the sensor determines several hundred detected and exit changes per day. However, we could not determine an impairment of the fall detection, nor was this confirmed by the vendor.

If the sensor has checked a situation to be examined more closely and its routines return a confirmation as a result, then a Confirmed event is sent. Then there should always be a Calling event. This is then only obligatory and triggers the “emergency call”. The confirmation that the sensor is sure that a fall has occurred is achieved with the confirmed event.

The sensor sends a status event every 60 seconds. If this is absent for 2 minutes, the sensor is interpreted as inactive.

An unstable WiFi connection of the sensor or a poor internet connection can lead to the loss of the status event.

The sensor also restarts itself every 24 hours. If the start and registration process takes longer than 2 minutes, the sensor is also interpreted as inactive.

For ceiling installation, the zMin value indicates the height of the detected person in the range from the floor to a height of 180 cm. In this case, a negative zMin value means that the detected person is detected in or under the floor.

The coordinates refer to the average of the readings and the sensor refers to the strongest value. This can be different. Therefore there can be situations where the sensor sees falls or presences in or under the floor. This behavior will be fixed in an upcoming sensor version.

Previously this function was called Vayyar debug mode. This mode enables telemetry and log forwarding to the vendor. The forwarding takes place from the cloud instance and not directly from the sensor. The transmission is encrypted. In the case of technical support (e.g. the creation of a Sensitivity Map) by the vendor, it may be necessary for it to receive this information.

There are 5 types of information passed to the vendor when optimization mode is enabled. These are:

• Events (e.g. status, presence, fall, configuration and analysis) that are also received and displayed by the cloud instance
• Sensor configuration resulting from the parameters and the room and region definition in the cloud instance
• System logs that are also received and displayed by the cloud instance
• Debug logs containing unreadable binary log information
• Telemetry data containing unreadable binary radar information

The telemetry data and debug logs can only be read and interpreted by the vendor.

For overlapping regions, the exclusion of falls/presence is rated stronger than the inclusion of falls/presence. This is evaluated by the sensor.

Yes, we can create a custom customer and corresponding login(s) for testing and demonstration. Get in touch with your contact person at PureSec.

The number displayed within a box indicates how many events with corresponding coordinate information the sensor has sent in the set period of time.

As an example: The value 100 is in a field and 2 days were selected as the period. This means that in the last 2 days the sensor has received 100 events containing these exact coordinates.

The value does not provide any information about how long the person stayed at this position, but how often the person was seen by the sensor at this position.

Once the sensor has been connected to the Vapro app and installed on the ceiling or wall in the room and the room dimensions have been entered into our software, the optimization mode and learning phase should be activated. Because only then do the sensor and the AI have the opportunity to get to know the room and to deliver a good result after the learning phase.

The period of 14 days is recommended by the vendor. Although it would be possible to shorten the period of time or not to start the learning phase at all, poorer results are then to be expected. We do not recommend this.

The end of the learning phase can be recognized by the fact that

1. the green "Play" symbol on the data tab in the "Status" tile is replaced by a white circle.
2. in the configuration under basic configuration the learning phase can be restarted with "Start".

All information previously sent to the vendor to create the sensitivity map will be reset and the creation process will be restarted.

This step is required if the room or furnishings are fundamentally changed or the sensor is installed in a different room.

The learning phase is only available if it has not yet been completed. Either it was stopped manually prematurely or the sensor is inactive.

Learning phase start is available once this has been completed.

The “Person on the ground” function (also known as “Sensitive mode” or “Suspicious fall”) works with a series of detections of a person detected on the ground. When “Sensitive Mode” is enabled, the sensor will check every 50-60 seconds to see if it detects a continuous presence at low altitude. Typically, this detection takes 5-12 minutes. This function is available from sensor firmware v0.38.