[extoc Title=”Table of Contents”]
Keep your hands of our code
If you have the same interests as me, then you can probably relate the way these programming sessions go; one succes after another, you keep coding and trying hours after hours and once you stumble accross a setback, you can’t get your head around how this could have gone wrong? How can this result not be what I expected it to be? Taking a step back, literally, often shines a new light on your problem.
So I made myself a cup of tea and then I suddenly realised I have seen this behaviour before. Code protection. It is a thing. Often these microchips have some bits you can set after testing so no one is able to steal your code of the chip. So I retreived the code protection bits and I confirmed my worst nightmare at that moment: this chip was code protected. No easy way to get code from this chip. If you want to reset these bits, you have to erase the whole chip, but that would defeat the purpose of what I was trying to achieve: getting the firmware in the first place before writing to the chip.
Enjoyed reading your article, too bad you didn’t succeed.
I will check back later to see if you see if any progress has been made.
In the worst case,. I have disposed of my e-thermostaat and help is too late for me
Thanks for your response. For now I paid the 24 Euros so I can use the thermostat for at least another year. So probably no updates from my side, but if so I’ll let you know.
Maybe it is possible to read the thermostat thermometer and rig the + and – button so you can control it with an Arduino or Pi Zero? Or even a step further, connect said Arduino or Pi to read the data that is going to the LCD?
That’s probably feasible, however I doubt if that would be much less work than designing my own thermostat and letting my home automation system control it. If you already go the extra mile to get an additional device such as Arduino or Pi to read the pins, switching a relay and reading a temperature sensor is not that much work either though.
I wonder if you were able to make any progress. The next year (for prolongate the subscription) is coming.
I’m asking myself if it couldn’t be better to design an open source thermostat. But I also agree that another €23,40 shouldn’t be the problem.
In the end I did design a very simple ESP8266 thermostat which communicates via SSL to my MQTT server. I can control it with my Home Assistant installation. It’s been working okay but because it sometimes crashes and I have to manually repower it, I haven’t released it yet. It’s designed to always fail safely so the heating turns off so it’s no big deal but it’s not ready to release.
At the moment I am also considering flashing Tasmota, which I use for some of my lights. I think that is a better option.
So to answer your question: no progress with this project and I probably never will. The thermostat was never perfect in the first place.
Hi, thanks for this read! It’s a few years later now, and I was wondering if you ever did an attempt to try things out with the base station?
Hi Robert, no I did not. This Essent E-thermostaat ship has sailed for me. I have moved in the meantime and am running a heat pump system now, so I have little need to control my thermostat remote anymore.
Last week I tried to dump the firmware of the device using a PicKit2 programmer. After connecting succesfully, and giving the “read” command, the software says “Code protect”. So indead the PIC is read-protected 🙁