Re: MyDomoAtHome - ImperiHome
Publié : 14 nov. 2023, 18:39
Non, pas de docker, une VM avec Debian 11 sous Virtual Machine Manager (synology).
Reprenez le contrôle de votre domotique
https://easydomoticz.com/forum/
Merci, ça marche cette fois. Mon image est une debian Linux 11epierre a écrit : 14 nov. 2023, 19:41 J'avais changé le chemin des logs, réessayes:
https://e-nef.com/domoticz/mdah/node-my ... -0.3.4.deb
Code : Tout sélectionner
root@domoticzvm:/home/pi# uname -a
Linux domoticzvm 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64 GNU/Linux
root@domoticzvm:/home/pi# cat /etc/debian_version
11.8
root@domoticzvm:/home/pi# dpkg -i node-mydomoathome-0.3.4.deb
(Lecture de la base de données... 198784 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de node-mydomoathome-0.3.4.deb ...
Dépaquetage de mydomoathome (0.3.4) sur (0.2.50) ...
Paramétrage de mydomoathome (0.3.4) ...
rebuilt dependencies successfully
npm notice
npm notice New major version of npm available! 8.13.2 -> 10.2.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.2.3
npm notice Run npm install -g npm@10.2.3 to update!
npm notice
Synchronizing state of mydomoathome.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mydomoathome
root@domoticzvm:/home/pi# service mydomoathome status
● mydomoathome.service - MDAH ISS Rest interface for Domoticz to Imperihome
Loaded: loaded (/etc/systemd/system/mydomoathome.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-11-14 20:16:06 CET; 10s ago
Process: 1633482 ExecStartPre=/bin/mkdir -p /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 1633483 ExecStartPre=/bin/chown www-data:www-data /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 1633484 ExecStartPre=/bin/chown www-data:www-data /etc/mydomoathome/config.json (code=exited, status=0/SUCCESS)
Process: 1633485 ExecStartPre=/bin/chmod 755 /run/mydomoathome (code=exited, status=0/SUCCESS)
Main PID: 1633486 (mydomoathome)
Tasks: 23 (limit: 2307)
Memory: 75.7M
CPU: 2.672s
CGroup: /system.slice/mydomoathome.service
├─1633486 /bin/bash /usr/share/mydomoathome/bin/mydomoathome
├─1633487 node /usr/bin/forever --minUptime 5000 --spinSleepTime 2000 --max-old-space-size=128 -a -l /var/log/mydomoathome/mdah.log /usr/share/mydomoathome/app/mdah.js
└─1633507 /usr/bin/node /usr/share/mydomoathome/app/mdah.js
nov. 14 20:16:06 domoticzvm systemd[1]: Starting MDAH ISS Rest interface for Domoticz to Imperihome...
nov. 14 20:16:06 domoticzvm systemd[1]: Started MDAH ISS Rest interface for Domoticz to Imperihome.
nov. 14 20:16:08 domoticzvm MDAH[1633487]: (node:1633487) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
nov. 14 20:16:08 domoticzvm MDAH[1633487]: (Use `node --trace-warnings ...` to show where the warning was created)
nov. 14 20:16:08 domoticzvm MDAH[1633487]: (node:1633487) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
Code : Tout sélectionner
root@domoticzvm:/home/pi# wget https://e-nef.com/domoticz/mdah/node-mydomoathome-0.3.6.deb
--2023-11-28 08:58:26-- https://e-nef.com/domoticz/mdah/node-mydomoathome-0.3.6.deb
Résolution de e-nef.com (e-nef.com)… 2001:41d0:301::23, 164.132.235.17
Connexion à e-nef.com (e-nef.com)|2001:41d0:301::23|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 16335830 (16M) [application/x-debian-package]
Sauvegarde en : « node-mydomoathome-0.3.6.deb »
node-mydomoathome-0.3.6.deb 100%[======================================================================================================>] 15,58M 29,0MB/s ds 0,5s
2023-11-28 08:58:27 (29,0 MB/s) — « node-mydomoathome-0.3.6.deb » sauvegardé [16335830/16335830]
root@domoticzvm:/home/pi# dpkg -i node-mydomoathome-0.3.6.deb
(Lecture de la base de données... 211206 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de node-mydomoathome-0.3.6.deb ...
Dépaquetage de mydomoathome (0.3.6) sur (0.3.4) ...
Paramétrage de mydomoathome (0.3.6) ...
rebuilt dependencies successfully
Synchronizing state of mydomoathome.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mydomoathome
Code : Tout sélectionner
● mydomoathome.service - MDAH ISS Rest interface for Domoticz to Imperihome
Loaded: loaded (/etc/systemd/system/mydomoathome.service; enabled; preset: enabled)
Active: active (running) since Wed 2025-05-28 16:17:23 CEST; 16h ago
Process: 680 ExecStartPre=/bin/mkdir -p /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 693 ExecStartPre=/bin/chown www-data:www-data /run/mydomoathome (code=exited, status=0/SUCCESS)
Process: 698 ExecStartPre=/bin/chown www-data:www-data /etc/mydomoathome/config.json (code=exited, status=0/SUCCESS)
Process: 712 ExecStartPre=/bin/chmod 755 /run/mydomoathome (code=exited, status=0/SUCCESS)
Main PID: 716 (mydomoathome)
Tasks: 19 (limit: 4631)
Memory: 126.5M
CPU: 6h 37min 37.219s
CGroup: /system.slice/mydomoathome.service
├─ 716 /bin/bash /usr/share/mydomoathome/bin/mydomoathome
├─ 754 node /usr/bin/forever --minUptime 5000 --spinSleepTime 2000 --max-old-space-size=128 -a -l /var/log/mydomoathome/mdah.log /usr/share/mydomoathome/app/mdah.js
└─649016 /usr/bin/node /usr/share/mydomoathome/app/mdah.js
mai 29 09:01:05 domoticzvm MDAH[754]: at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
mai 29 09:01:05 domoticzvm MDAH[754]: errno: -2,
mai 29 09:01:05 domoticzvm MDAH[754]: code: 'ENOENT',
mai 29 09:01:05 domoticzvm MDAH[754]: syscall: 'spawn npm',
mai 29 09:01:05 domoticzvm MDAH[754]: path: 'npm',
mai 29 09:01:05 domoticzvm MDAH[754]: spawnargs: [ '-v' ]
mai 29 09:01:05 domoticzvm MDAH[754]: }
mai 29 09:01:05 domoticzvm MDAH[754]: Node.js v18.19.0
mai 29 09:01:05 domoticzvm MDAH[754]: {"level":"error","message":"Forever detected script exited with code: 1"}
mai 29 09:01:07 domoticzvm MDAH[754]: {"level":"error","message":"Script restart attempt #19209"}