DE202015002194U1 - Smart home system based on Ethernet technology - Google Patents

Abstract

Smart home system based on Ethernet technology.

Description

I. Introduction

Topic & question

For the project "MyHome" we had two aspects:
On the one hand, we decided on the transition to the senior level in the P-seminar for a project on "renewable energies". The task in this seminar was to construct a working model on this topic.

On the other hand, we dealt with the subject areas "Smart Grid" and Smart Home Systems. In 2012, the participant Jonas Pfrang and two other students submitted a Youth Research Project ("POE @ Home"), which failed for various reasons. Unlike the project at the time, we do not aim to develop a bus system based on a proprietary PoE standard, but rely on a combination of renewable energy sources and proven standards that we expand. For this reason, no further use of the components from POE @ Home is possible.

Power over Ethernet is a method of supplying electrical equipment with power via network cables. This allows simultaneous transmission of power and data over the network.

Our essential research approach can be formulated as follows:

What could a user-oriented smart home system look like and function technically?

• – Die schlechte Usability/hohe Komplexität bestehender Smart-Home-Lösungen ( Billerbeck, 2013 )
• – Die hohe Vielzahl an verschiedenen inkompatiblen Standards: Schlechte Interoperabilität zwischen verschiedenen Geräten verschiedener Hersteller ( Nuissl, 2013 )
• – Hoher Preis bestehender Smart Home Lösungen ( Billerbeck, 2013 )
• – Komplizierte Installation bestehender Lösungen ( Fasse, 2013 )
• – Akzeptanz ist derzeit sehr schlecht trotz hohem Interesse ( Billerbeck, 2013 )

The following problems of current technology should be improved by our system:

• - The poor usability / high complexity of existing smart home solutions ( Billerbeck, 2013 )
• - The high number of different incompatible standards: poor interoperability between different devices of different manufacturers ( Nuissl, 2013 )
• - High price of existing smart home solutions ( Billerbeck, 2013 )
• - Complicated installation of existing solutions ( Barrel, 2013 )
• - Acceptance is currently very bad despite high interest ( Billerbeck, 2013 )

In the course of the P-seminar, we also dealt with new solar technologies and a partially self-sufficient energy supply, which we can not elaborate on in this work.

State of the art & market situation

In home automation systems, many different products and separate standards have been designed in recent years. Basically, you can distinguish three different approaches ( Sietman, 2014 ):
The most well-known of them is KNX ( Standard: ISO / IEC 14543-3 ). It is characterized by a clear separation of power supply and device control. All devices are powered by the standard 230V power line, while most (on) control components are connected via an additional 30V DC power supply, which also transmits the control data. Disadvantage of this installation is the high installation effort and a difficult configuration, which is why such installations with several thousand euros extra charge to book.

In addition, powerline systems can be cited. The control signals are "modulated" onto the building's internal power grid. Examples of such systems are "digitalStrom" or "X10" from Pico Electronics. The installation of these automation systems can not be done by laymen, but must be done by an electrician who installs the necessary building blocks (house control center, master per circuit). This in turn means that even when installing this type of smart home systems with a surcharge of several thousand euros compared to conventional installation is to be expected. In operation, the systems also have the disadvantage that only connected to the power supply devices can be controlled.

Finally, radio-based solutions for home automation must be mentioned. Of particular interest here are the standards "ZigBee" and "ZWave". Both communicate in the frequency range between 850 MHz and 900 MHz. Especially because of the low price, the systems are very popular. Their furnishing has become increasingly easier in recent years due to numerous new developments. Above all, the limited radio range and the energy supply of the sensors can be cited as problems of the technologies. This is usually (apart from "energy harvesting") solved by batteries that supply after some time no more energy and must be replaced (consuming). However, the main problem with radio solutions is their susceptibility to interference (in the mentioned frequency range, many devices are now transmitting) as well as the subject of data security: radio systems can be attacked comparatively easily.

Disadvantages of existing systems at a glance

KNX:

• - High installation effort (DC and AC mains, cable from sub-distribution to consumer → additional, long cable ways)
• - Elaborate configuration
• - Adapter blocks necessary for connecting other peripheral devices (eg smart TVs)
• - Partly high own power consumption
• - Installation and programming by electricians necessary
• - Very expensive

Powerline Systems:

