Quick navigation
Fico pred samitom EÚ: Podporujeme integráciu Ukrajiny do Únie
Oct 22 2025
4 min read
In some of the previous blogs, I wrote a lot about the IoT platform from Total.js. Like what it is, why it can be useful, how to install individual parts to get it working, and how to set it up and start using it. But there is still one part of the platform that has to be created or modified especially for your case. And those are drivers.
We published some of the custom drivers we used before, but now we have added universal drivers. These drivers are ready to use. We created universal drivers for the electrometer, weather, meteo data, and switch. In this blog, I will introduce them to you. You can use them as they are, create new drivers based on principles used in these drivers, or modify them for your case. Also, I will show you how to add a sensor to one of them, so you will be able to adjust them correctly for your case.
The difference I want to point out first is that we changed devEUI in the received JSON to id. If you are new here, just take it as best practice. If you used one of the drivers with an older JSON schema, be careful now, the old one was because of a custom implementation.
Each of these drivers is for a different device. We created them based on specifications so they can fit easily into any device of their own type. If you need to do some modifications, it is very easy with little knowledge about drivers, which you can get in the Total.js documentation, and some basic programming skills.
Each driver has its own properties that can be processed, and there is a possibility of setting a Token. This token is for security reasons. If you set some value there, each received message has to include the same value in the received headers in the property x-token. This will be validated, and if the received header value is different, the driver will not process any data from that request. If you do not set any value to this token, validation will be skipped, and every request will be processed. In some of the previous blogs, I wrote a lot about the IoT platform from Total.js. Like what it is, why it can be useful, how to install individual parts to get it working, and how to set it up and start using it. But there is still one part of the platform that has to be created or modified especially for your case. And those are drivers.
We published some of the custom drivers we used before, but now we have added universal drivers. These drivers are ready to use. We created universal drivers for the electrometer, weather, meteo data, and switch. In this blog, I will introduce them to you. You can use them as they are, create new drivers based on principles used in these drivers, or modify them for your case. Also, I will show you how to add a sensor to one of them, so you will be able to adjust them correctly for your case.
The difference I want to point out first is that we changed devEUI in the received JSON to id. If you are new here, just take it as best practice. If you used one of the drivers with an older JSON schema, be careful now, the old one was because of a custom implementation.
Each of these drivers is for a different device. We created them based on specifications so they can fit easily into any device of their own type. If you need to do some modifications, it is very easy with little knowledge about drivers, which you can get in the Total.js documentation, and some basic programming skills.
Each driver has its own properties that can be processed, and there is a possibility of setting a Token. This token is for security reasons. If you set some value there, each received message has to include the same value in the received headers in the property x-token. This will be validated, and if the received header value is different, the driver will not process any data from that request. If you do not set any value to this token, validation will be skipped, and every request will be processed.In some of the previous blogs, I wrote a lot about the IoT platform from Total.js. Like what it is, why it can be useful, how to install individual parts to get it working, and how to set it up and start using it. But there is still one part of the platform that has to be created or modified especially for your case. And those are drivers.
We published some of the custom drivers we used before, but now we have added universal drivers. These drivers are ready to use. We created universal drivers for the electrometer, weather, meteo data, and switch. In this blog, I will introduce them to you. You can use them as they are, create new drivers based on principles used in these drivers, or modify them for your case. Also, I will show you how to add a sensor to one of them, so you will be able to adjust them correctly for your case.
The difference I want to point out first is that we changed devEUI in the received JSON to id. If you are new here, just take it as best practice. If you used one of the drivers with an older JSON schema, be careful now, the old one was because of a custom implementation.
Each of these drivers is for a different device. We created them based on specifications so they can fit easily into any device of their own type. If you need to do some modifications, it is very easy with little knowledge about drivers, which you can get in the Total.js documentation, and some basic programming skills.
Each driver has its own properties that can be processed, and there is a possibility of setting a Token. This token is for security reasons. If you set some value there, each received message has to include the same value in the received headers in the property x-token. This will be validated, and if the received header value is different, the driver will not process any data from that request. If you do not set any value to this token, validation will be skipped, and every request will be processed.
We published some of the custom drivers we used before, but now we have added universal drivers. These drivers are ready to use. We created universal drivers for the electrometer, weather, meteo data, and switch. In this blog, I will introduce them to you. You can use them as they are, create new drivers based on principles used in these drivers, or modify them for your case. Also, I will show you how to add a sensor to one of them, so you will be able to adjust them correctly for your case.
The difference I want to point out first is that we changed devEUI in the received JSON to id. If you are new here, just take it as best practice. If you used one of the drivers with an older JSON schema, be careful now, the old one was because of a custom implementation.
Each of these drivers is for a different device. We created them based on specifications so they can fit easily into any device of their own type. If you need to do some modifications, it is very easy with little knowledge about drivers, which you can get in the Total.js documentation, and some basic programming skills.
Each driver has its own properties that can be processed, and there is a possibility of setting a Token. This token is for security reasons. If you set some value there, each received message has to include the same value in the received headers in the property x-token. This will be validated, and if the received header value is different, the driver will not process any data from that request. If you do not set any value to this token, validation will be skipped, and every request will be processed. In some of the previous blogs, I wrote a lot about the IoT platform from Total.js. Like what it is, why it can be useful, how to install individual parts to get it working, and how to set it up and start using it. But there is still one part of the platform that has to be created or modified especially for your case. And those are drivers.
We published some of the custom drivers we used before, but now we have added universal drivers. These drivers are ready to use. We created universal drivers for the electrometer, weather, meteo data, and switch. In this blog, I will introduce them to you. You can use them as they are, create new drivers based on principles used in these drivers, or modify them for your case. Also, I will show you how to add a sensor to one of them, so you will be able to adjust them correctly for your case.
The difference I want to point out first is that we changed devEUI in the received JSON to id. If you are new here, just take it as best practice. If you used one of the drivers with an older JSON schema, be careful now, the old one was because of a custom implementation.
Each of these drivers is for a different device. We created them based on specifications so they can fit easily into any device of their own type. If you need to do some modifications, it is very easy with little knowledge about drivers, which you can get in the Total.js documentation, and some basic programming skills.
Each driver has its own properties that can be processed, and there is a possibility of setting a Token. This token is for security reasons. If you set some value there, each received message has to include the same value in the received headers in the property x-token. This will be validated, and if the received header value is different, the driver will not process any data from that request. If you do not set any value to this token, validation will be skipped, and every request will be processed.In some of the previous blogs, I wrote a lot about the IoT platform from Total.js. Like what it is, why it can be useful, how to install individual parts to get it working, and how to set it up and start using it. But there is still one part of the platform that has to be created or modified especially for your case. And those are drivers.
We published some of the custom drivers we used before, but now we have added universal drivers. These drivers are ready to use. We created universal drivers for the electrometer, weather, meteo data, and switch. In this blog, I will introduce them to you. You can use them as they are, create new drivers based on principles used in these drivers, or modify them for your case. Also, I will show you how to add a sensor to one of them, so you will be able to adjust them correctly for your case.
The difference I want to point out first is that we changed devEUI in the received JSON to id. If you are new here, just take it as best practice. If you used one of the drivers with an older JSON schema, be careful now, the old one was because of a custom implementation.
Each of these drivers is for a different device. We created them based on specifications so they can fit easily into any device of their own type. If you need to do some modifications, it is very easy with little knowledge about drivers, which you can get in the Total.js documentation, and some basic programming skills.
Each driver has its own properties that can be processed, and there is a possibility of setting a Token. This token is for security reasons. If you set some value there, each received message has to include the same value in the received headers in the property x-token. This will be validated, and if the received header value is different, the driver will not process any data from that request. If you do not set any value to this token, validation will be skipped, and every request will be processed.
Similar posts
Popular tags