intermittent pyhtcc.pyhtcc.UnauthorizedError

[cjkrolak]

I have been seeing intermittent failures for pyhtcc.pyhtcc.UnauthorizedError since July 2023, maybe an artifact of changes made in 0.1.53. Traceback is below:

Traceback (most recent call last):
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/honeywell.py", line 218, in get_zones_info
    return_val = super().get_zones_info()
  File "/home/pi/.local/lib/python3.9/site-packages/pyhtcc/pyhtcc.py", line 684, in get_zones_info
    data = self._post_zone_list_data(page_num)
  File "/home/pi/.local/lib/python3.9/site-packages/pyhtcc/pyhtcc.py", line 618, in _post_zone_list_data
    return self._request_json(
  File "/home/pi/.local/lib/python3.9/site-packages/pyhtcc/pyhtcc.py", line 669, in _request_json
    raise UnauthorizedError("Got unauthorized response from server")
pyhtcc.pyhtcc.UnauthorizedError: Got unauthorized response from server

Sometimes the error is preceeded (triggered?) by one or more pyhtcc.pyhtcc.NoZonesFoundError exceptions (see below).

Traceback (most recent call last):
  File "/home/pi/github/ThermostatSupervisor/thermostatsupervisor/honeywell.py", line 218, in get_zones_info
    return_val = super().get_zones_info()
  File "/home/pi/.local/lib/python3.9/site-packages/pyhtcc/pyhtcc.py", line 686, in get_zones_info
    raise NoZonesFoundError("No zones were found from GetZoneListData")
pyhtcc.pyhtcc.NoZonesFoundError: No zones were found from GetZoneListData

Is anyone else seeing these errors?

[csm10495]

How long were you logged in with the same session/object before it happened? I wonder if the token times out or something.
My usage runs every minute to check / update the thermostats as needed. On each minute it gets a fresh PyHtcc object. I don't have this error in any logs for the last month or so.

[cjkrolak]

I re-login once every 24 hours. I poll the TCC website once every 10 minutes between logins. This failure happened on the 4th day of running, approximately 14 hours since the last login. Do you re-login every minute?

[csm10495]

Yep i login every minute (via getting a fresh obj)

(See next comment)

[csm10495]

Deleting the comment i just made since its wrong. In the worst case, i would login every minute. I actually only login if something changed from the control-side. If i change something via the webui or manually, it wouldn't know so it wouldn't login again until a planned schedule change happens.

In total i actually login only a few times a day.

[cjkrolak]

OK, I'll reduce my re-connect time from 24 hours to 8 hours and see if that resolves the issue. As I noted above, this is new behavior or a new failure message since about July of this year, so something must have changed on the TCC server side or the manifestation of this failure with the python code.

[csm10495]

Hopefully it helps out.

[cjkrolak]

updated, it failed again today, 6.3 hours since last login, I'm halving the login interval again to see if it helps.

[cjkrolak]

I don't think the login interval is going to fix my issue, I've reduced it down to 4.0 hours in between logins and still see the authorization errors, in the last run it occurred 1.2 hours after the last login. How often are you polling the TCC site? That's the next knob I will experiment with. I'm currently polling every 10 minutes.

[csm10495]

I poll on the temperature change in the schedule.

So I have a Google Sheet with times and temperatures. It polls that sheet every minute. If the time passes a timestamp on the sheet, it sends commands to match what that interval says and with that creates a new PyHTCC object to do the updates then moves on.

A special case is it skips updating if the last timestamp event is the same temperatures as this one (it caches that locally).

In total it logs in maybe 6 times a day max in the worst case with a lot of temperature changes. On each of those logins it does it's actions all within a minute before throwing out the object.

This allows me to manually change the thermostats and know that eventually the schedule will kick in again but not immediately overwrite what I did manually.

[cjkrolak]

@csm10495 so are you only hitting the TCC site about 6 times a day? In my case I'm hitting the TCC site every 10 minutes (144 times a day).

[csm10495]

Yep.

For fun I pickled a PyHTCC object and left it for a few days. Upon trying it again today, it still works too. No auth error or anything. I figured it would fail after leaving it stale for some time.

[cjkrolak]

anyone know how often a Honeywell thermostat talks to the TCC web site? I'm wondering if I'm hitting TCC too often with my script and triggering the AuthErrors as some type of DDOS defense

[csm10495]

No idea. I'm guessing it long polls or something like that.

For fun I'm running:

for i in range(250): 
    print(i, z.set_permanent_cool_setpoint(77))

and they all passed. So I didn't hit anything at least yet.

[csm10495]

Did the same thing 1000 times, to no issue either. I figured that would hit something but I guess not.