• - Need for a complex installation in the fuse box
• - Only possible to control components that are connected to the mains (eg problems with radiator thermostats)
• - For digital current, converters are required for the connection of devices from other manufacturers
• - very expensive (estimated cost of EFH: 13'000 €)

Radio systems:

• - Limited radio range
• - Power the sensors with batteries
• - susceptibility to interference
• - Lack of data security

Objective of the project

Based on the market analysis above, we are developing the exact objectives of our novel smart home system:

• • Low installation effort with the involvement of the user
• • Connection of the "standard network installation" with the Smart Home installation
• • Low component price
• • Easy initial configuration and reconfiguration of the system
• • Intuitive user interface for control
• • Expandability of the system through modular design, d. H. easy way to integrate other devices such as smart TVs later in the system
• • Consideration of privacy
• • Ensuring the reliability of the system
• • Increasing the attractiveness of the market

• - In order to optimally visualize and present the structure and function of our Smart Home system, we opt for the construction of a model house. In addition, we want to realize a partially self-contained energy supply in our model house.

II. Realization of the project

The first part of the realization (focus on the semi-autonomous energy supply) of our project took place within the project seminar "Regenerative Energies" at the grammar school Grafing. We worked on the realization over a whole year (> 400 h in total).

The implementation can be divided essentially into three sections: After a detailed planning of the partial aspects of our project, we have promoted various sponsors. The construction of the model house, together with the installation of the bus system and the power generation plants, characterizes the practical implementation of the theoretical approaches. For the implementation, we also set up an exact task list.

In the following, the way of realization focused on the smart home system is presented.

Construction of the model house and installation of the power supply

Before we can test and visualize our research aspect, we have to build the basic structure of our project: the model house together with the 'energy generation facilities'. The construction is fundamentally as follows:

1. Drawing construction plans

We construct accurate detailed plans of our model house. These include both general detailed plans of the dimensions of the model house as well as detailed plans regarding the electrical installation and network installation.

2. Purchase of building materials based on the plans

We already buy plates cut to our plans and sort them to start building the house.

3. Construction of the house skeleton and installation of exterior walls, ceilings and floors

The framework is screwed, the floors and outer walls as far as possible fastened with screws. Another part is glued for design reasons.

4. Creation of the necessary preliminary work for the electrical installation

In the next step, the cavity wall boxes for switches and lamps are drilled into the interior walls and ceilings. In addition, empty pipes are installed between the outer and inner walls, through which the cables of the electrical installation are to be routed.

Then all cables are laid and the first components, such as the PoE switches, are installed as a test.

5. Connection of the connections to the outside

In order to be able to connect the model as comfortably as possible to the Internet, power grid and measuring instruments, we implement corresponding interfaces on an outer wall.

6. Energy supply: assembly of the organic solar cells

Assembly of the organic solar cell sponsored by DTU from Denmark on the west side of our model house.

7. Energy supply: Installation of the monocrystalline solar module on the roof

The monocrystalline 50 Wp solar module is mounted on the roof of the model house using a special fixture. We pull the cables through the partition walls into the basement.

8. Structure of semi-independent power supply

In the basement of our model house, we mount a charge controller to feed the produced electricity into a 17 Ah battery. In addition, the charge controller supports the direct supply of our internal load circuit for our lamps and ventilation. In addition, we pull through the conduits the remaining electrical wiring.

Development of a smart home system:

The "Ethernet-based Smart Home Bus" - EBB

In the section on "state of the art and market situation" described above, it is noticeable that there are already a large number of developments in the field of home automation systems.

So why another system?

The "perfect" standard was not found in our opinion yet. For this reason, we explore whether a new and consistent standard is possible, taking into account our objectives.

• 1. Hardwareseitig setzen wir auf standardisierte Netzwerktechnik. Konkret besteht unser System aus einem Router (zuständig für die Zentralverwaltung aller Komponenten), zweier PoE Switche (Unterverteilung) und einer CAT. 6a AWG23 Netzwerkkabel-Installation. Alle Komponenten sind per Ethernet (oder per W-LAN) an den Bus angeschlossen. Als Vorteil dieses hardwareseitigen Aufbaus sehen wir vor allem die günstigen Kosten für Netzwerkkomponenten.
• 2. Der Nutzer muss im Vordergrund stehen. Kennzeichen unseres Systems ist die Ausrichtung auf Einfachheit für den Nutzer. Hardwareseitig setzen wir das durch Plug'n'Play bei der Hardware um. Dies bedeutet, dass der Nutzer jegliche Komponenten an den Bus anschließen kann, indem er einfach den Netzwerkstecker in das jeweilige Gerät steckt (Einfachere Installation von Komponenten). Vergleichbar ist dieser Vorgang mit dem Einstecken eines USB-Geräts in den Computer (Computer = Server des EBB). Durch den Einsatz von Power over Ethernet sind die Komponenten dadurch sowohl mit Strom als auch mit dem Datensignal versorgt (wie bei USB erkennt und konfiguriert der Server das Gerät automatisch). Unsere Software ist auf eine intuitive Bedienung ausgelegt. Durch eine WebApp stellen wir die Plattformunabhängigkeit sicher: Der Benutzer kann jedes Endgerät – sofern es HTML5 und Javascript unterstützt – zur Ansteuerung und Konfiguration (Konfiguration derzeit noch nicht implementiert) verwenden. Die Ansteuerung eines Geräts im EBB entspricht also der Ansteuerung eines USB Geräts, z. B. dem Senden eines Druckauftrags. Außerdem entwickeln wir für unser Smart-Home-System auch eine iPhone-App.
• 3. Ein modularer Aufbau des Systems hilft dabei, das System dynamisch erweiterbar zu machen. Ethernet wird bereits von vielen Geräten, wie z. B. Smart TVs, Stereo-Receivern etc. verwendet. Diese könnte man vergleichsweise einfach in unser System einbauen. Auch bei eventuell auftretenden Fehlern kann ein modular aufgebautes System einfacher repariert werden.

"Ethernet-based SmartHome bus" - that's what we call the smart home system developed and implemented by us. In the development we have confined ourselves to three basic goals, which result from the objective mentioned in I.

• 1. On the hardware side, we rely on standardized network technology. Specifically, our system consists of a router (responsible for the central administration of all components), two PoE switches (subdistribution) and one CAT. 6a AWG23 network cable installation. All components are connected to the bus via Ethernet (or via W-LAN). As an advantage of this hardware-based structure, we see above all the favorable costs for network components.
• 2. The user must be in the foreground. Characteristic of our system is the focus on simplicity for the user. On the hardware side, we implement this with plug'n'play hardware. This means that the user can connect any components to the bus simply by plugging the network plug into the device (simpler installation of components). Similar to this process with the insertion of a USB device into the computer (computer = server of the EBB). By using Power over Ethernet, the components are supplied with both power and data signal (as with USB, the server automatically detects and configures the device). Our software is designed for intuitive operation. Through a WebApp, we ensure the platform independence: The user can use any device - if it supports HTML5 and Javascript - for control and configuration (configuration not yet implemented). The control of a device in the EBB thus corresponds to the control of a USB device, eg. B. the sending of a print job. We also develop an iPhone app for our smart home system.
• 3. A modular design of the system helps to make the system dynamically expandable. Ethernet is already used by many devices such. As smart TVs, stereo receivers, etc. used. These could be installed relatively easily in our system. Even if errors occur, a modular system can be repaired more easily.

General structure of the "EBB" network in the model house

2

Dynamic Host Configuration Protocol: Automatische Zuweisung von Adressen und Gerätenamen im Netzwerk

und Wireless LAN Access Point. Direkt an diese angeschlossen ist unser stromsparender ARM3

3

ARM: besonders stromsparende Prozessorarchitektur

-Mini-Server (1, 1), ein „UDOO Quad”. Auf diesem läuft ein Webserver, welcher die WebApp unseres EBB bereitstellt. Installiert haben wir diese beiden Komponenten im Keller unseres Modellhauses.The basis of our smart home system are various standard network components. This includes a router in the form of an AVM Fritz! Box 3272 ( 1 . 2 ). It acts as a DHCP server in our system 2

2

Dynamic Host Configuration Protocol: Automatic assignment of addresses and device names in the network

and wireless LAN access point. Directly connected to this is our energy-saving ARM 3

3

ARM: particularly power-efficient processor architecture

Mini Server ( 1 . 1 ), a "UDOO quad". On it runs a web server, which provides the WebApp of our EBB. We have installed these two components in the basement of our model house.

4

Power Source Equipment: Gerät, welches Strom auf die Netzwerkleitungen gibt

fungieren. Sie stellen die (Netzwerk-)Unterverteilung in unseren jeweiligen Stockwerken dar und verbinden jegliche Buskomponenten mit dem Netzwerk. Über das PSE erfolgt die Stromversorgung der Buskomponenten (z. B. Schalter) als PD5

5

Powered Device: Gerät, welches Strom von den Netzwerkleitungen bezieht

via POE.Also connected to the router are two Allnet 8845PD PoE switches ( 1 . 3 ), called PSE 4

4

Power Source Equipment: Device that gives power to the network lines

act. They represent the (network) sub-distribution in our respective floors and connect any bus components to the network. The power supply of the bus components (eg switches) takes place via the PSE as PD 5

5

Powered Device: Device that receives power from the network cables

via POE.

The network cabling in the model house is in 1 shown.

hardware development

The switches

As a possible variant of a control component we develop a switch. On this we install an LCD display. This shows the user current information (eg the room temperature). Furthermore, there are eight buttons on the switch. This allows the user to trigger actions. In addition to the buttons there are additional LEDs, which show the current status of the linked device, eg. As a lamp, show. In addition, a brightness sensor and a temperature and humidity sensor are mounted on the switch. After further considerations, we equip our switches with a night lighting in the form of two LEDs and a USB interface for charging portable devices (eg smartphones).

The above components are all in one of us made of rigid PVC foam panels housing itself. They are connected via ribbon cable to the underlying board on which the interconnection takes place.

The executive unit of our switch is ultimately an Arduino Ethernet with PoE Shield. It is located on the back of the switch.

Overall, we have built two such switches and mounted in the model house.

The lamps

For our model house, we also build two "modern" lamps.

The lamp on the "ground floor" is an RGB LED shield, while the "upper floor" has a RGB LED strip with 144 LEDs. They are controlled via Arduino Ethernet controllers. Due to the high power consumption of the LEDs (P_max = 60 mA / LED), they are supplied via the 5 V DC circuit separately installed in the house. Later, this should also be possible via POE.

Software programming

The following communication concepts are in the 2 and 3 shown. It shows 2 the decentralized solution during 3 the central solution is illustrated. For the reference signs: ( 6 ) Lamp unit; ( 7 ) Switch unit; ( 8th ) Server with webapp; ( 9 ) Server with webapp and control software.

To ensure the simplest possible administration of all Internet-enabled devices, we opt for a centrally managed solution. This will allow the system to stay in sync. For example, if a lamp is assigned two switches and the lamp is turned on at switch 1, the central server automatically informs lamp 1 and switch 2 about the change. In addition, the centralized solution allows easy configuration and assignment of the devices without changing their software. The decentralized solution has the disadvantage that the components are often asynchronous. This means, for example, switch 1 shows "lamp 1 on" and switch 2 shows "lamp 1 off" even though the lamp is on. Synchronization is also possible with this solution, but more complex because the software would have to be updated every time the system changes on all affected devices. However, the advantage here is that the decentralized solution is independent of a server.

As a precursor to the central solution, we are developing this decentralized approach to simplify programming. This means that the components do not communicate with a central server, but only with each other. After successful testing of our components, we update our system to the central approach, as we see more benefits in this.

6

HyperText Transfer Protocol: Protokoll zur Übermittlung von Daten innerhalb eines Rechnernetzes

. The development of the software can be divided into three parts. All sections communicate with each other via the HTTP protocol 6

6

HyperText Transfer Protocol: protocol for the transmission of data within a computer network

,

The Arduino software (control of the EBB components)

Basically, here are the software for the microcontroller to control lamps and switches to distinguish. For programming, the Arduino dialect of C is used.

7

Zeit zwischen Anfrage und Ausführung eines Steuerungsbefehls

bei den Anfragen zu erreichen, muss die Auswertung und Generierung von Befehlen möglichst in Echtzeit erfolgen. Erschwert wird die Programmierung zusätzlich durch die volle Auslastung aller Ports auf dem Arduino bei unserem Schalter, sodass ein gleichzeitiger Betrieb mit serieller Schnittstelle zur Fehlersuche nicht möglich ist.Due to the small amount of work and program memory of the ATmega 328, we have to concentrate on resource-saving, hardware-oriented programming. To minimize latency 7

7

Time between request and execution of a control command

In order to reach the requests, the evaluation and generation of commands must be done in real time as far as possible. The programming is made even more difficult by the full utilization of all ports on the Arduino at our switch, so that a simultaneous operation with serial interface for troubleshooting is not possible.

The user interface

8

Sammlung von wichtigen Funktionen und Klassen zur Webprogrammierung

in Verbindung mit einem Theme für Admin-Oberflächen. Dieses bauen wir unseren Anforderungen entsprechend um. Als Hauptfunktion der WebApp des Modellhauses implementieren wir die Möglichkeit, die Lampen in unserem Haus anzusteuern. In der zentralen Lösung ist zusätzlich die Konfiguration der Komponenten angedacht.For the control of our bus components we develop a WebApp. It is important for us that this is characterized by an intuitive operation and works on any network-enabled devices (the goal of platform independence). We decide to create an HTML and Javascript based WebApp. As a basis, we use the Twitter Bootstrap 3 Framework 8th

8th

Collection of important functions and classes for web programming

in conjunction with a theme for admin interfaces. We build this according to our requirements. As the main function of the WebApp of the model house we implement the possibility to control the lamps in our house. The central solution also includes the configuration of the components.

To demonstrate that our system integrates natively into any other network-enabled system, we are developing an iPhone app in SWIFT. It has the same functionality as the web app.

The server in the central solution

As in the graph above ( 3 ), the central solution is the server in the center. He controls and manages all components.

9

Normalisierung ist der Vorgang, die Datenbank bestmöglich zu optimieren und alle doppelten Informationen zu vermeiden

). Diese speichert die Konfiguration und den Status der einzelnen Komponenten des EBB. Die Entgegennahme und Verarbeitung von Steuerungsbefehlen sowie die Aktualisierung der Datenbank auf dem Server erfolgt durch eigenentwickelte, serverseitige PHP-Skripte10

