Error: Cannot find module 'worker_threads'

philippe456 · Novembre 19, 2022, 10:01

bonjour, suite à un début de migration de openzwave à zwavejs :

installation MQTT : OK
mosquito : OK

zwavejs : dépendances : OK
démon : NOK → qqsoit le port sélectionné

dans mes logs j’ai :

Error: Cannot find module 'worker_threads'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:428:2642
at Object. (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:741:8846)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

Merci de votre aide

JEEDOM odroid c2 V4.3.10
cle AEOTEC Zwave gen5
clé GSM
RFXCOM433xl

Pour info : je viens de mettre en essai un odroid N2+ et la tout est bien lancé : Démon zwavejs OK …
je pêche …

Salvialf · Novembre 19, 2022, 11:05

Salut,

Elles n’ont pas l’air si OK que ça, tu peux partager les logs zwavejs_packages stp ?

philippe456 · Novembre 19, 2022, 11:33

bonjour @Salvialf ,
voici le log zwavejs_packages :

zwavejs_packages.log (4,5 Ko)

merci

bon weekend

Salvialf · Novembre 19, 2022, 11:37

Tu as fait la mise à jour du plugin de ce matin ? Si tu relances les dépendances tu as toujours ces erreurs ?

philippe456 · Novembre 19, 2022, 11:45

ok, je viens de faire les mises à jour : MQTT2 et zwavejs (qui n’apparaissaient pas sur le dashboard ??)
relance des dépendances
et là je n’ai plus l’icone de relance de démon ???

Salvialf · Novembre 19, 2022, 12:12

C’est qu’il doit y avoir un problème quelque part alors. Actives la gestion automatique du démon comme demandé (bouton vert Activer dans la partie Démon).

Tu peux partager les logs zwavejs_packages suite à la nouvelle installation des dépendances ?

philippe456 · Novembre 19, 2022, 12:20

OK, fait. Mais cela ne change rien

voici le log :
zwavejs_packages.log (4,5 Ko)

merci

philippe456 · Novembre 19, 2022, 12:29

ok pour l’icone de redémarrage du démon : MQTT n’avait pas re démarré. Et c’était devant mes yeux. post précédent. quand on veux aller trop vite … on ne voit plus rien. désolé

pour le redémarrage en lui même : toujours NOK

log :
zwavejs_packages.log (4,5 Ko)

Salvialf · Novembre 19, 2022, 12:36

Je pense que « Le démon MQTT Manager n’est pas démarré » tu ne crois pas ? Et vu que c’est indispensable au plugin Z-Wave JS je te laisse deviner la suite…

De toute façon tu as toujours l’erreur dans les logs d’installation des dépendances zwavejs.

Tu es en quelle version de Jeedom ? Ca sent la vieille version de nodejs pourtant le core doit le mettre à jour automatiquement en 4.3.X.
Peux-tu vérifier la version de nodejs dans la configuration Jeedom, onglet OS/DB > Vérifications des paquets système ?

Peux-tu aussi partager copie d’écran de la page santé et les logs mqtt2_packages également stp ? Utilises le bouton </> dans la barre au-dessus quand tu écris ton message stp c’est fastidieux de gérer ça en fichier texte.

philippe456 · Novembre 19, 2022, 12:50

JEEDOM V4.3.10 sur Odroid C2

version nodejs :

santé Jeedom:

MQTT2_packages.log : je ne trouve pas …

j’ai :

