Bonjour
Depuis ce matin je n’arrive pas a me connecter à mon jeedom
Je suis sous frebox delta
Ci joint capture d’ecran
Bonsoir,
Est-ce que l’adresse de la VM n’aurait pas changée, regardé rapidement ça n’a pas l’air d’avoir grand chose à voir avec Jeedom… peux être que tu tombe sur un autre équipement
Je ne pense pas car qd je me connecte a mafreebox.fr , l’adressr n’a pas changé et indique bien que jeedom est démarré
Voici le message entier :
# Jeedom
vice like \"Thermostat\" or \"Door Lock\", you're actualy thinking of a Service. Accessories can expose multiple services.\n * [Characteristic](src/lib/Characteristic.ts): Represents a particular typed variable assigned to a Service, for instance the `LockMechanism` Service contains a `CurrentDoorState` Characteristic describing whether the door is currently locked.\n\nAll known built-in Service and Characteristic types that HomeKit supports are exposed as a separate subclass in [HomeKitTypes](src/lib/gen/HomeKit.ts).\n\nSee each of the corresponding class files for more explanation and notes.\n\nNotes\n=====\n\nSpecial thanks to [Alex Skalozub](https://twitter.com/pieceofsummer), who reverse engineered the server side HAP. ~~You can find his research at [here](https://gist.github.com/pieceofsummer/13272bf76ac1d6b58a30).~~ (Sadly, on Nov 4, Apple sent the [DMCA](https://github.com/github/dmca/blob/master/2014/2014-11-04-Apple.md) request to Github to remove the research.)\n\n[There](http://instagram.com/p/t4cPlcDksQ/) is a video demo running this project on Intel Edison.\n\nIf you are interested in HAP over BTLE, you might want to check [this](https://gist.github.com/KhaosT/6ff09ba71d306d4c1079).\n\nProjects based on HAP-NodeJS\n============================\n\n* [Homebridge](https://github.com/nfarina/homebridge) - HomeKit support for the impatient - Pluggable HomeKit Bridge. Plugins available for e.g. Pilight, Telldus TDtool, Savant, Netatmo, Open Pixel Control, HomeWizard, Fritz!Box, LG WebOS TV, Home Assistant, HomeMatic and many many more.\n* [OpenHAB-HomeKit-Bridge](https://github.com/htreu/OpenHAB-HomeKit-Bridge) - OpenHAB HomeKit Bridge bridges openHAB items to Apple´s HomeKit Accessory Protocol.\n* [homekit2mqtt](https://github.com/hobbyquaker/homekit2mqtt) - HomeKit to MQTT bridge.\n* [pimatic-hap](https://github.com/michbeck100/pimatic-hap) - Pimatic homekit bridge.\n* [node-red-contrib-homekit](https://github.com/NRCHKB/node-red-contrib-homekit-bridged) - Node-RED nodes to simulate Apple HomeKit devices.\n* [ioBroker.homekit](https://github.com/ioBroker/ioBroker.homekit2) - connect ioBroker to HomeKit.\n* [AccessoryServer](https://github.com/Appyx/AccessoryServer) - HomeKit integration for IR/RF/IP-devices\n","readmeFilename":"README.md","gitHead":"799aaa561025eb6f8aca9d42fad7f521bdaa311c","_id":"hap-nodejs@0.5.12-beta.3","_nodeVersion":"10.20.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-GfqTxlykjkg20bp76VJJ6XlgTVzmv4K+wA0LtExW64H1tHzkrDswvop/+H7BRtU25DA/Y55UizqkBurDVabatw==","shasum":"27691d388de25a5be160eb36c5212b325fe2a5f0","tarball":"https://registry.npmjs.org/hap-nodejs/-/hap-nodejs-0.5.12-beta.3.tgz","fileCount":251,"unpackedSize":1767840,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJekpUSCRA9TVsSAnZWagAAJbUQAKGBGyQeg1IKbTmRCMpa\nhrIlHS7ZBSiwp39Ww2rMzUIlkvX+W0ufgsYLlxDxKsPxdkgHtefn6OfJEcaD\nmVQjWNVg9j4l4lw6jHQT+Lf3C6Tj6K1bVzxXxrYcZRq4mPwuKMSOWd/QjoIX\nYlnmm93N5qnea7rfaCk7CPO3ZsMAMJXsSrINvdnRro8JuL2M9dPkgXF60f8i\ngNhAZFgz+W3ULDIrzDgQ/wthDuXLe0YIpNBI6GV0OH1cExft/hR/MPgZnbwu\naakcqys6TKFXhNK9PYqwzVOpXr40EDsdjpzARXOuy3Mr+HLuGpmCZtKqYXF3\nu1yboKr31/UzN0Pb/d0DlreLyjuNhcDM0ECg3DOQVjGzUZY+W+CUCXqqPhjj\ndVDAxrfiHt7EXt2dY3EDvHMmtbcVJ+fIf4ebZWFJ16pmlimNIXGZIGtgW3wZ\nb+8+uucRJQfuVKz6z6mA3/6YiD94E3YpCPSwCrzs5BbUWFkwPHXoHAXk7hiu\nBU7vW6ra0jMb/Ugdl/LLrXfgvxvbuNtyMAQ9X43os75BfnSJVZplJwqZmxmn\nmLhcki45DiXv6lvRc7JzUmTaKRJzy6oKAdz1UjQod7qHVCcQyTeapvWj+5Qr\n4jghfAn5YGv5s8IFk0ROxSrQLrvUzzmzLbzI4cvZR2GTYhmeT3FtcRlp8zrZ\n5jq2\r\n=cFnv\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDd2YEDnKAGQCCdkg4RfDUKD861MHmKUtv09NBpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJej3lwCRA9TVsSAnZWagAAnMAP/0/ffGdoGdJSXrSROuv9\nTnRlIbXWkXEziN6J0RLa4CX8T8D3Z0QNBrq5FVkEZd5mxFcI5zejhXa2KqY0\nrL2dRIZtGPK62x9iTUNRubofVIUTS8KX4IdXqSxd+yMmJKz/RuB0V9qWINu7\nm5CCkNaOoldTU44jWe6KJAmgLiLmkqzQifUGYAb33aCyuOy45ymlXAsfDFVU\nYU3A4vKk165qn8ssw8Uy14cVieRITaxXnS3t6N+HShrFxs73c/YCVgSWCoJO\nKneNSP6xiMXs80p+DKOsT4riwDqbz+f9eRFcgq29I4QeZJSkh0HZvhPUtfm/\nuGQ5LsR9YxoZ7skmf6RKGC8oxhz2ilSmFzisr8rI7wAaRve6rsN+PdX9eCth\ndPWPcdPOX9aPUrT6Dp7+vJoKgVdhwZW9vu/C0KkU1nI8LbAC1yDURs71grb0\nH0sNtYgSSvnvpE+kKr5wSv0ET4+/sjsTyfX66Wa6Fu7hwGi29zQnXrfK2U5I\nnebYL8skdJXW3oGx4tzavY5EFbKa+xA7p54o925Fg0jjVOrNlJ+0rm7gj4GV\neEbE4fpi+V8RLHsStmk5Q5YkEEfQw5hKC83/Vo4WncahAF1IQO08/xka/3bG\nqpzcaxX48rxqvuF2z1TrDpuUQoG4HZMirIMpFgfvwOR4sQU0rut4AI9LAv5E\nv8to\r\n=Npne\r\n-----END PGP SIGNATURE-----\r\n","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFjgQ52cjvGmXj7K86fVvWPxzgEA/LVvTyslHTKoRRi1AiBAWpz2+TtZ8x93p6o8fzGcayWn7GuDsFGaJ9jksWHAUQ=="}]},"maintainers":[{"name":"khaost","email":"khaos.tian@gmail.com"},{"name":"nfarina","email":"nfarina@gmail.com"},{"name":"pdlove","email":"pdlovelace@gmail.com"}],"_npmUser":{"name":"khaost","email":"khaos.tian@gmail.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/hap-nodejs_0.5.10_1586461040398_0.7017209003439708"},"_hasShrinkwrap":false},"0.5.11":{"name":"hap-nodejs","version":"0.5.11","description":"HAP-NodeJS is a Node.js implementation of HomeKit Accessory Server.","main":"dist/index.js","types":"dist/index.d.ts","engines":{"node":">=10.17.0"},"dependencies":{"bonjour-hap":"^3.5.1","debug":"^4.1.1","decimal.js":"^10.2.0","fast-srp-hap":"^1.0.1","ip":"^1.1.3","node-persist":"^0.0.11","tweetnacl":"^1.0.3"},"devDependencies":{"@types/debug":"^4.1.5","@types/ip":"^1.1.0","@types/jest":"^25.2.1","@types/node":"^10.17.19","jest":"^25.3.0","rimraf":"^3.0.2","simple-plist":"^1.1.0","ts-jest":"^25.3.1","ts-node":"^8.8.2","typescript":"^3.8.3"},"scripts":{"clean":"rimraf dist/","build":"npm run clean && tsc","prepublishOnly":"npm run build","postpublish":"npm run clean","test":"jest","start":"node dist/BridgedCore.js"},"repository":{"type":"git","url":"git+https://github.com/KhaosT/HAP-NodeJS.git"},"author":{"name":"Khaos Tian","email":"khaos.tian@gmail.com","url":"http://tz.is/"},"license":"Apache-2.0","bugs":{"url":"https://github.com/KhaosT/HAP-NodeJS/issues"},"homepage":"https://github.com/KhaosT/HAP-NodeJS","gitHead":"9e86970e0fcdaf3603ecc40cdf889e2eeb751925","_id":"hap-nodejs@0.5.11","_nodeVersion":"10.20.0","_npmVersion":"6.14.4","dist":{"integrity":"sha512-l6jSuiN3IrTn7wEKg8GrUDoslUJDkP1dhmGpkBTRCLE9bA5V1RlBtVL4Sg9rHlPYbwIwUlq3qXa8gDiVVNCOwA==","shasum":"8b9bd71c889061be238bd84db8e818cefc375684","tarball":"https://registry.npmjs.org/hap-nodejs/-/hap-nodejs-0.5.11.tgz","fileCount":227,"unpackedSize":1648635,"npm-signature":"-----BEGIN PGP SIGNA":"pdlove","email":"pdlovelace@gmail.com"}],"_npmUser":{"name":"khaost","email":"khaos.tian@gmail.com"},"directories":{},"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/hap-nodejs_0.5.11_1586464572717_0.506185436479899"},"_hasShrinkwrap":false},"0.5.12-beta.0":{"name":"hap-nodejs","version":"0.5.12-beta.0","description":"HAP-NodeJS is a Node.js implementation of HomeKit Accessory Server.","main":"dist/index.js","types":"dist/index.d.ts","engines":{"node":">=10.17.0"},"dependencies":{"bonjour-hap":"^3.5.1","debug":"^4.1.1","decimal.js":"^10.2.0","fast-srp-hap":"^1.0.1","ip":"^1.1.3","node-persist":"^0.0.11","tweetnacl":"^1.0.3"},"devDependencies":{"@types/debug":"^4.1.5","@types/ip":"^1.1.0","@types/jest":"^25.2.1","@types/node":"^10.17.19","jest":"^25.3.0","rimraf":"^3.0.2","simple-plist":"^1.1.0","ts-jest":"^25.3.1","ts-node":"^8.8.2","typescript":"^3.8.3"},"scripts":{"clean":"rimraf dist/","build":"npm run clean && tsc","prepublishOnly":"npm run build","postpublish":"npm run clean","test":"jest","start":"node dist/BridgedCore.js"},"repository":{"type":"git","url":"git+https://github.com/KhaosT/HAP-NodeJS.git"},"author":{"name":"Khaos Tian","email":"khaos.tian@gmail.com","url":"http://tz.is/"},"license":"Apache-2.0","bugs":{"url":"https://github.com/KhaosT/HAP-NodeJS/issues"},"homepage":"https://github.com/KhaosT/HAP-NodeJS","readme":"\n\n# HAP-NodeJS\n\n[](safari-reader://192.168.0.35/%22https://www.npmjs.com/package/hap-nodejs\%22)\n[](safari-reader://192.168.0.35/%22https://www.npmjs.com/package/hap-nodejs\%22)\n[](safari-reader://192.168.0.35/%22https://github.com/KhaosT/HAP-NodeJS/actions?query=workflow%3A%22Node-CI%22\%22)\n\n\n\n\n\nHAP-NodeJS is a Node.js implementation of the HomeKit Accessory Server.\n\nWith this project, you should be able to create your own HomeKit Accessory on a Raspberry Pi, Intel Edison, or any other platform that can run Node.js :)\n\nThe implementation may not 100% follow the HAP MFi Specification since the MFi program doesn't allow individual developers to join.\n\nRemember to run `npm install` and `npm install --only=dev` before actually running the server.\n\nUsers can define their own accessories in: accessories/[name]_accessory.ts files, where [name] is a short description of the accessory. All defined accessories get loaded on server start. You can define accessories using an object literal notation (see [Fan_accessory.ts](src/accessories/Fan_accessory.ts) for an example) or you can use the API (see below).\n\nYou can use the following command to start the HAP Server in Bridged mode:\n\n```sh\nts-node --files src/BridgedCore.ts\n```\n\nOr, if you wish to host each Accessory as an independent HomeKit device:\n\n```sh\nts-node --files src/Core.ts\n```\n\nThe HAP-NodeJS library uses the [debug](https://github.com/visionmedia/debug) library for log output. You can print some or all of the logs by setting the `DEBUG` environment variable. For instance, to see all debug logs while running the server:\n\n```sh\nDEBUG=* ts-node --files src/BridgedCore.ts\n```\n\nHOMEKIT PROTOCOL\n================\n\nHint: the Homekit Application Protocol (HAP) allows that you can pair a Homekit device with one device. As soon as the Homekit device is paired, its not possible to pair with another iOS device anAh oui … on voit bien Jeedom …
Essaye en mettant *TONIP*/index.php?v=d&rescue=1
Je le mets ou? Excuse moi car je ne suis pas tres pointu
Si tu accèdes à Jeedom comme ça (par exemple) : http://192.168.1.10, met http://192.168.1.10/index.php?v=d&rescue=1
Peux-tu éditer ton message et mettre le texte entre balises de Texte préformaté pour que ce soit lisible ?
Et également modifier l’étiquette du post car ça ne concerne pas la Community mais plutôt l’utilisation du Core de jeedom.
Cela ne fonctionne pas non, j’arrive sur la meme page
Bon et ta VM a été redémarrée bien sur ?
Tu n’avais pas lancé de mise à jour ? Tu étais en quelle version ?
Ca fait combien de temps que tu avais été Jeedom histoire de voir depuis combien de temps potentiellement ton dernier backup serait pertinent. Dans ce cas il faut aller récupérer les backups via une connexion SFTP (avec winscp par exemple)
J’ai redémarré la vm oui mais tjs la meme chose…
J’utilise jeedom uniquement pour commander mes volets roulants (5) via l’appli maison apple.
Jai fais effectivement une maj ce matin et depuis voila le resultat… je faisais des maj on va dire tous les 2 mois des pluggins jeedom.
Peux tu m’expliquer la marche a suivre car je ne suis pas tres calé informatique, je n’ai pas envi de tout supprimer pour reparametrer tous mes volets… je dois surement avoir une sauvegarde qq part? La je n’ai plus du tout acces a jeedom via l’adresse…
Ça ressemble à Homebridge , peut être celui intégré à la freebox car ce texte vient du plugin homebridge-http-advanced-accessory. A moins que vous l’ayez installé sur le plugin Homebridge de jeedom c’est bien celui de la freebox.
Oui je l’avais installé dans jeedom pour gerer mes volets somfy via la freebox et mon univers apple
Avez vous une solution pour moi car tjs bloqué
Non mais donc ça ne semble pas être un problème jeedom, plus un problème freebox, ou de fixation d’adresse ip… si vous tombez sur Homebridge plutôt que jeedom c’est la configuration de la freebox
1 « J'aime »
C’est ce que j’ai pensé au départ mais on voit bien # Jeedom au départ dans sa page, c’est suspect non ?
Et puis si c’est suite à une MAJ et qu’il a le plugin Homebridge installé sur Jeedom il y a quand même plus de chance que ce soit bien à son Jeedom qu’il accède, non ?
@nicolars6, télécharge winscp Downloading WinSCP-6.3.3-Setup.exe :: WinSCP, installe le puis tente d’accéder à Jeedom en saisissant l’adresse IP (depuis ton réseau interne bien sûr)
Il faudra utiliser le compte et le mot de passe que tu as saisie en principe sur cet écran au moment de l’installation de Jeedom sur la Freebox :
Est-ce que tu y accèdes et qu’est-ce que tu vois ?
le code vient d’un plugin pour homebridge (dans le readme)… et il n’a pas dit s’il l’a installé ou pas. mais fort probable que freebox l’utilise pour configurer ses propres équipements.
son # Jeedom c’est un mauvais copier coller
Ok @nebz 
Bon ben @nicolars6 retour à la case départ.
Tu peux montrer des captures de ta VM Jeedom et quand tu es sur ta Freebox afin que l’on voit l’adresse IP et nous montrer une vraie capture de ton navigateur quand tu veux accéder à Jeedom ?
