Mon problème
Bonjour tout le monde,
Je viens de Jeedom, je suivais ma consommation électrique depuis le plugin:
Suivi Conso
, j’ai procédé à quelques essais. A ce jour, je n’ai pas trouvé la solution pour récupérer un affichage et un suivi de ma consommation,
J’ai le module
ZLinky_TIC
en zigbee, il remonte dans un:
container zigbee2mqtt
J’ai également mon
broker mosquitto dans un container
J’ai commencé par paramètrer mon recorder, j’ai installé FileSize, ajouté:
allowlist_external_dirs:
- "/config/"`
à mon fichier de configuration.yaml puis créé mon fichier recorder.yaml avec ce contenu:
purge_keep_days: 20
auto_purge: true
commit_interval: 30
# Include #
include:
domains:
- sensor
- switch
- binary_sensor
- person
- climate
- group
- zone
- sensor.*_energy
- sensor.compteur_denergie_*
- sensor.*_power
- sensor.sun*
- sensor.time_*
- sensor.date_*
- sensor.*_battery
# Exclude
exclude:
# Entity globs
entity_globs:
#- sensor.compteur_denergie_*
#- sensor.*_power
#- sensor.*_energy
#- sensor.sun*
- sensor.*_rssi_numeric
- media_player.*
- light.*
#- sensor.time_*
#- sensor.date_*
- sensor.*_linkquality
- sensor.*_low_battery_level
- update.*
- switch.*
- sensor.freebox_*
#- sensor.*_battery
# Entities
entities:
- sensor.last_boot
- sensor.time
- sensor.date
- sensor.pression_arrosage
- sensor.home_assistant_v2_db_size
- sensor.home_assistant_v2_db_last_updated
- sensor.sonoff_10014a73e9 #SPM
# Event types #
event_types:
- service_removed
- service_executed
- platform_discovered
- homeassistant_start
- homeassistant_stop
- feedreader
- service_registered
- call_service
- component_loaded
- automation_triggered
- script_started
- timer_out_of_sync
- browser_mod
# Domains
domains:
- automation
- camera
- counter
- cover
- device_tracker
- input_boolean
- input_datetime
- media_player
- notify
- persistent_notification
- remote
- scene
- lock
- script_started
- sun
- updater
- weather
- zone
- select
- zwave
- alarm_panel
- automation
- script
- shell_command
Ensuite, fichier configuration.yaml pour utility meter et hp/hc:
# Daily energy
daily_energy:
source: sensor.zlinky_tic_east
name: Daily Energy
cycle: daily
tariffs:
- hp
- hc
# Weekly energy
weekly_energy:
source: sensor.zlinky_tic_east
name: Weekly Energy
cycle: weekly
tariffs:
- hp
- hc
# Monthly energy
monthly_energy:
source: sensor.zlinky_tic_east
name: Monthly Energy
cycle: monthly
tariffs:
- hp
- hc
# Yearly energy
yearly_energy:
source: sensor.zlinky_tic_east
name: Yearly Energy
cycle: yearly
tariffs:
- hp
- hc
J’ai créé une automation pour changé les hc et hp:
alias: HeurePleine - HeureCreuse
description: ""
trigger:
- platform: time
at: "05:34:00"
variables:
tariff: hp
- platform: time
at: "21:34:00"
variables:
tariff: hc
condition: []
action:
- service: select.select_option
target:
entity_id: sensor.daily_total_energy
data:
option: "{{ tariff }}"
- service: select.select_option
target:
entity_id: sensor.weekly_total_energy
data:
option: "{{ tariff }}"
- service: select.select_option
target:
entity_id: sensor.monthly_total_energy
data:
option: "{{ tariff }}"
- service: select.select_option
target:
entity_id: sensor.yearly_total_energy
data:
option: "{{ tariff }}"
mode: single
J’ai également ajouté dess sensor conso et pourcentage:
# Daily energy heure creuse
daily_total_energy:
friendly_name: "Energie journalière consommée"
unit_of_measurement: "kWh"
value_template: "{{ (states('sensor.daily_energy_hp') | float + states('sensor.daily_energy_hc') | float) | round(2) }}"
# Weekly energy
weekly_total_energy:
friendly_name: "Energie hebdo consommée"
unit_of_measurement: "kWh"
value_template: "{{ (states('sensor.weekly_energy_hp') | float + states('sensor.weekly_energy_hc') | float) | round(2) }}"
# Monthly energy
monthly_total_energy:
friendly_name: "Energie mensuelle consommée"
unit_of_measurement: "kWh"
value_template: "{{ (states('sensor.monthly_energy_hp') | float + states('sensor.monthly_energy_hc') | float) | round(2) }}"
# Yearly energy
yearly_total_energy:
friendly_name: "Energie annuelle consommée"
unit_of_measurement: "kWh"
value_template: "{{ (states('sensor.yearly_energy_hp') | float + states('sensor.yearly_energy_hc') | float) | round(2) }}"
# HP / HC
hp_hc:
friendly_name: "Energie mensuelle € hp+hc"
unit_of_measurement: "€"
value_template: "{{ ((((states('sensor.monthly_energy_hp') | float) *
states('input_number.prix_hp') | float) + (( states('sensor.monthly_energy_hc') | float) * states('input_number.prix_hc') | float)) + states('input_number.prix_abo_hchp') | float ) | round (3) }}"
# Mensuel
mensuel:
friendly_name: "Energie mensuelle"
value_template: "{{ states('sensor.monthly_energy_hp') }} HC et {{ states('sensor.monthly_energy_hc') }} HP"
# HP / HC Pourcentage
hc_hp:
friendly_name: "Pourcentage"
value_template: >-
{% set hchp = (states('sensor.monthly_energy_hc') | float) / ((states('sensor.monthly_energy_hp') | float) + (states('sensor.monthly_energy_hc') | float)) %} {% if hchp <= 1 %} {{ hchp| round(2)}} % d'heures creuses {% endif %}
Et pour terminer j’ai ajouté des input_number:
# Prix heure pleine
prix_hp:
name: Prix hp
initial: 0.2228
min: 0
max: 1
step: 0.0001
mode: box
icon: mdi:currency-eur
unit_of_measurement: "€"
# Prix heure creuse
prix_hc:
name: Prix hc
initial: 0.1615
min: 0
max: 1
step: 0.0001
mode: box
icon: mdi:currency-eur
unit_of_measurement: "€"
# Prix abonnement heure creuse / heure pleine
prix_abo_hchp:
name: Prix abo hchp
initial: 15.99
min: 10
max: 20
step: 0.01
mode: box
icon: mdi:currency-eur
unit_of_measurement: "€"
# Contribution au service Public d'Electricite
prix_cspe:
name: Prix cspe
initial: 0.00100
min: 0
max: 1
step: 0.00001
mode: box
icon: mdi:currency-eur
unit_of_measurement: "€"
# Contribution Tarifaire d'Acheminement Electricité
prix_cta:
name: Prix cta
initial: 0.0012
min: 0
max: 1
step: 0.0001
mode: box
icon: mdi:currency-eur
unit_of_measurement: "€"
J’ai vérifié à plusieurs fois mes différents fichiers.configurations, le rendu de mes cartes sur mon Dashboard est incohérent si je compare aux données du tableau Energie,
J’ai une question concernant mon automatisation, actuellement je passe par un trigger time at pour basculer des heures pleines aux heures creuses et inversement,
Est-il possible de faire déclencher mon automatisation depuis l’information
sensor.zlinky_tic_current_price
Si vous avez une idée du pourquoi du comment je suis preneur, cela fait plusieurs jours que je tourne en rond sans trouver la solution,
Si il manque des informations, ne pas hésiter à me soliciter 
Merci pour vos retours,
Bonne journée,
*
Ma configuration
Texte à remplacer par votre configuration
System Information
| version | core-2023.9.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.11.5 |
| os_name | Linux |
| os_version | 6.1.45 |
| arch | x86_64 |
| timezone | Europe/Paris |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.33.0 |
| Stage | running |
| Available Repositories | 1298 |
| Downloaded Repositories | 38 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | 15 octobre 2023 à 02:00 |
| relayer_connected | true |
| relayer_region | eu-central-1 |
| remote_enabled | false |
| remote_connected | false |
| alexa_enabled | true |
| google_enabled | false |
| remote_server | eu-central-1-15.ui.nabu.casa |
| certificate_status | ready |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 10.5 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.09.2 |
| agent_version | 1.5.1 |
| docker_version | 23.0.6 |
| disk_total | 30.8 GB |
| disk_used | 13.1 GB |
| healthy | true |
| supported | true |
| board | ova |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Samba share (10.0.2), Terminal & SSH (9.7.1), SQLite Web (3.9.3), Studio Code Server (5.10.2), AppDaemon (0.13.5), File editor (5.6.0) |
Dashboards
| dashboards | 1 |
|---|---|
| resources | 27 |
| views | 19 |
| mode | storage |
Recorder
| oldest_recorder_run | 6 septembre 2023 à 20:41 |
|---|---|
| current_recorder_run | 26 septembre 2023 à 10:39 |
| estimated_db_size | 6015.88 MiB |
| database_engine | sqlite |
| database_version | 3.41.2 |