[2022-11-19 12:40:46]DEBUG : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php  plugin_id=mqtt2 function=pre_update callInstallFunction=1
[2022-11-19 12:40:47]INFO : Début d'activation du plugin
[2022-11-19 12:40:48]INFO : Info sur le démon : {"log":"mqtt2","state":"nok","launchable":"ok","launchable_message":"Gestion automatique d\u00e9sactiv\u00e9e","auto":"0","last_launch":"2022-11-18 20:14:36"}
[2022-11-19 12:40:49]DEBUG : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php  plugin_id=mqtt2 function=update callInstallFunction=1
[2022-11-19 13:25:20]INFO : Démarrage du démon MQTT Manager : sudo  /usr/bin/node /var/www/html/plugins/mqtt2/resources/mqtt2d/mqtt2d.js --loglevel debug --socketport 55035 --mqtt_server mqtts://127.0.0.1:8883 --client_key /var/www/html/plugins/mqtt2/data/ssl/client.key --client_crt /var/www/html/plugins/mqtt2/data/ssl/client.crt --ca /var/www/html/plugins/mqtt2/data/ssl/ca.crt --username jeedom --password 6haNDaICXmMcXijEIV02L5Xw7HUX9CUFTn2Onkb164PLH2mM1ynYE5ACsMMmZd6G --callback http://127.0.0.1:80/plugins/mqtt2/core/php/jeeMqtt2.php --apikey dwGZwDA7eLhFUQ7vkJgR0DhSAfWbVYq8bYAOkV4qRmEavlP1jOt2Z3HDe3SvI7AV --cycle 0.3 --pid /tmp/jeedom/mqtt2/deamon.pid
[2022-11-19 13:25:25]DEBUG : []

et

:

[2022-11-19 12:25:24]INFO : Start mqtt2d
[2022-11-19 12:25:24]INFO : Log level on  : debug
[2022-11-19 12:25:24]INFO : Socket port : 55035
[2022-11-19 12:25:24]INFO : MQTT : mqtts://127.0.0.1:8883
[2022-11-19 12:25:24]INFO : 
[2022-11-19 12:25:24]INFO : PID file : /tmp/jeedom/mqtt2/deamon.pid
[2022-11-19 12:25:24]INFO : Apikey : ************************************************
[2022-11-19 12:25:24]INFO : Callback : http://127.0.0.1:80/plugins/mqtt2/core/php/jeeMqtt2.php
[2022-11-19 12:25:24]INFO : Cycle : 0.3
[2022-11-19 12:25:24]INFO : Client key : /var/www/html/plugins/mqtt2/data/ssl/client.key
[2022-11-19 12:25:24]INFO : Client crt : /var/www/html/plugins/mqtt2/data/ssl/client.crt
[2022-11-19 12:25:24]INFO : CA : /var/www/html/plugins/mqtt2/data/ssl/ca.crt
[2022-11-19 12:25:25]INFO : Connect to mqtt server
[2022-11-19 12:25:25]DEBUG : HTTP listen on 127.0.0.1 port : 55035 started
[2022-11-19 12:25:25]INFO : Connection to mqtt server successfull
[2022-11-19 12:25:25]INFO : Subscription to all topics
[2022-11-19 12:25:25]INFO : Subscription to all topics succesfull

merci

philippe456 · Novembre 19, 2022, 12:53

et de nouveau le log zwavejs_packages : au bon format , désolé Effectivement, pour celui qui sait le lire, c’est plus clair

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_zwavejs
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ echo 'Pre installation de l'\''installation/mise à jour des dépendances zwavejs'
Pre installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ rm -R zwave-js-ui
+ git clone --branch v8.4.1 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: checking out 'ac29618bc7af457157be38f678eb5e190e21e77d'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b 
+ echo 'Pre install finished'
Pre install finished
+ echo 3
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ echo 'Post installation de l'\''installation/mise à jour des dépendances zwavejs'
Post installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ cd zwave-js-ui
+ sudo yarn install
internal/modules/cjs/loader.js:638
throw err;
^
Error: Cannot find module 'worker_threads'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:428:2642
at Object. (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:741:8846)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
+ sudo yarn run build
internal/modules/cjs/loader.js:638
throw err;
^
Error: Cannot find module 'worker_threads'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:428:2642
at Object. (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/.yarn/releases/yarn-3.2.1.cjs:741:8846)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md app.ts bin build config docker docs hass kubernetes kustomization.yaml lib nodemon.json package.json package.sh pkg snippets src static store test tsconfig.eslint.json tsconfig.json views wallaby.js yarn.lock
+ '[' -e /dev/ttyAMA0 ']'
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=
+ [[ '' == a\8 ]]
+ [[ '' == a\8 ]]
+ [[ '' == a\d ]]
+ echo 'Everything is successfully installed!'
Everything is successfully installed!
+ echo 4
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Salvialf · Novembre 19, 2022, 12:56

