Due to the limited ressources of our IoT-devices we should try to optimize our code, in case we do not want to wait long time each time we access our nodes. In this post I will present you some simple tricks how you can make your device more reactive. The actions are listed from very quick steps to a bit more complex tasks. (May I am going to update this post after some time.)
One (or many) of my future projects - for example: a private telegram bot - will need a central always-on device. So I had to find a good device for this use-case. Some of my criteria were: "powerful"/modern CPU, enough RAM to do some tasks in a parallel way, Ethernet or Wireless LAN, at least one USB-port, small and reasonable! But the most important feature: It should be able to run Node.js!
In a recent project my designer told me: "Ok, we need a video in the background and some text in the foreground.". My first thoughts were "easy as pie".
The last few weeks showed us that the Internet-of-Things can be pretty dangerous, e.g.: Mirai Again: DT Outage a Precursor to Larger DDoS Attack. Especially if the devices are able to communicate with the internet there is a high risk! But I think this is not the only hazard. What happens if someone gets into your network because of an insecure device? This posting will list some actions the possible of such an attack.
If you follow my blog you will have noticed that my TemperatureNode is now in a working state. Yes, i know...it's functionality is very limited. But I will not stop here! But for now I am going to mount it a few metres away from my PC and i do not want to cary my node every time to my computer to flash it. The solution is named OTA-updates or in it's long version over-the-air-updates. In this short posting I am going to describe one of two ways to realize it.