J’ai cassé homebridge ☹️

Hello,

J’ai un problème avec homebridge. Tout fonctionnait bien depuis des mois, et j’ai fait la connerie de monter une deuxième VM en récupérant le backup de mon Jeedom principal … Résultat, homebridge est parti en vrille …

Pour soigner, j’ai :

  • supprimer la maison dans Home
  • tenté une réparation puis réparation et réinstallation de homebridge

Côté homebridge, tout va bien, le démon est vert et tout semble fonctionner correctement, mais côté Home, impossible d’ajouter le pont HB. Au début je réussissais à l’ajouter mais tous les équipements indiquaient « pas de réponse », et maintenant il ne veut même plus installer le pont et le dit que la configuration doit être faite dans l’app du fabricant …

Je joins le log HB en cas

[11/6/2019, 7:14:37 PM] Loaded config.json with 0 accessories and 6 platforms.
[11/6/2019, 7:14:37 PM] ---
[11/6/2019, 7:14:37 PM] Loaded plugin: homebridge-alexa
[11/6/2019, 7:14:37 PM] Registering platform 'homebridge-alexa.Alexa'
[11/6/2019, 7:14:37 PM] ---
[11/6/2019, 7:14:37 PM] Loaded plugin: homebridge-camera-ffmpeg
[11/6/2019, 7:14:37 PM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[11/6/2019, 7:14:37 PM] ---
[11/6/2019, 7:14:37 PM] Loaded plugin: homebridge-jeedom
[11/6/2019, 7:14:37 PM] Registering platform 'homebridge-jeedom.Jeedom'
[11/6/2019, 7:14:37 PM] ---
[11/6/2019, 7:14:37 PM] Loading 6 platforms...
[11/6/2019, 7:14:37 PM] [Jeedom Master6] Initializing Jeedom platform...
[11/6/2019, 7:14:37 PM] [Jeedom Master6] debugLevel:100
[11/6/2019, 7:14:37 PM] [Jeedom Master6] [INFO] Adresse Jeedom bien configurée :http://192.168.0.25:80
[11/6/2019, 7:14:37 PM] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
[11/6/2019, 7:14:37 PM] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
[11/6/2019, 7:14:37 PM] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
[11/6/2019, 7:14:37 PM] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
[11/6/2019, 7:14:37 PM] [Camera-ffmpeg] Initializing Camera-ffmpeg platform...
Setup Payload:
X-HM://0023ISYX0514E
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-156 │
└────────────┘
[11/6/2019, 7:14:37 PM] [Jeedom Master6] Synchronisation Jeedom <> Homebridge...
Wed, 06 Nov 2019 18:14:37 GMT EventedHTTPServer Server listening on port 51826
[11/6/2019, 7:14:37 PM] Homebridge is running on port 51826.
Wed, 06 Nov 2019 18:14:37 GMT EventedHTTPServer Server listening on port 46499
[11/6/2019, 7:14:37 PM] Caméra portail is running on port 46499.
[11/6/2019, 7:14:37 PM] Please add [Caméra portail] manually in Home app. Setup Code: 031-45-156
Wed, 06 Nov 2019 18:14:37 GMT EventedHTTPServer Server listening on port 46871
[11/6/2019, 7:14:37 PM] Caméra terrasse is running on port 46871.
[11/6/2019, 7:14:37 PM] Please add [Caméra terrasse] manually in Home app. Setup Code: 031-45-156
Wed, 06 Nov 2019 18:14:37 GMT EventedHTTPServer Server listening on port 45743
[11/6/2019, 7:14:37 PM] Caméra salon is running on port 45743.
[11/6/2019, 7:14:37 PM] Please add [Caméra salon] manually in Home app. Setup Code: 031-45-156
Wed, 06 Nov 2019 18:14:37 GMT EventedHTTPServer Server listening on port 38719
[11/6/2019, 7:14:37 PM] Caméra garage is running on port 38719.
[11/6/2019, 7:14:37 PM] Please add [Caméra garage] manually in Home app. Setup Code: 031-45-156
Wed, 06 Nov 2019 18:14:37 GMT EventedHTTPServer Server listening on port 34963
[11/6/2019, 7:14:37 PM] Caméra cabanon is running on port 34963.
[11/6/2019, 7:14:37 PM] Please add [Caméra cabanon] manually in Home app. Setup Code: 031-45-156
[11/6/2019, 7:14:38 PM] [Jeedom Master6] [ERROR] #2 Erreur de récupération des données Jeedom:  null
Wed, 06 Nov 2019 18:15:02 GMT EventedHTTPServer [::ffff:192.168.0.14] New connection from client
Wed, 06 Nov 2019 18:15:02 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP server listening on port 37927
Wed, 06 Nov 2019 18:15:02 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pair-setup
Wed, 06 Nov 2019 18:15:02 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-setup
Wed, 06 Nov 2019 18:15:02 GMT HAPServer [14:C0:89:B8:51:4E] Pair step 1/5
Wed, 06 Nov 2019 18:15:03 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:04 GMT EventedHTTPServer [::ffff:192.168.0.14] Client connection closed
Wed, 06 Nov 2019 18:15:04 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP connection was closed
Wed, 06 Nov 2019 18:15:04 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP server was closed
Wed, 06 Nov 2019 18:15:11 GMT EventedHTTPServer [::ffff:192.168.0.14] New connection from client
Wed, 06 Nov 2019 18:15:11 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP server listening on port 39681
Wed, 06 Nov 2019 18:15:11 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pair-setup
Wed, 06 Nov 2019 18:15:11 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-setup
Wed, 06 Nov 2019 18:15:11 GMT HAPServer [14:C0:89:B8:51:4E] Pair step 1/5
Wed, 06 Nov 2019 18:15:11 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pair-setup
Wed, 06 Nov 2019 18:15:16 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-setup
Wed, 06 Nov 2019 18:15:16 GMT HAPServer [14:C0:89:B8:51:4E] Pair step 2/5
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pair-setup
Wed, 06 Nov 2019 18:15:16 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-setup
Wed, 06 Nov 2019 18:15:16 GMT HAPServer [14:C0:89:B8:51:4E] Pair step 3/5
Wed, 06 Nov 2019 18:15:16 GMT HAPServer [14:C0:89:B8:51:4E] Pair step 4/5
Wed, 06 Nov 2019 18:15:16 GMT HAPServer [14:C0:89:B8:51:4E] Pair step 5/5
Wed, 06 Nov 2019 18:15:16 GMT Accessory [Jeedom Master6] Paired with client 45FC35AE-4C40-4FDE-ABA8-440042173B83
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] Client connection closed
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP connection was closed
Wed, 06 Nov 2019 18:15:16 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP server was closed
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] New connection from client
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP server listening on port 44333
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pair-verify
Wed, 06 Nov 2019 18:15:17 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-verify
Wed, 06 Nov 2019 18:15:17 GMT HAPServer [14:C0:89:B8:51:4E] Pair verify step 1/2
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pair-verify
Wed, 06 Nov 2019 18:15:17 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-verify
Wed, 06 Nov 2019 18:15:17 GMT HAPServer [14:C0:89:B8:51:4E] Pair verify step 2/2
Wed, 06 Nov 2019 18:15:17 GMT HAPServer [14:C0:89:B8:51:4E] Client 45FC35AE-4C40-4FDE-ABA8-440042173B83 verification complete
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /accessories
Wed, 06 Nov 2019 18:15:17 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: GET /accessories
Wed, 06 Nov 2019 18:15:17 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] New connection from client
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP server listening on port 44017
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP request: /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] Pair verify step 1/2
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP request: /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] Pair verify step 2/2
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] Client 45FC35AE-4C40-4FDE-ABA8-440042173B83 verification complete
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP request: /accessories
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: GET /accessories
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] New connection from client
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP server listening on port 39947
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP request: /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] Pair verify step 1/2
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP request: /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pair-verify
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] Pair verify step 2/2
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] Client 45FC35AE-4C40-4FDE-ABA8-440042173B83 verification complete
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP request: /accessories
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: GET /accessories
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP Response is finished
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /characteristics
Wed, 06 Nov 2019 18:15:19 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: PUT /characteristics
Wed, 06 Nov 2019 18:15:19 GMT Accessory [Jeedom Master6] Processing characteristic set: [{"aid":1,"iid":2,"value":true}]
Wed, 06 Nov 2019 18:15:19 GMT Accessory [Jeedom Master6] Setting Characteristic "Identify" to value true
Wed, 06 Nov 2019 18:15:19 GMT Accessory [Jeedom Master6] Identification request
Wed, 06 Nov 2019 18:15:19 GMT Accessory [Jeedom Master6] Identification request ignored; no listeners to 'identify' event
Wed, 06 Nov 2019 18:15:19 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:39 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP request: /pairings
Wed, 06 Nov 2019 18:15:39 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pairings
Wed, 06 Nov 2019 18:15:39 GMT HAPServer [14:C0:89:B8:51:4E] Removing pairing info for client
Wed, 06 Nov 2019 18:15:39 GMT Accessory [Jeedom Master6] Unpairing with client 45FC35AE-4C40-4FDE-ABA8-440042173B83
Wed, 06 Nov 2019 18:15:39 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP Response is finished
Wed, 06 Nov 2019 18:15:40 GMT EventedHTTPServer [::ffff:192.168.0.14] Client connection closed
Wed, 06 Nov 2019 18:15:40 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP connection was closed
Wed, 06 Nov 2019 18:15:40 GMT EventedHTTPServer [::ffff:192.168.0.14] HTTP server was closed
Wed, 06 Nov 2019 18:15:42 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP request: /pairings
Wed, 06 Nov 2019 18:15:42 GMT HAPServer [14:C0:89:B8:51:4E] HAP Request: POST /pairings
Wed, 06 Nov 2019 18:15:42 GMT HAPServer [14:C0:89:B8:51:4E] Removing pairing info for client
Wed, 06 Nov 2019 18:15:42 GMT Accessory [Jeedom Master6] Unpairing with client 45FC35AE-4C40-4FDE-ABA8-440042173B83
Wed, 06 Nov 2019 18:15:42 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP Response is finished
Wed, 06 Nov 2019 18:15:42 GMT EventedHTTPServer [::ffff:192.168.0.10] Client connection closed
Wed, 06 Nov 2019 18:15:42 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP connection was closed
Wed, 06 Nov 2019 18:15:42 GMT EventedHTTPServer [::ffff:192.168.0.10] HTTP server was closed
Wed, 06 Nov 2019 18:15:45 GMT EventedHTTPServer [::ffff:192.168.0.16] Client connection closed
Wed, 06 Nov 2019 18:15:45 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP connection was closed
Wed, 06 Nov 2019 18:15:45 GMT EventedHTTPServer [::ffff:192.168.0.16] HTTP server was closed

