Ecobee thermostat can’t connect to servers
-
@stephenw10 said in Ecobee thermostat can’t connect to servers:
Good question. And they may not stop responding. We need to gather more data from the failed situation.
I assume you see nothing blocked in the logs?
I've put my Ecobee back through the pfSense. We'll see how long it lasts until it stops connecting. I did just update to 25.07.1 on the pfSense yesterday.
@GPz1100 said in Ecobee thermostat can’t connect to servers:
@ezhawk When behind pfsense, and lost ecobee connectivity, did you try rebooting the ecobee?
You can reboot it by pulling it off the wall, or a better way is flip the breaker for the hvac system. Leave it off a few sec, then turn it back on.
As I mentioned earlier in this thread, the only issues i've had with ecobee have been with the lite version where after a period of time it would develop morse code in the data. Likely due to a memory leak or some run away process. Rebooting it would fix this for a while. Ecobee eventually replaced the unit with the premium (which has better cpu/more ram), which hasn't has this issue.
Edit: I didn't have to make any special adjustmentsfor pfsense states/ecobee client settings. Whatever default state timeouts are in place work fine here.
Is the cisco router using the same primary internet connection as pfsense?
I've rebooted the Ecobee countless times. If that was the fix, I'd be glad, but it isn't. I don't have a lite, I have a premium.
Yes, the Cisco and pfSense are literally plugged into the same modem with each device getting its own unique public IP.
-
@ezhawk Each firewall is getting a different public ip. That complicates things.
Test with the same public IP for each device.
-
@GPz1100 said in Ecobee thermostat can’t connect to servers:
@ezhawk Each firewall is getting a different public ip. That complicates things.
Test with the same public IP for each device.
I cannot run both at the same time with having the same IP and I also don't have static IPs. As I've said multiple times, behind pfSense it'll work for a few weeks and the stop. The temp fix is to spoof and get a new IP. I had the Ecobee behind the a Cisco with the same IP for more than 2 months and it never dropped once. I've been through more than a dozen different IPs trying to figure it out by using spoofing methods. The IP itself isn't the issue.
-
And just to confirm when this happens everything else behind pfSense remains functional? Only the Ecobee seems to be affected?
-
@stephenw10 said in Ecobee thermostat can’t connect to servers:
And just to confirm when this happens everything else behind pfSense remains functional? Only the Ecobee seems to be affected?
That is correct. Every other device that goes through the pfSense works normally.
-
@stephenw10
well, that didn't take long. once again, behind the pfsense my ecobee now shows disconnected. Network connectivity is all up. I can ping out from the ecobee by ip and dns name, but the pfsense is blocking its connection to the ecobee.com servers. -
@ezhawk said in Ecobee thermostat can’t connect to servers:
but the pfsense is blocking its connection to the ecobee.com servers.
Blocking : what pfSense rule blocks traffic from the bee ?
Can you list the firewall rules on that LAN ?
Is the bee set up to use DHCP ? If so : read How to change Kea DHCP log level so now you know how to log DHCP leases : and the question is : did it get a DHCP lease (that is an IP, a network, a gateway, a DNS - check these all) ?
If static : what is it's setup ? -
Mmm, what connection is actually being blocked?
If you kill all the states from the thermostat and allow it to open new states does that fix the connection? If not do any of those states have one way traffic with no replies?
-
Under steady state conditions I show the ecobee premium connecting to a single ip.
and periodic connections to the dns server (x.y.100.2).
Using any packages that may be doing traffic inspection?
-
I've killed all the states and the connection doesn't restore. I reboot the ecobee and after letting everything come up clear out these are what i'm left with for states and the ecobee cannot connect to the ecobee servers.
(I had this exact same issue with Google Nest and assumed it was something with Nest which is why I now have an ecobee.)
-
Hmm, OK so two way traffic but both state sets are in FIN-WAIT rather than established and only 4 packets.
Try pcapping that traffic and see what's going on.
Interesting that it's the same remote address for both of you.
Can you try routing that traffic over a VPN to get a completely different source IP?
-
I did pcaps from the WAN and LAN and rebooted the ecobee each time but not sure exactly what i'd be looking for in the pcap. I don't have a VPN to route traffic over.
-
I'm away right now so I can't setup a drop-link. But do the captures show just the 4 packets shown in the state table for each connection?
-
@stephenw10
i see some fin acks both ways. after a while all the states drop and then it comes back and in the states it just sits at fin wait. -
Can we see the pcap from the pfSense gui with the TCP flags? You can obscure the IPs if you need.
We need to see which side stops responding.
-
-
Hmm, interesting. That dupe ACK is odd. Like the server expects to see something from the client and doesn't. Except the dupe comes 12 microseconds after the first. Other than that it looks like a pretty normal TCP connection. The client just isn't sending or pulling anything. I do note there are no large packets shown. But they are not present on either interface. pfSense seems to be passing that traffic as expected.
Even when the dupe ACK doesn't happen the server sends a fin-ack pretty much immediately. -
@ezhawk re vpn
You can set up a free cloudflare warp wireguard connection using this project - https://github.com/ViRb3/wgcf .
From the releases page download the one appropriate for your pfsense architecture (or a linux vm).
Run
wgcf registerthenwgcf generateThis will create a .conf file from which you can pull the necessary credentials to supply pf's wg package. Use policy based routing to pass ecobee traffic through the cf tunnel. Don't forget to create an outbound nat rule.
-
@stephenw10 It would be interesting to compare the state timeout values between pfsense and the other firewall @ezhawk is using. Possible some values are longer in pfsense and/or not playing nicely with the isp?
Looking at the pfs/system_advanced_firewall.php page, all mine are default. WAN MTU at 1500 too (att fiber connection).
-
@GPz1100
mine are all default in the firewall settings too. WAN mtu is actually just using the adaptors default. Don't have any defined MTU.
