/lm.png
IoT Advisor and Developer helping SMB companies create enterprise-grade solutions.
I provide AGREED VALUE in a DEFINED TIMEFRAME for the FIXED PRICE under CLEAR CONDITIONS.

The state-of-the-art IoT implementation at Tesla

Disclaimer: I do not have any relation with Tesla. To write this post, I used publicly available information shared by Tesla (mainly from the 2023 Investor Day). This is my personal interpretation of those materials. Tesla 2023 Investor Day Recently I watched the Tesla 2023 Investor Day video on YouTube. It was a very interesting presentation on the world-class Industrial Internet of Things deployment. I noticed many insights that I would like to share with you.

Warszawskie Dni Informatyki 2023 - VoD

I recorded a VoD for the Warsaw IT Days conference. In my video, I covered the general introduction to the Internet of Things and reviewed the AWS IoT Core service. I will share my presentation and code samples soon! Subscribe to my newsletter if you want to receive the notification.

IoT Thing does not represent an IoT Device connected to the AWS IoT Core.

I often say that the IoT Thing is a virtual representation of a physical device or logical entity (for instance, an application). Today, I want to be more specific than that. The IoT Thing stores the metadata describing the IoT Device. By metadata, I mean: Thing Name Thing Attributes Thing Type Thing Group Device Shadow But IoT Thing does not store the identity of a related IoT Device. The X.509 Certificate registered in the AWS IoT Core represents the connected IoT Device.

How can we trust the AWS IoT Core?

Introduction Today I will explain how connected devices can establish trust with the AWS IoT Core. To trust someone, we need to confirm their identity. The same is true in the ecosystem of connected devices. AWS IoT Core exposes an MQTT Broker so devices can establish the MQTT connectivity. What if some villain actor creates an MQTT Broker and tries to mislead devices? Is there a way to verify the real identity of the exposed endpoint?

The Architecture Review outcomes

The Architecture Review is a very tricky task not only because of the technical aspects. I find the Architecture Review challenging because of my expectations. When hired to do the Architecture Review, I should find some areas of improvement. I know that isn’t true, but my subconscious can not accept that. The Architecture Review is not about finding something - it is about reviewing the existing design. There are two outcomes of that review:

Gateway vs. Gateway-less Industrial IoT considerations

Introduction In this post, I will describe two approaches to the Industrial Internet of Things deployments and provide my perspective. Hopefully, it will help you choose the proper architecture for your specific case. Before we start, I will briefly define the Edge Gateway. Definition of the Edge Gateway Edge Gateway is a computer located inside a factory or some other facility. That computer is connected to the internal network and can communicate with local devices using industrial protocols.