Broadlink invalid literal for int() with base 10: ''

[jmu]

Bonjour,
Le log de mon plugin broadlink génère l’erreur broadlink invalid literal for int() with base 10: '' toutes les 5 mn.
Par ailleurs, tout fonctionne normalement.
Voici ce que donne le debug :

[2024-04-29 16:17:45.190][ERROR] : invalid literal for int() with base 10: ''
[2024-04-29 16:22:45.207][ERROR] : invalid literal for int() with base 10: ''
[2024-04-29 16:27:45.227][ERROR] : invalid literal for int() with base 10: ''
[2024-04-29 16:32:45.230][ERROR] : invalid literal for int() with base 10: ''
[2024-04-29 16:37:45.247][ERROR] : invalid literal for int() with base 10: ''
[2024-04-29 16:42:45.257][ERROR] : invalid literal for int() with base 10: ''
[2024-04-29 16:47:42][INFO] : Lancement démon broadlink : sudo /usr/bin/python3 /var/www/html/plugins/broadlink/resources/broadlinkd/broadlinkd.py --loglevel debug --socketport 55013 --sockethost 127.0.0.1 --callback http://127.0.0.1:80/plugins/broadlink/core/php/jeeBroadlink.php --apikey 3fwC6JnlXHvTfMTVKAMS11KU25L89JwyHhtwWI7DiODkjqlnq6atK0D8Z1Gy4kSA --cycle 0.3 --pid /tmp/jeedom/broadlink/deamon.pid
/usr/local/lib/python3.7/dist-packages/requests/__init__.py:114: RequestsDependencyWarning: urllib3 (2.0.7) or chardet (3.0.4)/charset_normalizer (2.0.12) doesn't match a supported version!
  RequestsDependencyWarning,
