Bonjour,
Je viens de faire l’acquisition de 2 prises Smart Plug Philips Hue pour contrôler l’allumage et l’extinction de la pompe et du chauffage de piscine. Serait-il possible que l’on voit ensemble pour l’intégration de celles-ci dans le service ?
Merci beaucoup par avance.
Voici ce qu’il faut faire:
Merci @Tlse-vins de ton retour.
[
{
"name":"Prise pompe Piscine",
"service_id":"86b98c11-f85f-44e4-8f18-030576b3ee9d",
"external_id":"philips-hue-light:ecb5fa25a522:3",
"selector":"philips-hue-light:ecb5fa25a522:3",
"should_poll":true,
"model":"LOM002",
"poll_frequency":60000,
"features":[],
"not_handled":true,
"raw_philips_hue_device":
{
"_rawData":
{
"state":
{
"on":false,
"alert":"select",
"mode":"homeautomation",
"reachable":true
},
"swupdate":
{
"state":"noupdates",
"lastinstall":"2020-04-26T12:13:30"
},
"type":"On/Off plug-in unit",
"name":"Prise pompe Piscine",
"modelid":"LOM002",
"manufacturername":"Signify Netherlands B.V.",
"productname":"Hue Smart plug",
"capabilities":
{
"certified":true,
"control":{},
"streaming":
{
"renderer":false,
"proxy":false
}
},
"config":
{
"archetype":"plug",
"function":"functional",
"direction":"omnidirectional",
"startup":
{
"mode":"safety",
"configured":true
}
},
"uniqueid":"00:17:88:01:08:9d:f7:5a-0b",
"swversion":"1.65.9_hB3217DF",
"swconfigid":"4303D274",
"productid":"SmartPlug_OnOff_v01-00_02"
},
"_id":3
}
}
Au besoin @pierre-gilles ou autre, dites moi si je peux être utile
Il y a eu une discussion pour que les nouveaux périphériques soient détecté et rajouté (me semble t’il) tout seul.
Je ne sais pas où sa en ai.
@Terdious je regarde pour implémenter les prises, j’aurai besoin de toi pour test car je n’en possède pas
Oui bien sûr @VonOx, aucun soucis, fait moi signe quand tu as besoin
Salut @VonOx,
Je viens de l’implémenter en dev de la manière suivante :
Ca fonctionne impec :
@VonOx est-ce que tu valides ? Faut-il faire un test avant ? Car ça je ne sais pas faire …^^ Après si on m’apprend, car je n’arrive pas à suivre la doc, je peux m’en occuper.
J’en aurais besoin pour démarrer la pompe du puit toute les heures pendant 5 minutes.
Comme vu en mp, j’ai effectué la PR #781 pour l’ajout du modèle Hue Smart Plug LOM002. J’ai modifié 2 fichiers (light.getLights.js dans server/service/philips-hue/lib/light - voir post ci-dessus / et lights.json dans server/test/services) :
,
{
"_rawData": {
"state": {
"on": true,
"bri": 254,
"alert": "none",
"mode": "homeautomation",
"reachable": false
},
"swupdate": {
"state": "noupdates",
"lastinstall": "2020-04-25T10:55:36"
},
"type":"On/Off plug-in unit",
"name":"Prise chauffage Piscine",
"modelid": "LOM002",
"manufacturername": "Signify Netherlands B.V.",
"productname": "Hue Smart plug",
"capabilities": {
"certified": true,
"control": {},
"streaming": {
"renderer": false,
"proxy": false
}
},
"config": {
"archetype": "plug",
"function": "functional",
"direction": "omnidirectional",
"startup": {
"mode": "safety",
"configured": true
}
},
"uniqueid": "00:17:88:01:08:9f:97:bd-0c",
"swversion": "1.55.10_r29112",
"swconfigid": "4303D274",
"productid": "SmartPlug_OnOff_v01-00_02"
},
"_id": 25,
"id": 25
}
Mais le npm test ne passe pas :
~\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server [Philips-Hue-L0M002 +0 ~1 -0 !]> npm test
> gladys-server@ pretest C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server
> npm run eslint
> gladys-server@ eslint C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server
> eslint .
C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\usb\api\usb.controller.js
13:17 warning Unexpected unnamed function func-names
C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\zwave\index.js
7:25 error Unable to resolve path to module 'openzwave-shared' import/no-unresolved
C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\test\benchmark\triggers.js
61:8 warning Unexpected constant condition no-constant-condition
C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\test\lib\gateway\GladysGatewayClientMock.test.js
4:33 warning Unexpected unnamed function func-names
✖ 4 problems (1 error, 3 warnings)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gladys-server@ eslint: `eslint .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the gladys-server@ eslint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\tlemaistre\AppData\Roaming\npm-cache\_logs\2020-05-11T11_08_21_953Z-debug.log
npm ERR! Test failed. See above for more details.
Je n’ai pourtant fait ni plus ni moins l’exemple que m’a fournis @VonOx pour son dernier ajout de modèle. Peut-être un problème d’installation ? Mais il me trouve une erreur sur le service zwave …
Merci d’avance
Tu es sur Windows , le module npm n’est pas installé a priori.
Essaye de voir si le npm install pour le server renvoi une erreur.
En effet :
2020-05-11T14:02:34+0200 <info> install_service_dependencies.js:17 () Installing dependencies in folder C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\xiaomi
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for gladys-xiaomi@: wanted {"os":"darwin,linux","arch":"x64,arm,arm64"} (current: {"os":"win32","arch":"x64"})
npm ERR! notsup Valid OS: darwin,linux
npm ERR! notsup Valid Arch: x64,arm,arm64
npm ERR! notsup Actual OS: win32
npm ERR! notsup Actual Arch: x64
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\tlemaistre\AppData\Roaming\npm-cache\_logs\2020-05-11T12_02_37_165Z-debug.log
2020-05-11T14:02:37+0200 <warn> install_service_dependencies.js:23 () Error: Command failed: cd C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\xiaomi && npm install --unsafe-perm
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for gladys-xiaomi@: wanted {"os":"darwin,linux","arch":"x64,arm,arm64"} (current: {"os":"win32","arch":"x64"})
npm ERR! notsup Valid OS: darwin,linux
npm ERR! notsup Valid Arch: x64,arm,arm64
npm ERR! notsup Actual OS: win32
npm ERR! notsup Actual Arch: x64
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\tlemaistre\AppData\Roaming\npm-cache\_logs\2020-05-11T12_02_37_165Z-debug.log
at checkExecSyncError (child_process.js:630:11)
at execSync (child_process.js:666:15)
at C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\cli\install_service_dependencies.js:19:5
at Array.forEach (<anonymous>)
at Object.<anonymous> (C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\cli\install_service_dependencies.js:16:13)
at Module._compile (internal/modules/cjs/loader.js:1157:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1177:10)
at Module.load (internal/modules/cjs/loader.js:1001:32)
at Function.Module._load (internal/modules/cjs/loader.js:900:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12) {
status: 1,
signal: null,
output: [
null,
<Buffer >,
<Buffer 6e 70 6d 20 45 52 52 21 20 63 6f 64 65 20 45 42 41 44 50 4c 41 54 46 4f 52 4d 0a 6e 70 6d 20 45 52 52 21 20 6e 6f 74 73 75 70 20 55 6e 73 75 70 70 6f ... 432 more
bytes>
],
pid: 6656,
stdout: <Buffer >,
stderr: <Buffer 6e 70 6d 20 45 52 52 21 20 63 6f 64 65 20 45 42 41 44 50 4c 41 54 46 4f 52 4d 0a 6e 70 6d 20 45 52 52 21 20 6e 6f 74 73 75 70 20 55 6e 73 75 70 70 6f ... 432 more bytes>
}
2020-05-11T14:02:37+0200 <info> install_service_dependencies.js:17 () Installing dependencies in folder C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\zwave
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\package.json'
npm WARN ozwinstall-g2cmil No description
npm WARN ozwinstall-g2cmil No repository field.
npm WARN ozwinstall-g2cmil No README data
npm WARN ozwinstall-g2cmil No license field.
fs.js:35
} = primordials;
^
ReferenceError: primordials is not defined
at fs.js:35:5
at req_ (C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\node_modules\natives\index.js:143:24)
at Object.req [as require] (C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\node_modules\natives\index.js:55:10)
at Object.<anonymous> (C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\node_modules\fstream\node_modules\graceful-fs\fs.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:1157:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1177:10)
at Module.load (internal/modules/cjs/loader.js:1001:32)
at Function.Module._load (internal/modules/cjs/loader.js:900:14)
at Module.require (internal/modules/cjs/loader.js:1043:19)
at require (internal/modules/cjs/helpers.js:77:18)
npm WARN rollback Rolling back openzwave-shared@1.5.8 failed (this is probably harmless): EPERM: operation not permitted, scandir 'C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\zwave\node_modules'
npm WARN gladys-zwave@ No description
npm WARN gladys-zwave@ No repository field.
npm WARN gladys-zwave@ No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! openzwave-shared@1.5.8 preinstall: `node lib/install-ozw.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the openzwave-shared@1.5.8 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\tlemaistre\AppData\Roaming\npm-cache\_logs\2020-05-11T12_02_57_763Z-debug.log
2020-05-11T14:02:57+0200 <warn> install_service_dependencies.js:23 () Error: Command failed: cd C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\zwave && npm install --unsafe-perm
npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\package.json'
npm WARN ozwinstall-g2cmil No description
npm WARN ozwinstall-g2cmil No repository field.
npm WARN ozwinstall-g2cmil No README data
npm WARN ozwinstall-g2cmil No license field.
fs.js:35
} = primordials;
^
ReferenceError: primordials is not defined
at fs.js:35:5
at req_ (C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\node_modules\natives\index.js:143:24)
at Object.req [as require] (C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\node_modules\natives\index.js:55:10)
at Object.<anonymous> (C:\Users\TLEMAI~1\AppData\Local\Temp\ozwinstall-g2cmil\node_modules\fstream\node_modules\graceful-fs\fs.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:1157:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1177:10)
at Module.load (internal/modules/cjs/loader.js:1001:32)
at Function.Module._load (internal/modules/cjs/loader.js:900:14)
at Module.require (internal/modules/cjs/loader.js:1043:19)
at require (internal/modules/cjs/helpers.js:77:18)
npm WARN rollback Rolling back openzwave-shared@1.5.8 failed (this is probably harmless): EPERM: operation not permitted, scandir 'C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\services\zwave\node_modules'
npm WARN gladys-zwave@ No description
npm WARN gladys-zwave@ No repository field.
npm WARN gladys-zwave@ No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! openzwave-shared@1.5.8 preinstall: `node lib/install-ozw.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the openzwave-shared@1.5.8 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\tlemaistre\AppData\Roaming\npm-cache\_logs\2020-05-11T12_02_57_763Z-debug.log
at checkExecSyncError (child_process.js:630:11)
at execSync (child_process.js:666:15)
at C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\cli\install_service_dependencies.js:19:5
at Array.forEach (<anonymous>)
at Object.<anonymous> (C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\cli\install_service_dependencies.js:16:13)
at Module._compile (internal/modules/cjs/loader.js:1157:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1177:10)
at Module.load (internal/modules/cjs/loader.js:1001:32)
at Function.Module._load (internal/modules/cjs/loader.js:900:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12) {
status: 1,
signal: null,
output: [
null,
<Buffer 0a 3e 20 6f 70 65 6e 7a 77 61 76 65 2d 73 68 61 72 65 64 40 31 2e 35 2e 38 20 70 72 65 69 6e 73 74 61 6c 6c 20 43 3a 5c 55 73 65 72 73 5c 74 6c 65 6d ... 241 more
bytes>,
<Buffer 6e 70 6d 20 57 41 52 4e 20 64 65 70 72 65 63 61 74 65 64 20 77 72 65 6e 63 68 40 31 2e 35 2e 39 3a 20 77 72 65 6e 63 68 2e 6a 73 20 69 73 20 64 65 70 ... 2649 more bytes>
],
pid: 19104,
stdout: <Buffer 0a 3e 20 6f 70 65 6e 7a 77 61 76 65 2d 73 68 61 72 65 64 40 31 2e 35 2e 38 20 70 72 65 69 6e 73 74 61 6c 6c 20 43 3a 5c 55 73 65 72 73 5c 74 6c 65 6d ... 241 more bytes>,
stderr: <Buffer 6e 70 6d 20 57 41 52 4e 20 64 65 70 72 65 63 61 74 65 64 20 77 72 65 6e 63 68 40 31 2e 35 2e 39 3a 20 77 72 65 6e 63 68 2e 6a 73 20 69 73 20 64 65 70 ... 2649 more bytes>
}
npm WARN eslint-config-airbnb@17.1.1 requires a peer of eslint-plugin-jsx-a11y@^6.2.3 but none is installed. You must install peer dependencies yourself.
npm WARN eslint-config-airbnb@17.1.1 requires a peer of eslint-plugin-react@^7.14.2 but none is installed. You must install peer dependencies yourself.
npm WARN ts-enum-util@4.0.1 requires a peer of typescript@>= 2.9.1 but none is installed. You must install peer dependencies yourself.
npm WARN ts-type@1.2.9 requires a peer of @types/bluebird@* but none is installed. You must install peer dependencies yourself.
npm WARN gladys-server@ No description
npm WARN gladys-server@ No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
added 2 packages from 2 contributors, removed 8 packages, updated 18 packages and audited 5410 packages in 80.326s
1 package is looking for funding
run `npm fund` for details
found 148 vulnerabilities (133 low, 3 moderate, 11 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
Et pourtant le service Philips Hue, qui est en erreur par exemple, tourne bien.
Tu as bien le package windows-build-tools d’installé sur ta machine ?
npm install --global windows-build-tools
Tout d’abord merci pour ton aide @VonOx.
Alors oui je l’avais bien d’installé, dans le doute je l’ai relancé, j’ai eu une màj c’est tout. Pas d’erreur.
J’ai relancé un nom install, même erreur que précédemment. npm test également !!
Dans le doute, ci-dessous le fichier log du npm test :
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\tlemaistre\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'eslint'
1 verbose cli ]
2 info using npm@6.13.7
3 info using node@v12.16.0
4 verbose run-script [ 'preeslint', 'eslint', 'posteslint' ]
5 info lifecycle gladys-server@~preeslint: gladys-server@
6 info lifecycle gladys-server@~eslint: gladys-server@
7 verbose lifecycle gladys-server@~eslint: unsafe-perm in lifecycle true
8 verbose lifecycle gladys-server@~eslint: PATH: C:\Users\tlemaistre\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server\node_modules\.bin;C:\Program Files (x86)\Google\Chrome\Application;C:\Program Files (x86)\Microsoft Office\Office16\;C:\Python27\;C:\Python27\Scripts;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\AdoptOpenJDK\jre-8.0.212.03-hotspot\bin;C:\Program Files (x86)\AdoptOpenJDK\jre-8.0.212.03-hotspot\bin;C:\Program Files\AdoptOpenJDK\jre-11.0.3.7-hotspot\bin;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\PuTTY\;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Program Files\Git\cmd;C:\Users\tlemaistre\AppData\Local\Microsoft\WindowsApps;;C:\Users\tlemaistre\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\tlemaistre\AppData\Roaming\npm;C:\Program Files\Git\bin;C:\Users\tlemaistre\Documents\Gladys\Software\PowerShell\scripts;C:\Users\tlemaistre\Documents\Gladys\Software\gnuplot\gnuplotscript\powershell
9 verbose lifecycle gladys-server@~eslint: CWD: C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server
10 silly lifecycle gladys-server@~eslint: Args: [ '/d /s /c', 'eslint .' ]
11 silly lifecycle gladys-server@~eslint: Returned: code: 1 signal: null
12 info lifecycle gladys-server@~eslint: Failed to exec eslint script
13 verbose stack Error: gladys-server@ eslint: `eslint .`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\tlemaistre\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:321:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\tlemaistre\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:321:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid gladys-server@
15 verbose cwd C:\Users\tlemaistre\Documents\Gladys\Gladys-Master-Philips Hue\Gladys\server
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\tlemaistre\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "eslint"
18 verbose node v12.16.0
19 verbose npm v6.13.7
20 error code ELIFECYCLE
21 error errno 1
22 error gladys-server@ eslint: `eslint .`
22 error Exit status 1
23 error Failed at the gladys-server@ eslint script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
J’ai la même chose sur mon windows ( je dois investiguer )
Ouf tu me rassure ^^ J’attends ton retour !!
Du coup pour gladys-dev, pour que les tests passent, vous faites ça sur quel support ? Pas sur rpi je suppose.
Hello !!
Je me permet de revenir vers vous concernant ce souci de test car après de multiple recherche, je ne trouve rien… et toi @VonOx aurais-tu par chance trouvé quelque chose ?
@pierre-gilles aurais-tu une idée ? dans le cas contraire car je sais que tu n’utilises pas windows, aurais-tu ou auriez-vous une solution pour passer ces tests ? (nouvelle install sur raspi, sur NAS Asustor ? sur machine virtuelle ?) Ou bien, quelqu’un pourrait-il s’en charger ? Ce serait dommage qu’un si petit ajout ne soit pas intégré à la prochaine màj ^^
A nouveau, merci d’avance !!
Va falloir patienter un peu @Terdious , j’ai pas eu le temps d’approfondir 
. Je testerai ta PR sur linux pour confirmer que tout est ok et que @pierre-gilles puisse merge.
ça va pas résoudre ton problème sur WIndows mais au moins ça fera avancer le schmilblick