10

Skripte sind kleine, im Hintergrund ablaufende Programme

.We build a database on the server (columns, tables and normalization 9

9

Normalization is the process of optimizing the database in the best possible way and avoiding duplicate information

). This saves the configuration and the status of the individual components of the EBB. The receipt and processing of control commands as well as the updating of the database on the server is carried out by proprietary, server-side PHP scripts 10

10

Scripts are small, background programs

,

But the software on the microcontrollers will also be adapted once, as it now has to use the server as a central resource. This means that all commands are accepted by the server and sent to the server.

In the following, the communication process within the EBB is shown as an example using the example "Print a push-button on a switch":
The user presses the button of a switch. The switch then sends a request to the server, which receives and evaluates it. The server now sends a request to the linked lamp. The component lamp processes this request and executes it (switch on the lamp). If the lamp is switched on, the lamp sends another request to the server. The server receives the request, evaluates it and updates its database accordingly. Upon completion of this process, a request is made to the associated switches. The switches, in turn, process the requests and make corresponding status changes.

III. discussion of Results

The EBB

• • Standardisierte Netzwerktechnologie: Wie in der Zielsetzung festgelegt, können wir ein vollständig ethernetbasiertes Bussystem vorweisen. Wir haben es somit geschafft, die „Standard-Netzwerkinstallation” mit der Smart-Home-Installation zu verknüpfen. Resultierend aus der Verwendung von Standardnetzwerkausrüstung – welche heute Massenware ist – ist es möglich, die Kosten für ein solches System weiter zu senken.
• • Geringer Installationsaufwand unter Einbeziehung des Nutzers: Auf einen Elektriker können wir nicht ganz verzichten. Er müsste weiterhin eine leicht abgewandelte Standard-Elektroinstallation vornehmen. An einigen Stellen werden zusätzlich Netzwerkkabel ergänzt oder NYM-Kabel durch sie ersetzt. Die Notwendigkeit einer komplexen Verkabelung im Vergleich zu KNX entfällt weitgehend, ebenso lange Kabelstrecken durch das Aktor-/Sensor-Konzept. Die Aktoren sind im EBB System direkt in den einzelnen Komponenten enthalten. Eine komplexe Unterverteilung im Sicherungskasten ist nicht notwendig. Ein wichtiger Unterschied zu KNX ist auch, dass der nicht-technikversierte Nutzer dazu in der Lage ist, jegliche Buskomponenten, z. B. Schalter, selbstständig an das System anzuschließen.
• • Plug'n'Play: Sofern die Komponenten unseres EBB einmal konfiguriert sind, zeichnen sie sich dadurch aus, dass sie jederzeit einfach vom Bus getrennt und an anderer Stelle wieder an ihn angeschlossen werden können. Hierbei ist es nur nötig, die Buskomponente mit dem Netzwerkkabel zu verbinden. Die Stromversorgung sowie die Datenverbindung sind dank PoE hiermit hergestellt. In den darauffolgenden Schritten findet die Initialisierung statt. Danach ist jede Komponente sofort nutzbar.
• • Durch die aktuell entwickelte zentrale Lösung lassen sich die Komponenten zusätzlich über die Apps umkonfigurieren und in Zukunft eventuell auch ersteinrichten. Damit wäre ein komplett modulares System erreicht, da weitere Komponenten ohne spezielle Vorbereitung direkt eingebunden werden können.
• • Die Ansteuerung unserer Komponenten durch ein ansprechendes und intuitives User-Interface konnten wir ebenfalls im Laufe unseres Projektes realisieren. Sowohl unsere WebApp als auch unsere iPhone-App sind einfach zu bedienen und steuern die Hardware im Modellhaus problemlos an. Zusätzlich ist die WebApp mit fast allen Endgeräten kompatibel.
• • Dadurch dass (zumeist) kein Funk zur Übermittlung der Steuerungsdaten verwendet wird, zeichnet sich unser System durch eine höhere Zuverlässigkeit aus. Zudem erschwert diese Tatsache den Angriff auf unser System.