[2024-04-29 16:47:43.345][INFO] : Start broadlinkd
[2024-04-29 16:47:43.346][INFO] : Log level : debug
[2024-04-29 16:47:43.346][INFO] : Socket port : 55013
[2024-04-29 16:47:43.346][INFO] : Socket host : 127.0.0.1
[2024-04-29 16:47:43.346][INFO] : PID file : /tmp/jeedom/broadlink/deamon.pid
[2024-04-29 16:47:43.346][INFO] : Apikey : ***********
[2024-04-29 16:47:43.346][INFO] : Callback : http://127.0.0.1:80/plugins/broadlink/core/php/jeeBroadlink.php
[2024-04-29 16:47:43.347][INFO] : Cycle : 0.3
[2024-04-29 16:47:43.347][DEBUG] : Writing PID 17000 to /tmp/jeedom/broadlink/deamon.pid
[2024-04-29 16:47:43.347][DEBUG] : Init request module v2.28.1
[2024-04-29 16:47:43.354][DEBUG] : Starting new HTTP connection (1): 127.0.0.1:80
[2024-04-29 16:47:43.367][DEBUG] : http://127.0.0.1:80 "GET /plugins/broadlink/core/php/jeeBroadlink.php?apikey=*********** HTTP/1.1" 200 0
[2024-04-29 16:47:43.369][DEBUG] : Start listening...
[2024-04-29 16:47:43.369][DEBUG] : Socket interface started
[2024-04-29 16:47:43.370][DEBUG] : LoopNetServer Thread started
[2024-04-29 16:47:43.370][DEBUG] : Listening on: [127.0.0.1:55013]
[2024-04-29 16:47:45.719][DEBUG] : Client connected to [127.0.0.1:49552]
[2024-04-29 16:47:45.720][DEBUG] : Message read from socket: b'{"apikey":"***********","cmd":"add","device":{"mac":"e816567d6a44","ip":"192.168.0.26","name":"Telco_IR_PAC","delay":"300","port":"80","type":"rm4"}}'
[2024-04-29 16:47:45.720][DEBUG] : Client disconnected from [127.0.0.1:49552]
[2024-04-29 16:47:45.724][DEBUG] : Message received in socket JEEDOM_SOCKET_MESSAGE
[2024-04-29 16:47:45.725][DEBUG] : Add device : {'mac': '***********', 'ip': '***********', 'name': 'Telco_IR_PAC', 'delay': '300', 'port': '80', 'type': 'rm4'}
[2024-04-29 16:47:45.725][DEBUG] : Handling RM4 for Telco_IR_PAC
[2024-04-29 16:47:45.904][DEBUG] : Connecting to Broadlink device with name Telco_IR_PAC....
[2024-04-29 16:47:45.978][DEBUG] : Connected to Broadlink device with name Telco_IR_PAC....
[2024-04-29 16:47:46.001][DEBUG] : {'mac': '***********', 'temperature': 0.0, 'humidity': 0.0}
[2024-04-29 16:47:46.054][DEBUG] : Send to jeedom : {'devices': {'***********': {'mac': '***********', 'temperature': 0.0, 'humidity': 0.0}}}
[2024-04-29 16:47:46.058][DEBUG] : Starting new HTTP connection (1): 127.0.0.1:80
[2024-04-29 16:47:46.080][DEBUG] : http://127.0.0.1:80 "POST /plugins/broadlink/core/php/jeeBroadlink.php?apikey=*********** HTTP/1.1" 200 0
[2024-04-29 16:52:45.734][DEBUG] : Handling RM4 for Telco_IR_PAC
[2024-04-29 16:52:45.735][DEBUG] : Connecting to Broadlink device with name Telco_IR_PAC....
[2024-04-29 16:52:45.820][DEBUG] : Connected to Broadlink device with name Telco_IR_PAC....
[2024-04-29 16:52:45.843][DEBUG] : {'mac': '***********', 'temperature': 0.0, 'humidity': 0.0}
[2024-04-29 16:55:03.318][DEBUG] : Client connected to [127.0.0.1:50726]
[2024-04-29 16:55:03.319][DEBUG] : Message read from socket: b'{"apikey":"***********","cmd":"send","cmdType":"command","mac":"***********","device":{"hex2send":"26004c026a360e290c290d0e0d0e0c0f0d290c0e0e0d0d290c2a0c0f0c290d0e0d0e0d290d280e0d0d290d290d0e0c0e0e290c0e0d0e0d290c0e0e0d0d0f0c0e0d0e0d0e0d0e0c0f0d0d0d0f0c0e0e0d0d0e0d0e0c0f0d0e0c0f0c0e0e0d0d0e0d290d0e0d0e0c0e0e0d0d0f0c290d0e0d0e0c0e0e0d0d290d0e0d290c0e0e0d0d0f0c0e0d0e0d0e0d0e0c0f0d0e0c0f0c0e0e0d0d0e0d0e0c0f0d0e0c290e0d0d0e0f270d0e0c290e0d0d0f0c0e0d290d0e0c290d0f0c0e0d0e0d0e0d0e0c0e0e0e0c0f0c0e0d0e0d0e0d0e0c0f0d0e0c0f0c0e0e0d0d0e0d0e0c0f0d290c0e0e0d0d0e0d0e0d290c0f0c0e0e0d0d0f0c0e0d0e0d0e0d0e0c0e0e0d0d0f0c0e0d0e0d0e0d0e0c0e0e0e0c0f0c0e0d0e0d0e0d0e0c0f0d0e0c0f0c290d0e0d0e0c2a0c290e280d0001a96b360d290d290c0e0e0e0c0e0d290d0e0c0f0c2a0c290d0e0d290c0e0e0e0c290d290d0e0d290c290d0e0d0e0d280e0e0c0f0c290d0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d0e0d0e0d0e0c0f0c0e0e290c0e0d0e0d0e0d0e0c0e0e290c0e0d0e0d0e0d0e0d290c0f0c2a0c0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d0e0d290c0f0d0d0e290c0e0d290d0e0d0d0e0e0c290d0f0c290d0d0e0e0c0f0c0e0d0f0c0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d290d0e0c0f0d0d0e0e0c290d0f0c0e0d0e0d0d0e0e0c0f0c0e0d0f0c0e0d0e0d0d0e0e0c0f0c0e0d0f0c0e0d0e0d0e0d0e0c0f0c0e0e0e0c0e0d0e0d0e0d290c0e0e0e0c290d290c290e000d0500000000000000000000","ip":"***********","port":"80","type":"rm4","name":"Telco_IR_PAC","mac":"***********"}}'
[2024-04-29 16:55:03.319][DEBUG] : Client disconnected from [127.0.0.1:50726]
[2024-04-29 16:55:03.335][DEBUG] : Message received in socket JEEDOM_SOCKET_MESSAGE
[2024-04-29 16:55:03.336][DEBUG] : Send command
[2024-04-29 16:55:03.337][DEBUG] : Connecting to Broadlink device with name Telco_IR_PAC....
[2024-04-29 16:55:03.459][DEBUG] : Connected to Broadlink device with name Telco_IR_PAC....
[2024-04-29 16:55:03.474][DEBUG] : Code Sent....

