Chat freely about anything...

User avatar
By sylayo
#37771 Hi,
I have a small project: Add a thermostat in my workshop to control the heater automatically and be able to manually raise the temperature from my phone before to go to work in it. Based on what I've read, I would be able to do this with only an ESP8266 (no Arduino).

I've been looking at some example for some time but I need some clarification. I've been looking in a few forum but I can't figure it out. Maybe somebody could point me in the right direction.

Here are some of my questions:
- It looks like there are many approach to program that board: AT, LUA... What are their differences?
- I have a bit of experience in Arduino, is one would be better for me?

Thanks
User avatar
By eduperez
#37865 If you have experience using Arduinos, I would definitively go for the Arduino sketches; I do not see any advantage using another language.
User avatar
By krzychb
#37872 @ sylayo,

As indicated by eduperez If you have experience using Arduino, go for the Arduino sketches.

If you are looking for “some example” check this step by step guide. This is hygrostat project using DHT22 sensor (Digital Humidity and Temperature sensor). Instead of reading humidity, read temperature from this sensor. Instead of humidifier, connect the heater and you will have a thermostat.

If your workshop is in coverage of your home Wi-Fi and you would like to operate thermostat from your phone connected to the same Wi-Fi then this guide has all you need. If you would like to operate thermostat using your phone outside of your home Wi-Fi, then check this post.

Hope this helps and good luck with your workshop automation project!


Krzysztof
User avatar
By jeffrey92
#37927 Figure out how to do it on the arduino (the manual raising/lowering), then hook the arduino up to the esp8266 and communicate via serial. Personally I would just go straight ESP8266 to simplify the design but C is not everyone's forte. But I disagree that an Arduino alone is any good. For IoT applications Arduino's just don't cut it. Not enough ram, crappy hardware, buggy code... No bueno