MyDomoAtHome - ImperiHome

Forum dédié aux autres applis Android ou Apple.
Vous en connaissez une sympa, vous avez un problème de config ? C'est ici.
epierre
Messages : 648
Inscription : 27 mai 2015, 09:32
Contact :

Re: MyDomoAtHome - ImperiHome

Message par epierre »

mickaelr30 a écrit : 10 déc. 2021, 09:55 bon, je viens de refaire une install propre sur un raspberry,maintenant j'ai un problème quand je fais :
wget -qO - https://www.e-nef.com/domoticz/mdah/gpg.mykey | sudo apt-key add -
gpg: no valid OpenPGP data found.
c'est marrant car il me semble qu'hier la commande wget fonctionnait
si la clef est déjà dans le porte clef c'est normal
mickaelr30 a écrit : 10 déc. 2021, 09:55 c'est normal si quand je vais dans : https://www.e-nef.com/domoticz/mdah, gpg.mykey soit en rouge ?
tu as du le télécharger depuis le navigateur ou l'ouvrir c'est tout
Imperihome & Domoticz: MyDomoAtHome !
eedomus+ - Domoticz - MySensors
zigbee zwave nrf24l rfx
mickaelr30
Messages : 210
Inscription : 29 août 2015, 15:57

Re: MyDomoAtHome - ImperiHome

Message par mickaelr30 »

quand ca veux pas, ca veux pas
j'ai continué l'install quand je fais :

Code : Tout sélectionner

 sudo dpkg -i node-mydomoathome-0.2.45
dpkg: error: cannot access archive 'node-mydomoathome-0.2.45': No such file or directory

Code : Tout sélectionner

sudo dpkg -i node-mydomoathome-0.2.45.deb
dpkg: error: cannot access archive 'node-mydomoathome-0.2.45.deb': No such file or directory

Code : Tout sélectionner

sudo dpkg -i http://e-nef.com/domoticz/mdah/dists/buster/contrib/binary-armhf/node-mydomoathome-0.2.45.deb
dpkg: error: cannot access archive 'http://e-nef.com/domoticz/mdah/dists/buster/contrib/binary-armhf/node-mydomoathome-0.2.45.deb': No such file or directory

Code : Tout sélectionner

 sudo dpkg -i https://e-nef.com/domoticz/mdah/dists/buster/contrib/binary-armhf/node-mydomoathome-0.2.45.deb
dpkg: error: cannot access archive 'https://e-nef.com/domoticz/mdah/dists/buster/contrib/binary-armhf/node-mydomoathome-0.2.45.deb': No such file or directory
Domoticz + Imperihome + Mydomoathome
1-wire : 12 DS18b20 + 3 DS2413
Z-Wave : 8 FGR221 + 3 FGS222 + 3 FGSD002
téléinfo : 2 modules ( consommation + production)
Mysensors+2 éclairages ws2812 et WLED
2 caméra IP +1 raspberry piscine + 1 nuc domoticz
epierre
Messages : 648
Inscription : 27 mai 2015, 09:32
Contact :

Re: MyDomoAtHome - ImperiHome

Message par epierre »

dpkg ne fonctione que sur un paquet en local, donc fait d'abord un wget de l'URL
Imperihome & Domoticz: MyDomoAtHome !
eedomus+ - Domoticz - MySensors
zigbee zwave nrf24l rfx
mickaelr30
Messages : 210
Inscription : 29 août 2015, 15:57

Re: MyDomoAtHome - ImperiHome

Message par mickaelr30 »

j'ai fait sudo dpkg -i http://e-nef.com/domoticz/mdah/dists/bu ... ary-armhf/
dpkg: error: cannot access archive 'https://e-nef.com/domoticz/mdah/dists/b ... ary-armhf/': No such file or directory
donc je me suis lancé des noms d'oiseaux :lol: :lol: tout ça pour dire que je suis toujours autant mauvais sur debian
du coup j'ai recupéré le fichier node-mydomoathome-0.2.45.deb que j'ai récupéré sous : http://e-nef.com/domoticz/mdah/dists/bu ... ary-armhf/ et que j'ai mis sur la carte sd avec Wincsp mais j'ai pas fait de chmod +x
puis j'ai fait un sudo dpkg -i node-mydomoathome-0.2.45.deb et j'ai de nouveau ca :

Code : Tout sélectionner

 sudo dpkg -i node-mydomoathome-0.2.45.deb
