Impossible d'utiliser le plugin depuis la mise en place d'un code de vérification sur Dyson Link

Bonjour,
Depuis l’ajout d’un code de vérification lors de la connexion sur l’application Dyson Link, le plugin n’arrive pas à démarrer son Demon.

J’ai tenté de ré-installer les dépendences et le plugin sans changement.

Voici la log:

[2021-04-06 09:50:03][ERROR] : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
internal/fs/utils.js:779
throw new ERR_INVALID_ARG_TYPE(
^
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number (30526)
at Object.writeFile (fs.js:1436:5)
at Object.Jeedom.write_pid (/var/www/html/plugins/dyson/resources/dysond/jeedom/jeedom.js:70:6)
at Object.<anonymous> (/var/www/html/plugins/dyson/resources/dysond/dysond.js:37:8)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47 {
code: 'ERR_INVALID_ARG_TYPE'
}
[2021-04-06 09:50:33][ERROR] : Impossible de lancer le démon dysond, vérifiez le log

Bonjour,

Pour information (sans savoir si c’est la solution à votre problème) il faut installer la version du plugin publiée ce jour (04/06)
Et très certainement, réinstaller les dépendances de ce plugin.

Bonjour,
Je confirme il y a une maj a faire pour que le plugin marche

1 « J'aime »

J’ai la même erreur sur le demon malgré la mise à jour.
Le statut est NOK mais la configuration est OK.

Merci de vos retours.
Le plugin est bien a jour (Version 2021-04-06 01:03:45) et les dépendances réinstallées. L’erreur reste la même dans la log.

Voici la log des Dépendances

********************************************************
*             Installation des dépendances             *
********************************************************
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:3 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:4 https://deb.nodesource.com/node_14.x buster InRelease
Fetched 117 kB in 1s (115 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.2).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u3).
lsb-release is already the newest version (10.2019051400).
0 upgraded, 0 newly installed, 0 to remove and 93 not upgraded.
[Check Version NodeJS actuelle : v14.16.0 : [  OK  ]
┌──────────────────────────────────────────────────────┐
│               npm update check failed                │
│         Try running with sudo or get access          │
│         to the local update config store via         │
│ sudo chown -R $USER:$(id -gn $USER) /var/www/.config │
└──────────────────────────────────────────────────────┘
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
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 (>= 6.11~) but it is not going to be installed
Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed
Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed
Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed
Depends: node-aproba (>= 1.2~) but it is not going to be installed
Depends: node-archy (>= 1.0~) but it is not going to be installed
Depends: node-cacache (>= 10.0.4~) but it is not going to be installed
Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed
Depends: node-call-limit (>= 1.1~) but it is not going to be installed
Depends: node-chownr (>= 1.0.1~) but it is not going to be installed
Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed
Depends: node-detect-indent (>= 5.0~) but it is not going to be installed
Depends: node-detect-newline (>= 2.1~) but it is not going to be installed
Depends: node-editor (>= 1.0~) but it is not going to be installed
Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed
Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed
Depends: node-glob (>= 7.1.2~) but it is not going to be installed
Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed
Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed
Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed
Depends: node-iferr (>= 0.1.5~) but it is not going to be installed
Depends: node-inflight (>= 1.0.6~) but it is not going to be installed
Depends: node-inherits (>= 2.0.3~) but it is not going to be installed
Depends: node-ini (>= 1.3.5~) but it is not going to be installed
Depends: node-npm-package-arg but it is not going to be installed
Depends: node-promzard but it is not going to be installed
Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed
Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed
Depends: node-lazy-property (>= 1.0~) but it is not going to be installed
Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed
Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed
Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed
Depends: node-mississippi (>= 3.0~) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed
Depends: node-nopt but it is not going to be installed
Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed
Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
Depends: node-resolve-from (>= 4.0~) but it is not going to be installed
Depends: node-encoding but it is not going to be installed
Depends: node-errno but it is not going to be installed
Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed
Depends: node-once (>= 1.4~) but it is not going to be installed
Depends: node-opener (>= 1.4.3~) but it is not going to be installed
Depends: node-osenv (>= 0.1.5~) but it is not going to be installed
Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed
Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed
Depends: node-ansi but it is not going to be installed
Depends: node-qw (>= 1.0.1~) but it is not going to be installed
Depends: node-read (>= 1.0.7~) but it is not going to be installed
Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed
Depends: node-request (>= 2.83~) but it is not going to be installed
Depends: node-retry (>= 0.10.1~) but it is not going to be installed
Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed
Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed
Depends: node-semver (>= 5.5~) but it is not going to be installed
Depends: node-sha (>= 2.0.1~) but it is not going to be installed
Depends: node-slide (>= 1.1.6~) but it is not going to be installed
Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed
Depends: node-from2 but it is not going to be installed
Depends: node-stream-iterate but it is not going to be installed
Depends: node-ssri (>= 5.2.4~) but it is not going to be installed
Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed
Depends: node-tar (>= 4.4~) but it is not going to be installed
Depends: node-text-table (>= 0.2~) but it is not going to be installed
Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed
Depends: node-unique-filename (>= 1.1~) but it is not going to be installed
Depends: node-unpipe (>= 1.0~) but it is not going to be installed
Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
Depends: node-import-lazy but it is not going to be installed
Depends: node-is-npm (>= 1.0~) but it is not going to be installed
Depends: node-latest-version (>= 3.0~) but it is not going to be installed
Depends: node-semver-diff (>= 2.0~) but it is not going to be installed
Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed
Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed
Depends: node-which (>= 1.3~) but it is not going to be installed
Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed
Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN dyson@1.0.1 No repository field.
npm WARN dyson@1.0.1 No license field.
added 195 packages from 139 contributors and audited 195 packages in 11.836s
12 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
********************************************************
*             Installation terminée                    *
********************************************************

Je viens de reforcer une synchronisation market mais je pense que le probleme est autre car je viens de tester sur un rpi, une smart et en x86-64 aucun soucis le plugin marche parfaitement avec la correction.

Toujours pareil.

[2021-04-06 16:01:34][ERROR] : Impossible de lancer le démon dysond, vérifiez le log
[2021-04-06 16:02:52][ERROR] : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
internal/fs/utils.js:779
throw new ERR_INVALID_ARG_TYPE(
^
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number (8643)
at Object.writeFile (fs.js:1436:5)
at Object.Jeedom.write_pid (/var/www/html/plugins/dyson/resources/dysond/jeedom/jeedom.js:70:6)
at Object.<anonymous> (/var/www/html/plugins/dyson/resources/dysond/dysond.js:37:8)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47 {
code: 'ERR_INVALID_ARG_TYPE'
}
[2021-04-06 16:03:22][ERROR] : Impossible de lancer le démon dysond, vérifiez le log

Tu as un soucis de maj qui se fait pas alors ouvre un ticket la.

j’ai ça aussi qui apparait lors de la mise à jour toutes les 15 min

Echec de la requête http : http://127.0.0.1:55026/device/sensor?id=NN2-EU-NEB2865A&apikey=TtjGNA9xegCZBBrEcsH0sJYnxu3tjwUn Curl error : Failed to connect to 127.0.0.1 port 55026: Connection refused

Ca c’est normal si le demon tourne pas alors forcement impossible de recuperer l’état du dyson

OK bon ben ticket créé. Il n’y a plus qu’à attendre

J’ai repondu deja au ticket j’attend ton retour

Ticket également ouvert de mon côté.

Quand vous avez un retour, faîtes un petit point ici pour le partage.
Merci

La correction est ligne il suffit de mettre a jour le plugin

1 « J'aime »

Mise à jour installée.
Le démon se lance bien et la synchronisation s’est effectuée sans problème.

Merci à tous

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.