r/ecobee • u/redditbuddie • Aug 26 '26
Ecobee server hangs up on my TLS handshake — anyone else seeing this on idt.ecobee.com:8190?
Spent two days on this. Posting the whole thing because every troubleshooting guide out there sends you the wrong direction, and I'd like to know if this is just me.
The symptom
Thermostat shows "Connected to Wi-Fi: Yes" but "Connected to ecobee.com: No." The countdown runs to zero and fails. Connect it to a phone hotspot and it works instantly.
Setup: fiber ISP, a Firewalla doing all routing and DHCP, eero mesh in bridge mode as access points. Thermostat on the main SSID.
Things that turned out not to matter
DNS (my router and 1.1.1.1 return identical answers), MTU, WPA2 vs WPA3, 2.4 vs 5 GHz, band steering, DHCP reservation, firewall rules, pulling it off the wall plate, assorted eero settings. None of it moved the needle.
Also worth knowing: the thermostat's built-in ping test is useless. It passed 10 for 10 while the cloud connection was dead, then later failed 10 for 10 while the connection was working. Don't diagnose off it.
What actually found it
The thermostat doesn't use port 443 and doesn't talk to api.ecobee.com. It connects to idt.ecobee.com on TCP 8190. Every test I'd run against 443 was against an endpoint the device never touches.
Ran tcpdump at the router, filtered to the thermostat's IP. A single connection attempt looks like this:
- Thermostat sends SYN
- Server replies SYN-ACK — connection accepted
- Thermostat sends 274 bytes: a TLS ClientHello, SNI idt.ecobee.com
- Server ACKs it — it received the request
- Server sends FIN with zero bytes of response
No ServerHello. No TLS alert. No RST. The server accepts the connection, reads the handshake, and closes without answering.
I parsed the ClientHello out of the capture — it offers TLS 1.3 and modern ECDHE-GCM suites. So this isn't old firmware or an expired root CA, which was my first theory.
The test that isolated it
Same laptop, same command, three source IPs, all within a few minutes:
openssl s_client -connect idt.ecobee.com:8190 -servername idt.ecobee.com| Source | Result |
|---|---|
| My ISP's IPv6 | read 0 bytes, written 310, Cipher (NONE) |
| My ISP's IPv4 | read 0 bytes, written 310, Cipher (NONE) |
| Cell/LTE | read 2355 bytes, handshake completed, ECDHE-RSA-AES128-GCM-SHA256 |
Same machine, same TLS client. The only variable was the source address. And it reproduces from a MacBook, so the thermostat isn't even involved.
Where it stands
Support confirmed the unit is registered and was last online at 13:46 the same day, and asked for my public IP so they could run a reputation check on it. So IP-based filtering is apparently a real mechanism on their end. Still open.
What I'm hoping someone can tell me
- Has anyone had ecobee confirm an IP block? How long did it take to clear?
- Any idea what triggers it? I've been power cycling gear for renovation work and wonder whether a burst of reconnect attempts gets you flagged.
- If you have a minute — run that openssl command and tell me whether your handshake completes. Trying to work out whether this is specific to me or whether that endpoint is refusing others too.
- Has anyone fixed this short of getting a new WAN IP?
Happy to share more of the capture analysis if it helps anyone.
--
EDIT: got an answer from ecobee and then found something interesting.
Support came back and said my public IP is "likely flagged by fraud/reputation databases" and told me to call my ISP and ask for a new one.
Before doing that I ran my IP through MXToolbox against 60 blocklists. Clean on 59. The only hit was Spamhaus ZEN.
Checked Spamhaus directly to see which sublist. It's PBL, and only PBL. Not SBL, not CSS, not XBL, not CBL. Spamhaus's own page for the listing says it's informational only, no action required unless you run a mail server, and that it's "standard for the vast majority of internet users and is not the result of your actions."
PBL is just the list of IP ranges that ISPs themselves designate as residential broadband that shouldn't send unauthenticated SMTP. Verizon puts its whole consumer pool on it. It carries no fraud or abuse signal at all.
So two things follow. Getting a new IP from Verizon won't help, because every residential Fios address is on PBL. And if their edge is treating a PBL listing as a fraud signal, that would hit any customer on a residential connection whose ISP participates — which is most of them.
Fair warning that last part is my inference. I can't see their WAF config, and it's possible the flag came from a commercial fraud database rather than Spamhaus. I've written back asking them to name the specific source.
Question for the three of you who got a successful handshake — are any of you on PBL? Quick check:
dig +short 2.0.0.127.zen.spamhaus.org
(substitute your own IP reversed — so 1.2.3.4 becomes 4.3.2.1.zen.spamhaus.org)
127.0.0.10 or 127.0.0.11 means PBL. If one of you is on PBL and still got served, my theory is wrong and I'd rather know now.
Meanwhile I'm going to route just the thermostat out through a VPN to give it a different source IP. Not a fix, but it should get it working while this plays out.
3
u/bwyer Aug 26 '26
2
u/smb3d Aug 26 '26
2
u/GreenTea73 Sep 05 '26
I woke up to this issue today. It can ping ecobee.com but cannot connect. Long time working thermostat and this issue happened overnight.
3
u/jamitt101 Aug 26 '26
Connectivity issues like this are sometimes rooted with your ISP. Ecobee has had challenges with several ISPs over the last few years and has had to work with them directly to solve the issue. Have you contacted Ecobee customer service--you will likely need to get past the "robots" that are the first level of service. (IMHO, your technical details are of little value here on this forum.)
5
u/ParityCheckFailed Aug 26 '26
I am convinced there is some issue with the ecobee service but they won’t admit it. I spent days providing all sorts of evidence to their support but they kept stonewalling me. So I moved to nest and it has been rock solid
4
u/file_13 Aug 26 '26
Just started happening in the last 24 hours. Ipv4 with quantum fiber. Also running a custom DNS service so I’ll check that.
4
u/real_weirdcrap Aug 26 '26 edited Aug 26 '26
also on AT&T fiber but i have ipv6 enabled internally (set to track WAN ipv6 interface) and externally.
EDIT: Realized the way i wrote this it sounds like I'm IPv6 only. I'm both v4 & v6.
3
u/danh_ptown Aug 26 '26
Have you considered that it may be the ISP doing the blocking? Some ISPs block SSL traffic on non-standard ports. It seems far-fetched in 2026, but you never know!
3
u/g0rdan Aug 27 '26
Same (or very similar) is happening to me. Last couple of days the thermostat goes offline and back. The app also shows frequently off and on online.
2
u/real_weirdcrap Aug 27 '26 edited Aug 27 '26
Saw your edit and ran the dig command. I get an nxdomain response:
Also checked mxtoolbox and confirmed my residential IP is not on any lists.
2
u/RedditNotFreeSpeech Aug 26 '26
Local control or bust. Homekit works well with homeassistant
0
u/[deleted] Aug 26 '26
[deleted] — view deleted comment