Wichtige Info

Die Inhalte, die du hier siehst stelle ich dir ohne Werbeanzeigen und ohne Tracking deiner Daten zur Verfügung. Trotzdem muss ich die Server bezahlen sowie Zeit in Recherche, Umsetzung sowie Mail Support stecken.
Um dies leisten zu können, verlinke ich in einigen Artikeln auf die Plattform Amazon. Alle diese Links nennen sich Afiliate Links. Wenn du dir mit diesem Link etwas kaufst, dann erhalte ich eine kleine Provision. Dies ändert jedoch NICHT den Preis, den du bezahlst!
Falls du mich also unterstützen möchtest, kannst du auf den Link zum Produkt klicken und hilfst mir dabei, dieses Hobby weiter zu betreiben.
Da ich Keine Werbung schalte und keine Spenden sammle, ist dies die einzige Möglichkeit, meine Systeme und mich zu finanzieren. Ich hoffe du kannst das verstehen :)


Thread - Now once correctly explained


Introduction

For months there is hardly anything else in the world of Smarthome, as thread... Devices to get the thread as an update, devices that do not get an update and devices that are now brand new to Market come... Everyone has something to say to Thread, but no one can to say in general what the real advantage of Thread should be. Sure it should be faster and better, but that I also expect from a “NEUEN” standard, otherwise you could also give it. I want to know what exactly does thread like that different? – Why is thread “the protocol of the future” and why isn't that easy for the others as an update?

In this post, I would like to clarify all the questions. For the I have been through nearly 30 different websites, 15 pages Information collected, some of which are speaks again what my immity over this whole hype seating to make it understandable. At present, it seems that everyone wants to Thread say whether the hand and foot has or not.

Main part

The little things first

First of all, how thread works should be clarified. Other as many other network standards, thread does not define the complete OSI stack, but focuses on existing technologies (802.15.4) – thus defines layer 3 – 5 and uses it for the underlying Layers of other technologies. Also does not define thread Layers 6 and 7, for example later, by Matterimplemented. And here is a very important point for me. Wear: Thread Devices will not necessarily speak witheinader (at least not so that they start something with the data ). If a thread device should be deleted, which is not Matter used, then the device can in any case be easily inserted into the Thread network and also send the data there, however, these data are not without a corresponding router incl. Translator from other threadable devices can.
However, if only thread devices are certified which also using Matter, this would of course not be a problem. Of which I am not currently out, as there are no statements on this.

How is the communication?

As already mentioned in the previous point, thread is supported 802.15. This standard defines the first two layers of the OSI Models and builds up a so-called WPAN network. These two layers I don't define more. For this part Communication interested, for example here Look. In summary, 802.15.4 ensures that data is very efficient can be sent and also implements the P2P, star and mesh functionality. Furthermore, this standard also implements the Device Types RFD (Reduced Function Devices) and FFD (Full Function) Devices), this uses thread to, for example, senses as RFD to be used. This creates a lot of energy in these devices saved because they themselves only act as a terminal and not yet as a terminal Router. These devices transmit data when they arrive.

Thread builds an IPv6 supported network between the devices and ensures the transmission. To communicate between the To enable devices, so-called “order routers” are used. These replace the hubs so to speak and can be installed within a network occur several times. As a result, other also distributed networks are within a thread network possible. A thread network can are also connected to different external IP subnets, which for example the problem of Auto Discovery over various networks can solve.

Mesh and “Self healing”

Thread is capable with the mesh due to 802.15.4 Topology to work. That means that FFD’s (Full Function Devices) can also send data from devices to other devices and also themselves serve as access points. This gives the possibility to bridge large physical distances and continue, especially in narrow mesh nets, have a very good connection density, which in low laths are likely to end.
Furthermore, many websites say that the network “Self healing” is, I personally do not see this. There is the possibility of other devices through mesh functionality to use communication when a special router fails an RFD (Reduced Function Device) is connected, fails automatically uses another router (if there is one). These Functionality is called self healing by many. It is but important to say that this only works when the others Routers have the opportunity to get into the target network. In particular larger networks and Border routers in different networks then Redundant has to work because the network otherwise is not self healing. At the end of the day becomes quite classic mesh used and Self Healing will apply more or less only if either simple installations are created, or the Border Router are set up redundantly. But generally Self Healing would be Thread only, when the broken device is magically repaired or if a device is removed, this magically reappeared... Both will not . At the end of the day, thread is also just a protocol which tries to use alternative routes.
The simplest Example is the following: A user has a Border router (e.g. Alexa) and otherwise only RFD’s – sensors for temperature, doors etc. If Alexa is out of herbal udder, there's nothing left Heal, then the network is no longer functional. The same thing of course on board routers that include automations.

Communication security

So that a new standard can be introduced nowadays and then also has success in the market, necessarily also communication be secured. To access the communication within the thread network encrypt, set thread to AES. Some platforms talk about “Banking Class public key cryptography”. What that should be, I know not. Technically, Thread uses a metric key, which is the same in the entire network. This is periodically changes so that if an attacker by e.g. Brute Force key can guess, only access to a limited time Record has.
To add new devices to an existing network integrating, asymmetrical encryption is used. In the event of a failure to comply with this Regulation, the competent authorities of the Member State concerned shall inform the competent authorities of the Member State concerned. someone wants to know exactly how this works, who can read this on the official website of thread.
Finally, CRC is also used to ensure the integrity of the data.

Conclusion

With this we have now received a short technical copy into the “new” thread protocol.
It is clear that thread in any case an enrichment for the Smarthome The world will be. However, thread is only a network protocol of many and unlike e.g. ZigBee, Thread needs another protocol for the user data.
Especially for HomeKit users thread is probably to be interesting. Outside of Apple, thread becomes more a Be complementary and not “change everything fundamentally”.

There are now the first devices on the market, which are more or function less stable, but thread is in the first release published. At the moment everything is new and the field use becomes Promote problems for days, which are then fixed.
A clearer Advantage, which I promise by thread is the possibility for sustainable products. Update management is simpler by thread and users do not have to do vie to update the devices.
Furthermore, Thread builds the way to a simple Smarthome with universal protocols, but this is from manufacturers dependent. There are already some modifications of the Log what is active on thread (Matter). When manufacturers decide to sell Matter Router, which with its own Devices can “more” then everything has not been much broke. Then where ZigBee is. Like Phillips Hue. With a general ZigBee Hub can be used to use the luminaires, but can only the Hue Bridge depict all the functionalities of a Hue lamp.
It is accordingly waiting. Who is already a working smart Home has, does not need to run to change everything to thread and also in the future there will be ZigBee, ZWave and other radios, which are used. This will not change in the next time.

Back…