Push message uni-PRO APP With this function block the controller sends notifications directly to the uni-PRO APP - even when the APP is closed on the phone. Tapping the notification opens the APP.
Unlike the Push message Pushover block, this requires no third-party service and no account, and no additional app has to be installed. The message is sent to every device whose APP has logged on to this controller at least once.
Setup:
Inputs |
||
| TR |
Trigger |
Trigger on which the message is sent.
See parameter Trigger. |
| WT / W1..W8 |
Value |
Optional values. Values connected here
can be inserted into the title or the message. The placeholder %1
in the title or message is replaced with the value of the first
value input, %2 with the second and so on. The number of value
inputs is set with the parameter Number
of inputs. Formatting follows the data type of the linked
address (integer, floating point or string); if no address is
linked, floating point is used. |
Outputs |
||
| FE |
Error |
Number of errors. |
| AZ |
Count |
Number of messages sent. |
| FT |
Filter |
Remaining filter time in seconds. After a message has been sent, this output counts down from the time set in the parameter Filter to 0. As long as the value is greater than 0, no further messages are sent. |
Parameters |
||
| Trigger |
|
|
| Title |
Optional title of the message. If the parameter is left empty, uni-PRO is shown. | |
| Message | Message that is sent. Mandatory field
- if the parameter is empty, nothing is sent and the output FE
Error is increased. |
|
| Group |
Optional label that marks related messages. Messages of the same group replace each other on the phone instead of piling up. This is useful for a doorbell, for example: entering door here means that even after repeated ringing only a single, current message is shown on the screen. If the parameter is left empty, every message is shown separately. The label can be chosen freely and is not displayed on the device. | |
| Page |
Optionally the name of a page of the visualisation. Tapping the message on the device opens the app directly on that page. If the parameter is left empty, the app is only brought to the front and shows the page it was last on. If the page does not exist in the project, the display remains unchanged. | |
| Recipient |
Optionally restricts the message to
certain devices. Separate several of them with a semicolon. If the
parameter is left empty, the message goes to every registered device. A device is addressed by the user logged on in the app. If nobody is logged on, only its token at the push service remains. That token changes as soon as the app is reinstalled or its storage is cleared - the device then has to be selected again. A logged-on user is therefore the better choice. The button at the right-hand end of the input field shows the devices known to the controller and enters the selection; this requires a connection to the controller. The device name shown there (for example Samsung SM-G991B) is assigned by the app itself. It only serves to tell the devices apart and cannot be entered as a recipient - identical models carry the same name. Important: If something is entered here, devices that no entry matches no longer receive anything. If the entry does not match a single device, the controller reports this in the log. |
|
| Filter |
Waiting time in seconds until the next message is sent. While the time is running, further triggers are discarded. The remaining time is available at output FT. With 0 the filter is switched off. | |
| Send cyclically |
The message is sent repeatedly as long as the trigger condition is present. With the setting Value change there is no pending condition, therefore cyclic sending is not possible there and the parameter is hidden. | |
| Cycle time |
Interval between two cyclic messages in minutes. If the filter is active, the cycle waits until the filter time has elapsed. | |
| Number of inputs |
Number of value inputs (1 to 8) that are available for the placeholders %1 to %8. | |