MyElectricalData - Vos données Linky chez vous :)

hello

normal , il suffi de lire les post précédents
pour info tu y berras qu un seul capteur
https://forum.hacf.fr/uploads/default/original/3X/2/0/206d7fe91ab600367c7f923613ec62979b1aaf68.jpeg

la
https://forum.hacf.fr/t/myelectricaldata/6679/711?u=classicred
et la
https://forum.hacf.fr/t/myelectricaldata/6679/712?u=classicred

1 « J'aime »

Bonsoir,

on est d’accord qu’une fois la config terminée, il devrait y avoir une entité sensor.myelectricaldata_xxxxxxxxxxx qui remonte automatiquement
J’ai bien les données dans mon broker MQTT
mais rien qui remonte

cycle: 14400
debug: true
home_assistant:
  card_myenedis: true
  discovery_prefix: homeassistant
  enable: false
influxdb:
  asynchronous: 'false'
  bucket: myelectricaldata
  enable: false
  host: influxdb
  org: myelectricaldata
  port: 8086
  token: XXXXXXXXXXX
mqtt:
  client_id: myelectricaldata
  enable: true
  hostname: 192.168.1.30
  password: 'xxxxxxxxxxx'
  port: 1883
  prefix: myelectricaldata
  qos: 0
  retain: true
  username: 'xxxxxxxxxx'
myelectricaldata:
  "xxxxxxxxxxxx":
    cache: true
    consumption: true
    consumption_detail: true
    consumption_detail_max_date: ''
    consumption_max_date: ''
    consumption_price_base: 0.1740
    consumption_price_hc: 0
    consumption_price_hp: 0
    offpeak_hours_0: 3H26-7H26;12H26-16H26              # LUNDI
    offpeak_hours_1: 3H26-7H26;12H26-16H26             # MARDI
    offpeak_hours_2: 3H26-7H26;12H26-16H26               # MERCREDI
    offpeak_hours_3: 3H26-7H26;12H26-16H26               # JEUDI
    offpeak_hours_4: 3H26-7H26;12H26-16H26               # VENDREDI
    offpeak_hours_5: 3H26-7H26;12H26-16H26   # SAMEDI
    offpeak_hours_6: 3H26-7H26;12H26-16H26   # DIMANCHE
    enable: true
    plan: BASE
    production: false
    production_detail: false
    production_detail_max_date: ''
    production_max_date: ''
    production_price: 0
    token: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Merci, je trouve pas ou je manque juste de patience sur la remontée des données

Hello
@Cyrille_Fremont
tu as une erreur dans ta config

modifie

en

oh purée comment j’ai fait pour pas le voir…
en même temps j’ai mis 45mn avant de me rendre compte que j’avais pas tapé le bon hostname 10.168 au lieu de 192.168…

je suis un boulet, je sors…

Merci beaucoup

1 « J'aime »

t’inquiète ca arrive , et a force on voit plus son erreur

ca m’arrive des fois , de ce fait je laisse tombé et j’y reviens plus tard sur le souci …

1 « J'aime »

Salut,

Je comprends pas j’ai un crash quand je lance l’app.
Ma config est celle ci (je suis en v1 influxdb) :

cycle: 14400
debug: true
home_assistant:
  card_myenedis: true
  discovery_prefix: homeassistant
  enable: true
influxdb:
  enable: true
  hostname: xxxx-influxdb
  port: 8086
  token: xxxx:xxxx
  org: "-"
  bucket: "myelectricdata/ret"
  method: batching
mqtt:
  client_id: myelectricaldata
  enable: true
  hostname: IP
  password: "xxxx"
  port: 1883
  prefix: myelectricaldata
  qos: 0
  retain: true
  username: "xxxx"
myelectricaldata:
  "xxxxxxxxxxxxxx":
    cache: true
    consumption: true
    consumption_detail: true
    consumption_detail_max_date: ""
    consumption_max_date: ""
    consumption_price_base: 0.1740
    consumption_price_hc: 0
    consumption_price_hp: 0
    offpeak_hours_0: 3H26-7H26;12H26-16H26 # LUNDI
    offpeak_hours_1: 3H26-7H26;12H26-16H26 # MARDI
    offpeak_hours_2: 3H26-7H26;12H26-16H26 # MERCREDI
    offpeak_hours_3: 3H26-7H26;12H26-16H26 # JEUDI
    offpeak_hours_4: 3H26-7H26;12H26-16H26 # VENDREDI
    offpeak_hours_5: 3H26-7H26;12H26-16H26 # SAMEDI
    offpeak_hours_6: 3H26-7H26;12H26-16H26 # DIMANCHE
    enable: true
    plan: BASE
    production: false
    production_detail: false
    production_detail_max_date: ""
    production_max_date: ""
    production_price: 0
    token: "xxxxxxxxxx"

