Lesson 6 - Water-Monitor/IoT-Portfolio-FJS GitHub Wiki

This lesson we worked on:

• Introduction IoTEmpowered
• Communicate with hardware over MQTT

Reflection Stijn

The introduction of IoTEmpowered was for me too long. I understand that for the teacher it is his lifework and he is really proud of it, but it does not really interest me. I am interested in using his framework and create programs and products with it myself by using IoTEmpowered.

It was refreshing to see that a lot of things that I have been using in the past lessons are actually part of IoTEmpowered. I know that it is told to me, but I did not really categorize it until this lesson. On the otherside it also made me a little bit sad, because running a mqtt_broker, hosting an accesspoint and running node-red is all very easy and very helpfull while programming IoT. I would like to see those things implemented in such an easy way in other applications or frameworks as well. On the otherhand, I am always able to clone and use his github project.

The fact that there is also an observability pattern implemented gives space for more complex systems and specific implementations. I think the system could be implemented in companies as well as for schools. Even only with the Accesspoint and MQTT-broker for example is it already totally worth it to implement it in your company.

Besides the fact that I could not really work by myself, because of the naming conflicts in the beginning, when it worked, I was really happy. I love the fact how sensors talk with each other, it just makes me happy for some reason.

Reflection Fadi

In this lesson, we got a deeper view of IoTempower, in the lesson before we tried it out but I did not really understand the concept of IoTempower. The more I got to know how IoTempower worked the more I liked it actually, I think it's important to first learn the basics and how it works from the beginning because in IoTempower you only need to use prepared codes that do the job for you. Im looking forward to learn more about IoTempower.

Reflection Johanna

When we had to do the scaling&testing part, I was very overwhelmed. I was not really sure how to answer the questions and what my wishes could be, since I am not familiar with working on other frameworks. My horizon is (or was) very small, if it is about IoT. So, it felt more like forcing myself to find some answers that might not really fit. The start with iotempower was a bit overwhelming as well, but after doing the first steps on my own, I felt more self-assured. Overall, I don't want to return to iotempower anymore, after understanding it.