search

dubocr / homebridge-tahoma

Homebridge plugin for TaHoma, Connexoon, Cozytouch, Energeasy Connect.
Apache License 2.0
133 stars 42 forks source link

Les accessoires Tahoma ne répondent plus les matins #478

Closed MXCZK closed 8 months ago

MXCZK commented 1 year ago

Bonjour,

Tous les matins, les accessoires Tahoma ne répondent plus dans Maison. Je suis obligé de redémarrer homebridge tous les matins pour que ça fonctionne à nouveau.

J’ai tenté de redémarrer ma box mais ça ne change rien.

Savez-vous quel peut être le problème ?

merci

MXCZK commented 1 year ago

Voici le log :

[31/05/2023, 00:01:53] [Homebridge UI] Running scheduled instance backup... [31/05/2023, 00:01:53] [Homebridge UI] Creating temporary backup archive at /tmp/homebridge-backup-n9HUKb/homebridge-backup-0ED3EEDC6314.tar.gz [31/05/2023, 01:10:30] [Homebridge UI] Running job to cleanup config.json backup files older than 60 days... [31/05/2023, 06:00:00] [TaHoma] [Virtual Alarm] disarm[] [31/05/2023, 06:00:06] [TaHoma] [Virtual Alarm] disarm COMPLETED [31/05/2023, 07:00:16] [TaHoma] Polling error - Parse Error: Invalid header value char [31/05/2023, 07:01:11] [TaHoma] Polling error - Parse Error: Invalid header value char [31/05/2023, 07:02:19] [TaHoma] Polling error - Parse Error: Invalid header value char [31/05/2023, 07:03:17] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED) [31/05/2023, 07:04:42] [TaHoma] Registration error - Parse Error: Invalid header value char [31/05/2023, 07:53:15] [TaHoma] [Volet Maïwenn] setClosure[0] [31/05/2023, 07:53:15] [TaHoma] [Volet Maïwenn] setClosure Parse Error: Invalid header value char [31/05/2023, 08:07:21] [TaHoma] [Volet Maïwenn] setClosure[0] [31/05/2023, 08:07:21] [TaHoma] [Volet Maïwenn] setClosure Parse Error: Invalid header value char [31/05/2023, 08:07:36] [TaHoma] [Volet bureau] open[] [31/05/2023, 08:07:37] [TaHoma] [Volet bureau] open Parse Error: Invalid header value char [31/05/2023, 08:49:36] [TaHoma] [Volet Eliott] open[] [31/05/2023, 08:49:37] [TaHoma] [Volet Eliott] open Parse Error: Invalid header value char [31/05/2023, 08:49:39] [TaHoma] [Volet Eliott] open[] [31/05/2023, 08:49:39] [TaHoma] [Volet Eliott] open Parse Error: Invalid header value char

fiky16 commented 1 year ago

Salut ! J'ai également ce problème (tous les jours à la base).

Depuis j’effectue un reboot de la pi via un script tous les jours a 00h30. Le reboot a résolu ce problème en partie. De tous les jours c'est passé à une fois toutes les deux semaines environ. Je ne comprend pas non plus pourquoi... J'ai effectué une mise à jour du plugin hier, il à peut être résolu le problème !

MXCZK commented 1 year ago

Hello,

Moi j’ai l’impression que ça a commencé avec une MAJ récente d’Apple. Entre temps, j’ai updaté la Tahoma. Et ce matin, l’app Maison a mis à jour le domicile avec une nouvelle architecture. Peut-être que tout ce bazar va résoudre le problème ?

grmelacz commented 1 year ago

Hi, I can confirm this problem:

[31. 5. 2023 14:11:07] [TaHoma] [My EVB Pro io] open[]
[31. 5. 2023 14:11:07] [TaHoma] [My EVB Pro io] open Parse Error: Invalid header value char
[31. 5. 2023 14:11:08] [TaHoma] [My EVB Pro io] setClosureAndOrientation[100,100]
[31. 5. 2023 14:11:08] [TaHoma] [My EVB Pro io] setClosureAndOrientation Parse Error: Invalid header value char
[31. 5. 2023 14:11:11] [TaHoma] [My EVB Pro io] setClosureAndOrientation[100,100]
[31. 5. 2023 14:11:11] [TaHoma] [My EVB Pro io] setClosureAndOrientation Parse Error: Invalid header value char
[31. 5. 2023 14:11:15] [TaHoma] [My EVB Pro io] setClosureAndOrientation[100,100]
[31. 5. 2023 14:11:15] [TaHoma] [My EVB Pro io] setClosureAndOrientation Parse Error: Invalid header value char
[31. 5. 2023 14:11:16] [TaHoma] [My EVB Pro io] setClosureAndOrientation[100,100]
[31. 5. 2023 14:11:17] [TaHoma] [My EVB Pro io] setClosureAndOrientation Parse Error: Invalid header value char
[31. 5. 2023 14:11:17] [TaHoma] [My EVB Pro io] open[]
[31. 5. 2023 14:11:17] [TaHoma] [My EVB Pro io] open Parse Error: Invalid header value char
[31. 5. 2023 14:11:18] [TaHoma] [My EVB Pro io] open[]
[31. 5. 2023 14:11:18] [TaHoma] [My EVB Pro io] open Parse Error: Invalid header value char

This error earlier today might be also associated with the issue:

[31. 5. 2023 7:00:24] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:01:24] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:02:29] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[31. 5. 2023 7:04:21] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:06:21] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:07:24] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[31. 5. 2023 7:08:56] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:11:56] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:12:56] [TaHoma] Polling error - Parse Error: Invalid header value char
[31. 5. 2023 7:13:57] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[31. 5. 2023 7:14:42] [TaHoma] Registration error - Parse Error: Invalid header value char

Accessory not responding in Apple Home. I have not yet updated the Home architecture though. Rebooting HB solved this, at least temporarily.

sxc731 commented 1 year ago

The smoking gun appears to be [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED). This suggests that the plugin looses its session and finds itself unauthenticated; at which point it becomes disabled until a homebridge reboot is performed.

I've had this happen up to several times a day recently (my timezone is CEST). I'm on the latest version of the plugin (v2.2.54):

$ grep 'RESOURCE_ACCESS_DENIED' homebridge.log
[15/05/2023, 22:44:47] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[16/05/2023, 00:03:58] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[16/05/2023, 10:42:18] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[16/05/2023, 10:44:29] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[16/05/2023, 10:46:40] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[16/05/2023, 22:07:51] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[16/05/2023, 22:32:37] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[25/05/2023, 02:13:12] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[25/05/2023, 15:01:56] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[25/05/2023, 18:53:07] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[27/05/2023, 02:50:05] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[27/05/2023, 07:03:32] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[28/05/2023, 17:00:59] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[28/05/2023, 22:26:51] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[29/05/2023, 11:26:12] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[29/05/2023, 11:35:32] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[29/05/2023, 11:59:53] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[29/05/2023, 12:53:14] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[29/05/2023, 13:24:40] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[29/05/2023, 22:54:50] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[30/05/2023, 03:17:11] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[30/05/2023, 07:32:27] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[31/05/2023, 02:02:19] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
[31/05/2023, 07:02:46] [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)
MXCZK commented 1 year ago

Hi,

Just for info, it works again. I don't know what was the problem.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Please make sure to update to the latest Homebridge TaHoma version to see if that solves the issue. This issue will be closed in case of inactivity.

Flavien06 commented 7 months ago

Bonjour, j'ai également régulièrement le message [TaHoma] Polling error - Error 401 Not authenticated (RESOURCE_ACCESS_DENIED)

Je me suis rendu compte que ce message intervient quand on interroge trop souvent les serveur TaHoma ou Cozytouch (dans mon cas) Sans doute une limitation du nombre de requête vers leur serveur ( dans l'heure, la journée ou autre ??)

J'ai augmenter les intervalle de vérification pour avoir le message moins souvent. "pollingPeriod": 1800, "refreshPeriod": 60, Si je fait trop de modifications j'ai le message.

Est ce que il serait possible de forcer le plugin à optenir un nouvelle clé d'authentification par exemple ?

Édit : le redémarrage de Homebridge initialise le plugin et donc permet d'optenir une nouvelle clé d'authentification