Selecting previously unselected package mydomoathome.
(Reading database ... 125195 files and directories currently installed.)
Preparing to unpack node-mydomoathome-0.2.45.deb ...
/usr/local/bin/forever -> /usr/local/lib/node_modules/forever/bin/forever
forever@4.0.1 /usr/local/lib/node_modules/forever
├── object-assign@4.1.1
├── clone@2.1.2
├── eventemitter2@6.4.4
├── async@1.5.2
├── colors@0.6.2
├── mkdirp@0.5.5 (minimist@1.2.5)
├── configstore@4.0.0 (xdg-basedir@3.0.0, graceful-fs@4.2.8, dot-prop@4.2.1, unique-string@1.0.0, make-dir@1.3.0, write-file-atomic@2.4.3)
├── nssocket@0.6.0 (eventemitter2@0.4.14, lazy@1.0.11)
├── cliff@0.1.10 (eyes@0.1.8, colors@1.0.3)
├── prettyjson@1.2.1 (minimist@1.2.5, colors@1.4.0)
├── winston@0.8.3 (cycle@1.0.3, eyes@0.1.8, async@0.2.10, stack-trace@0.0.10, isstream@0.1.2, pkginfo@0.3.1)
├── shush@1.0.0 (strip-json-comments@0.1.3, caller@0.0.1)
├── forever-monitor@3.0.3 (minimatch@3.0.4, ps-tree@1.2.0, chokidar@2.1.8)
└── flatiron@0.4.3 (director@1.2.7, optimist@0.6.0, broadway@0.3.6, prompt@0.2.14)

> bufferutil@4.0.5 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil/build'
  CC(target) Release/obj.target/bufferutil/src/bufferutil.o
../src/bufferutil.c:3:22: fatal error: node_api.h: No such file or directory
 #include <node_api.h>
                      ^
compilation terminated.
bufferutil.target.mk:94: recipe for target 'Release/obj.target/bufferutil/src/bufferutil.o' failed
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Linux 4.9.41-v7+
gyp ERR! command "/usr/bin/nodejs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil
gyp ERR! node -v v4.8.2
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok

> utf-8-validate@5.0.7 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate/build'
  CC(target) Release/obj.target/validation/src/validation.o
../src/validation.c:4:22: fatal error: node_api.h: No such file or directory
 #include <node_api.h>
                      ^
compilation terminated.
validation.target.mk:94: recipe for target 'Release/obj.target/validation/src/validation.o' failed
make: *** [Release/obj.target/validation/src/validation.o] Error 1
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Linux 4.9.41-v7+
gyp ERR! command "/usr/bin/nodejs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate
gyp ERR! node -v v4.8.2
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok

> utf-8-validate@5.0.7 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate/build'
  CC(target) Release/obj.target/validation/src/validation.o
../src/validation.c:4:22: fatal error: node_api.h: No such file or directory
 #include <node_api.h>
                      ^
compilation terminated.
validation.target.mk:94: recipe for target 'Release/obj.target/validation/src/validation.o' failed
make: *** [Release/obj.target/validation/src/validation.o] Error 1
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Linux 4.9.41-v7+
gyp ERR! command "/usr/bin/nodejs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate
gyp ERR! node -v v4.8.2
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok

> bufferutil@4.0.5 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil/build'
  CC(target) Release/obj.target/bufferutil/src/bufferutil.o
../src/bufferutil.c:3:22: fatal error: node_api.h: No such file or directory
 #include <node_api.h>
                      ^
compilation terminated.
bufferutil.target.mk:94: recipe for target 'Release/obj.target/bufferutil/src/bufferutil.o' failed
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:12)
gyp ERR! System Linux 4.9.41-v7+
gyp ERR! command "/usr/bin/nodejs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil
gyp ERR! node -v v4.8.2
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
npm ERR! Linux 4.9.41-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/local/bin/npm" "install" "-g" "pm2"
npm ERR! node v4.8.2
npm ERR! npm  v2.15.12
npm ERR! code ELIFECYCLE

npm ERR! bufferutil@4.0.5 install: `node-gyp-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bufferutil@4.0.5 install script 'node-gyp-build'.
npm ERR! This is most likely a problem with the bufferutil package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs bufferutil
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls bufferutil
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /npm-debug.log
dpkg: error processing archive node-mydomoathome-0.2.45.deb (--install):
 subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
 node-mydomoathome-0.2.45.deb
c'est grave docteur ?
Domoticz + Imperihome + Mydomoathome
1-wire : 12 DS18b20 + 3 DS2413
Z-Wave : 8 FGR221 + 3 FGS222 + 3 FGSD002
téléinfo : 2 modules ( consommation + production)
Mysensors+2 éclairages ws2812 et WLED
2 caméra IP +1 raspberry piscine + 1 nuc domoticz
epierre
Messages : 648
Inscription : 27 mai 2015, 09:32
Contact :

Re: MyDomoAtHome - ImperiHome

Message par epierre »

Bon on avance, par contre quelle est ta version de nodejs ?
node -v
v10.19.0
npm -v
2.15.12


précédemment tu parlais de 4.8.2 qui est très vieille pour une distribution récente, il faudrait upgrader je pense. Buster est donné en version 10:
https://packages.debian.org/buster/nodejs
Imperihome & Domoticz: MyDomoAtHome !
eedomus+ - Domoticz - MySensors
zigbee zwave nrf24l rfx
mickaelr30
Messages : 210
Inscription : 29 août 2015, 15:57

Re: MyDomoAtHome - ImperiHome

Message par mickaelr30 »

ok du coup j'ai fait une mise à jour sudo curl -sL https://deb.nodesource.com/setup_17.x | sudo -E bash -

j'ai :
node v8.11.1
npm 2.15.12
du coup j'ai refais un : sudo dpkg -i node-mydomoathome-0.2.45.deb

Code : Tout sélectionner

(Reading database ... 126525 files and directories currently installed.)
Preparing to unpack node-mydomoathome-0.2.45.deb ...
/usr/local/bin/forever -> /usr/local/lib/node_modules/forever/bin/forever
forever@4.0.1 /usr/local/lib/node_modules/forever
├── object-assign@4.1.1
├── clone@2.1.2
├── eventemitter2@6.4.4
├── colors@0.6.2
├── async@1.5.2
├── mkdirp@0.5.5 (minimist@1.2.5)
├── configstore@4.0.0 (xdg-basedir@3.0.0, graceful-fs@4.2.8, dot-prop@4.2.1, unique-string@1.0.0, make-dir@1.3.0, write-file-atomic@2.4.3)
├── nssocket@0.6.0 (eventemitter2@0.4.14, lazy@1.0.11)
├── cliff@0.1.10 (eyes@0.1.8, colors@1.0.3)
├── prettyjson@1.2.1 (minimist@1.2.5, colors@1.4.0)
├── winston@0.8.3 (cycle@1.0.3, eyes@0.1.8, async@0.2.10, stack-trace@0.0.10, isstream@0.1.2, pkginfo@0.3.1)
├── shush@1.0.0 (strip-json-comments@0.1.3, caller@0.0.1)
├── forever-monitor@3.0.3 (minimatch@3.0.4, ps-tree@1.2.0, chokidar@2.1.8)
└── flatiron@0.4.3 (director@1.2.7, optimist@0.6.0, broadway@0.3.6, prompt@0.2.14)

> bufferutil@4.0.5 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil/build'
  CC(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  COPY Release/bufferutil.node
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/bufferutil/build'

> bufferutil@4.0.5 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil/build'
  CC(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  COPY Release/bufferutil.node
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/bufferutil/build'

> utf-8-validate@5.0.7 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate/build'
  CC(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  COPY Release/validation.node
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/js-api/node_modules/utf-8-validate/build'

> utf-8-validate@5.0.7 install /usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate
> node-gyp-build

make: Entering directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate/build'
  CC(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  COPY Release/validation.node
make: Leaving directory '/usr/local/lib/node_modules/pm2/node_modules/@pm2/agent/node_modules/utf-8-validate/build'
/usr/local/bin/pm2 -> /usr/local/lib/node_modules/pm2/bin/pm2
/usr/local/bin/pm2-dev -> /usr/local/lib/node_modules/pm2/bin/pm2-dev
/usr/local/bin/pm2-docker -> /usr/local/lib/node_modules/pm2/bin/pm2-docker
/usr/local/bin/pm2-runtime -> /usr/local/lib/node_modules/pm2/bin/pm2-runtime
pm2@5.1.2 /usr/local/lib/node_modules/pm2
├── @pm2/pm2-version-check@1.0.4
├── cli-tableau@2.0.1
├── commander@2.15.1
├── eventemitter2@5.0.1
├── pm2-axon-rpc@0.7.1
├── sprintf-js@1.1.2
├── mkdirp@1.0.4
├── fclone@1.0.11
├── debug@4.3.3 (ms@2.1.2)
├── pidusage@2.0.21 (safe-buffer@5.2.1)
├── pm2-deploy@1.0.2 (run-series@1.1.9, tv4@1.3.0)
├── pm2-multimeter@0.1.2 (charm@0.1.2)
├── promptly@2.2.0 (read@1.0.7)
├── pm2-axon@4.0.1 (amp-message@0.1.2, escape-string-regexp@4.0.0, amp@0.3.1)
├── source-map-support@0.5.19 (buffer-from@1.1.2, source-map@0.6.1)
├── chalk@3.0.0 (supports-color@7.2.0, ansi-styles@4.3.0)
├── enquirer@2.3.6 (ansi-colors@4.1.1)
├── pm2-sysmonit@1.2.8 (systeminformation@5.9.17, tx2@1.0.5)
├── chokidar@3.5.2 (normalize-path@3.0.0, glob-parent@5.1.2, is-glob@4.0.3, is-binary-path@2.1.0, anymatch@3.1.2, readdirp@3.6.0, braces@3.0.2)
├── semver@7.3.5 (lru-cache@6.0.0)
├── blessed@0.1.81
├── needle@2.4.0 (sax@1.2.4, debug@3.2.7, iconv-lite@0.4.24)
├── yamljs@0.3.0 (glob@7.2.0, argparse@1.0.10)
├── async@3.2.2
├── dayjs@1.8.36
├── cron@1.8.2 (moment-timezone@0.5.34)
├── vizion@2.2.1 (ini@1.3.8, git-node-fs@1.0.0, js-git@0.7.8, async@2.6.3)
├── @pm2/io@5.0.0 (signal-exit@3.0.6, eventemitter2@6.4.5, semver@6.3.0, shimmer@1.2.1, tslib@1.9.3, require-in-the-middle@5.1.0, @opencensus/core@0.0.9, @opencensus/propagation-b3@0.0.8, async@2.6.3)
├── @pm2/js-api@0.6.7 (eventemitter2@6.4.5, axios@0.21.4, async@2.6.3, bufferutil@4.0.5, utf-8-validate@5.0.7, ws@7.5.6)
└── @pm2/agent@2.0.1 (fast-json-patch@3.1.0, semver@7.2.3, nssocket@0.6.0, proxy-agent@5.0.0, bufferutil@4.0.5, utf-8-validate@5.0.7, ws@7.4.6)
Unpacking mydomoathome (0.2.45) ...
dpkg: dependency problems prevent configuration of mydomoathome:
 mydomoathome depends on npm (>= 3.5.2); however:
  Version of npm on system is 2.14.7.

dpkg: error processing package mydomoathome (--install):
 dependency problems - leaving unconfigured
Processing triggers for systemd (232-25+deb9u1) ...
Errors were encountered while processing:
 mydomoathome
Domoticz + Imperihome + Mydomoathome
1-wire : 12 DS18b20 + 3 DS2413
Z-Wave : 8 FGR221 + 3 FGS222 + 3 FGSD002
téléinfo : 2 modules ( consommation + production)
Mysensors+2 éclairages ws2812 et WLED
2 caméra IP +1 raspberry piscine + 1 nuc domoticz
epierre
Messages : 648
Inscription : 27 mai 2015, 09:32
Contact :

Re: MyDomoAtHome - ImperiHome

Message par epierre »

ça avance bien encore, là:
mydomoathome depends on npm (>= 3.5.2); however:
Version of npm on system is 2.14.7.
Buster a la version 5,
https://packages.debian.org/buster/npm

regardes par ici si tu ne le prends pas du repo debian:https://docs.npmjs.com/try-the-latest-s ... ion-of-npm
Imperihome & Domoticz: MyDomoAtHome !
eedomus+ - Domoticz - MySensors
zigbee zwave nrf24l rfx
mickaelr30
Messages : 210
Inscription : 29 août 2015, 15:57

Re: MyDomoAtHome - ImperiHome

Message par mickaelr30 »

Code : Tout sélectionner

sudo npm install -g npm@latest
npm ERR! Linux 4.9.41-v7+
npm ERR! argv "/usr/bin/node" "/usr/local/bin/npm" "install" "-g" "npm@latest"
npm ERR! node v8.11.1
npm ERR! npm  v2.15.12
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module '/usr/local/lib/node_modules/npm/lib/build.js'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log
Domoticz + Imperihome + Mydomoathome
1-wire : 12 DS18b20 + 3 DS2413
Z-Wave : 8 FGR221 + 3 FGS222 + 3 FGSD002
téléinfo : 2 modules ( consommation + production)
Mysensors+2 éclairages ws2812 et WLED
2 caméra IP +1 raspberry piscine + 1 nuc domoticz
mickaelr30
Messages : 210
Inscription : 29 août 2015, 15:57

Re: MyDomoAtHome - ImperiHome

Message par mickaelr30 »

par contre je vais finir par me faire baffer :D :D
je suis en stretch et non en buster, ça peux poser problème ou pas ?
Domoticz + Imperihome + Mydomoathome
1-wire : 12 DS18b20 + 3 DS2413
Z-Wave : 8 FGR221 + 3 FGS222 + 3 FGSD002
téléinfo : 2 modules ( consommation + production)
Mysensors+2 éclairages ws2812 et WLED
2 caméra IP +1 raspberry piscine + 1 nuc domoticz
epierre
Messages : 648
Inscription : 27 mai 2015, 09:32
Contact :

Re: MyDomoAtHome - ImperiHome

Message par epierre »

ouf je comprends mieux, regardes alors ici:

https://linuxhint.com/install_npm_debian/
Imperihome & Domoticz: MyDomoAtHome !
eedomus+ - Domoticz - MySensors
zigbee zwave nrf24l rfx
Répondre