Ecobee thermostat can’t connect to servers
-
Ok what I would do here is connect it behind pfSense, where it presumably will initially be working, and note the connections it opens to the servers.
Then compare that with the open connections when it stops working.
Two weeks is an odd period of time. It's hard to think what might change in that time. Your public IP changes perhaps?
Some server address resolves to something different? Maybe the Cisco router is not resolving directly and pfSense is?
-
@ezhawk Your IP address might be getting blacklisted by Ecobee servers. I’m not sure which provider they use to host their services, but it could be blocking your ip for doing fishy activities online. Are you running any services that are possibly scraping the internet or continuously attempting to reach the internet anything that could determine your IP to be fishy? In my case I was running a service that was testing proxy urls to check which ones worked non stop 24/7. After I put that service on a vpn I have had no issues with Ecobee lol… So this may not even be a Pfsense issue for you..
-
@stephenw10 said in Ecobee thermostat can’t connect to servers:
Ok what I would do here is connect it behind pfSense, where it presumably will initially be working, and note the connections it opens to the servers.
Then compare that with the open connections when it stops working.
------The last time I looked at the states for the Ecobee between when it was and wasn't working, nothing was different.Two weeks is an odd period of time. It's hard to think what might change in that time. Your public IP changes perhaps?
-----My public IP doesn't change until I spoof macs to get a new one. As soon as I get a new one, it'll start working. It is almost like the connection gets stale and doesn't refresh. I've tried deleting all states, but that didn't resolve it either.Some server address resolves to something different? Maybe the Cisco router is not resolving directly and pfSense is?
---My clients do not use pfSense as a resolver or the Cisco. I have my own DNS servers that are being used regardless if the connection is going out the pfSense or the Cisco.@xmacj said in Ecobee thermostat can’t connect to servers:
@ezhawk Your IP address might be getting blacklisted by Ecobee servers. I’m not sure which provider they use to host their services, but it could be blocking your ip for doing fishy activities online. Are you running any services that are possibly scraping the internet or continuously attempting to reach the internet anything that could determine your IP to be fishy? In my case I was running a service that was testing proxy urls to check which ones worked non stop 24/7. After I put that service on a vpn I have had no issues with Ecobee lol… So this may not even be a Pfsense issue for you..
No, I don't have any services that do scraping. Also, I had this same exact problem with Google Nest as well. I thought it might of been Google so I switched to Ecobee and still have the same problem.
-
Hmm, states may be the same. The client device will still be trying to reach the servers. Or should be at least. But perhaps the servers just stop responding?
-
@stephenw10
If the servers just stop responding, why do they only stop responding behind pfSense and not when it is behind a Cisco device? -
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?
-
@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?
-
@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.