We can show the following results through the construction of the EBB:

• • Standardized network technology: As defined in the objective, we can boast a fully Ethernet-based bus system. We have thus managed to combine the "standard network installation" with the smart home installation. As a result of the use of standard networking equipment - which is now mass-produced - it is possible to further reduce the cost of such a system.
• • Low installation effort with the involvement of the user: We can not completely do without an electrician. He would continue to make a slightly modified standard electrical installation. In some places additional network cables are added or NYM cables replaced by them. The need for complex cabling in comparison to KNX is largely eliminated, as long cable runs through the actuator / sensor concept. The actuators are contained in the EBB system directly in the individual components. A complex sub-distribution in the fuse box is not necessary. An important difference to KNX is also that the non-tech-versed user is able to any bus components, such. B. switch to connect independently to the system.
• • Plug'n'Play: If the components of our EBB are configured once, they are characterized by the fact that they can easily be disconnected from the bus at any time and connected to it again at another location. It is only necessary to connect the bus component to the network cable. The power supply as well as the data connection are hereby made thanks to PoE. In the following steps the initialization takes place. After that, every component can be used immediately.
• • Due to the currently developed central solution, the components can also be reconfigured via the apps and may also be set up in the future. This would result in a completely modular system, since additional components can be integrated directly without special preparation.
• • The control of our components through an appealing and intuitive user interface, we could also realize in the course of our project. Both our WebApp and our iPhone app are easy to use and control the hardware in the model house easily. In addition, the WebApp is compatible with almost all devices.
• • The fact that (mostly) no radio is used to transmit the control data, our system is characterized by a higher reliability. In addition, this fact complicates the attack on our system.