OK c’est bien la version de nodejs qui pose problème.

Il faudrait relancer les dépendances MQTT Manager dans un 1er temps puis vérifier la version de nodejs à l’issue.

Si toujours en nodejs 10, tu peux exécuter le script manuellement depuis la configuration Jeedom, onglet OS/DB > Administration système en tapant :

sudo /var/www/html/resources/install_nodejs.sh

Si jamais la relance des dépendances MQTT n’est pas suffisante pour mettre à jour nodejs, je veux bien les logs mqtt2_packages en retour stp

PS: attention à ne pas partager de clé API en public à l’avenir

philippe456 · Novembre 19, 2022, 12:59

Ok je fais cela et dis ce qu’il en est ASAP

MERCI pour ton aide.

philippe456 · Novembre 19, 2022, 1:15

relance dépendances MQTT Manager : OK

nodejs :

pas de changement de version : toujours en 10

je ne trouve pas les logs mqtt2_packages , j’ai seulement

j’ai executé la commande

:
voici le résultat :

Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://httpredir.debian.org/debian buster InRelease
Hit:3 http://httpredir.debian.org/debian buster-updates InRelease
Hit:4 http://httpredir.debian.org/debian buster-backports InRelease
Hit:5 http://armbian.systemonachip.net/apt buster InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u4).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
/var/www/html/resources/install_nodejs.sh: line 52: lsb_release: command not found
[Check Version NodeJS actuelle : v10.24.0 : [  KO  ]
Installation de NodeJS 16
Utilisation du dépot officiel

## Installing the NodeSource Node.js 16.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://httpredir.debian.org/debian buster InRelease
Hit:3 http://httpredir.debian.org/debian buster-updates InRelease
Hit:4 http://httpredir.debian.org/debian buster-backports InRelease
Hit:5 http://armbian.hosthatch.com/apt buster InRelease
Reading package lists...

## Installing packages required for setup: lsb-release...

+ apt-get install -y lsb-release > /dev/null 2>&1
main: line 210: lsb_release: command not found
main: line 216: lsb_release: command not found

## Confirming "" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_16.x/dists//Release'

## Your distribution, identified as "", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libc-ares2 libnode64
Suggested packages:
  npm
Recommended packages:
  nodejs-doc
The following NEW packages will be installed:
  libc-ares2 libnode64 nodejs
0 upgraded, 3 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/5454 kB of archives.
After this operation, 22.9 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2: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 ... 57452 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1+deb10u1_arm64.deb ...
Unpacking libc-ares2:arm64 (1.14.0-1+deb10u1) ...
Selecting previously unselected package libnode64:arm64.
Preparing to unpack .../libnode64_10.24.0~dfsg-1~deb10u2_arm64.deb ...
Unpacking libnode64:arm64 (10.24.0~dfsg-1~deb10u2) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_10.24.0~dfsg-1~deb10u2_arm64.deb ...
Unpacking nodejs (10.24.0~dfsg-1~deb10u2) ...
Setting up libc-ares2:arm64 (1.14.0-1+deb10u1) ...
Setting up libnode64:arm64 (10.24.0~dfsg-1~deb10u2) ...
Setting up nodejs (10.24.0~dfsg-1~deb10u2) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.28-10+deb10u2) ...
Processing triggers for man-db (2.8.5-2) ...
[Check Version NodeJS après install : v10.24.0 : [  KO  ] -> relancez les dépendances
[Check Prefix : /usr/local and sudo prefix : /usr/local and www-data prefix : /usr/local : [  OK  ]

ca ne sent pas bon …

philippe456 · Novembre 19, 2022, 1:19

toujours en

je me demande si je ne devrais pas repartir sur une install neuve sur mon odroid C2 (de poduction) et remettre ma sauvegarde ensuite …

Typher · Novembre 19, 2022, 1:26

C’est quoi le retour de cette commande ?

lsb_release -d
lsb_release -c -s

philippe456 · Novembre 19, 2022, 1:31

sh: 1: lsb_release: not found

philippe456 · Novembre 19, 2022, 1:33

j’installe en SSH les packages :

`Last login: Sat Nov 19 11:55:58 2022 from 192.168.1.120
odroid@jeedom:~$ lsb_release -d

Command ‹ lsb_release › not found, but can be installed with:

sudo apt install lsb-release

odroid@jeedom:~$ sudo apt install lsb-release
[sudo] password for odroid:
Sorry, try again.
[sudo] password for odroid:
Reading package lists… Done
Building dependency tree
Reading state information… Done
lsb-release is already the newest version (10.2019051400).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
odroid@jeedom:~$ ^C
odroid@jeedom:~$
`

Typher · Novembre 19, 2022, 1:34

Visiblement Odroid C2 n’est pas supporté dans l’installation de NodeJs, en tous cas quand tu regardes le tableau des compatibilités dans l’installation il n’y a rien concernant ta version


DISTRO=$(lsb_release -c -s)

check_alt() {
    if [ "X${DISTRO}" == "X${2}" ]; then
        echo
        echo "## You seem to be using ${1} version ${DISTRO}."
        echo "## This maps to ${3} \"${4}\"... Adjusting for you..."
        DISTRO="${4}"
    fi
}

check_alt "Astra Linux"    "orel"            "Debian"        "stretch"
check_alt "BOSS"           "anokha"          "Debian"        "wheezy"
check_alt "BOSS"           "anoop"           "Debian"        "jessie"
check_alt "BOSS"           "drishti"         "Debian"        "stretch"
check_alt "BOSS"           "unnati"          "Debian"        "buster"
check_alt "BOSS"           "urja"            "Debian"        "bullseye"
check_alt "bunsenlabs"     "bunsen-hydrogen" "Debian"        "jessie"
check_alt "bunsenlabs"     "helium"          "Debian"        "stretch"
check_alt "bunsenlabs"     "lithium"         "Debian"        "buster"
check_alt "Devuan"         "jessie"          "Debian"        "jessie"
check_alt "Devuan"         "ascii"           "Debian"        "stretch"
check_alt "Devuan"         "beowulf"         "Debian"        "buster"
check_alt "Devuan"         "chimaera"        "Debian"        "bullseye"
check_alt "Devuan"         "ceres"           "Debian"        "sid"
check_alt "Deepin"         "panda"           "Debian"        "sid"
check_alt "Deepin"         "unstable"        "Debian"        "sid"
check_alt "Deepin"         "stable"          "Debian"        "buster"
check_alt "Deepin"         "apricot"         "Debian"        "buster"
check_alt "elementaryOS"   "luna"            "Ubuntu"        "precise"
check_alt "elementaryOS"   "freya"           "Ubuntu"        "trusty"
check_alt "elementaryOS"   "loki"            "Ubuntu"        "xenial"
check_alt "elementaryOS"   "juno"            "Ubuntu"        "bionic"
check_alt "elementaryOS"   "hera"            "Ubuntu"        "bionic"
check_alt "elementaryOS"   "odin"            "Ubuntu"        "focal"
check_alt "elementaryOS"   "jolnir"          "Ubuntu"        "focal"
check_alt "Kali"           "sana"            "Debian"        "jessie"
check_alt "Kali"           "kali-rolling"    "Debian"        "bullseye"
check_alt "Linux Mint"     "maya"            "Ubuntu"        "precise"
check_alt "Linux Mint"     "qiana"           "Ubuntu"        "trusty"
check_alt "Linux Mint"     "rafaela"         "Ubuntu"        "trusty"
check_alt "Linux Mint"     "rebecca"         "Ubuntu"        "trusty"
check_alt "Linux Mint"     "rosa"            "Ubuntu"        "trusty"
check_alt "Linux Mint"     "sarah"           "Ubuntu"        "xenial"
check_alt "Linux Mint"     "serena"          "Ubuntu"        "xenial"
check_alt "Linux Mint"     "sonya"           "Ubuntu"        "xenial"
check_alt "Linux Mint"     "sylvia"          "Ubuntu"        "xenial"
check_alt "Linux Mint"     "tara"            "Ubuntu"        "bionic"
check_alt "Linux Mint"     "tessa"           "Ubuntu"        "bionic"
check_alt "Linux Mint"     "tina"            "Ubuntu"        "bionic"
check_alt "Linux Mint"     "tricia"          "Ubuntu"        "bionic"
check_alt "Linux Mint"     "ulyana"          "Ubuntu"        "focal"
check_alt "Linux Mint"     "ulyssa"          "Ubuntu"        "focal"
check_alt "Linux Mint"     "uma"             "Ubuntu"        "focal"
check_alt "Linux Mint"     "una"             "Ubuntu"        "focal"
check_alt "Linux Mint"     "vanessa"         "Ubuntu"        "jammy"
check_alt "Liquid Lemur"   "lemur-3"         "Debian"        "stretch"
check_alt "LMDE"           "betsy"           "Debian"        "jessie"
check_alt "LMDE"           "cindy"           "Debian"        "stretch"
check_alt "LMDE"           "debbie"          "Debian"        "buster"
check_alt "LMDE"           "elsie"           "Debian"        "bullseye"
check_alt "MX Linux 17"    "Horizon"         "Debian"        "stretch"
check_alt "MX Linux 18"    "Continuum"       "Debian"        "stretch"
check_alt "MX Linux 19"    "patito feo"      "Debian"        "buster"
check_alt "MX Linux 21"    "wildflower"      "Debian"        "bullseye"
check_alt "Pardus"         "onyedi"          "Debian"        "stretch"
check_alt "Parrot"         "ara"             "Debian"        "bullseye"
check_alt "PureOS"         "green"           "Debian"        "sid"
check_alt "PureOS"         "amber"           "Debian"        "buster"
check_alt "PureOS"         "byzantium"       "Debian"        "bullseye"
check_alt "SolydXK"        "solydxk-9"       "Debian"        "stretch"
check_alt "Sparky Linux"   "Tyche"           "Debian"        "stretch"
check_alt "Sparky Linux"   "Nibiru"          "Debian"        "buster"
check_alt "Sparky Linux"   "Po-Tolo"         "Debian"        "bullseye"
check_alt "Tanglu"         "chromodoris"     "Debian"        "jessie"
check_alt "Trisquel"       "toutatis"        "Ubuntu"        "precise"
check_alt "Trisquel"       "belenos"         "Ubuntu"        "trusty"
check_alt "Trisquel"       "flidas"          "Ubuntu"        "xenial"
check_alt "Trisquel"       "etiona"          "Ubuntu"        "bionic"
check_alt "Ubilinux"       "dolcetto"        "Debian"        "stretch"
check_alt "Uruk GNU/Linux" "lugalbanda"      "Ubuntu"        "xenial"

philippe456 · Novembre 19, 2022, 1:40

bon, je suis en train de tester un odroid N2+ depuis ce matin . Cela semble fonctionner avec les nouveaux plugins. j’ai mis une version ARMBIAN Armbian_21.08.1_Odroidn2_bullseye_current_5.10.60.img

Je vais refaire une install bien propre sur le N2+ pour pouvoir le mettre en production à la place du C2.

en attendant je vais rester en open zwave sur mon C2. Tant pis

en tout cas un grand merci pour votre aide. @Salvialf et @Typher .

bon weekend