Oui mais je ne trouve pas mon erreur…
MQTT est déjà installé sur mon HA, je ne comrpends pas si je dois utiliser une installation alternative ou pas…j’ai ensuite installé le addon Gazapr 2 MQTT…Est ce que l’erreur provient de la facon dont est installé le broker ? l’addon ?
J’ai modifié mon YAML, une partie des erreurs à été résolue…
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Copying config
[16:18:27] INFO: ... mqtt_autodiscover is defined in options, attempting autodiscovery...
[16:18:27] INFO: ... MQTT service found, fetching server detail (you can enter those manually in your config file) ...
MQTT_HOST=core-mosquitto
MQTT_PORT=1883
MQTT_SSL=false
MQTT_USERNAME=addons
MQTT_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxxxxshoo8s
2024-10-05 16:18:29,385 INFO -----------------------------------------------------------
2024-10-05 16:18:29,385 INFO # Welcome to gazpar2mqtt #
2024-10-05 16:18:29,385 INFO -----------------------------------------------------------
2024-10-05 16:18:29,385 INFO Program version : 0.8.7
2024-10-05 16:18:29,386 INFO Database version : 0.4.0
2024-10-05 16:18:29,386 INFO Influxdb version : 0.1.0
2024-10-05 16:18:29,386 INFO Please note that the the tool is under development, various functions may disappear or be modified.
2024-10-05 16:18:29,387 INFO -----------------------------------------------------------
2024-10-05 16:18:29,387 INFO # Program parameters #
2024-10-05 16:18:29,387 INFO -----------------------------------------------------------
2024-10-05 16:18:29,387 INFO MQTT broker config : host = core-mosquitto, port = 1883, clientId = gazpar_client_haos, qos = 1, topic = gazpar_haos, retain = True, ssl = False
2024-10-05 16:18:29,387 INFO Standlone mode : Enable = False
2024-10-05 16:18:29,387 INFO Home Assistant discovery : Enable = False, Topic prefix = homeassistant, Device name = gazpar
2024-10-05 16:18:29,388 INFO Threshold options : Warning percentage = 80
2024-10-05 16:18:29,388 INFO Database options : Force reinitialization = False, Path = /data
2024-10-05 16:18:29,388 INFO Debug mode : Enable = False
2024-10-05 16:18:29,388 INFO Check parameters...
2024-10-05 16:18:29,388 WARNING Both Standalone mode and Home assistant discovery are disable. No value will be published to MQTT ! Please check your parameters.
2024-10-05 16:18:29,388 INFO Parameters are ok !
2024-10-05 16:18:29,389 INFO -----------------------------------------------------------
2024-10-05 16:18:29,389 INFO # Connection to SQLite database #
2024-10-05 16:18:29,389 INFO -----------------------------------------------------------
2024-10-05 16:18:29,389 INFO Connection to SQLite database...
2024-10-05 16:18:29,391 INFO SQLite database connected !
2024-10-05 16:18:29,393 INFO Last execution date 2024-10-05 10:34:43.691124, program was in version 0.8.7.
2024-10-05 16:18:29,393 INFO Checking database version...
2024-10-05 16:18:29,393 INFO Your database is already up to date : version 0.4.0.
2024-10-05 16:18:29,394 INFO Retrieve database statistics...
2024-10-05 16:18:29,394 INFO 0 informatives measures stored
2024-10-05 16:18:29,395 INFO 0 PCE(s)
2024-10-05 16:18:29,395 INFO First measure : None
2024-10-05 16:18:29,395 INFO Last measure : None
2024-10-05 16:18:29,395 INFO -----------------------------------------------------------
2024-10-05 16:18:29,395 INFO # Connection to Mqtt broker #
2024-10-05 16:18:29,395 INFO -----------------------------------------------------------
2024-10-05 16:18:29,395 INFO Connect to Mqtt broker...
2024-10-05 16:18:33,401 INFO Mqtt broker connected !
2024-10-05 16:18:33,402 INFO -----------------------------------------------------------
2024-10-05 16:18:33,402 INFO # Get data from GRDF website #
2024-10-05 16:18:33,402 INFO -----------------------------------------------------------
2024-10-05 16:18:33,590 INFO Unable to login to GRDF website
2024-10-05 16:18:33,590 INFO Wait 20 seconds (0 min) before next try
Encore sans debug… je ne suis pas clairvoyant et tant des gens preuvent que ça marche
EDIT: et cacher ton mdp
Ok, Je ne dis pas que ca ne fonctionne pas, je sais bien que le probleme vient de chez moi mais j’aimerais le trouver…voilà avec debug activé, ca fonctionnait avec l’ancienne version, j’ai modifié a nouveau mon YAML…
Copying config
[18:39:38] INFO: ... mqtt_autodiscover is defined in options, attempting autodiscovery...
[18:39:39] INFO: ... MQTT service found, fetching server detail (you can enter those manually in your config file) ...
MQTT_HOST=core-mosquitto
MQTT_PORT=1883
MQTT_SSL=false
MQTT_USERNAME=addons
MQTT_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2024-10-05 18:39:41,080 INFO -----------------------------------------------------------
2024-10-05 18:39:41,080 INFO # Welcome to gazpar2mqtt #
2024-10-05 18:39:41,080 INFO -----------------------------------------------------------
2024-10-05 18:39:41,080 INFO Program version : 0.8.7
2024-10-05 18:39:41,081 INFO Database version : 0.4.0
2024-10-05 18:39:41,081 INFO Influxdb version : 0.1.0
2024-10-05 18:39:41,081 INFO Please note that the the tool is under development, various functions may disappear or be modified.
2024-10-05 18:39:41,082 DEBUG If you can read this line, you are in DEBUG mode.
2024-10-05 18:39:41,082 INFO -----------------------------------------------------------
2024-10-05 18:39:41,082 INFO # Program parameters #
2024-10-05 18:39:41,082 INFO -----------------------------------------------------------
2024-10-05 18:39:41,082 DEBUG GRDF config : username = xxxxxxx@gmail.com, password = xxxxxxxxxxxxxx
2024-10-05 18:39:41,082 INFO MQTT broker config : host = core-mosquitto, port = 1883, clientId = gazpar_client_haos, qos = 1, topic = gazpar_haos, retain = True, ssl = False
2024-10-05 18:39:41,082 INFO Standlone mode : Enable = False
2024-10-05 18:39:41,083 INFO Home Assistant discovery : Enable = True, Topic prefix = homeassistant, Device name = gazpar
2024-10-05 18:39:41,083 INFO Threshold options : Warning percentage = 80
2024-10-05 18:39:41,083 INFO Database options : Force reinitialization = False, Path = /data
2024-10-05 18:39:41,083 INFO Debug mode : Enable = True
2024-10-05 18:39:41,083 INFO Check parameters...
2024-10-05 18:39:41,083 INFO Parameters are ok !
2024-10-05 18:39:41,083 INFO -----------------------------------------------------------
2024-10-05 18:39:41,083 INFO # Connection to SQLite database #
2024-10-05 18:39:41,083 INFO -----------------------------------------------------------
2024-10-05 18:39:41,083 INFO Connection to SQLite database...
2024-10-05 18:39:41,084 DEBUG Connexion to database
2024-10-05 18:39:41,084 INFO SQLite database connected !
2024-10-05 18:39:41,085 INFO Last execution date 2024-10-05 10:34:43.691124, program was in version 0.8.7.
2024-10-05 18:39:41,085 INFO Checking database version...
2024-10-05 18:39:41,085 INFO Your database is already up to date : version 0.4.0.
2024-10-05 18:39:41,086 INFO Retrieve database statistics...
2024-10-05 18:39:41,086 INFO 0 informatives measures stored
2024-10-05 18:39:41,086 INFO 0 PCE(s)
2024-10-05 18:39:41,087 INFO First measure : None
2024-10-05 18:39:41,087 INFO Last measure : None
2024-10-05 18:39:41,087 INFO -----------------------------------------------------------
2024-10-05 18:39:41,087 INFO # Connection to Mqtt broker #
2024-10-05 18:39:41,087 INFO -----------------------------------------------------------
2024-10-05 18:39:41,087 INFO Connect to Mqtt broker...
2024-10-05 18:39:41,088 DEBUG Mqtt connect : activation of callbacks
2024-10-05 18:39:41,088 DEBUG Mqtt connect : connection to broker core-mosquitto:1883...
2024-10-05 18:39:41,091 DEBUG Wait for conexion callback
2024-10-05 18:39:43,093 DEBUG Mqtt on_connect callback : Connection Accepted.
2024-10-05 18:39:43,093 DEBUG Mqtt on_connect callback : connected
2024-10-05 18:39:45,093 INFO Mqtt broker connected !
2024-10-05 18:39:45,093 INFO -----------------------------------------------------------
2024-10-05 18:39:45,093 INFO # Get data from GRDF website #
2024-10-05 18:39:45,093 INFO -----------------------------------------------------------
2024-10-05 18:39:45,094 DEBUG Connection to GRDF, try 1/14...
2024-10-05 18:39:45,094 DEBUG After init
2024-10-05 18:39:45,094 DEBUG After myGrdf
2024-10-05 18:39:45,102 DEBUG Starting new HTTPS connection (1): connexion.grdf.fr:443
2024-10-05 18:39:45,291 DEBUG https://connexion.grdf.fr:443 "POST /api/v1/authn HTTP/11" 401 None
2024-10-05 18:39:45,297 INFO Unable to login to GRDF website
2024-10-05 18:39:45,297 INFO Wait 20 seconds (0 min) before next try
J’ai bien testé les identifiants sur l’URL GRDF et ca fonctionne…
De la part dev-guide:
The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource .
1. Verify credentials fr FR · vingerha/gazpar_2_mqtt Wiki (github.com)
Mes identifiants ont été testés, ils fonctionnent…
J’ai vérifié 10 fois, il n’y a pas d’erreur dans les identifiants inscrits dans le yaml…
Néanmoins…l’erreur est claire. Car tu ne veux pas partager tes coord. (et je le respecte)…plus d’idées
Les champs sont bien renseignés dans mon YAML ??
GRDF_USERNAME="xxxxxxxxxxxx@gmail.com"
GRDF_PASSWORD="xxxxxxxxxxxxxx"
Avec bien sur les memes identifiants que ceux saisis dans l’URL GRDF…
Un peu d’aide svp. Voici mes logs:
DEBUG Add price : pce = XXXXXX, startDate = 2019-01-01, endDate = 2099-12-31, pricekWh = 0.10346, priceFix = 1.32
2024-10-06 06:35:41,482 INFO 1 range(s) of prices found !
2024-10-06 06:35:41,482 INFO -----------------------------------------------------------
2024-10-06 06:35:41,482 INFO # Write prices #
2024-10-06 06:35:41,483 INFO -----------------------------------------------------------
2024-10-06 06:35:41,483 DEBUG Query_I: UPDATE measures SET price= ( energyGrossConsumed * 0.10346 ) + 1.32 where pce = 'XXXXXX' and type = 'informative' and date between '2019-01-01' and '2099-12-31'
2024-10-06 06:35:41,488 DEBUG Query_P: UPDATE measures SET price= ( energyGrossConsumed * 0.10346 ) + ((JulianDay(periodEnd) - JulianDay(periodStart)) * 1.32) where pce = 'XXXXXX' and type = 'published' and date between '2019-01-01' and '2099-12-31'
2024-10-06 06:35:41,492 INFO -----------------------------------------------------------
2024-10-06 06:35:41,493 INFO # Home assistant Long Term Statistics (WebService) #
2024-10-06 06:35:41,493 INFO -----------------------------------------------------------
2024-10-06 06:35:41,510 INFO Writing webservice information of PCE XXXXXX alias Maison...
2024-10-06 06:35:41,513 DEBUG Writing Websocket Home Assistant LTS for PCE: XXXXXXX sensor name: gazpar:gazpar_maison_consumption_stat
2024-10-06 06:35:41,513 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,514 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,514 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,514 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,514 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,514 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,514 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,514 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,514 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,514 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,514 CRITICAL The configuration of the Websocket Home Assistant WebSocket is erroneous
2024-10-06 06:35:41,514 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,514 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,514 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,514 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,515 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,515 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,515 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,515 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,515 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,515 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,515 CRITICAL The configuration of the Websocket Home Assistant WebSocket is erroneous
2024-10-06 06:35:41,515 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,515 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,515 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,515 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,515 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,515 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,516 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,516 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,516 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,516 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,516 CRITICAL The configuration of the Websocket Home Assistant WebSocket is erroneous
2024-10-06 06:35:41,516 DEBUG Writing Websocket Home Assistant Published LTS for PCE: XXXXXXX, sensor name: gazpar:gazpar_maison_consumption_pub_stat
2024-10-06 06:35:41,516 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,516 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,516 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,516 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,516 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,516 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,516 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,516 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,516 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,516 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,517 CRITICAL The configuration of the Websocket Home Assistant WebSocket is erroneous
2024-10-06 06:35:41,517 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,517 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,517 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,517 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,517 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,517 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,517 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,517 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,517 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,517 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,517 CRITICAL The configuration of the Websocket Home Assistant WebSocket is erroneous
2024-10-06 06:35:41,517 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,517 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,518 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,518 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,518 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,518 INFO Connection to WebSocket Home Assistant wss://192.168.1.76:8123/api/websocket
2024-10-06 06:35:41,518 ERROR [Errno 111] Connection refused
2024-10-06 06:35:41,518 CRITICAL Connection to Websocket Home Assistant failed
2024-10-06 06:35:41,518 WARNING => WARNING, the WebSocket will be banned after multiple unsuccesful login attempts.
2024-10-06 06:35:41,518 WARNING => ex: 403: Forbidden
2024-10-06 06:35:41,518 CRITICAL The configuration of the Websocket Home Assistant WebSocket is erroneous
2024-10-06 06:35:41,518 INFO -----------------------------------------------------------
2024-10-06 06:35:41,518 INFO # Disconnection from MQTT #
2024-10-06 06:35:41,518 INFO -----------------------------------------------------------
2024-10-06 06:35:42,279 DEBUG Mqtt disconnect : disconnection...
2024-10-06 06:35:42,280 INFO Mqtt broker disconnected
2024-10-06 06:35:42,280 INFO -----------------------------------------------------------
2024-10-06 06:35:42,280 INFO # Disconnection from SQLite database #
2024-10-06 06:35:42,281 INFO -----------------------------------------------------------
2024-10-06 06:35:42,281 DEBUG Disconnexion of the database
2024-10-06 06:35:42,282 INFO SQLite database disconnected
2024-10-06 06:35:42,282 INFO -----------------------------------------------------------
2024-10-06 06:35:42,282 INFO # Next run #
2024-10-06 06:35:42,283 INFO -----------------------------------------------------------
2024-10-06 06:35:42,283 INFO gazpar2mqtt next run scheduled at 06:35
2024-10-06 06:35:42,283 INFO -----------------------------------------------------------
2024-10-06 06:35:42,283 INFO # End of program #
2024-10-06 06:35:42,283 INFO -----------------------------------------------------------
Chercher ce post et utiliser la docu
en effet … je suis passé par l’integration HASS …
Du coup execute latest sur un docker et cela fonctionne
Ca y est ! ca fonctionne enfin chez moi, ne me demandez pas comment, mon probleme d’authentification s’est résolu miraculeusement…
Les couts sont OK, les stats également mais il me reste une question, quelle distinction faites vous entre les stats journalières et les stats périodiques ? Quelle est celle à integrer dans le dash energy ?
Bonjour,
depuis quelques jours (peut-être depuis les dernières mises à jour de HA 2024.10 où j’ai eu un message d’erreur concernant gazpar et les données LTS sans classe ID) je n’ai plus de mise à jour des données de consommation.
Il y a deux erreur dans les logs :
2024-10-09 09:49:30,088 INFO 1 PCE found !
2024-10-09 09:49:30,088 DEBUG Store PCE xxxxxxxxxx into database
2024-10-09 09:49:30,096 INFO ---------------------------------
2024-10-09 09:49:30,096 INFO Get measures of PCE xxxxxxxxx alias home
2024-10-09 09:49:30,096 INFO Range period : from 2021-10-09 (3 years ago) to 2024-10-09 (today) ...
2024-10-09 09:49:30,096 INFO Range period : from 2021-10-09 (self defined) to 2024-10-09 (today) ...
2024-10-09 09:49:30,096 INFO ---------------
2024-10-09 09:49:30,096 INFO Retrieve informative measures...
2024-10-09 09:49:30,552 DEBUG https://monespace.grdf.fr:443 "GET /api/e-conso/pce/consommation/informatives?dateDebut=2021-10-09&dateFin=2024-10-09&pceList%5B%5D=xxxxxxxxxx HTTP/11" 500 None
2024-10-09 09:49:30,552 ERROR Error during informative measures collection
2024-10-09 09:49:30,552 INFO ---------------
2024-10-09 09:49:30,552 INFO Retrieve published measures...
2024-10-09 09:49:30,869 DEBUG https://monespace.grdf.fr:443 "GET /api/e-conso/pce/consommation/publiees?dateDebut=2021-10-09&dateFin=2024-10-09&pceList%5B%5D=xxxxxxxxx HTTP/11" 500 None
2024-10-09 09:49:30,869 ERROR Error during published measures collection
2024-10-09 09:49:30,869 INFO ---------------
2024-10-09 09:49:30,869 INFO Unable to store any measure for PCE xxxxxxxx to database !
2024-10-09 09:49:30,869 INFO ---------------
Je ne vois aucune autre erreur dans les logs gazpar ou HA.
J’ai tout supprimé tout réinstallé au cas où…
Une idée de ce que cela pourrait être ou comment chercher la cause du pb ?
Merci pour votre aide !
Encore / de nouveau des soucis chez grdf… j’ai pareil depuis une semaine
merci pour le retour.
je touche plus rien, le problème semble donc être de l’autre coté du compteur
Bonjour, bizarre chez moi tout est nickel, j’ai vérifié hier soir (récup des datas à 17h30…).
Il me manque juste la conso de dimanche (mais elle n’est pas non plus sur le site de GRDF), sinon tous les autres jours sont ok jusqu’à lundi (normal puisque 2 jours de décalage).
Tants des idées…je pense que je suis bloqué cause de mes commentaires sur leur qualité
De mon coté, rien sur le site GRDF depuis le 7/10… Qui correspond au dernier jour ou j’a ides données sur G2M…La publication des données reste trés aléatoire j’ai l’impression…
Oui mais ça c’est normal, les relevés GRDF ne sont dispos que J-2 maximum.
En fin d’après-midi, tu auras le relevé du 8/10 (on est le 10 aujourd’hui), et ainsi de suite.
C’est pour ça que chez moi le plug-in est lancé en auto à 17h30, pour être sûr avoir le relevé J-2
Regarde sur mon espace c’est idem, ça s’arrête aussi au 7…
Il me manque le 5 mais ça arrive qu’il manque un jour par ci par là…
résolu en ajoutant dans le fichier de conf GRDF_STARTDATE avec une date pour laquelle des données existes coté GRDF.