I get the need for a physical display on a heating system. I went for a Nextion display, which I find I use much more than the smartphone when I want to see what the temperature is, or make a change. I only really use the Blynk option for turning the heating/aircon on when I’m out and about and what to come home to a house that nice and warm/cool.
100% agree with the other comments, bridged D1 Minis or NodeMCUs are a much better option.
Display is a must. It’s much faster to check status on screen than to find a phone, open an app. What happens when you lose internet. It’s really depends on location wordwide. We here in Croatia have awful internet connections and we lose connection often. I’ll check all suggestions. Did’n know you can bridge two modules.
Heh… I like them all. It just depends on what you want to do.
Mega & ESP-01 for massive IO and sufficient speed unless you are really pushing the timers and calculations… I am and it is still clocking along just fine.
ESP-01 solo for that wee little WiFi project that only needs a pin or two (or as Shield for existing Arduino projects that need a kick into IoT world, without massive rewrites)
ESP8266 (NodeMCU & Wemos) for both dev use or finished midsize projects
ESP32 (@oseloth Which is now as easy to install in the IDE as an ESP8266 and flashes the exact same way) for when you want a good combo of IO, clock speed and fansnazy built-in features (Touch pins, Dual Core, Multifunction pins, Ultra Low Power sleep mode). It is still new and has teething issues, but it is also the future.
RPi - pick a model based on needs… With my RPi3 nothing else I have can run as multiple Blynk Clients (JS & Python) while processing camera video, sourcing image files and running my Local Server, all at the same time (however, I do use the Ethernet, not WiFi, as I want my server link to be as solid as possible)
It seams that I found out what was buging my nodeMcu and loss of connection. Few days ago, just as this started I was testing a wifi repeater that I need for remote location. As I left it on to work in similar distance as my wifi modem, nodeMcu got confused and it was connecting from repeater to wifi to repeater and so on in loop. I turned it off few hours ago and reseting stoped. So it might be the case.
Yeap, I would do that usualy but this was just a plain test to check something and than I forgot about it pluged in a wall. But I am still checking to confirm if this was the cause.