A priori (journal d’installation), tout c’est bien déroulé mais je n’ai aucun sensor qui apparait sous InfluxDB. J’ai donc du rater quelque chose. Si quelqu’un a une piste, je suis preneur
Journal :
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: InfluxDB
Scalable datastore for metrics, events, and real-time analytics
-----------------------------------------------------------
Add-on version: 4.7.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.7.1
Home Assistant Supervisor: 2023.07.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[08:04:03] INFO: Configuring timezone (Europe/Paris)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/create-users.sh
cont-init: info: /etc/cont-init.d/create-users.sh exited 0
cont-init: info: running /etc/cont-init.d/influxdb.sh
cont-init: info: /etc/cont-init.d/influxdb.sh exited 0
cont-init: info: running /etc/cont-init.d/kapacitor.sh
cont-init: info: /etc/cont-init.d/kapacitor.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun chronograf (no readiness notification)
services-up: info: copying legacy longrun influxdb (no readiness notification)
services-up: info: copying legacy longrun kapacitor (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[08:04:06] INFO: Kapacitor is waiting until InfluxDB is available...
s6-rc: info: service legacy-services successfully started
[08:04:06] INFO: Chronograf is waiting until InfluxDB is available...
[08:04:06] INFO: Starting the InfluxDB...
[08:04:27] INFO: Starting Chronograf...
[08:04:27] INFO: Starting the Kapacitor
'##:::'##::::'###::::'########:::::'###:::::'######::'####:'########::'#######::'########::
##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:
##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:
#####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::
##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::
##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::
##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:
..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::
2023/07/10 08:04:27 Using configuration at: /etc/kapacitor/kapacitor.conf
time="2023-07-10T08:04:39+02:00" level=info msg="Moving from version 1.8.0"
time="2023-07-10T08:04:39+02:00" level=info msg="Moving to version 1.10.1"
time="2023-07-10T08:04:39+02:00" level=info msg="Successfully created /data/backup/chronograf.db.1.8.0"
time="2023-07-10T08:04:39+02:00" level=info msg="Reporting usage stats" component=usage freq=24h reporting_addr="https://usage.influxdata.com" stats="os,arch,version,cluster_id,uptime"
time="2023-07-10T08:04:39+02:00" level=info msg="Serving chronograf at http://127.0.0.1:8889" component=server
[08:04:39] INFO: Starting NGINX...
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:55326" response_time="618.525µs" status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:55334" response_time="473.547µs" status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:55348" response_time="462.139µs" status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:55356" response_time=7.539003ms status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:55360" response_time=4.905609ms status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: No Content" component=server method=GET remote_addr="127.0.0.1:55364" response_time=1.699097ms status=204
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:55374" response_time="412.288µs" status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:55390" response_time=3.338861ms status=200
time="2023-07-10T08:09:58+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:55392" response_time=2.820539ms status=200
time="2023-07-10T08:10:01+02:00" level=info msg="Response: No Content" component=server method=GET remote_addr="127.0.0.1:55406" response_time=1.420603ms status=204
time="2023-07-10T08:10:01+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:55422" response_time=2.06146ms status=200
time="2023-07-10T08:10:01+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:55428" response_time=2.072701ms status=200
time="2023-07-10T08:10:01+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:55436" response_time=2.728651ms status=200
time="2023-07-10T08:10:01+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:55452" response_time=3.359509ms status=200
time="2023-07-10T08:10:08+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:48978" response_time="195.607µs" status=200
time="2023-07-10T08:10:18+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:33122" response_time="96.647µs" status=200`Texte préformaté`
File editor (5.6.0), Mosquitto broker (6.2.1), Zigbee2MQTT (1.32.1-1), Terminal & SSH (9.7.1), Studio Code Server (5.8.1), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.5.0), Node-RED (14.3.0), InfluxDB (4.7.0)
Dashboards
dashboards
1
resources
4
views
1
mode
storage
Recorder
oldest_recorder_run
2 juillet 2023 à 00:42
current_recorder_run
10 juillet 2023 à 07:56
estimated_db_size
54.05 MiB
database_engine
sqlite
database_version
3.41.2
[/center]
Comment récupérer ma configuration :
Dans votre HA, Menu latéral `Paramètres` > `Système` > `Corrections` puis les trois petits points en haut a droite > `Informations Système` puis une fois en bas `Copier`
___
As-tu regardé en détails les infos HA et notamment les logs HA (tu as déjà posté ceux de influxdb, et il n’y a rien d’anormal) ?
Accessoirement, regarde bien la fin du tuto, notament la partie include/exclude… Si tu n’as rien indiqué, à HA, normal que rien ne remonte
Effectivement, je n’ai rien indiqué
Je me suis arrêté ici :
Vérifier le fonctionnement de InfluxDB.
Une fois redémarré, allez sur InfluxDB, puis sur Explore, s’il y a des sensors dans votre Home Assistant, vous devriez voir apparaître plusieurs unités de mesure après avoir cliqué sur votre base de données créée auparavant. Si vous n’avez pas de sensor créés, reportez vous à l’article suivant.
Je vais modifier mon fichier Configuration.yaml en ajoutant un capteur.
Toujours pas de capteur, mais j’ai une erreur 401 dans les logs de HA : Texte préformaté2023-07-10 15:10:27.702 ERROR (SyncWorker_2) [homeassistant.components.influxdb] InfluxDB database is not accessible due to ‹ 401: {« error »:« authorization failed »} ›. Please check that the database, username and password are correct and that the specified user has the correct permissions set. Retrying in 60 seconds.Texte préformaté
