Bonjour,
Pouvez-vous vérifier de quoi provient le fait que depuis le 9 Février dernier, les données Index HC et HP, tous les jours à 00:00 tombent à 0 svp ?
Alors qu’on devrait avoir une graphique qui s’incrémente en augmentant pas marches, pallier (le compteur ne peut pas revenir en arrière).
Ca fonctionnait trés bien jusque là.
merci de votre aide.
"TELEINFO DEMONCONSO"
[2021-02-09 21:43:58][ERROR] : Error on send request to jeedom, return code 500
[2021-02-13 20:47:06][INFO] : GLOBAL------Shutdown
[2021-02-13 20:47:06][INFO] : Removing PID file /tmp/jeedom/teleinfo/teleinfo_conso.pid
[2021-02-13 20:47:06][DEBUG] : LoopNetServer Thread stopped
[2021-02-13 20:47:06][DEBUG] : Exit 0
[2021-02-13 20:48:37][INFO] : GLOBAL------Start teleinfod
[2021-02-13 20:48:37][INFO] : GLOBAL------Cycle Sommeil : 0.5
[2021-02-13 20:48:37][INFO] : GLOBAL------Socket port : 55062
[2021-02-13 20:48:37][INFO] : GLOBAL------Socket host : 127.0.0.1
[2021-02-13 20:48:37][INFO] : GLOBAL------Log level : debug
[2021-02-13 20:48:37][INFO] : GLOBAL------Callback : http://127.0.0.1:80/plugins/teleinfo/core/php/jeeTeleinfo.php
[2021-02-13 20:48:37][INFO] : GLOBAL------Vitesse : 1200
[2021-02-13 20:48:37][INFO] : GLOBAL------Cycle : 0.3
[2021-02-13 20:48:37][INFO] : GLOBAL------Port : /dev/ttyUSB1
[2021-02-13 20:48:37][INFO] : GLOBAL------Type : conso
[2021-02-13 20:48:37][INFO] : GLOBAL------Mode : historique
[2021-02-13 20:48:37][DEBUG] : Writing PID 1135 to /tmp/jeedom/teleinfo/teleinfo_conso.pid
[2021-02-13 20:48:37][DEBUG] : Init request module v2.21.0
[2021-02-13 20:48:37][DEBUG] : Starting new HTTP connection (1): 127.0.0.1:80
[2021-02-13 20:48:37][DEBUG] : Socket interface started
[2021-02-13 20:48:37][DEBUG] : LoopNetServer Thread started
[2021-02-13 20:48:37][INFO] : GLOBAL------Start listening...
[2021-02-13 20:48:37][DEBUG] : Listening on: [127.0.0.1:55062]
[2021-02-13 20:48:37][DEBUG] : TELEINFO------INIT CONNECTION
[2021-02-13 20:48:37][INFO] : GLOBAL------Preparing Teleinfo...
[2021-02-13 20:48:37][DEBUG] : GLOBAL------Read Socket Thread Launched
[2021-02-13 20:48:37][INFO] : TELEINFO------RUN
[2021-02-13 20:48:37][INFO] : TELEINFO------OPEN CONNECTION
[2021-02-13 20:48:37][INFO] : TELEINFO------CONNECTION OPENED
[
[2021-02-13 20:50:02][DEBUG] : TELEINFO------WAITING : 52 octets dans la file apres sleep
[2021-02-13 20:50:03][DEBUG] : TELEINFO------name : ADCO value : 022061820832 checksum : 9
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : OPTARIF value : HC.. checksum : <
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : ISOUSC value : 45 checksum : ?
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : HCHC value : 001920494 checksum : #
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : HCHP value : 002741335 checksum : ,
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : PTEC value : HP..
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : IINST value : 006 checksum : ]
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : IMAX value : 090 checksum : H
[2021-02-13 20:50:04][DEBUG] : TELEINFO------name : PAPP value : 01590 checksum : 0
[2021-02-13 20:50:05][DEBUG] : TELEINFO------name : HHPHC value : A checksum : ,
[2021-02-13 20:50:05][DEBUG] : TELEINFO------name : MOTDETAT value : 000000 checksum : B
[2021-02-13 20:50:05][DEBUG] : TELEINFO------START SLEEPING 0.5 seconds
[2021-02-13 20:50:05][DEBUG] : Send to jeedom : {'device': {'022061820832': {'device': '022061820832', 'PAPP': '01590', 'HCHP': '002741335'}}}
[2021-02-13 20:50:05][DEBUG] : Starting new HTTP connection (1): 127.0.0.1:80
[2021-02-13 20:50:05][DEBUG] : TELEINFO------WAITING : 56 octets dans la file apres sleep
[2021-02-13 20:50:06][DEBUG] : TELEINFO------name : ADCO value : 022061820832 checksum : 9
[2021-02-13 20:50:07][DEBUG] : TELEINFO------name : OPTARIF value : HC.. checksum : <
[2021-02-13 20:50:07][DEBUG] : TELEINFO------name : ISOUSC value : 45 checksum : ?
[2021-02-13 20:50:07][DEBUG] : TELEINFO------name : HCHC value : 001920494 checksum : #
[2021-02-13 20:50:07][INFO] : GLOBAL------Passage des logs en normal
Merci de votre aide.
Cordialement.
Dans le doute, j’ai relancé Démons et Dépendances. Crest le même état pour le moment.
Seul changement, j’ai désormais le login Teleinfo update (le 3ème qui est désormais visible, comme sur la doc) :
Lancement de l'installation/mise à jour des dépendances Téléinfo Raffraichissement du système Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Hit:3 http://ftp.uk.debian.org/debian buster InRelease Hit:4 http://www.deb-multimedia.org buster InRelease Get:5 http://ftp.uk.debian.org/debian buster-updates InRelease [51.9 kB] Get:6 http://security.debian.org/debian-security buster/updates/main Sources [178 kB] Get:7 http://security.debian.org/debian-security buster/updates/main arm64 Packages [262 kB] Err:2 https://repo.jeedom.com/odroid stable InRelease 502 Bad Gateway [IP: 51.178.69.128 443] Err:8 https://oph.mdrjr.net/meveric all InRelease Could not connect to oph.mdrjr.net:443 (216.155.132.189), connection timed out Err:9 https://oph.mdrjr.net/meveric buster InRelease Unable to connect to oph.mdrjr.net:https: Fetched 557 kB in 31s (18.2 kB/s) Reading package lists... W: Failed to fetch http://repo.jeedom.com/odroid/dists/stable/InRelease 502 Bad Gateway [IP: 51.178.69.128 443] W: Failed to fetch https://oph.mdrjr.net/meveric/dists/all/InRelease Could not connect to oph.mdrjr.net:443 (216.155.132.189), connection timed out W: Failed to fetch https://oph.mdrjr.net/meveric/dists/buster/InRelease Unable to connect to oph.mdrjr.net:https: W: Some index files failed to download. They have been ignored, or old ones used instead. Installation de la librairie ftdi pour modem 2 compteurs Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package python-ftdi Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libftdi1-2 The following NEW packages will be installed: libftdi1-2 python-ftdi1 0 upgraded, 2 newly installed, 0 to remove and 103 not upgraded. Need to get 74.5 kB of archives. After this operation, 374 kB of additional disk space will be used. Get:1 http://ftp.uk.debian.org/debian buster/main arm64 libftdi1-2 arm64 1.4-1+b2 [27.8 kB] Get:2 http://ftp.uk.debian.org/debian buster/main arm64 python-ftdi1 arm64 1.4-1+b2 [46.7 kB] debconf: unable to initialize frontend: Dialog debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (This frontend requires a controlling tty.) debconf: falling back to frontend: Teletype dpkg-preconfigure: unable to re-open stdin: Fetched 74.5 kB in 0s (155 kB/s) Selecting previously unselected package libftdi1-2:arm64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 76576 files and directories currently installed.) Preparing to unpack .../libftdi1-2_1.4-1+b2_arm64.deb ... Unpacking libftdi1-2:arm64 (1.4-1+b2) ... Selecting previously unselected package python-ftdi1. Preparing to unpack .../python-ftdi1_1.4-1+b2_arm64.deb ... Unpacking python-ftdi1 (1.4-1+b2) ... Setting up libftdi1-2:arm64 (1.4-1+b2) ... Setting up python-ftdi1 (1.4-1+b2) ... Processing triggers for libc-bin (2.28-10) ... Collecting pylibftdi Downloading https://files.pythonhosted.org/packages/b0/b5/6413399489ebc7147079b0d6ebbd15cf5fe3b5ae06707cf3606977fa575b/pylibftdi-0.19.0-py2.py3-none-any.whl Installing collected packages: pylibftdi Successfully installed pylibftdi-0.19.0 Installation de la librairie serial Skipping serial as it is not installed. Requirement already satisfied: pyserial in /usr/lib/python2.7/dist-packages (3.4) Requirement already satisfied: setuptools in /usr/lib/python2.7/dist-packages (40.8.0) Requirement already satisfied: requests in /usr/lib/python2.7/dist-packages (2.21.0) Requirement already satisfied: pyudev in /usr/lib/python2.7/dist-packages (0.21.0) Mise à jour de cmdline ou inittab suivant système Everything is successfully installed!
Bonsoir, à priori la situation est revenue à la normale d’elle même… Un bug côté ENEDIS ? j’attends leur réponse.
Sans rapport, je vous conseille de régénérer la valeur APIKEY qui vous est personnelle et n’aurait pas dû être publiée sur un forum.
Voir la partie configuration de Jeedom.
Bonjour Jean Bapiste,
Merci pour l’info, je ne savais pas, je viens de la supprimer des messages publiés précédemment.