hello,

en effet, ton ip jeedom et port sont bien : http://192.168.0.25:80 ?

si c’est le cas, vérifie que tu as bien ouvert les api jsonrpc dans la config de jeedom.

le démon ne parvient pas à discuter avec l’api de jeedom.

Salut nebz,

Merci du support.

Oui l’IP et port sont bons, et l’accès à API JSONRPC est bien sur « Activé ».

malgré ca il n’y arrive pas…

[ERROR] #2 Erreur de récupération des données Jeedom:  null

peut-etre que ta clé api a changé (celle de l’utilisateur Admin), si c’est le cas, redémarre le démon.

sinon envoi moi le DebugInfo (voir doc)

J’ai redémarré le démon à de multiple reprises.

Pour DebugInfo, j’ai l’erreur suivante lorsque je clique

Call to a member function getDisplay() on boolean 

Alors je vois pas… le démon ne parviens pas à communiquer avec ton jeedom c’est tout ce que je remarque

Je pencherais pour un périphérique qui à un problème!..

Ça marchait nickel jusqu’à ce que je lance cette deuxième VM.
Je viens de supprimer le plugin et de repartir de zéro, c’est pas mieux.

Si je te donne un accès, tu sais pas regarder ce qui cloche ?

J’ai eu ce genre de problème une fois, j’ai réussi à remettre en fonction après suppression de homebridge et réinstallation de la dernière sauvegarde fonctionnelle.
Mais je n’avais rien supprimé dans maison .

