Skip to content

Authentification expirée et impossible de se réauthentifier #826

Closed

Description

@JPdeLaval

J'ai la version Version : 2025.12.4.

Depuis ma dernière mise à jour du core d'Home Assistant (ce matin), mon intégration Hilo ne fonctionne plus. Il est indiqué que l'authentification est expirée pour mon adresse courriel. Quand je tente de reconnecter, ça dit que l'authentification est réussie, puis ça me déconnecte instantanément et me ramène au même endroit. Dans le menu de l'intégration, ça dit : "Échec de la configuration : 'NoneType' object has no attribute 'get'.

Dans les options de configuration de l'intégration, je n'avais pratiquement rien de coché. J'ai ajouté "Générer compteurs de consommation électrique" et j'ai mis l'intervalle de mise à jour à 60 secondes.

J'ai tenté de redémarrer HA et l'intégration, mais sans réussite. J'ai aussi validé que mon mot de passe était bien le bon. de plus, je suis encore en mesure de me connecter à l'application Hilo elle-même.

Voici quelques mentions de mon journal d'erreurs (il y en a plus, mais c'est redondant). Je remarque des erreurs en date d'hier soir, mais mon automatisation de défi de ce matin semble avoir fonctionné ce matin.

Merci !

2025-12-13 17:01:08.772 WARNING (MainThread) [custom_components.hilo] Invalid credentials? Refreshing websocket infos
2025-12-13 17:01:19.101 ERROR (MainThread) [pyhilo] Unable to connect to WS server 404, message='Invalid response status', url='https://device.hiloenergie.com/client/?hub=devicehub&asrs.op=%2FDeviceHub&asrs_request_id=smzk29MIAAA%3D&id=0cetsz5plhBm0yPvEmVxkQmYHjZQo02&access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InQtMDQ1MTE0MGUtOGY1Mi00YjRmLWI4MGMtMTZiOGFkYmU3ZTlmLTE3NzUwMzQ5In0.eyJhc3JzLnMuYXV0IjoiQXV0aGVudGljYXRpb25UeXBlcy5GZWRlcmF0aW9uIiwiYXNycy5zLmRlcnJvciI6IlRydWUiLCJhc3JzLnUuYXVkIjoiNjA0OWY0MDUtOGI3Ny00ZmM0LWIxYTAtNzI1ZGQ1YTM0OWYxIiwiYXNycy51LmlzcyI6Imh0dHBzOi8vY29ubmV4aW9uLmhpbG9lbmVyZ2llLmNvbS9lOGFlOGM1YS1hMDY3LTQ3NTMtOGQzNC1lZTM0ZDM5ZjMzMDcvdjIuMC8iLCJhc3JzLnUuZXhwIjoiMTc2NTY2NjUyNyIsImFzcnMudS5uYmYiOiIxNzY1NjYyOTI3Iiwic3ViIjoiYjAzMTIyMjAtNjIxYS00MDk2LWI4MzEtNjA2NzlhMmMzMWRjIiwibmFtZSI6IkfDqWxpbmFzLCBKZWFuLVBoaWxpcHBlIiwidWlkIjoiYjAzMTIyMjAtNjIxYS00MDk2LWI4MzEtNjA2NzlhMmMzMWRjQEhpbG9EaXJlY3RvcnlCMkMub25taWNyb3NvZnQuY29tIiwiZW1haWwiOiJqLnBfZ2VsaW5hc0Bob3RtYWlsLmNvbSIsImdpdmVuX25hbWUiOiJKZWFuLVBoaWxpcHBlIiwiZmFtaWx5X25hbWUiOiJHw6lsaW5hcyIsInVybjpjb206aGlsb2VuZXJnaWU6cHJvZmlsZTpsb2NhdGlvbl9oaWxvX2lkIjoidXJuOmhpbG86Y3JtOjQ2MDU1NTgtazBtOW04OjAiLCJ0aWQiOiJlOGFlOGM1YS1hMDY3LTQ3NTMtOGQzNC1lZTM0ZDM5ZjMzMDciLCJpc0ZvcmdvdFBhc3N3b3JkIjpmYWxzZSwiaXNTaWduVXAiOmZhbHNlLCJzY3AiOiJ1c2VyX2ltcGVyc29uYXRpb24iLCJhc3JzLnUuYXpwIjoiMWNhOWY1ODUtNGE1NS00MDg1LThlMzAtOTc0NmE2NWZhNTYxIiwidmVyIjoiMS4wIiwiYXNycy51LmlhdCI6IjE3NjU2NjI5MjciLCJ1c2VyX3R5cGUiOiJIaWxvIiwibmJmIjoxNzY1NjYzMjY4LCJleHAiOjE3NjU2NjY4NjgsImlhdCI6MTc2NTY2MzI2OCwiYXVkIjoiaHR0cHM6Ly9zaWdyLWRvbW8tcHJvZC0wMS5zZXJ2aWNlLnNpZ25hbHIubmV0L2NsaWVudC8_aHViPWRldmljZWh1YiJ9.0RNwykL4wdYN1gRFw6H3R-B3TCy-ueZyXQmoEMz0jNE'
2025-12-13 17:01:19.110 WARNING (MainThread) [custom_components.hilo] Invalid credentials? Refreshing websocket infos
2025-12-13 17:01:25.685 WARNING (MainThread) [pyhilo] Delaying invoke SubscribeToLocation 0 [60505]: Websocket not ready.
2025-12-13 22:52:19.223 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.outdoor_weather_hilo is taking over 10 seconds
2025-12-13 22:59:46.839 WARNING (MainThread) [homeassistant.components.switch] Updating adguard switch took longer than the scheduled update interval 0:00:10
2025-12-13 23:07:22.022 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.outdoor_weather_hilo is taking over 10 seconds
2025-12-14 06:55:27.146 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.162 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hilo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.184 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.189 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pitboss which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.193 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.197 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hilo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.201 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:27.205 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pitboss which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-14 06:55:37.199 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2025-12-14 06:55:37.543 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=84 from 2025-12-13 15:35:59.122541)
2025-12-14 06:56:20.250 WARNING (MainThread) [homeassistant.components.vizio.media_player] Lost connection to 192.168.0.155:9000
2025-12-14 06:56:21.446 WARNING (MainThread) [homeassistant.config_entries] Config entry 'j.p_gelinas@hotmail.com' for hilo integration could not authenticate: 'NoneType' object has no attribute 'get'
2025-12-14 06:58:54.129 WARNING (MainThread) [homeassistant.config_entries] Config entry 'j.p_gelinas@hotmail.com' for hilo integration could not authenticate: 'NoneType' object has no attribute 'get'
2025-12-14 07:02:45.188 WARNING (MainThread) [homeassistant.config_entries] Config entry 'j.p_gelinas@hotmail.com' for hilo integration could not authenticate: 'NoneType' object has no attribute 'get'
2025-12-14 07:03:03.513 WARNING (MainThread) [homeassistant.config_entries] Config entry 'j.p_gelinas@hotmail.com' for hilo integration could not authenticate: 'NoneType' object has no attribute 'get'

