{"id":37423,"date":"2019-10-31T22:17:33","date_gmt":"2019-10-31T19:17:33","guid":{"rendered":"https:\/\/prohoster.info\/blog\/shiotiny-ventilyatsiya-vlazhnogo-pomeshheniya-proekt-primer\/"},"modified":"2019-10-31T22:17:33","modified_gmt":"2019-10-31T19:17:33","slug":"shiotiny-ventilyatsiya-vlazhnogo-pomeshheniya-proekt-primer","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/shiotiny-ventilyatsiya-vlazhnogo-pomeshheniya-proekt-primer","title":{"rendered":"ShIoTiny: ventilation of a humid room (example project)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"ShIoTiny:<\/p>\n

Main theses or what this article is about<\/h4>\n

\nWe continue the series of articles on ShIoTiny<\/b> \u2014 a visually programmable controller based on a chip ESP8266<\/b>.<\/p>\n

This article explains, using the example of a project for controlling ventilation in a bathroom or another room with high humidity, how to build a program for ShIoTiny<\/b>.<\/p>\n

The previous articles in the series.<\/h4>\n

\nShIoTiny: small automation, Internet of Things, or 'half a year before vacation'<\/a><\/noindex>
\nShIoTiny: nodes, connections, and events or features of program visualization<\/a><\/noindex><\/p>\n

Links<\/h4>\n

\nBinary firmware, controller schematic, and documentation<\/a><\/noindex>
\nInstructions and description of the nodes<\/a><\/noindex>
\nSetting up the MQTT broker cloudmqtt.com<\/a><\/noindex>
\nMQTT dashboard for Android<\/a><\/noindex>
\n<\/a><\/noindex><\/p>\n

Introduction<\/h4>\n

\nUnderstanding comes from experience. This is a truth proven by time and generations. Thus, there is nothing better for learning practical skills than trying to do something on your own. Examples that illustrate what can be done and what should be avoided will come in handy here. Others' mistakes may not prevent your own failures, but they can help reduce their number.<\/p>\n

Questions and letters from readers of previous articles prompted me to create a small example project for controlling ventilation to demonstrate how ShIoTiny nodes work.<\/p>\n

The original idea upon which the controller was based ShIoTiny<\/b> \u2014 a pump-irrigation station \u2014 won't suit everyone and may not be of interest. Therefore, I chose a universally understood and useful ventilation control system as an example.<\/p>\n

I should mention that the project idea is not mine; I derived it from here<\/a><\/noindex> and then adapted it to ShIoTiny<\/b>.<\/p>\n

First, understand what you want<\/h4>\n

\nThe process of improvement is infinite. This characteristic has led to the downfall of many good ideas and projects. Instead of releasing something that, while not perfect, is functional, developers often continue perfecting it. They refine it until their competitors surpass them by launching something that, albeit imperfect (and often downright shabby), works.<\/p>\n

Therefore, it is crucial to know where to draw the line in a project. In other words, we need to determine what we want to achieve at the end of the project based on what we have at the beginning. In Russian, there is a wonderful concise term 'plan' for a document created specifically to describe the process of creating something, which lazy translators and deficient managers have recently bizarrely started calling a 'roadmap.' But let that be.<\/p>\n

Our plan will be as follows. Let's assume there is a room where the humidity can sometimes rise significantly, such as a bathroom or kitchen. Humidity is unpleasant, and the time-honored way to combat it is to ventilate the space. There are many methods of ventilation. However, we'll skip over exotic and outdated methods such as fans operated by people and focus on a regular fan. Fans are cheaper and easier to find in our area.<\/p>\n

In short, we want to control the fan: turn it on and, accordingly, turn it off. More precisely, we want it to turn on and off automatically as needed.<\/p>\n

Now we need to determine the conditions under which the fan should turn on and the conditions under which it should turn off.<\/p>\n

This is quite obvious: if the humidity exceeds a certain threshold, the fan turns on and exhausts the air; if the humidity normalizes, the fan turns off.<\/p>\n

An observant reader will immediately latch onto the word \"threshold.\" Set by whom? How is it set?<\/p>\n

The threshold humidity can be set in several ways. We will consider two of them: the first \u2014 using a variable resistor, and the second \u2014 via the network using the MQTT protocol. Each of these methods has its advantages and disadvantages, which will be discussed later.<\/p>\n

For those who didn't understand, let me clarify that \"threshold humidity\" is the level of humidity at which the fan must be turned on.<\/p>\n

The next question is whether to give the user the right to turn on the fan directly. That is, regardless of the humidity level, at the push of a button? We will provide such an option. After all, the fan may be needed not only when the humidity is high but also to eliminate, for example, unpleasant odors, commonly referred to as \"stench.\"<\/p>\n

So, we understand what we want and even a bit about how it will work. Let's briefly list all the functions of our ventilation control system:<\/p>\n