Module MetersToHA : ne semble plus fonctionnel pour remonter les informations Veolia

Bonjour,
Je débute sur HA venant de Domoticz. et ces débuts se passent plutôt bien :slight_smile: .

J’accroche pour le moment sur la mise en place de MetersToHA.
J’utilise l’addon MetersToHA sur Ha OS (dernier patchs appliqués) que j’ai installé via module complémentaire en ajoutant le repo.

Jusqu’à la tout va bien, je fais la configuration de la partie Veolia qui m’intéresse, le module démarre.

Dans les logs, aucunes erreurs (CF ci-dessus), les configs semblent bien prise en compte.

s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------

 Add-on: MetersToHA
 MetersToHA add-on for Home Assistant
-----------------------------------------------------------
 Add-on version: dev
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.0  (amd64 / generic-x86-64)
 Home Assistant Core: 2024.8.1
 Home Assistant Supervisor: 2024.08.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Cloning into 'MetersToHA'...
git checkout 
Your branch is up to date with 'origin/meters-to-ha'.
MetersToHA Container version: dev.017 #2815b130869d0d7b049de3b0fc03f3e3  /run.sh
MetersToHA Python GIT version: 30665a2 on Fri Mar 1 17:59:13 2024 +0100
Generate configuration file
Generated configuration file '/m2h_config.json':
{
    "log_level":"debug",
    "logs_folder":"/config",
    "veolia_login":"xxxxx",
    "veolia_password":"xxxxxx",
    "veolia_contract":"xxxxxxx",
    "timeout":"30",
    "download_folder":"/config",
    "ha_server": "http://supervisor/core",
    "ha_token": "xxxxx",
    "type": "ha"
}
DISPLAY:'xxxxxx:3.0'
EVENT CONF: veolia:call_veolia grdf:call_grdf
=== Generated script '/execEvent.sh': ==========
#!/bin/bash
{
  TARGET_OPT=""
  [[ "$1" == "call_veolia" ]] && TARGET_OPT=--veolia
    [[ "$1" == "call_grdf" ]] && TARGET_OPT=--grdf
    [[ "$1" == "homeassistant_started" ]] && TARGET_OPT="-k --skip-download  --veolia --grdf"

  [[ "$TARGET_OPT" == "" ]] && ( echo "Unrecognized event '$1'" ; exit 1 )
  date
  echo "python3  MetersToHA/apps/meters_to_ha/meters_to_ha.py  -l /config --display --screenshot --keep-output -c \"/m2h_config.json\" $TARGET_OPT -r"
  python3  MetersToHA/apps/meters_to_ha/meters_to_ha.py  -l /config --display --screenshot --keep-output -c "/m2h_config.json" $TARGET_OPT -r
  # Copy chrome logs
  for i in ~/.config/*/chrome_debug.log ; do
    [[ -r "$i" ]] || continue
    SUBDIR="/config/$(basename "$(dirname "$i")")"
    mkdir -p "${SUBDIR}"
    cp -p "$i" "${SUBDIR}"
  done
  echo "Done $(date)"
} >> "/config/m2h_exec.log" 2>&1
=== End of Generated script '/execEvent.sh': ===

Test access to Home Assistant API (should show '{"message":"API running."}')
curl -H 'Authorization: Bearer xxxxxxx ' -H 'Content-Type: application/json' http://supervisor/core/api/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100    26  100    26    0     0   1900      0 --:--:-- --:--:-- --:--:--  2000
{"message":"API running."}
"./haevent2exec.py" --config-json "/m2h_config.json" --external-program "/execEvent.sh" --log-level="debug"  call_veolia call_grdf homeassistant_started
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Received {'type': 'auth_required', 'ha_version': '2024.8.1'}
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Connected
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Result of subscription for 'call_veolia': None
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Result of subscription for 'call_grdf': None
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Result of subscription for 'homeassistant_started': None
[2024/08/14 11:02:02] (haevent2exec.py) INFO    send_event_msg: Got id (4,)
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Subscribed, waiting for messages
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Received WSMessage(type=<WSMsgType.TEXT: 1>, data='{"id":1,"type":"result","success":true,"result":null}', extra='')
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Received WSMessage(type=<WSMsgType.TEXT: 1>, data='{"id":2,"type":"result","success":true,"result":null}', extra='')
[2024/08/14 11:02:02] (haevent2exec.py) INFO    Received WSMessage(type=<WSMsgType.TEXT: 1>, data='{"id":3,"type":"result","success":true,"result":null}', extra='')

Il semble que je sois pas le seul dans ce cas , est ce que l’addon est toujours fonctionnel ?

Je prends toutes les idées/pistes, merci d’avance.