Je ne comprends pas ce qu’il se passe.
J’ai bien vu le message de @chrissy2 en juin 2022, mais je ne vois pas le défaut.

J’espère que l’un d’entre vous pourra éclairer ma lanterne !
Merci !

[Mips]

Bonjour,

@jmu

J’ai bien vu le message de

un lien ca serait sympa histoire qu’on ne doive pas chercher de quoi vous parlez?

il manque la page santé jeedom aussi au minimum + log d’install des dépendances car là il y a un paquet qui manque manifestement

[jmu]

Merci, je vais regarder de plus près et vous donner ce qui manque.

[jmu]

Bonjour,

Et merci de votre aide. J’ajoute que je fais régulièrement la mise à jour de Jeedom, mais j’attends un peu pour la dernière.
À ce sujet, j’ajoute que je n’ai pas fait de màj de l’OS depuis un moment et je constate une longue liste de paquets. J’aurais sûrement intérêt à le faire ? (je ne l’avais encore jamais fait depuis l’interface Jeedom).

Voici le lien que j’avais consulté au préalable : https://community.jeedom.com/t/erreur-invalid-literal-for-int-with-base-10/86446
Je précise que le plugin fonctionne parfaitement par ailleurs.

Ensuite le log d’install :

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_broadlink
+ echo 1
+ echo 2
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
+ sudo sudo dpkg --configure -a --force-confdef
+ sudo apt update

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Hit:1 https://deb.nodesource.com/node_18.x nodistro InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Get:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [400 kB]
Fetched 13.5 MB in 8s (1678 kB/s)
Reading package lists...

Building dependency tree...
Reading state information...
297 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 3
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-serial

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  python3-wxgtk3.0 | python3-wxgtk
The following NEW packages will be installed:
  python3-serial
0 upgraded, 1 newly installed, 0 to remove and 297 not upgraded.
Need to get 67.6 kB of archives.
After this operation, 379 kB of additional disk space will be used.
Get:1 http://mirrors.ircam.fr/pub/raspbian/raspbian buster/main armhf python3-serial all 3.4-4 [67.6 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 67.6 kB in 1s (129 kB/s)
Selecting previously unselected package python3-serial.
(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 ... 71602 files and directories currently installed.)
Preparing to unpack .../python3-serial_3.4-4_all.deb ...
Unpacking python3-serial (3.4-4) ...
Setting up python3-serial (3.4-4) ...
+ echo 4
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end broadlink
+ echo 5
+ rm /tmp/jeedom_install_in_progress_broadlink
+ echo '*******************End of package installation******************'
*******************End of package installation******************

et enfin la santé :

Merci d’avance !

[jmu]

Bonjour,

Je viens d’effectuer la mise à jour vers 4.4.5 et là, miracle, plus de problème avec Broadlink , et weather à pris la mise à jour.
Je ne comprends rien, mais je considère le problème résolu !
Bonne journée à tous.