Connection refused while upgrading basic_pellet_stove firmware

ESPHome
1

I’d like to troubleshoot this error but I am not a programmer; I am (or was) a network technician. The pellet stove works just fine, so if I don’t figure it out there’s no loss. It’s more that errors like this just pique my curiosity, and I want to fix them. The error message:

INFO Successfully compiled program.
INFO Connecting to 192.168.50.126 port 3232...
ERROR Connecting to 192.168.50.126 port 3232 failed: [Errno 111] Connection refused
ERROR Connection failed.
2

could be your router the DHCP how many connection you got on your network.

3

The error message does say the connection (this likely means it was able to find the IP address, but probably not) was refused.

I would make sure I really knew what the IP address was and that it was correct.

I would also use USB/serial to do the connection and not OTA. That will likely reduce the number of things that have to be correct to achieve success.

4

The point is that it has worked fine for 2 years now, both in service and when doing firmware updates, so why did it all of a sudden stop working? The ip address is correct; this device has a dhcp reservation. Why it stopped being able to successfully update firmware but yet still work normally as a pellet stove is what I want to find out.

5

That’s the funny thing, most things work fine until they don’t and the challenge is always figuring out why. Some people REALLY want to know why, many people just want it fixed.

I don’t believe anyone out here can tell you why your device is not working in your environment right now, even knowing that it used to work fine previously. You will need the be, at least, the eyes and ears of the people playing detective. Figuring out these types of issues is always some detective work.

You said you were a network technician. Did you capture a packet trace and look at the communication between the two devices? With what? Over the air or just on the wired network!? What did it show?

The message to me says the host (the one trying to do the update) contacted the esphome device at the IP level on the listed port and the connection was refused. It didn’t say it couldn’t connect. It said the connection was refused. What does the packet capture show? That is what I would want to know.

But, that still wouldn’t say WHY the connection was refused (assuming it was).

Unless I REALLY wanted to know WHY, I would just flash it with USB. If I had this problem several times and I REALLY wanted to KNOW, I might decide to look deeper.

I keep track of how often my devices reboot. I don’t usually look at the data, but I did recently and saw many of my devices rebooting due to things other than a power failure. At first I blamed esphome, the I looked and saw my Tasmota devices were doing the same thing (not at the same time). Since everything is still working, I could just ignore it. I am going to dig a little deeper and see if I can learn the restart reason (log it) so I can know what to look at next. I expect it will take some time to figure out. I am not sure how much I really care as things are working, but it is a good idea to figure it out.

1 Like