@homebridge-plugins/homebridge-tado 9.1.0 → 9.1.1

package/CHANGELOG.md

@@ -1,5 +1,8 @@
 # Changelog
 
+# v9.1.1 - 2026-05-09
+- Fix: Missing access token for identity verification (#198)
+
 # v9.1.0 - 2026-05-06
 - Add support for multiple bridges in Config UI
 - Validate tado account after authentication

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homebridge-plugins/homebridge-tado",
-  "version": "9.1.0",
+  "version": "9.1.1",
   "description": "Homebridge plugin for controlling tado° devices.",
   "main": "index.js",
   "scripts": {
@@ -36,7 +36,7 @@
     "@homebridge/plugin-ui-utils": "^2.2.3",
     "fakegato-history": "^0.6.7",
     "form-data": "^4.0.5",
-    "fs-extra": "^11.3.4",
+    "fs-extra": "^11.3.5",
     "got": "^15.0.5",
     "moment": "^2.30.1"
   },

package/src/tado/tado-api.js

@@ -225,7 +225,7 @@ export default class Tado {
       if (tokenResponse?.body) {
         const { access_token, refresh_token } = tokenResponse.body;
         if (access_token && refresh_token) {
-          await this._verifyAuthenticatedIdentity();
+          await this._verifyAuthenticatedIdentity(access_token);
           await writeFile(this._tadoInternalTokenFilePath, JSON.stringify({ access_token, refresh_token }));
           this._tadoBearerToken = { access_token, refresh_token, timestamp: Date.now() };
           Logger.info("Authentication successful!");
@@ -246,9 +246,8 @@ export default class Tado {
    * poisons a token file. Uses got directly because apiCall -> getToken would
    * re-enter the in-flight token promise and deadlock.
    */
-  async _verifyAuthenticatedIdentity() {
+  async _verifyAuthenticatedIdentity(access_token) {
     if (!this.username) return;
-    const access_token = this._tadoBearerToken?.access_token;
     if (!access_token) throw new Error('No access token available for identity verification.');
     const url = `${this.tadoApiUrl}/api/v2/me`;
     let me;