Je prends cette erreur au démarrage :

2022-12-10 23:14:11.514 -     INFO :  Connect to MQTT broker IP:1883
2022-12-10 23:14:11.518 -     INFO :   => Connection success
2022-12-10 23:14:11.519 -     INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2022-12-10 23:14:11.519 -     INFO :  Connect to InfluxDB IP:8086
2022-12-10 23:14:11.558 -     INFO :   => Connection success
2022-12-10 23:14:11.558 -     INFO :   => Methode d'importation : BATCHING
Traceback (most recent call last):
  File "/app/main.py", line 81, in <module>
    INFLUXDB = InfluxDB(
  File "/app/models/influxdb.py", line 63, in __init__
    self.connect()
  File "/app/models/influxdb.py", line 117, in connect
    self.get_list_retention_policies()
  File "/app/models/influxdb.py", line 137, in get_list_retention_policies
    buckets = self.buckets_api.find_buckets().buckets
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/client/bucket_api.py", line 119, in find_buckets
    return self._buckets_service.get_buckets(**kwargs)
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/service/buckets_service.py", line 548, in get_buckets
    (data) = self.get_buckets_with_http_info(**kwargs)  # noqa: E501
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/service/buckets_service.py", line 575, in get_buckets_with_http_info
    return self.api_client.call_api(
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/_sync/api_client.py", line 343, in call_api
    return self.__call_api(resource_path, method,
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/_sync/api_client.py", line 173, in __call_api
    response_data = self.request(
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/_sync/api_client.py", line 365, in request
    return self.rest_client.GET(url,
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/_sync/rest.py", line 268, in GET
    return self.request("GET", url,
  File "/usr/local/lib/python3.9/site-packages/influxdb_client/_sync/rest.py", line 261, in request
    raise ApiException(http_resp=r)
influxdb_client.rest.ApiException: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'Content-Type': 'text/plain; charset=utf-8', 'X-Content-Type-Options': 'nosniff', 'X-Influxdb-Build': 'OSS', 'X-Influxdb-Version': '1.8.10', 'Date': 'Sat, 10 Dec 2022 22:14:11 GMT', 'Content-Length': '19'})
HTTP response body: 404 page not found
[23:14:11] FATAL: The app has crashed. Are you sure you entered the correct config options?

Hello

et oui dû a influxdb
desactive le pour le moment un PR est en cours
il faut vous rendre sur le git de myelectradata pour suivre comme l’a demande @M4dm4rtig4n
le PR

Les bugs

et quelque autres !!

Hello,

Je viens de faire une mise en prod de la passerelle qui malheuresement demande un renouvellement des consentements.

Désolé pour la gêne occasionnée :confused:

C’est une assez grosse MAJ dans le sens où j’ai :

  • Basculer tt le système de base de données vers de l’ORM via SQLAlchemy
  • Ajouter d’un endpoint Tempo (avec cache local pour eviter de spam RTE)
  • Ajouter d’un endpoint Ecowatt via RTE (avec cache local pour eviter de spam RTE)

J’ai quelques truc à push encore sur la passerelle, et ensuite je referais une passe sur les issue du client MyElectricalData.

2 « J'aime »

Bonjour M4dm4rtig4n,

Vous n’avez pas à l’être !

Un grand merci à vous pour la mise à disposition de cette passerelle (et le travail que cela demande) qui nous permet de récupérer les données d’ Enedis, qui sans vous resteraient indisponibles.

Merci !

Mcp

1 « J'aime »

J’ai encore le meme soucis de mon coté, meme erreur

Bjr je souhaitera repartie de zéro pour l’install car je ne vous suis plus.

Marche à suivre Merci

Bonjour et merci à toi pour ton aide, donc ça je l’avais fait la semaine, ça a bien démarré mais il ne me remontait que de fausses infos et jamais celle de la veille, j’ai donc laissé tourné la semaine et chaque jour pareille… Là aujourd’hui j’ai mit à jour l’addons, j’ai refait le consentement comme mentionné et vérifié que la collecte des données est bine active sur enedis, voici les retours:

➜  ~ curl -X GET "https://www.myelectricaldata.fr/valid_access/24323878276236" -H "Authorization: Rk_AMzlSHCUbwhVVJ69LipkE3eBuVQS1EHaVS2YupZQ="

{"valid":true,"information":"","consent_expiration_date":"2025-12-11T14:02:04","call_number":0,"quota_reached":false,"quota_limit":50,"quota_reset_at":"2022-12-11T23:59:59.999999","last_call":"2022-12-11T14:02:04.100252","ban":false}#  
➜  ~ curl -X GET "https://www.myelectricaldata.fr/consumption_load_curve/24323878276236/start/2022-12-03/end/2022-12-10" -H "Authorization: Rk_AMzlSHCUbwhVVJ69LipkE3eBuVQS1EHaVS2YupZQ=" | jq

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 30612  100 30612    0     0   5672      0  0:00:05  0:00:05 --:--:--  7363
{
  "meter_reading": {
    "usage_point_id": "24323878276236",
    "start": "2022-12-03",
    "end": "2022-12-10",
    "quality": "BRUT",
    "reading_type": {
      "measurement_kind": "power",
      "unit": "W",
      "aggregate": "average"
    },
    "interval_reading": [
      {
        "value": "518",
        "date": "2022-12-03 00:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "974",
        "date": "2022-12-03 01:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "534",
        "date": "2022-12-03 01:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "536",
        "date": "2022-12-03 02:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "922",
        "date": "2022-12-03 02:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "694",
        "date": "2022-12-03 03:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "508",
        "date": "2022-12-03 03:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "608",
        "date": "2022-12-03 04:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "930",
        "date": "2022-12-03 04:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "518",
        "date": "2022-12-03 05:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "494",
        "date": "2022-12-03 05:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "892",
        "date": "2022-12-03 06:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "648",
        "date": "2022-12-03 06:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "470",
        "date": "2022-12-03 07:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "598",
        "date": "2022-12-03 07:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "1424",
        "date": "2022-12-03 08:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "714",
        "date": "2022-12-03 08:30:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "2400",
        "date": "2022-12-03 09:00:00",
        "interval_length": "PT30M",
        "measure_type": "B"
      },
      {
        "value": "2230",



Je n’ai pas tout mit :wink:

et quand je démarre l’addons MyElectricalData :

Starting...
/etc/cont-init.d/00-banner.sh: executing
-----------------------------------------------------------
 Add-on: MyElectricalData
 Use Enedis Gateway API to send data in your MQTT Broker (latest channel)
-----------------------------------------------------------
 Add-on version: 0.8.8
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.3  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2022.12.1
 Home Assistant Supervisor: 2022.11.2
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
 https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
CONFIG_LOCATION='/config/enedisgateway2mqtt/config.yaml'
TZ='Europe/Paris'
mqtt_autodiscover='true'
verbose='true'
/etc/cont-init.d/01-custom_script.sh: executing
[14:16:11] INFO: Execute /config/enedisgateway2mqtt.sh if existing
[14:16:11] INFO: ... no script found
/etc/cont-init.d/91-mqtt_autodiscover.sh: executing
[14:16:12] INFO: mqtt_autodiscover is defined in options, attempting autodiscovery...
[14:16:12] INFO: ... MQTT service found, fetching server detail (you can enter those manually in your config file) ...
Config file is a valid yaml
creating symlink
[14:17:20] INFO: Using database file found in /config/enedisgateway2mqtt/enedisgateway.db
 
[14:17:20] INFO: Starting the app
 
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
2022-12-11 14:17:28.523 -  WARNING : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ▲ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2022-12-11 14:17:28.524 -  WARNING :  MIGRATION DE L'ANCIENNE BASE DE DONNÉES VERS LA NOUVELLE STRUCTURE.
2022-12-11 14:17:28.526 -  WARNING : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ▲ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2022-12-11 14:17:28.529 -  WARNING :  Migration des "consumption_daily"
2022-12-11 14:17:28.703 -  WARNING :   - 2022 => 5.75kW
2022-12-11 14:17:28.827 -  WARNING :  Migration des "consumption_detail"
2022-12-11 14:17:29.086 -  WARNING :   - 2022-03 => 0.62kW
2022-12-11 14:17:29.561 -  WARNING :   - 2022-04 => 530.95kW
2022-12-11 14:17:30.360 -  WARNING :   - 2022-05 => 549.33kW
2022-12-11 14:17:30.982 -  WARNING :   - 2022-06 => 412.24kW
2022-12-11 14:17:31.488 -  WARNING :   - 2022-07 => 386.93kW
2022-12-11 14:17:32.162 -  WARNING :   - 2022-08 => 559.67kW
2022-12-11 14:17:32.838 -  WARNING :   - 2022-09 => 659.71kW
2022-12-11 14:17:33.405 -  WARNING :   - 2022-10 => 421.87kW
2022-12-11 14:17:33.878 -  WARNING :   - 2022-11 => 297.81kW
2022-12-11 14:17:35.864 -  WARNING :  Migration des "production_daily"
2022-12-11 14:17:35.873 -  WARNING :  Migration des "production_detail"
2022-12-11 14:17:35.892 -     INFO :  Configure Databases
/app/models/database.py:114: SAWarning: Column 'consumption_daily.id' is marked as a member of the primary key for table 'consumption_daily', but has no Python-side or server-side default generator indicated, nor does it indicate 'autoincrement=True' or 'nullable=True', and no explicit value is passed.  Primary key columns typically may not store NULL.
  day = self.session.scalars(query).one_or_none()
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
    cursor.execute(statement, parameters)
sqlite3.IntegrityError: NOT NULL constraint failed: consumption_daily.id
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/app/main.py", line 9, in <module>
    from models.ajax import Ajax
  File "/app/models/ajax.py", line 3, in <module>
    from models.jobs import Job
  File "/app/models/jobs.py", line 6, in <module>
    from models.database import Database
  File "/app/models/database.py", line 1141, in <module>
    Database().init_database()
  File "/app/models/database.py", line 114, in init_database
    day = self.session.scalars(query).one_or_none()
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1771, in scalars
    return self.execute(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1660, in execute
    ) = compile_state_cls.orm_pre_session_exec(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/context.py", line 312, in orm_pre_session_exec
    session._autoflush()
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2257, in _autoflush
    util.raise_(e, with_traceback=sys.exc_info()[2])
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 208, in raise_
    raise exception
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2246, in _autoflush
    self.flush()
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 3386, in flush
    self._flush(objects)
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 3526, in _flush
    transaction.rollback(_capture_exception=True)
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__
    compat.raise_(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 208, in raise_
    raise exception
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 3486, in _flush
    flush_context.execute()
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/unitofwork.py", line 456, in execute
    rec.execute(self)
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/unitofwork.py", line 630, in execute
    util.preloaded.orm_persistence.save_obj(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/persistence.py", line 245, in save_obj
    _emit_insert_statements(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/orm/persistence.py", line 1238, in _emit_insert_statements
    result = connection._execute_20(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1705, in _execute_20
    return meth(self, args_10style, kwargs_10style, execution_options)
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/sql/elements.py", line 333, in _execute_on_connection
    return connection._execute_clauseelement(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1572, in _execute_clauseelement
    ret = self._execute_context(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1943, in _execute_context
    self._handle_dbapi_exception(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 2124, in _handle_dbapi_exception
    util.raise_(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 208, in raise_
    raise exception
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.IntegrityError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely)
(sqlite3.IntegrityError) NOT NULL constraint failed: consumption_daily.id
[SQL: INSERT INTO consumption_daily (usage_point_id, date, value, blacklist, fail_count) VALUES (?, ?, ?, ?, ?)]
[parameters: ('24323878276236', '2022-03-02 00:00:00.000000', 5755, 0, 0)]
(Background on this error at: https://sqlalche.me/e/14/gkpj)
[14:17:38] FATAL: The app has crashed. Are you sure you entered the correct config options?

Mon fichier de configuration n’a pas changé, je suis nul mais de ce que je comprends on dirait une erreur du coté de la database.

Merci d’avance pour ton aide

Hello

désinstalle myelectra , supprime le dossier complet dans /config

reboot
réinstalle my electra, démarre le , il va planté , normal car le config est pas mis en place .
arrête myelectra, vas dans son dossier , et met ce config.

j’ai mis au max tes infos,
ajoute ton PDL / TOKEN
et la partie MQTT

cycle: 14400
debug: false
wipe_cache: true
wipe_influxdb: false
home_assistant:
  enable: true
  discovery: true
  discovery_prefix: homeassistant
  card_myenedis: true
influxdb:
  enable: false
  hostname: 192.168.X.X
  port: 8086
  token: XXXXXX:XXXXXXXX
  org: "-"
  bucket: myelectricaldata
  method: asynchronous
mqtt:
  enable: true
  hostname: core-mosquitto
  port: 1883
  username: XXXXX
  password: XXXXXX
  prefix: myelectricaldata
  client_id: myelectricaldata
  retain: true
  qos: 0
myelectricaldata:
  2XXXXXXXXXX:
    enable: true
    token: XXXXXXX
    name: Maison
    addresses: true
    cache: true
    consumption: true
    consumption_detail: true
    consumption_detail_max_date: ''
    consumption_max_date: ''
    consumption_price_base: 0
    consumption_price_hc: 0.1470
    consumption_price_hp: 0.1841
    offpeak_hours_0: 23H30-7H30
    offpeak_hours_1: 23H30-7H30
    offpeak_hours_2: 23H30-7H30
    offpeak_hours_3: 23H30-7H30
    offpeak_hours_4: 23H30-7H30
    offpeak_hours_5: 23H30-7H30
    offpeak_hours_6: 23H30-7H30
    plan: HC/HP
#    production: false
#    production_detail: false
#    production_detail_max_date: ''
#    production_max_date: ''
#    production_price: 0
    refresh_addresse: false
    refresh_contract: false

j’ai viré le tarif base que tu as mis , car si tu es HP/HC tu peux pas avoir de Base de tarif.
Envoi une production a RTE ? car si non tu as pas besoin d’activé cela , chose que je bloque a la fin du config.

Ne met pas de backup, essai aussi simplement que possible.

1 « J'aime »

J’ai fait exactement les manips que tu mentionnes et j’obtiens encore une erreur, un espace si je comprends bien à la première ligne, mais il y en a pas ^^:

 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
 https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
CONFIG_LOCATION='/config/enedisgateway2mqtt/config.yaml'
TZ='Europe/Paris'
mqtt_autodiscover='true'
verbose='true'
/etc/cont-init.d/01-custom_script.sh: executing
[15:20:43] INFO: Execute /config/enedisgateway2mqtt.sh if existing
[15:20:43] INFO: ... no script found
/etc/cont-init.d/91-mqtt_autodiscover.sh: executing
[15:20:44] INFO: mqtt_autodiscover is defined in options, attempting autodiscovery...
[15:20:45] INFO: ... MQTT service found, fetching server detail (you can enter those manually in your config file) ...
/etc/cont-init.d/91-mqtt_autodiscover.sh: exiting 2
/etc/cont-init.d/99-run.sh: executing
[15:20:48] INFO: Using config file found in /config/enedisgateway2mqtt/config.yaml
/config/enedisgateway2mqtt/config.yaml
  1:13      error    wrong new line character: expected \n  (new-lines)
[15:20:49] FATAL: Config file has an invalid yaml format. Please check the file in /config/enedisgateway2mqtt/config.yaml. Errors list above. You can check yaml validity with the online tool yamllint.com
/etc/cont-init.d/99-run.sh: exiting 1

Re,

oui un espace !
tu te sers de quoi comme éditeur de fichier ?

cycle: 14400| le curseur doit etre collé
si
cycle: 14400 | la le curseur est decalé de 1 donc souci

notepad++ j’ai vérifié le fichier au complet bien sur avant de poster, tu me l’a mentionné la semaine dernière je m’en rappel :slight_smile:

c’est possible , lol
mais comme je dors aussi je retient pas tout ce que je dit :grinning:

Je peux t’envoyer mon fichier en mp ?

edit non je peux pas ^^

grrr , 20 minutes :face_with_thermometer:

Pour information, j’ai un petit soucis sur les consentement qui son HS au bout d’un certain temps.
Je suis sur le sujet :slight_smile:

3 « J'aime »