In conclusion, we have managed, as planned, to align the system as close as possible to the user.

In our experiments, we were also able to show that bus systems can also be implemented via Ethernet with real-time communication. For the user, there are no noticeable waiting times and everything runs smoothly. Due to the easy extensibility, we see a very sensible use of this system in the future.

Possibility of (partially) self-sufficient energy supply

A partially self-contained energy supply is also available in our project. The energy supply of our model house components works with the energy stored in the battery, which is generated by the solar panel on the roof. On a large scale, a house could be supplied with this model for a short time completely self-sufficient. However, in reality this is difficult to implement economically due to limited sunshine duration and / or low battery capacity, which is why we tend to have a semi-autonomous energy supply on a large scale.

future visions

The EBB

11

Energy Efficient Ethernet: Absenken des Stromverbrauchs der Ethernet Verbindung im Leerlaufbetrieb (Wikipedia (Hg.), Energy-Efficient Ethernet, 2014)

unterstützen → signifikante Einsparungen) und die Verwendung besserer PoE-Komponenten weiter senken (z. B. bessere DC/DC Wandler, Nutzung von EEPoE12

12

Energy Efficient Power over Ethernet: Senken der Verlustleistung auf PoE Leitungen (Daniel Feldman, 2011)

). In der KNX Norm ist beschrieben, dass der Energieverbrauch pro Komponente 0,36 W nicht überschreiten darf. Durch die oben genannten Verbesserungen könnten wir uns sogar vorstellen, dass man damit den Energieverbrauch pro Buskomponente unter 0,36 W absenken kann. Ein weiterer Punkt ist, dass die Arduino-Plattform nicht für den Einsatz abseits der Entwicklung gedacht ist und hierfür auch entsprechend wenig optimiert wurde.Regarding the EBB, some aspects should still be considered:
Currently, the own power consumption of the components is still too high. We achieve values of just under one watt for our switch (calculated). Extrapolated to a whole house, the power consumption for the bus system is currently too large. However, this can be achieved by switching to suitable microcontrollers, the use of energy-saving Ethernet ICs (possibly also using components that meet the EEE standard 11

11

Energy Efficient Ethernet: Lowering the power consumption of the Ethernet connection during idle operation (Wikipedia (ed.), Energy-Efficient Ethernet, 2014)

support → significant savings) and further reduce the use of better PoE components (eg better DC / DC converters, use of EEPoE 12

12

Energy Efficient Power over Ethernet: Lowering power loss on PoE lines (Daniel Feldman, 2011)

). The KNX standard describes that the energy consumption per component must not exceed 0.36 W. With the above improvements, we could even imagine lowering the power consumption per bus component below 0.36W. Another point is that the Arduino platform is not intended for off-the-fly use and has not been optimized accordingly.

