WarC0zes
commented
5 days ago Bonjour, même problème remarqué depuis deux jours.
2024-11-07 17:02:29.410 - INFO : Récupération des données : 2024-11-02 => 2024-11-09
2024-11-07 17:02:29.432 - INFO : - 4319m absente du relevé.
2024-11-07 17:02:29.434 - INFO : Chargement des données depuis MyElectricalData 2024-11-02 => 2024-11-09
2024-11-07 17:02:34.326 - INFO : Chargement des données depuis MyElectricalData 2024-06-21 => 2024-06-22
2024-11-07 17:02:35.763 - INFO : 127.0.0.1:53602 - "GET / HTTP/1.1" 200
2024-11-07 17:02:36.144 - ERROR : Echec de la récupération des données.
2024-11-07 17:02:36.144 - ERROR : => no measure found for this usage point
2024-11-07 17:02:36.145 - ERROR : => 2024-06-21 -> 2024-06-222024-11-07 17:02:06.129 - INFO : offpeak_hours_0: 20H56-4H56
2024-11-07 17:02:06.129 - INFO : offpeak_hours_1: 20H56-4H56
2024-11-07 17:02:06.129 - INFO : offpeak_hours_2: 20H56-4H56
2024-11-07 17:02:06.129 - INFO : offpeak_hours_3: 20H56-4H56
2024-11-07 17:02:06.130 - INFO : offpeak_hours_4: 20H56-4H56
2024-11-07 17:02:06.130 - INFO : offpeak_hours_5: 20H56-4H56
2024-11-07 17:02:06.130 - INFO : offpeak_hours_6: 20H56-4H56
2024-11-07 17:02:06.130 - INFO : plan: HC/HP
2024-11-07 17:02:06.130 - INFO : tempo:
2024-11-07 17:02:06.130 - INFO : enable: False
2024-11-07 17:02:06.130 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-11-07 17:02:06.130 - INFO : Check config.yaml :
2024-11-07 17:02:06.130 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-11-07 17:02:06.130 - INFO : CONFIG VALID
2024-11-07 17:02:06.130 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
2024-11-07 17:02:07.591 - INFO : Configure Databases
2024-11-07 17:02:07.659 - INFO : => day
2024-11-07 17:02:07.666 - INFO : => call_number
2024-11-07 17:02:07.670 - INFO : => max_call
2024-11-07 17:02:07.674 - INFO : => version
2024-11-07 17:02:07.680 - INFO : => lock
2024-11-07 17:02:07.684 - INFO : => lastUpdate
2024-11-07 17:02:07.684 - INFO : Success
2024-11-07 17:02:07.684 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-11-07 17:02:07.684 - INFO : Connect to MQTT broker core-mosquitto:1883
2024-11-07 17:02:07.696 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-11-07 17:02:07.696 - INFO : CONNECTION SUCCESS
2024-11-07 17:02:07.696 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
/app/models/query_contract.py:40: SyntaxWarning: invalid escape sequence '\('
offpeak_hours = re.search("HC \((.*)\)", contracts["offpeak_hours"]).group(1)
2024-11-07 17:02:08.451 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2024-11-07 17:02:08.451 - INFO : RUN IN PRODUCTION MODE
2024-11-07 17:02:08.452 - INFO : ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ◦ ❖ ◦ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━dans le supervisor 2024.10.2, quand je redémarre MED:
2024-11-07 17:01:48.218 INFO (SyncWorker_6) [supervisor.docker.manager] Stopping addon_db21ed7f_enedisgateway2mqtt application
2024-11-07 17:01:48.625 INFO (SyncWorker_6) [supervisor.docker.manager] Cleaning addon_db21ed7f_enedisgateway2mqtt application
2024-11-07 17:01:48.742 ERROR (MainThread) [supervisor.docker.addon] Add-on MyElectricalData try to access to blocked device sda!
2024-11-07 17:01:48.749 ERROR (MainThread) [supervisor.docker.addon] Add-on MyElectricalData try to access to blocked device sda1!
2024-11-07 17:01:48.756 ERROR (MainThread) [supervisor.docker.addon] Add-on MyElectricalData try to access to blocked device sda7!
2024-11-07 17:01:48.756 ERROR (MainThread) [supervisor.docker.addon] Add-on MyElectricalData try to access to blocked device sda8!
2024-11-07 17:01:49.468 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/alexbelgium/myelectricaldata-aarch64 with version 0.13.2config.yaml
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: xxxxxxxxxxxxxxxxx
password: xxxxxxxxxxxxxxxxxx
prefix: myelectricaldata
client_id: myelectricaldata
retain: true
qos: 0
myelectricaldata:
"2414xxxxxxxxxx":
enable: 'true'
token: guHxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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
offpeak_hours_1: 20H56-4H56
offpeak_hours_2: 20H56-4H56
offpeak_hours_3: 20H56-4H56
offpeak_hours_4: 20H56-4H56
offpeak_hours_5: 20H56-4H56
offpeak_hours_6: 20H56-4H56
plan: HC/HP
tempo:
enable: falseHAOS: 13.1 core: 2024.11.0 supervisor: 2024.11.2 MyElectricalData: 0.13.2
ArBohe
Description du bug Depuis quelques jours, plus rien n'arrive dans le content card. J'ai creusé un peu et je m'aperçois que les logs montrent des choses apparement contrdictoires... je suis en Tempo.
Configuration (config.yaml)
```yaml backend: uri: sqlite:////data/myelectricaldata.db gateway: ssl: true url: myelectricaldata.fr home_assistant: discovery_prefix: homeassistant enable: true home_assistant_ws: batch_size: 1000 enable: true max_date: null purge: false ssl: true token: *********** url: ********* 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: 192.168.68.150 method: synchronous org: myelectricaldata port: 8086 scheme: http timezone: UTC token: myelectricaldata wipe: false logging: debug: true log2file: false log_format: '%(asctime)s.%(msecs)03d - %(levelname)8s : %(message)s' log_format_date: '%Y-%m-%d %H:%M:%S' log_http: false mqtt: cert: false client_id: myelectricaldata enable: true hostname: core-mosquitto password: ********************* port: 1883 prefix: myelectricaldata qos: 0 retain: true username: homeassistant myelectricaldata: '***************': addresses: true cache: true consumption: true consumption_detail: true consumption_detail_max_date: '2023-01-01' consumption_max_date: '2023-01-01' consumption_max_power: true consumption_price_base: 0.145907 consumption_price_hc: 0.124364 consumption_price_hp: 0.164915 enable: true name: Maison 56 offpeak_hours_0: 22H00-6H00 offpeak_hours_1: 22H00-6H00 offpeak_hours_2: 22H00-6H00 offpeak_hours_3: 22H00-6H00 offpeak_hours_4: 22H00-6H00 offpeak_hours_5: 22H00-6H00 offpeak_hours_6: 22H00-6H00 plan: Tempo production: false production_detail: false production_detail_max_date: '2023-01-01' production_max_date: '2023-01-01' production_price: 0.0 refresh_addresse: false refresh_contract: false token: Q3CRkUU2jeaUP_YsncA1hVoe0tFPA56DqSJIu4w7PWA= server: certfile: '' cidr: 0.0.0.0 cycle: 14400 keyfile: '' port: 5000 tempo: enable: true price_blue_hc: 0.1056 price_blue_hp: 0.1369 price_red_hc: 0.1328 price_red_hp: 0.7324 price_white_hc: 0.1246 price_white_hp: 0.1654 ```Voici ce que je vois dans les logs:
Tout d'abord, config OK
Tout semble OK au départ
Tout est OK sur la passerelle
et la, ca se gate :)
Notez le consent OK et le quota_reach OK
et la:
etc... tout est en erreur, et rien n'est ramené
Merci pour votre aide !!!
Type d'installation
Version : 0.13.2