Bonjour,
Comment afficher dans grafana une consommation annuelle ou mensuelle
j’ai réussi a le faire par heure et journalière
que mettre dans le bloc « time(?) »
J’ai essayé M ou m mais ce sont des minutes
Ma configuration
[center]## System Information
| version |
core-2025.2.5 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| user |
root |
| virtualenv |
false |
| python_version |
3.13.1 |
| os_name |
Linux |
| os_version |
6.6.73-haos |
| arch |
x86_64 |
| 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 |
1546 |
| Downloaded Repositories |
13 |
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 14.2 |
| update_channel |
stable |
| supervisor_version |
supervisor-2025.02.1 |
| agent_version |
1.6.0 |
| docker_version |
27.2.0 |
| disk_total |
30.8 GB |
| disk_used |
15.5 GB |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
true |
| virtualization |
kvm |
| board |
ova |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
Advanced SSH & Web Terminal (20.0.1), File editor (5.8.0), InfluxDB (5.0.2), Matter Server (7.0.0), Z-Wave JS UI (3.21.0), ESPHome Device Builder (2025.2.0) |
Dashboards
| dashboards |
2 |
| resources |
7 |
| views |
7 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), enp0s3 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth68d2b50 (disabled), veth3585d62 (disabled), veth56014d7 (disabled), veth235a622 (disabled), vethe33f6e9 (disabled), vethd038076 (disabled), veth53841bd (disabled), veth6b067a0 (disabled), veth39a4040 (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), enp0s3 (192.168.1.236/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth68d2b50 (), veth3585d62 (), veth56014d7 (), veth235a622 (), vethe33f6e9 (), vethd038076 (), veth53841bd (), veth6b067a0 (), veth39a4040 () |
| ipv6_addresses |
lo (::1/128), enp0s3 (fd56:f9a4:a026:934e:c082:834a:7885:a14e/64, fe80::3a8b:3792:5962:f78/64), docker0 (fe80::42:5cff:fee5:e68e/64), hassio (fe80::42:ddff:fe87:1a7b/64), veth68d2b50 (fe80::1801:97ff:fedb:46bc/64), veth3585d62 (fe80::6c55:b0ff:fe1d:e182/64), veth56014d7 (fe80::4c34:c3ff:fec8:819/64), veth235a622 (fe80::10fc:3dff:fe1b:3567/64), vethe33f6e9 (fe80::bc46:72ff:fef6:f255/64), vethd038076 (fe80::1c1e:78ff:feb7:bd77/64), veth53841bd (fe80::68bb:63ff:fe38:b573/64), veth6b067a0 (fe80::f4b2:abff:fe39:5d36/64), veth39a4040 (fe80::d457:f1ff:febb:d021/64) |
| announce_addresses |
192.168.1.236, fd56:f9a4:a026:934e:c082:834a:7885:a14e, fe80::3a8b:3792:5962:f78 |
Recorder
| oldest_recorder_run |
8 février 2025 à 10:32 |
| current_recorder_run |
22 février 2025 à 09:21 |
| estimated_db_size |
1193.49 MiB |
| database_engine |
sqlite |
| database_version |
3.47.1 |
j’ai trouvé une solution
elle n’est pas ideale mais fonctionne tous de même
...GROUP BY time(30d)