Furthermore, the initial configuration has not yet been implemented in the current system and will probably only be completed in stages until the competition. Together with the configuration, automation is also useful. In order to save electricity and heat in the home, the detection of idle times and habits of the residents are helpful. This allows lamps to be switched on and off intelligently. The same applies to the heating and the control of shutters or blinds.

13

„American Wire Gauge”: Leiterquerschnittskennzeichnung (kleinere Nummer → größerer Querschnitt) (Wikipedia (Hg.), American Wire Gauge, 2015)

des Kabels) dürfen, um die Wirtschaftlichkeit zu erhalten. Durch Cat. 8 sollte dieses Problem jedoch gelöst werden, da dieser Standard die AWG23 Klassifizierung voraussetzt, welche einen ausreichend hohen Leiterquerschnitt bringt14

14

67 Ohm/1000 Meter (Wikipedia (Hg.), American Wire Gauge, 2015)

und es zudem zukünftig einen dieser Leistung angemessenen neuen RJ45-Stecker geben soll. Aktuell verwenden unsere EBB-Komponenten den 802.3af Standard . Bei höheren Leistungen wird es zusätzlich erforderlich, einen PoE Standard zu verwenden, der dies erlaubt, beispielsweise 802.3at++15

15

802.3af hat eine maximale Leistungsabgabe von 15,4 W (Schnabel, 2015) , 802.3at++ von 90 W. (Allnet GmbH Computersysteme, 2015)

