Device randomly stops reporting to Anantha. Have to power cycle thermastat

[gokou340]

I seem to be having an issue where the thermostat stops reporting or Anantha stops reporting stats. Causing the AC or furnace not to kick on until its power cycled.

The logs show the following:
21:40:54.403434 serve.go:417: HTTP Req from 10.9.201.62:27499: www.api.ing.carrier.com.
21:41:24.412648 serve.go:417: HTTP Req from 10.9.201.62:27499: www.api.ing.carrier.com.
21:43:19.502879 serve.go:417: HTTP Req from 10.9.201.62:19894: www.api.ing.carrier.com.
21:43:24.474978 serve.go:417: HTTP Req from 10.9.201.62:19894: www.api.ing.carrier.com.
21:43:39.478966 serve.go:417: HTTP Req from 10.9.201.62:19894: www.api.ing.carrier.com.
21:44:09.495924 serve.go:417: HTTP Req from 10.9.201.62:19894: www.api.ing.carrier.com.
21:45:04.548208 serve.go:417: HTTP Req from 10.9.201.62:2231: www.api.ing.carrier.com.
21:46:42.876311 serve.go:404: MQTT Req from 10.9.201.62:2749: mqtt.res.carrier.io.

But nothing happens. After power cycling, it gets the certificate and then starts properly reporting. However, for the last updated area, the time and date is wrong.

I have to switch back to a regular firmware for now because I can't have the heat in the house getting up to 85. I'm happy to try new versions after they are released!

Thank you for this software!

[anupcshan]

@gokou340 I had a very similar issue as well for several weeks. It turned out to be an issue with how the thermostat connected to my Wifi AP (Unifi NanoHD). It turned out that this AP has intermittent dropout issues with 2.4GHz devices. It appeared like packets would flow only in one direction (thermostat -> Anantha) but not the other.

My solution was to run an access point on a Raspberry Pi 4 instead - I've not had any dropout issues since then. This AP is only used by the thermostat and the Pi is running nothing else (not even Anantha).

What Wifi AP are you using?

[gokou340]

@gokou340 I had a very similar issue as well for several weeks. It turned out to be an issue with how the thermostat connected to my Wifi AP (Unifi NanoHD). It turned out that this AP has intermittent dropout issues with 2.4GHz devices. It appeared like packets would flow only in one direction (thermostat -> Anantha) but not the other.

My solution was to run an access point on a Raspberry Pi 4 instead - I've not had any dropout issues since then. This AP is only used by the thermostat and the Pi is running nothing else (not even Anantha).

What Wifi AP are you using?

Hello! I have 3 Unifi APs. 2 U6 Pros and 1 U7 Pro. However, it mainly stays on one of the two U6 Pros. Is this a Thermostat only issue, as none of my other 2.4 devices have this type of issue. It is also a 2.4 only network

[anupcshan]

@gokou340 I had a very similar issue as well for several weeks. It turned out to be an issue with how the thermostat connected to my Wifi AP (Unifi NanoHD). It turned out that this AP has intermittent dropout issues with 2.4GHz devices. It appeared like packets would flow only in one direction (thermostat -> Anantha) but not the other.
My solution was to run an access point on a Raspberry Pi 4 instead - I've not had any dropout issues since then. This AP is only used by the thermostat and the Pi is running nothing else (not even Anantha).
What Wifi AP are you using?

Hello! I have 3 Unifi APs. 2 U6 Pros and 1 U7 Pro. However, it mainly stays on one of the two U6 Pros. Is this a Thermostat only issue, as none of my other 2.4 devices have this type of issue. It is also a 2.4 only network

Based on https://gist.github.com/Fanman03/72ae53516a7d610e1150c1524f8b7237, U7-Pro might have issues with 2.4GHz devices. I'm know that my issues went away after I switched to using a Raspberry Pi as the AP - nanoHD was definitely the component causing issues. I'd suggest trying it out to confirm/rule-out if Wifi is the issue.

... that being said, its also possible that having the MQTT endpoint with very low RTT from the thermostat might be triggering some kind of bug in the firmware TCP stack causing it to hang and require a reset from time to time. I'll experiment with introducing some delays when I get some time.

I was hoping to switch to a U6-Pro in the future to not need the Pi AP workaround, but your experience is giving me pause :(

[gokou340]

I can confirm that the thermostat never went to the U7 Access point. Stayed on the U6 Pro