Conflit Gammu ikea?

Bonjour à tous,
Voici la chrono de mon problème :
Plugin Ikea ok, plugin gammu non fonctionnel.
Je débranche la clef 3g, le même jour, le plugin ikea tombe en rade (demon nok).
Je désinstalle gammu, puis ikea, puis résintall ikea, toujours la me log de dépendance :

********************************************************
*             Installation des dépendances             *
********************************************************
Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Hit:3 https://deb.nodesource.com/node_12.x stretch InRelease
Fetched 40.3 kB in 1s (23.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (9.20161125+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up gammu-smsd (1.38.1-1) ...
Configuration file '/etc/gammu-smsdrc'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
D     : show the differences between the versions
Z     : start a shell to examine the situation
The default action is to keep your current version.
*** gammu-smsdrc (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package gammu-smsd (--configure):
end of file on stdin at conffile prompt
Errors were encountered while processing:
gammu-smsd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Version actuelle : 12
Ok, version suffisante
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
npm : Depends: nodejs but it is not going to be installed
Depends: node-abbrev (>= 1.0.4) but it is not going to be installed
Depends: node-ansi (>= 0.3.0-2) but it is not going to be installed
Depends: node-ansi-color-table but it is not going to be installed
Depends: node-archy but it is not going to be installed
Depends: node-block-stream but it is not going to be installed
Depends: node-fstream (>= 0.1.22) but it is not going to be installed
Depends: node-fstream-ignore but it is not going to be installed
Depends: node-github-url-from-git but it is not going to be installed
Depends: node-glob (>= 3.1.21) but it is not going to be installed
Depends: node-graceful-fs (>= 2.0.0) but it is not going to be installed
Depends: node-inherits but it is not going to be installed
Depends: node-ini (>= 1.1.0) but it is not going to be installed
Depends: node-lockfile but it is not going to be installed
Depends: node-lru-cache (>= 2.3.0) but it is not going to be installed
Depends: node-minimatch (>= 0.2.11) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-gyp (>= 0.10.9) but it is not going to be installed
Depends: node-nopt (>= 3.0.1) but it is not going to be installed
Depends: node-npmlog but it is not going to be installed
Depends: node-once but it is not going to be installed
Depends: node-osenv but it is not going to be installed
Depends: node-read but it is not going to be installed
Depends: node-read-package-json (>= 1.1.0) but it is not going to be installed
Depends: node-request (>= 2.25.0) but it is not going to be installed
Depends: node-retry but it is not going to be installed
Depends: node-rimraf (>= 2.2.2) but it is not going to be installed
Depends: node-semver (>= 2.1.0) but it is not going to be installed
Depends: node-sha but it is not going to be installed
Depends: node-slide but it is not going to be installed
Depends: node-tar (>= 0.1.18) but it is not going to be installed
Depends: node-underscore but it is not going to be installed
Depends: node-which but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

les clefs api sont ok.
Je ne vois pas quelle prérogative peut avoir un plugin pour en flinguer un autre…
Merci
elembee (dans le noir)

Bonjour,
C’est le systeme de package os qui deconne la, j’ai fait un bouton de correction dans l’interface systeme de jeedom mais pour l’instant c’est en beta, je n’ai pas de date pour la stable donc il faudrai dans l’interface systeme faire la commande :
sudo dpkg --configure -a --force-confdef" | sudo at now

Bonjour Loïc,
Merci pour ta réponse.
en passant sudo dpkg --configure -a --force-confdef, j’obtiens :
Setting up gammu-smsd (1.38.1-1) …
Job for gammu-smsd.service failed because of unavailable resources or another system error.
See « systemctl status gammu-smsd.service » and « journalctl -xe » for details.
invoke-rc.d: initscript gammu-smsd, action « start » failed.

  • gammu-smsd.service - SMS daemon for Gammu
    Loaded: loaded (/lib/systemd/system/gammu-smsd.service; enabled; vendor preset: enabled)
    Active: failed (Result: resources) since Sat 2019-11-30 08:56:38 CET; 55ms ago
    Docs: man:gammu-smsd(1)
    Process: 3988 ExecStart=/usr/bin/gammu-smsd --pid=/var/run/gammu-smsd.pid --daemon (code=exited, status=0/SUCCESS)

Nov 30 08:56:38 raspberrypi systemd[1]: Starting SMS daemon for Gammu…
Nov 30 08:56:38 raspberrypi gammu-smsd[3990]: Created POSIX RW shared memory at 0x76ff1000
Nov 30 08:56:38 raspberrypi gammu-smsd[3990]: Starting phone communication…
Nov 30 08:56:38 raspberrypi gammu-smsd[3990]: Can’t open device: Error opening device. Unknown, busy or no permissions. (DEVICEOPENERROR[2])
Nov 30 08:56:38 raspberrypi systemd[1]: gammu-smsd.service: PID 3990 read from file /var/run/gammu-smsd.pid does not exist or is a zombie.
Nov 30 08:56:38 raspberrypi systemd[1]: Failed to start SMS daemon for Gammu.
Nov 30 08:56:38 raspberrypi systemd[1]: gammu-smsd.service: Unit entered failed state.
Nov 30 08:56:38 raspberrypi systemd[1]: gammu-smsd.service: Failed with result ‹ resources ›.
dpkg: error processing package gammu-smsd (–configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
gammu-smsd

puis en passant sudo at now
warning: commands will be executed using /bin/sh
job 32 at Sat Nov 30 08:59:00 2019

puis reboot du système, réinstallation du plugin, ajout ip et clé gateway, sauvegarde, lancement installation des dépendances, relance du demon, mais toujours le même souci.

elembee

La faut voir avec le dev du plugin gammu

Bonsoir,
Après ré-install et désintall de gammu, j’obtiens :
The following packages have unmet dependencies:
npm : Depends: nodejs but it is not going to be installed

avec ensuite une longue liste du type
Depends: node-abbrev (>= 1.0.4) but it is not going to be installed

et enfin :

E: Unable to correct problems, you have held broken packages.

node-aead-crypto@2.1.4 install /var/www/html/plugins/ikealight/resources/ikealightd/node_modules/node-aead-crypto
node lib/install.js
node-aead-crypto is no longer needed on NodeJS 10+
npm WARN saveError ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for node-aead-crypto@2.1.4: wanted: {« node »:« >4 <10 »} (current: {« node »:« 12.13.1 »,« npm »:« 6.12.1 »})
npm WARN notsup Not compatible with your version of node/npm: node-aead-crypto@2.1.4
npm WARN enoent ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN ikealightd No description
npm WARN ikealightd No repository field.
npm WARN ikealightd No README data
npm WARN ikealightd No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 (node_modules/node-aead-crypto):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 install: node lib/install.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

  • node-tradfri-client@2.1.0
    added 14 packages from 13 contributors and audited 116 packages in 15.172s
    found 0 vulnerabilities

node-aead-crypto@2.1.4 install /var/www/html/plugins/ikealight/resources/ikealightd/node_modules/node-aead-crypto
node lib/install.js
node-aead-crypto is no longer needed on NodeJS 10+
npm WARN saveError ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN enoent ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN ikealightd No description
npm WARN ikealightd No repository field.
npm WARN ikealightd No README data
npm WARN ikealightd No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 (node_modules/node-aead-crypto):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 install: node lib/install.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

  • fs@0.0.1-security
    added 1 package and audited 341 packages in 7.515s
    found 0 vulnerabilities

node-aead-crypto@2.1.4 install /var/www/html/plugins/ikealight/resources/ikealightd/node_modules/node-aead-crypto
node lib/install.js
node-aead-crypto is no longer needed on NodeJS 10+
npm WARN saveError ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN enoent ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN ikealightd No description
npm WARN ikealightd No repository field.
npm WARN ikealightd No README data
npm WARN ikealightd No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 (node_modules/node-aead-crypto):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 install: node lib/install.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

  • request@2.88.0
    added 47 packages from 58 contributors and audited 404 packages in 14.245s
    found 0 vulnerabilities

node-aead-crypto@2.1.4 install /var/www/html/plugins/ikealight/resources/ikealightd/node_modules/node-aead-crypto
node lib/install.js
node-aead-crypto is no longer needed on NodeJS 10+
npm WARN saveError ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN enoent ENOENT: no such file or directory, open ‹ /var/www/html/plugins/ikealight/resources/ikealightd/package.json ›
npm WARN ikealightd No description
npm WARN ikealightd No repository field.
npm WARN ikealightd No README data
npm WARN ikealightd No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 (node_modules/node-aead-crypto):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-aead-crypto@2.1.4 install: node lib/install.js
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

  • express@4.17.1
    added 55 packages from 35 contributors and audited 654 packages in 17.406s
    found 0 vulnerabilities

  •         Installation terminée                    *
    

********************************************************
est-ce que celà donne une nouvelle piste ?
Merci.
Luc-Marie