.In the future, it could also be interesting to supply and simultaneously control smaller consumers such as LED lamps via PoE. This saves you further cable installation effort and money. It should be noted here that no losses are too great due to the small cross-section of network cables (the decisive factor here is the AWG classification 13

13

"American Wire Gauge": Conductor cross-section identification (smaller number → larger cross section) (Wikipedia (ed.), American Wire Gauge, 2015)

of the cable) in order to maintain the economy. By Cat. However, this problem should be solved since this standard requires the AWG23 classification, which provides a sufficiently high conductor cross section 14

14

67 ohms / 1000 meters (Wikipedia (ed.), American Wire Gauge, 2015)

and, in the future, there should be a new RJ45 plug suitable for this performance. Currently our EBB components use the 802.3af standard , For higher performance it is additionally necessary to use a PoE standard that allows this, for example 802.3at ++ 15

15

802.3af has a maximum power output of 15.4 W (Schnabel, 2015) . 802.3at ++ from 90 W. (Allnet GmbH Computersysteme, 2015)

,

16

PowerLAN ist eine Technik, das Netzwerksignal über die 230 V Hausverkabelung zu übertragen.

angebunden werden. WLAN halten wir für die Anbindung von frei stehenden Heizkörpern (keine Flächenheizungen) für sinnvoll, da so viele Kabelstrecken gespart werden. Auch ist hier die garantiert zuverlässige Anbindung weniger kritisch als beispielsweise bei Schaltern und Lampen. PowerLAN ist für uns die beste Lösung zur Verbindung von Großverbrauchern und auch Lampen, die (ohne große Verluste) nicht über PoE versorgt werden können.In a later step, we can also imagine that other components also via WLAN or PowerLAN 16

16

PowerLAN is a technique to transmit the network signal via the 230 V home wiring.

be connected. WLAN we consider for the connection of free-standing radiators (no surface heating) makes sense, since so many cable routes are saved. Also, the guaranteed reliable connection is less critical here than, for example, with switches and lamps. PowerLAN is for us the best solution for connecting large consumers and also lamps that can not be supplied via PoE (without great losses).

Importantly, the system is easily extensible with components that support the HTTP network protocol. Maybe an open-source standard would be useful here.

"Smart Grid API"