Activity

  1. ic-dev21 commented on Dec 14, 2025

    @ic-dev21
    Collaborator

    Delete hilo_state.yaml et restart.

  2. JPdeLaval commented on Dec 14, 2025

    @JPdeLaval
    Author

    Ça a fonctionné ! Merci !

  3. prug30 commented on Feb 7, 2026

    @prug30

    Je confirme également avoir rencontré le même problème, avec la même solution. Le fichier était vide après que le disque ait été complètement rempli…

    2026-02-05 23:44:53.570 DEBUG (MainThread) [pyhilo] Websocket access token is ******** 2026-02-05 23:44:53.571 DEBUG (MainThread) [pyhilo] Extracted URN: urn:hilo:crm:******:0 2026-02-05 23:44:53.571 DEBUG (MainThread) [pyhilo] Websocket _async_post_init running 2026-02-05 23:44:53.576 DEBUG (MainThread) [pyhilo] Loading state from yaml 2026-02-05 23:44:53.579 WARNING (MainThread) [homeassistant.config_entries] Config entry 'user@email.hilo' for hilo integration could not authenticate: 'NoneType' object has no attribute 'get' 2026-02-05 23:44:53.580 DEBUG (MainThread) [custom_components.hilo] async_step_reauth

    Serait-il possible d’inclure cette information dans le message d’erreur?

  4. ic-dev21 commented on Feb 7, 2026

    @ic-dev21
    Collaborator

    [homeassistant.config_entries] Config entry 'user@email.hilo' for hilo integration could not authenticate: 'NoneType' object has no attribute 'get' 2026-02-05 23:44:53.580 DEBUG (MainThread) [custom_components.hilo] async_step_reauth`

    Serait-il possible d’inclure cette information dans le message d’erreur?

    Pas vraiment, l'erreur ci-haut vient de python lui même, safe_load retourne None, on peut pas faire un get sur None.

    C'était très fréquent avec notre ancienne librairie yaml (ruyaml), ça s'est grandement amélioré avec pyaml.

    Je travaille sur un petit quelque chose mais je n'ai pas fini de le tester.
    dvd-dev/python-hilo#382

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions