Improve auth-flow & check killswitch every 15min

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object

[jacobbaungard]

Auth flow
Instead of doing a full login flow at every update (i.e 1 min interval from HA), we re-use the JWT token if possible. If the JWT token is expired, we refresh the token if possible, instead of running the full login flow. This should be a much more efficient flow. When checking expire of the jwt/refresh token, we add a one minute margin, to ensure clients have time to complete their requests after the login flow.

Clients will need to pass in (by reference) a CheckwattStateInfo. This is meant to keep the state in memory between multiple CheckwattManagers (HA creates a new one every update, perhaps that can be changed in the future).

Kill switch
It turns out the checking of the killswitch is what causes the 429 seen in various installations. After agreement
with CW, with this PR we check it only every 15minute, which should lower the load on CWs server significantly.

On startup we check the killswitch immediately, and then generate a random time interval for the next check. This should ensure the load gets evenly spread out between installations.

Testing
I've tested this quite a bit over the last week or so, making adjusts as I go. Everything seems to work fine, although in my installation I still get 429s when checking the killswitch - likely we'd need many people to update before we see the effect of this change.

If someone wants to test this on an actual HA installation, this is how I've run my docker-based HA installation:

• Create a new dockerfile for HA:

FROM homeassistant/home-assistant:2025.8.3
RUN git clone -b check-jwt-expiry https://github.com/jacobbaungard/pyCheckwatt.git /tmp/pyCheckwatt
RUN pip install -e /tmp/pyCheckwatt/

• Build the a new image from the docker file, and create an approiate tag
• Update your HA deployment (docker-compose etc) to use the new image
• Update the ha-checkwatt component to the following branch: https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object.
• Restart your HA.

You may also want to increase the logging level to debug while testing:

logger:
logs:
custom_components.checkwatt: debug
pycheckwatt: debug

[mattiasclaesson]

Think this is the correct way to go. I will take a look at the other suggestions from @jenshorn aswell.

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Could we rely on the checkwatt server to complain if the tokens are not valid? Instead of having the client check the token?

[jacobbaungard]

Looks like we need a PR on the ha-checkwatt as well for the auth_info?

Yes. If this get merges, that is needed. I have an implementation ready here https://github.com/jacobbaungard/ha-checkwatt/tree/reuse-cw-object