Oui je peux, si cette solution ne fonctionne pas mais ça sera plus tard ce soir

Honnêtement, je n’y tiens pas.
J’ai ce problème depuis le we dernier, et en parallèle j’ai refais tout mon réseau z-wave, qui est maintenant nickel. Si je réinstalle une sauvegarde d’avant le we, je vais tomber sur une configuration bancale avec des modules inclus dans la clé et pas dans Jeedom, etc …

Nebz, je t’envoie les infos par MP, y’a pas le feu, regarde ça quand tu peux.
Merci.

tu as un problème dans certains périphériques :

object_id = -1 c’est pas normal

@Loic

dans quel cas un object_id peut-il être -1 ? si c’est aucun c’est vide normalement…

évidemment ca pose problème à jeeObject::byId() qui n’est pas fait pour :

Aucun peut soit etre vide soit etre égale à -1

ok, tu pourrais mettre à jour byId pour refléter ce fait ?

(en stable, v3 aussi btw)

Et pour info ces équipements sont un reliquat du plugin IPX800 que j’ai viré… je pensais les avoir dégagés en passant par Résumé Domotique, mais il y en a visiblement d’autres et ceux-la n’apparaissent pas dans Résumé Domotique …

Voir https://community.jeedom.com/t/suppression-d-equipements-dans-bdd/5328/6

@Loic

ah, en plus de jeeObject::byId, pourrais-tu aussi mettre à jour le Résumé Domotique pour refléter ce fait ?

C’est fait partout ca sera donc dans la prochaine stable, pour résumé domotique j’ai pas compris la demande

tu ne prends que les null aussi et pas les -1 pour la catégorie « Aucun »

mais ton premier fix va peut-etre corriger ca aussi…