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

The sensor is reachable with PING (ICMP echo request). This PING can be used the monitor the reachability of the sensor without being dependent of the event transmission.

No, this is not possible. When mounting on the wall, make sure that the power cable runs down towards the floor and that the sensor is not rotated by 90° or 180°. For this purpose, the sensor has a marking on the back which side has to point upwards.

There are different materials and objects which can influence the (fall-) detection of the sensor. Some of this are:

• Metal clothes rack
• radiators
• Mirror and glass surfaces
• Furniture made of metal or solid wood
• large electronic devices
• Wheelchairs
• Curtains
• Patient lift
• Raising aid or bed gallows

For moving objects such as fans or chandeliers, the minimum distance between the object and the sensor is 1 meter from the edge of the object closest to the sensor.

For fixed objects such as beams and lamps, the distance between the object and the sensor should be twice the height of the object.

The amount of data transferred depends on the number of events that the sensor has to transmit. In an empty room there are always two events per minute, in a busy room there can be up to 11 events per minute.

From our observations, the usual amount of data transferred is between 0.7 and 1.2 GB per month per sensor. This corresponds to approximately 24 to 40 MB per day per sensor.

In exceptional cases, when the telemetry strategy is set to "On", the amount of data transferred can be up to 15 GB per month. This setting is not recommended for continuous operation.

The sensor currently has a wifi chip installed for the frequency of 2.4 GHz. The wifi frequency with 5 GHz cannot be used with it.

The wifi signal strength and quality is important the sensor can work reliable and transfer its events. With a RSSI value of:

• -80 there will be some disconnects and the sensor often marked as inactive
• -70 its the minimum value to work reliable
• -60 and higher it is the recommended value to work proper

The sensor has an operating temperature of approximately 70 degrees Celsius. Depending on the room temperature, power supply (in the case of the Type C sensor) and the amount of falls in the room, the temperature can be higher.

• The average minimum temperature is around 55 degrees Celsius.
• The average operating temperature is around 70 degrees Celsius.
• The average maximum temperature is around 85 degrees Celsius. It can also be higher. Therefore, it is OK if the sensor feels hot.
• The maximum temperature of the chip is reached at 100 degrees Celsius.

No, the wifi connection is always required because the sensor must receive configuration and software updates via an active connection to the cloud (instance). If the wifi connection is disconnected, the sensor would restart itself after a certain time in order to reestablish the connection.

No, if the sensor loses power or restarts, the locally cached configuration is lost. This is obtained again from the cloud (instance) during the start process.

A sensor with dry contact can manually be triggered by pressing the button on the top of the device for less the one second.

Yes, the wifi connection is always required, as the sensor must receive configuration and software updates via an active connection to the cloud (instance).

The dry contact message is triggered once the confirmation phase is complete. Then it takes about 30 seconds until the calling.

At the current time, only the first dry contact can be used to report fall information. There are already developments to report leaving a region via the dry contact. However, these are not yet complete.

The following accesses to the Internet or to the PureLife Cloud instance are necessary.

• Ping / ICMP to 1.1.1.1, google.com, 8.8.8.8 and 8.8.4.4
  • to check the connection during provisioning
• DNS / udp+tcp 53 to the DNS server
  • which is distributed in the WiFi via DHCP
• NTP/udp 123 to pool.ntp.org
  • can be changed on a self-hosted instance
• HTTPS / tcp 443 to the PureLife Cloud instance
  • if our service is used, it is the DNS name: vayyar-cloud.smart-altern.de
• MQTTS / tcp 8883 to the PureLife Cloud instance
  • if our service is used, it is the DNS name: vayyar-cloud.smart-altern.de

The sensor has a maximum power consumption of 15 watts. In normal operation, the power consumption is around 5 watts.

• A USB power supply with 5 volts / 3 amperes should therefore be used with the sensor type A.
• With the sensor type C, the power supply used must deliver the appropriate amperes depending on the voltage (12 or 24 volts).

For the sensor with USB type A connector, the length of the power cable is approximately 1.4 meters. In most cases, this length is not sufficient for a ceiling installation and the power cable needs to be extended.

It must be ensured that no USB extension cable can be used, since the USB power supply unit (5V / 3A) is not sufficient. The extension must be made on the 230 volt supply line to the USB power supply.

The YLTC-357 power supply with USB type A and USB type C port cannot be used to operate the Sensor type C. The type C sensor does not start and must be supplied with a voltage of 12 or 24 volts.

A sensitivity map improves the sensor’s fall detection and prevents false alarms. To create a sensitivity map, the optimization mode must be activated and the learning phase started. As long as the learning phase is not completed, the recognition result may be worse. A sensitivity map is automatically created by the vendor during the 14-day learning phase.

As long as optimization mode is enabled, the AI continuously and regularly optimizes the sensitivity map based on events and data that meet the map optimization algorithm criteria. The sensitivity map is regularly downloaded and installed on the sensor.

In order for a sensitivity map to be created or updated, there must be two identical false fall events at the same location within 60 days. This prevents a sensitivity map from being created too quickly or too often and real falls from not being detected.

A sensitivity map is always linked to the sensor, the room (not the region) and the firmware version. After one of these things has changed, a new sensitivity map must be created.

These messages can occur if the sensor has a poor Wi-Fi or internet connection. If a fall event occurs and telemetry data is generated and sent, a poor connection may result in missing radar recordings.

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.

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.

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 “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.