FAQ

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.

The maximum detection range differs depending on the installation location (wall or ceiling).

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

Ceiling: 4 x 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 x 5 meters
(2 meters towards the button, 2 meters towards the cable, 2.5 meters to the right, 2.5 meters to the left)

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 transferred data size is dependent of the amount of events which the sensor has to send. In a clean room there are only two events per minute per sensor. In a occupied room the sensor can create up to 11 events per minute per sensor.

We observed that the transferred data size is between 1,0 und 1,5 GB per month per sensor. This corresponds to 34 to 51 MB each day per sensor.

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 approx. 70 degrees Celsius. Depending on the room temperature, power supply (in the case of the sensor type C) and the number of falls in the room, the temperature can be higher. At a temperature of:

• below 75 degrees Celsius everything is fine.
• 75 to 85 degrees Celsius the sensor is “hot” but the temperature is still within the limit.
• 100 degrees Celsius the maximum temperature of the chip has reached.

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.