In the next few years, due to the energy turnaround, many base load power plants will be shut down. Most regenerative energy sources can not provide this base load because their yield depends on the weather. To prevent blackouts, it makes sense to match supply and demand. We think that through our EBB it is possible to create an interface with which the energy company can operate intelligent load management.

V. Bibliography

• Allnet GmbH Computer Systems. (19. 01 2015). Allnet ALL048900 / Power over Ethernet AT ++ 90 W. From http://www.allnet.de/de/allnet-brand/produkte/poe/poe-injector/p/allnet-all048900-power-over-ethernet-injektor-at -90w / accessed
• Billerbeck, D.-IJ (2013). Study: Smart home solutions have not arrived at the consumer. VDI News (33/34), 12 ,
• Daniel Feldman, RK (2011). Energy Efficient (Power over) Ethernet. Ethernet Alliance ,
• Fasse, S. (2013). Gigaset wants to bring home networking in rental housing. VDI News (33/34), 12 ,
• Nuissl, N. (2013). Smart house is about to start construction. VDI News (33/34), 12 ,
• Schnabel, P. (19.01.2015). Power over Ethernet (PoE) / IEEE 802.af / IEEE 802.3at. From http://www.elektronik-kompendium.de/sites/net/0807021.htm accessed
• Sietman, R. (04.10.2014). Biodiversity. c't, pp. 136-141 ,
• Wikipedia (ed.). (18. 01 2014). Energy-Efficient Ethernet. From http://en.wikipedia.org/w/index.php?title=Energy-Efficient_Ethernet&oldid=625247111 accessed
• Wikipedia (ed.). (18. 01 2015). American Wire Gauge. From http://en.wikipedia.org/w/index.php?title=American_Wire_Gauge&oldid=131626350 accessed

LIST OF REFERENCE NUMBERS

1

server

2

router

3

PoE switch

4

lamp unit

5

switch unit

6

lamp unit

7

switch unit

8th

Server with webapp

9

Server with webapp and control software

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• Billerbeck, 2013 [0005]
• Nuissl, 2013 [0005]
• Billerbeck, 2013 [0005]
• Barrel, 2013 [0005]
• Billerbeck, 2013 [0005]
• Sietman, 2014 [0007]
• Standard: ISO / IEC 14543-3 [0007]
• Energy Efficient Ethernet: Lowering the power consumption of the Ethernet connection during idle operation (Wikipedia (ed.), Energy-Efficient Ethernet, 2014) [0052]
• Energy Efficient Power over Ethernet: Reduction of power loss on PoE lines (Daniel Feldman, 2011) [0052]
• "American Wire Gauge": conductor cross-section marking (smaller number → larger cross section) (Wikipedia (Ed.), American Wire Gauge, 2015) [0054]
• 67 ohms / 1000 meters (Wikipedia (Ed.), American Wire Gauge, 2015) [0054]
• 802.3af standard [0054]
• 802.3af has a maximum power output of 15.4 W (Schnabel, 2015) [0054]
• 802.3at ++ of 90 W. (Allnet GmbH Computer Systems, 2015) [0054]

Claims (10)

Smart home system based on Ethernet technology. The smart home system according to claim 1 characterized by the use of a router that handles the IPv4 / IPv6 or DNS name forgiveness, the use of network switches connecting the devices to the network and a server that handles the central office, control tasks, and Configuration of the system allows. Smart home system according to claim 1 or 2 characterized by the hardware-side connection of most devices via network cable with two-sided or one-sided plug, preferably according to the standard RJ45 and thus the Plug'n'Play principle. Smart home system according to claim one of the preceding claims characterized by the power and data supply of some bus components via the PoE technology through the use of PoE switches and / or injectors. Smart home system according to one of the preceding claims characterized by the connection of other devices to the system via PowerLAN or a wireless technology, preferably via WLAN. Smart home system according to one of the preceding claims characterized by the possibility of hardware and software-side integration of other ethernetfähiger devices preferred by the Plug'n'Play principle. Smart home system according to one of the preceding claims characterized by the use of the http protocol or a comparable protocol for communication within the system. Smart home system according to one of the preceding claims characterized by the use of the server instead of the router to assign the IPv4, IPv6 or DNS address. Smart home system according to one of the preceding claims characterized by the direct communication of the devices with each other instead of a server. Smart home system according to one of the preceding claims characterized by interfaces for control and configuration options that can be used by applications for smartphones, Phablets, tablets, smartwatches or similar devices and are optionally accessible from outside the local network.

Images