Voici ma configue MQTT:
mqtt:
enable: true
hostname: core-mosquitto
port: 1883
username: myelectricaldata
password: xxxxxxxxxxxxxxxxx
prefix: myelectricaldata
client_id: myelectricaldata
retain: true
qos: 0
J’ai créé un utilisateur spécifique pour MED:
Merci pour ton retour.
J’ai créé l’utilisateur, j’ai modifié les paramètres mqtt dans config.yaml.
Quand je relance mqtt mosquitto, j’obtiens cela :
[17:02:44] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs 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 fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[19:03:15] INFO: Setting up user mqqt
[19:03:15] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[19:03:15] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[19:03:16] INFO: Starting mosquitto MQTT broker...
2024-07-26 19:03:16: Warning: Mosquitto should not be run as root/administrator.
2024-07-26 19:03:16: mosquitto version 2.0.18 starting
2024-07-26 19:03:16: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-07-26 19:03:16: Loading plugin: /usr/share/mosquitto/go-auth.so
2024-07-26 19:03:16: ├── Username/password checking enabled.
2024-07-26 19:03:16: ├── TLS-PSK checking enabled.
2024-07-26 19:03:16: └── Extended authentication not enabled.
2024-07-26 19:03:16: Opening ipv4 listen socket on port 1883.
2024-07-26 19:03:16: Opening ipv6 listen socket on port 1883.
2024-07-26 19:03:16: Opening websockets listen socket on port 1884.
2024-07-26 19:03:16: mosquitto version 2.0.18 running
2024-07-26 19:03:16: New connection from ::1:41414 on port 1883.
2024-07-26 19:03:16: Client <unknown> disconnected due to protocol error.
[19:03:16] INFO: Successfully send discovery information to Home Assistant.
[19:03:16] INFO: Successfully send service information to the Supervisor.
2024-07-26 19:03:17: Expiring client 6c74da46-tydom2mqtt2024-07-13 18:35:47.991341 due to timeout.
2024-07-26 19:03:17: Expiring client 9afc8f77-tydom2mqtt2024-07-14 18:47:18.523714 due to timeout.
2024-07-26 19:03:20: New connection from 172.30.32.1:44318 on port 1883.
2024-07-26 19:03:20: New client connected from 172.30.32.1:44318 as 9afc8f77-tydom2mqtt2024-07-14 18:47:18.523714 (p5, c0, k60, u'mqtt').
2024-07-26 19:03:20: New connection from 172.30.32.1:44324 on port 1883.
2024-07-26 19:03:20: New client connected from 172.30.32.1:44324 as 6c74da46-tydom2mqtt2024-07-13 18:35:47.991341 (p5, c0, k60, u'mqtt').
2024-07-26 19:03:22: New connection from 172.30.32.1:41959 on port 1883.
2024-07-26 19:03:22: New client connected from 172.30.32.1:41959 as 3BYNjyziCA1F9eykwFTaXZ (p2, c1, k60, u'homeassistant').
2024-07-26 19:03:29: New connection from 172.30.33.6:60403 on port 1883.
2024-07-26 19:03:29: Client myelectricaldata disconnected, not authorised.
C’est le découragement.
Voici toute ma configue de MED:
cycle: 14400
debug: false
log2file: false
wipe_influxdb: false
home_assistant:
enable: true
discovery: true
discovery_prefix: homeassistant
home_assistant_ws:
enable: false
influxdb:
enable: false
mqtt:
enable: true
hostname: core-mosquitto
port: 1883
username: myelectricaldata
password: xxxxxxxxxxxxxxxxxxxx
prefix: myelectricaldata
client_id: myelectricaldata
retain: true
qos: 0
myelectricaldata:
"24xxxxxxxxxxxxxx":
enable: 'true'
token: guH07xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
name: "Maison"
addresses: 'true'
cache: 'true'
consumption: 'true'
consumption_detail: 'true'
consumption_price_base: '0.2516'
consumption_price_hc: '0.1656'
consumption_price_hp: '0.2288'
consumption_max_date: "2024-06-21"
consumption_detail_max_date: "2024-06-21"
offpeak_hours_0: 20H56-4H56 # LUNDI
offpeak_hours_1: 20H56-4H56 # MARDI
offpeak_hours_2: 20H56-4H56 # MERCREDI
offpeak_hours_3: 20H56-4H56 # JEUDI
offpeak_hours_4: 20H56-4H56 # VENDREDI
offpeak_hours_5: 20H56-4H56 # SAMEDI
offpeak_hours_6: 20H56-4H56 # DIMANCHE
plan: HC/HP
tempo:
enable: false
Je ne sais pas ce qui te bloque.
J’ai fait ce que tu m’as indiqué.
Créer un utilisateur myelectricaldata. (administrateur)
Dans le config.yaml je mets ta partie mqtt ajoutant les données de l’utilisateur « myelectricaldata ».
Quand je relance HA, j’obtiens ceci :
L’adons « tydom2mqtt » se connecte et remonte les données Tydom (deltadore) mais bloque sur « myelectricaldata ».
Je ne trouve pas d’issue à ce problème.
[08:08:13] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs 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 fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[10:08:18] INFO: Setting up user mqqt
[10:08:18] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[10:08:18] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[10:08:19] INFO: Starting mosquitto MQTT broker...
2024-07-27 10:08:19: Warning: Mosquitto should not be run as root/administrator.
2024-07-27 10:08:19: mosquitto version 2.0.18 starting
2024-07-27 10:08:19: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-07-27 10:08:19: Loading plugin: /usr/share/mosquitto/go-auth.so
2024-07-27 10:08:19: ├── Username/password checking enabled.
2024-07-27 10:08:19: ├── TLS-PSK checking enabled.
2024-07-27 10:08:19: └── Extended authentication not enabled.
2024-07-27 10:08:19: Opening ipv4 listen socket on port 1883.
2024-07-27 10:08:19: Opening ipv6 listen socket on port 1883.
2024-07-27 10:08:19: Opening websockets listen socket on port 1884.
2024-07-27 10:08:19: mosquitto version 2.0.18 running
2024-07-27 10:08:19: New connection from ::1:34368 on port 1883.
2024-07-27 10:08:19: Client <unknown> disconnected due to protocol error.
2024-07-27 10:08:19: New connection from 172.30.32.1:46096 on port 1883.
2024-07-27 10:08:19: New client connected from 172.30.32.1:46096 as 6c74da46-tydom2mqtt2024-07-13 18:35:47.991341 (p5, c0, k60, u'mqtt').
2024-07-27 10:08:19: New connection from 172.30.32.1:46112 on port 1883.
2024-07-27 10:08:19: New client connected from 172.30.32.1:46112 as 9afc8f77-tydom2mqtt2024-07-14 18:47:18.523714 (p5, c0, k60, u'mqtt').
[10:08:19] INFO: Successfully send discovery information to Home Assistant.
[10:08:20] INFO: Successfully send service information to the Supervisor.
2024-07-27 10:08:21: New connection from 172.30.33.6:49073 on port 1883.
2024-07-27 10:08:21: Client myelectricaldata disconnected, not authorised.
2024-07-27 10:08:23: New connection from 172.30.32.1:52223 on port 1883.
2024-07-27 10:08:23: New client connected from 172.30.32.1:52223 as 3BYNjyziCA1F9eykwFTaXZ (p2, c1, k60, u'homeassistant').
2024-07-27 10:10:21: New connection from 172.30.33.6:60661 on port 1883.
2024-07-27 10:10:21: Client myelectricaldata disconnected, not authorised.
2024-07-27 10:12:21: New connection from 172.30.33.6:54899 on port 1883.
2024-07-27 10:12:21: Client myelectricaldata disconnected, not authorised.
2024-07-27 10:14:21: New connection from 172.30.33.6:37905 on port 1883.
2024-07-27 10:14:21: Client myelectricaldata disconnected, not authorised.
2024-07-27 10:16:22: New connection from 172.30.33.6:37325 on port 1883.
2024-07-27 10:16:22: Client myelectricaldata disconnected, not authorised.
Difficile de continuer sans savoir où est l’erreur et quoi fournir pour être aider correctement.
Merci pour ta patience.
Bonsoir,
J’ai retesté d’installer tout cela, j’y suis presque, j’arrive à accéder à la page Myelectricaldata, les données sont bien rapatriées :
mais lorsque je saisie de mon fichier configuration.yaml :
- platform: template
sensors:
myelectricaldata_daily_cost:
friendly_name: "Coût d'hier"
unit_of_measurement: "€"
value_template: "{{ states.sensor.linky_XXX_consumption.attributes.daily_cost}}"
myelectricaldata_yesterday:
friendly_name: "Hier"
value_template: "{{ states.sensor.linky_XXX_consumption.attributes.day_2 }}"
unit_of_measurement: "kWh"
myelectricaldata_current_week:
value_template: "{{ states.sensor.linky_XXX_consumption.attributes.current_week }}"
friendly_name: "Conso de la semaine"
unit_of_measurement: "KWh"
etc.......
je n’ai pas mes entités dans Outils de développement/Etats/ → « myelectricaldata_yesterday » ou « Hier »
du coup ca ne marche pas quand je crée mes cartes … quelqu’un a une idée ?
Bonjour,
les entités son nommé sensor.linky_xxxxxxxxxxxxxxxx_consumption, ou xxxxxxxxxxxxxxxx est le numéro de PDL de ton compteur. Elle sont plus nommer myelectricaldata, ca changer il y a quelques mois.
Merci @WarC0zes !
Mais alors qu’est ce que je dois mettre dans les cartes pour rapatrier les infos.
Car si je met
type: vertical-stack
cards:
- title: Consommation Kwh
type: horizontal-stack
cards:
- type: custom:mushroom-entity-card
entity: sensor.myelectricaldata_yesterday
icon: mdi:flash
icon_color: blue
layout: vertical
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
primary_info: name
secondary_info: state
name: Hier
icon_type: icon
fill_container: false
- type: custom:mushroom-entity-card
entity: sensor.myelectricaldata_current_week
icon: mdi:flash
icon_color: amber
layout: vertical
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
primary_info: name
secondary_info: state
name: sur 7 jours
icon_type: icon
- type: custom:mushroom-entity-card
entity: sensor.myelectricaldata_current_month
icon: mdi:flash
icon_color: green
layout: vertical
tap_action:
action: more-info
hold_action:
action: none
double_tap_action:
action: none
name: Mois en cours
primary_info: name
secondary_info: state
icon_type: icon
Ça ne fonctionne pas
Et si je remplace les sensor.myelectricaldata par sensor.liny_monPDL, ça ne fonctionne pas non plus.
Et si je met sensor.linky_monPDL_consumption, j’ai bien une valeur mais toujours la même
Et sensor.linky_PDL_consumption.attributes.yesterday ne marche pas
Pour ceux template sensor, la source est l’entité sensor.linky_XXX_consumption, et le sensor template se nommera sensor.myelectricaldata_daily_cost.
Dans ta carte, il faut utiliser le sensor template, donc sensor.myelectricaldata_daily_cost.
Vérifie que l’entité sensor.linky_XXX_consumption remontent bien les informations.
Vérifie que le template donne bien un résultat, dans l’outil de dev et modèle
{{ states.sensor.linky_XXX_consumption.attributes.daily_cost}}
Vérifie que l’entité sensor template, sensor.myelectricaldata_daily_cost est bien créer dans l’outils de dev / état.
Dans le dev/etat, je n’ai pas l’entité : sensor.myelectricaldata_daily_cost
pourtant bien déclaré dans mon configuration.yaml, cf msg plus haut, c’est ca que je comprend pas …
@WarC0zes j’ai trouvé!!!
En fait j’avais tous mes sensors dans mon fichier configuration.yaml, et ca ne marchait pas.
Il faut dans le fichier ‹ configuration.yaml › :
sensor: !include sensors.yaml
et dans le fichier ‹ sensors.yaml ›
#MY ELECTRICAL DATA
- platform: template
sensors:
myelectricaldata_daily_cost:
friendly_name: "Coût d'hier"
unit_of_measurement: "€"
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.daily_cost}}"
myelectricaldata_yesterday:
friendly_name: "Hier"
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.day_2 }}"
unit_of_measurement: "kWh"
myelectricaldata_current_week:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.current_week }}"
friendly_name: "Conso de la semaine"
unit_of_measurement: "KWh"
myelectricaldata_current_month:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.current_month }}"
friendly_name: "Conso du mois"
unit_of_measurement: "KWh"
myelectricaldata_current_year:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.current_year }}"
friendly_name: "Conso de l'année'"
unit_of_measurement: "KWh"
myelectricaldata_last_week:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.last_week }}"
friendly_name: "Conso semaine dernière"
unit_of_measurement: "KWh"
myelectricaldata_last_month:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.last_month }}"
friendly_name: "Conso du mois dernier"
unit_of_measurement: "KWh"
myelectricaldata_last_year:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.last_year }}"
friendly_name: "Conso de l'année dernière'"
unit_of_measurement: "KWh"
myelectricaldata_last_update:
value_template: "{{ as_timestamp(states.sensor.linky_19515195254897_consumption.attributes.lastUpdate,0) | timestamp_custom('%d-%m-%Y %H:%M',local=True)}}"
friendly_name: "Date Mise à Jour"
myelectricaldata_last_week_cost:
value_template: "{{'%.2f'|format((states('sensor.myelectricaldata_last_week')|float) * 0.1410)}}"
friendly_name: "Coût dernière semaine'"
unit_of_measurement: "€"
myelectricaldata_last_month_cost:
value_template: "{{'%.2f'|format((states('sensor.myelectricaldata_last_month')|float) * 0.1410)}}"
friendly_name: "Coût du mois dernier'"
unit_of_measurement: "€"
myelectricaldata_last_year_cost:
value_template: "{{'%.2f'|format((states('sensor.myelectricaldata_last_year')|float) * 0.1410)}}"
friendly_name: "Coût de l'année dernière'"
unit_of_measurement: "€"
#YesterdayConsumptionMaxPower
myelectricaldata_yesterdayconsumptionmaxpower:
#value_template: "{{ float(states.sensor.linky_19515195254897_consumption.attributes.yesterdayConsumptionMaxPower) * 0.001 }}"
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.YesterdayConsumptionMaxPower }}"
friendly_name: "Puissance Max d'hier"
unit_of_measurement: "KVa"
#subscribed_power
myelectricaldata_subscribed_power:
value_template: "{{ states.sensor.linky_19515195254897_consumption.attributes.subscribed_power }}"
friendly_name: "Puissance Souscrite"
unit_of_measurement: "KVa"
Cela fait des semaines que je voulais utiliser les includes pour les sensors, et j’avais toujours des errors… chose faite 
Bonjour,
Par contre tu devrais mettre à jour tes templates au nouveau format.
Cela t’évitera d’y revenir quand ce sera basculé.
Salut quel templates au nouveau format ?? tu as un exemple
Voir la doc :
C’est plus parlant. Et pas mal de conversations ici.
Salut chez moi le sensor template, sensor.myelectricaldata_daily_cost est bien créer dans l’outils de dev / état. mais je n’ai pas de retour
Si tu cherche plus des valeurs, p.e. si t’es sur Tempo, on peut les télécharger depuis MQTT, p.e.
mqtt:
sensor:
- state_topic: myelectricaldata/xxxxx/consumption/annual/current/thisYear/tempo/BLUE_HC/kWh
value_template: "{{ value_json }}"
unique_id: linky_consumption_annual_blue_hc
name: linky consumption annual blue hc
icon: mdi:lightning-bolt
device_class: energy
unit_of_measurement: kWh
state_class: total_increasing
- state_topic: myelectricaldata/xxxx/consumption/annual/current/thisYear/tempo/BLUE_HP/kWh
value_template: "{{ value_json }}"
unique_id: linky_consumption_annual_blue_hp
name: linky consumption annual blue hp
icon: mdi:lightning-bolt
device_class: energy
unit_of_measurement: kWh
state_class: total_increasingDans sensor.yaml
### MyelectricalData ###
- platform: template
sensors:
myelectricaldata_daily_cost:
friendly_name: "Coût d'hier"
unit_of_measurement: "€"
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.daily_cost }}"
myelectricaldata_yesterday:
friendly_name: "Hier"
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.day_2 }}"
unit_of_measurement: "kWh"
myelectricaldata_current_week:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.current_week }}"
friendly_name: "Conso de la semaine"
unit_of_measurement: "KWh"
myelectricaldata_current_month:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.current_month }}"
friendly_name: "Conso du mois"
unit_of_measurement: "KWh"
myelectricaldata_current_year:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.current_year }}"
friendly_name: "Conso de l'année'"
unit_of_measurement: "KWh"
myelectricaldata_last_week:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.last_week }}"
friendly_name: "Conso semaine dernière"
unit_of_measurement: "KWh"
myelectricaldata_last_month:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.last_month }}"
friendly_name: "Conso du mois dernier"
unit_of_measurement: "KWh"
myelectricaldata_last_year:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.last_year }}"
friendly_name: "Conso de l'année dernière'"
unit_of_measurement: "KWh"
myelectricaldata_last_update:
value_template: "{{ as_timestamp(states.sensor.linky_consumption_162XXXXXXX6741.attributes.lastUpdate,0) | timestamp_custom('%d-%m-%Y %H:%M',local=True)}}"
friendly_name: "Date Mise à Jour"
myelectricaldata_last_week_cost:
value_template: "{{'%.2f'|format((states('sensor.linky_last_week')|float) * 0.1410)}}"
friendly_name: "Coût dernière semaine'"
unit_of_measurement: "€"
myelectricaldata_last_month_cost:
value_template: "{{'%.2f'|format((states('sensor.linky_last_month')|float) * 0.1410)}}"
friendly_name: "Coût du mois dernier'"
unit_of_measurement: "€"
myelectricaldata_last_year_cost:
value_template: "{{'%.2f'|format((states('sensor.linky_last_year')|float) * 0.1410)}}"
friendly_name: "Coût de l'année dernière'"
unit_of_measurement: "€"
#YesterdayConsumptionMaxPower
myelectricaldata_yesterdayconsumptionmaxpower:
#value_template: "{{ float(states.sensor.linky_consumption_<num pdl>.attributes.yesterdayConsumptionMaxPower) * 0.001 }}"
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.YesterdayConsumptionMaxPower }}"
friendly_name: "Puissance Max d'hier"
unit_of_measurement: "KVa"
#subscribed_power
myelectricaldata_subscribed_power:
value_template: "{{ states.sensor.linky_consumption_162XXXXXXX6741.attributes.subscribed_power }}"
friendly_name: "Puissance Souscrite"
unit_of_measurement: "KVa"
Dans config.yaml
cycle: 14400
debug: false
home_assistant:
discovery: true
discovery_prefix: homeassistant
enable: true
home_assistant_ws:
enable: true
ssl: false
token: eyJhbGciOiJIUzI1NiIsXXXXXXXXXXXXXXXXXXZjhjMDk5ZGU5ZDM5ZiIsImlhdCI6MTcyMTkzOTU4NiwiZXhwIjoyMDM3Mjk5NTg2fQ.XPm6RwC3AqrznlnNe_Q7Q0y4NViQgGDRmswQG9dDp1Q
url: http://192.168.2.189:8123/
influxdb:
batching_options:
batch_size: 1000
exponential_base: 2
flush_interval: 1000
jitter_interval: 0
max_retries: 5
max_retry_delay: 125000
max_retry_time: 180000
retry_interval: 5000
bucket: myelectricaldata
enable: false
hostname: a0d7b954-influxdb
method: synchronous
org: myelectricaldata
port: 8086
token: myelectricaldata:myelectricaldata
log2file: false
mqtt:
client_id: myelectricaldata
enable: true
hostname: core-mosquitto
password: moXXXXXtto
port: 1883
prefix: myelectricaldata
qos: 0
retain: true
username: moXXXXXtto
myelectricaldata:
1622XXXXXX6741:
addresses: 'true'
cache: true
consumption: true
consumption_detail: true
consumption_detail_max_date: '2024-01-01'
consumption_max_date: '2024-01-01'
consumption_max_power: true
consumption_price_base: 0.2161
consumption_price_hc: 0.1668
consumption_price_hp: 0.2161
enable: true
name: Maison
offpeak_hours_0: 23H56-7H56
offpeak_hours_1: 23H56-7H56
offpeak_hours_2: 23H56-7H56
offpeak_hours_3: 23H56-7H56
offpeak_hours_4: 23H56-7H56
offpeak_hours_5: 23H56-7H56
offpeak_hours_6: 23H56-7H56
plan: HC/HP
production: false
production_detail: false
production_detail_max_date: '2024-01-01'
production_max_date: '2024-01-01'
production_price: 0.0
refresh_addresse: false
refresh_contract: false
token: afnSXXXXXXXXLUKCs49jG-_3vqXXXXXXXXXRUhjg_1nY8=
wipe_influxdb: false
Et dans configuration.yaml
sensor: !include sensors.yaml
Bonjour @idefix24,
utilise la balise texte préformaté 
quand tu colles du code dans un message. Ça permet une meilleure visibilité du code et respecte les espaces.
J’ai corrigé ton message.
edit:
Ta supprimer ma modification 
Bonjour @WarC0zes,
Il me semble avoir aperçu dans une capture plus récente que tu avais récupéré l’icone…
Te souviens tu de la solution? Car je rencontre le même problème 
D’avance merci 
Bonjour,
il faut utiliser c’est carte, ça été corrigé depuis un moment. Il faut mettre à jour la carte.
Avant, l’icon Linky était recupéré d’un site web, pas souvent dispo.
Maintenant, l’icone est local (dossie; icons)
Un vidage du cache du navigateur, peu aider.
salut,
J’ai parcouru ton github et sous la page de l’energie il y a aucune info et j’ai pas trouvé ailleurs.
Je trouve ta page bien faite.