Bonjour,
L’autosuffisance du module énergie reste bloquée à 0%, malgré le fait que toutes les mesures de consommation edf et de production solaire soient bien affichées.
Ci-jointes quelques copies d’écrans
.
Auriez vous une piste svp ?
Merci.
Ma configuration
[center]## System Information
| version |
core-2025.12.5 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| container_arch |
aarch64 |
| user |
root |
| virtualenv |
false |
| python_version |
3.13.9 |
| os_name |
Linux |
| os_version |
6.12.47-haos-raspi |
| arch |
aarch64 |
| timezone |
Europe/Paris |
| config_dir |
/config |
Home Assistant Community Store
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| HACS Data |
ok |
| GitHub API Calls Remaining |
5000 |
| Installed Version |
2.0.5 |
| Stage |
running |
| Available Repositories |
2519 |
| Downloaded Repositories |
18 |
Solcast Solar
Home Assistant Cloud
| logged_in |
false |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
Home Assistant Supervisor
| host_os |
Home Assistant OS 16.3 |
| update_channel |
stable |
| supervisor_version |
supervisor-2025.12.3 |
| agent_version |
1.7.2 |
| docker_version |
28.3.3 |
| disk_total |
116.6 GB |
| disk_used |
23.1 GB |
| nameservers |
8.8.4.4, 8.8.8.8, 192.168.50.1 |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
true |
| virtualization |
|
| board |
rpi5-64 |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
Matter Server (8.1.2), File editor (5.8.0), Z-Wave JS UI (6.1.2), Zigbee2MQTT (2.7.2-1), Terminal & SSH (9.21.0), Z-Wave JS (0.27.0), Mosquitto broker (6.5.2), ESPHome Device Builder (2025.12.4), Samba share (12.5.4) |
Dashboards
| dashboards |
4 |
| resources |
7 |
| views |
11 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethd56584f (disabled), veth0f83f8e (disabled), veth9011591 (disabled), vethf0fa4be (disabled), veth22e2bee (disabled), veth4793a28 (disabled), vethde32825 (disabled), veth3423d21 (disabled), veth5967647 (disabled), vethe05009c (disabled), veth558e33e (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), end0 (192.168.50.200/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethd56584f (), veth0f83f8e (), veth9011591 (), vethf0fa4be (), veth22e2bee (), veth4793a28 (), vethde32825 (), veth3423d21 (), veth5967647 (), vethe05009c (), veth558e33e () |
| ipv6_addresses |
lo (::1/128), end0 (fe80::3cb6:9e07:e821:d68a/64), hassio (fe80::e4e8:83ff:fe5b:4015/64), docker0 (fe80::54b0:a4ff:fe6d:6c29/64), vethd56584f (fe80::84bc:77ff:fec8:9bba/64), veth0f83f8e (fe80::74ec:12ff:fe27:8353/64), veth9011591 (fe80::d4d6:b3ff:fed2:bee2/64), vethf0fa4be (fe80::aca9:f1ff:fedf:bad2/64), veth22e2bee (fe80::88d8:64ff:fed4:d46b/64), veth4793a28 (fe80::dc25:30ff:fe6b:e31/64), vethde32825 (fe80::18e0:7ff:fefa:1f0d/64), veth3423d21 (fe80::9426:26ff:fe06:1ea8/64), veth5967647 (fe80::94ac:6cff:fea8:3058/64), vethe05009c (fe80::30e9:fdff:fe54:d647/64), veth558e33e (fe80::bccb:31ff:fe35:e70c/64) |
| announce_addresses |
192.168.50.200, fe80::3cb6:9e07:e821:d68a |
Recorder
| oldest_recorder_run |
24 décembre 2025 à 06:05 |
| current_recorder_run |
4 janvier 2026 à 07:32 |
| estimated_db_size |
1621.82 MiB |
| database_engine |
sqlite |
| database_version |
3.49.2 |
Xiaomi Miot
| component_version |
1.1.1 |
| can_reach_server |
ok |
| can_reach_spec |
ok |
| logged_accounts |
1 |
| total_devices |
3 |
[/center]
Salut,
soit ta config du dashboard énergie n’est pas bonne, soit c’est ok et tu es vraiment ) 0% 
Mais en tout cas les chiffres semblent s’équilibrer tu consommes autant pour ta maison que tu soutires du réseau… donc 0% d’autosuffisance semble correct.
Cette valeur c’est le ratio entre ces 2 capteurs.
