Status objects
Back Forward | Help / Project / Status objects
States of the HomeServer can each be linked to one communication object in this screen. The communication objects entered here change their value to 1 or not equal to zero when the HomeServer accepts the state.
Both internal and external (EIB) communication objects can be assigned here.
When using the EIB communication objects, there is an implicit type conversion (as in logic).
These can then e.g. be further processed in the logic.
Status objects that document errors are reset to zero after a successful state.

System start
A communication object can be assigned here. It assumes the value 1 when the HomeServer has been started.
During operation, the value always remains at 1.
Portal use
A communication object can be assigned here.
This assumes the value 1 when the HomeServer is successfully connected to the portal.
If the HomeServer is no longer connected to the portal then the value is zero.
ISDN use
A communication object can be assigned here.
This assumes the value 1 when the HomeServer is connected to the internet via ISDN.
A tone alert (see the Network bar) can also be emitted.
Memory space (assigned)
A communication object can be assigned here.
It assumes a value between 0 and 100% and shows the assignment of the retentive memory.
All transaction data (data/picture archive, light scenes, lists) are stored in this memory.
Flushing memory (number)
A communication object can be assigned here. It assumes the value of more than zero when the HomeServer is in danger of overflowing.
Before reaching the memory limit, the HomeServer deletes (flushes) the last 20% of all archives.
This value should be linked to an alarm signal and thereby monitored!
An exact size of the required memory space can not be determined when creating the project.
Data compression algorithms are used in the HomeServer. The compression rate varies depending on the nature of the data.
If the memory limit is reached often then the archive should be reduced in size or parts of the archive should be stored externally using ftp or E-mail.
Successful connections
The communication objects for successful connections are entered in this column.
Failed connections
The communication objects for failed connections are entered in this column.
E-mail
Connection to the E-mail server. The state of this communication object returns no information regarding whether the E-mail was able to be sent!
FTP (Server 1)
Connection to ftp server; no information on whether the data could be transferred
FTP (Server 2)
Refer to FTP (Server 1)
SMS
Connection to the SMS provider; no information on whether the SMS could be sent
NTP
Connection to the NTP server
ISDN
Connection to the ISDN network
Portal
Connection to the set portal
DynDNS
Connection to, e.g. nnn.dyndns.org