ha-bridge 🚀 - Release Candidate pour les tests 5.2.0 | bleepcoder.com (2024)

OK - voici quelques entrées de journal:

01-03-2018 23: 54: 00.782 | DEBUG | Obtenez des appareils FHEM | com.bwssystems.HABridge.devicemanagmeent.DeviceResource
- | - | - | -
01-03-2018 23: 54: 00.782 | DEBUG | appareils de consolidation pour FHEM | com.bwssystems.HABridge.plugins.fhem.FHEMHome
01-03-2018 23: 54: 00.783 | DEBUG | doHttpRequest avec l'url: http://192.168.178.26 : 8083 / fhem? cmd = jsonlist2% 20room = HaBridge avec la commande http: GET avec le corps: null | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-03-2018 23: 54: 00.784 | DEBUG | Faire un appel sortant dans doHttpRequest: <<>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-03-2018 23: 54: 00.848 | DEBUG | GET execute (0) sur l'URL a répondu: 200

01-03-2018 23: 54: 00.850 | DEBUG | Réponse réussie - La réponse http est <<<

{"Arg": "room = HaBridge", "Results": [{"Name": " wifi_steckdose3 ", "PossibleSets": "on: noArg off: noArg off on toggle", "PossibleAttrs": "alias comment: textField -Long chambre groupe eventmap suppressReading utilisation rReadings: textField long verbeux: 0 , 1,2,3,4,5 QOS IODev conservent publishSet publishSet _ * _ * subscribeReading autoSubscribeReadings événement sur le changement de lecture événement sur la mise à jour de lecture.. événement min-intervalle st-aggrégateur événement ateFormat: textField long horodatage sur changement de lecture al armDevice: Acteur , Capteur alarmSettings cmdIcon devStateIcon devStateStyle icône lightSceneParamsToSave lightSceneRestoreOnly IfChanged: 1 , 0 sortby structexclude webCmd nous bCmdLabel: textField long userattr widgetOverride "," Internals ": {" CHANGED ":" null "," NAME ":" wifi_steckdose3 "," NR ":" 270 "," STATE ":" off "," TYPE ":" MQTT_DEVICE "," retenir " : " : 1"}, "Readings": {"state": {"Value": "OFF", "Time": "2018-01-01 23:01:21"}, "transmission-state": { "Valeur": "abonnement reconnu", "Heure": "2018-01-03 22:34:00"}},

>>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
- | - | - | -
01-03-2018 23: 54: 00.851 | DEBUG | GET FHEM States - data: html PUBLIC "- // W3C // DTD XHTML 1.0 Strict // EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"

subscribeReading _. * autoSubscribeReadings event-on-change-reading event-on-update-reading event-aggregator event-min-interval st ateFormat: textField-long timestamp-on-change-reading al armDevice: Actor , Sensor alarmSettings cmdIcon devStateIcon icône devStateStyle lightSceneParamsToSave lightSceneRestoreOnly IfChanged: 1 , 0 sortby structexclude webCmd we bCmdLabel: textField-long widgetOverride userattr "," Internals ": {" CHANGED ":" null "," NAME ":" wifi_steckdose3 "," NR ":" myBroker ", "alias": "Stecki", "devStateIcon": "on: black_Steckdose.on off: black_Steckdose.off", "event-on-change-reading": "state", " eventMap ":" ON: on OFF: off "," publishSet ":" on off bascule / SmartHome / az / stecker / cmnd / POWER "," retient ":" 1 "," room ":" HaBridge, Arbeitsz immer, mqtt "," stateFormat ":" state "," subscribeReading_state ":" / SmartHome / az / stecker / stat / POWER "," webCmd ":" on: off: toggle "}}]," totalResultsReturned ": 1 } | com.bwssystems.HABridge.plugins.fhem.FHEMInstance
01-03-2018 23: 54: 03.984 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 1; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool
01-03-2018 23: 54: 08.985 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 1; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool

01-03-2018 23: 54: 10.147 | DEBUG | Obtenez logmsgs. | com.bwssystems.HABridge.SystemControl
01-03-2018 23: 54: 13.986 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 1; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool
01-03-2018 23: 54: 18.987 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 1; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool
01-03-2018 23: 54: 23.317 | DEBUG | Obtenez logmsgs. | com.bwssystems.HABridge.SystemControl
01-03-2018 23: 54: 23.989 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 1; max: 200]

Comme décrit ci-dessus - je n'ai défini que la pièce "HaBridge". J'ai eu une entrée dans l'appareil Fhem mais il n'était pas possible pour moi de générer un appareil Habridge à partir de cette liste très simple (nom de l'appareil manquant sur cette liste et autres choses ...)

Bien sûr, envoyez le fichier à [emailprotected].

Salut,

ha-bridge ne trouve aucune scène fournie par mon fibaro hc2.

lorsque "On with First Dim" est faux
et de l' état de l' appareil éteint ou allumé
et commande de luminosité envoyée depuis l'harmonie:
habridge semble envoyer sur (domoticz), dim (passthru), puis sur (domoticz) à nouveau. Un seul journal pour off / on, car identique.

01-09-2018 17: 03: 47.580 | DEBUG | HueMulator PUT appelé sur api / * avec la requête << >>, et le corps <<< {"xy": [0,0], "on": true, "bri": 204} >>> | com.bwssystems.HABridge.hue.HueMulator
- | - | - | -
01-09-2018 17: 03: 47.584 | DEBUG | changement d'état de teinte demandé: 8d93f0339d524fd28d1f13f44a2eeba3 à partir de 192.168.2.10 corps: {"xy": [0,0], "on": true, "bri": 204} | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.586 | DEBUG | Décodez Json pour les éléments d'url: [{"item": " http://192.168.2.240 : 9000 / json.htm? Type = command & param = switchlight & idx = 143 & switchcmd = On", "type": "domoticzDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.589 | DEBUG | Appelant le gestionnaire d'appareil domestique pour le type: domoticzDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.738 | DEBUG | Décodez Json pour les éléments d'URL: [{"item": "{\" ipAddress \ ": \" 192.168.2.230 \ ", \" deviceId \ ": \" 7 \ ", \" hueName \ ": \" Philips Hue \ "}", "type": "hueDevice"}, {"item": "{\" ipAddress \ ": \" 192.168.2.230 \ ", \" deviceId \ ": \" 8 \ ", \" hueName \ ": \" Philips Hue \ "}", "type": "hueDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.741 | DEBUG | Appel du gestionnaire d'appareil domestique pour type: hueDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.854 | DEBUG | Appel du gestionnaire d'appareil domestique pour le type: hueDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.991 | DEBUG | Décodez Json pour les éléments d'url: [{"item": " http://192.168.2.240 : 9000 / json.htm? Type = command & param = switchlight & idx = 143 & switchcmd = On", "type": "domoticzDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 47.994 | DEBUG | Appelant le gestionnaire d'appareil domestique pour le type: domoticzDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 03: 48.043 | DEBUG | La réponse est en erreur: null

testera des scénarios supplémentaires et ajoutera à un message distinct.

lorsque "On with First Dim" est vrai
et de l' état de l' appareil est hors tension ou sur
et commande de luminosité envoyée depuis l'harmonie:
habridge semble envoyer "on" 3 fois. Un seul journal pour off / on, car identique.

01-09-2018 17: 13: 13.389 | DEBUG | HueMulator PUT appelé sur api / * avec la requête << >>, et le corps <<< {"xy": [0,0], "on": true, "bri": 204} >>> | com.bwssystems.HABridge.hue.HueMulator
- | - | - | -
01-09-2018 17: 13: 13.390 | DEBUG | changement d'état de teinte demandé: 8d93f0339d524fd28d1f13f44a2eeba3 à partir de 192.168.2.10 corps: {"xy": [0,0], "on": true, "bri": 204} | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.391 | DEBUG | Décodez Json pour les éléments d'url: [{"item": " http://192.168.2.240 : 9000 / json.htm? Type = command & param = switchlight & idx = 143 & switchcmd = On", "type": "domoticzDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.392 | DEBUG | Appelant le gestionnaire d'appareil domestique pour le type: domoticzDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.393 | DEBUG | doHttpRequest avec url: http://192.168.2.240 : 9000 / json.htm? type = command & param = switchlight & idx = 143 & switchcmd = On avec http commande: null avec corps: null | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.393 | DEBUG | Faire un appel sortant dans doHttpRequest: <<>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.432 | DEBUG | GET execute (0) sur l'URL a répondu: 200 | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.433 | DEBUG | Réponse réussie - La réponse http est <<< {"status": "OK", "title": "SwitchLight"} >>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.536 | DEBUG | Décodez Json pour les éléments d'url: [{"item": " http://192.168.2.240 : 9000 / json.htm? Type = command & param = switchlight & idx = 143 & switchcmd = On", "type": "domoticzDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.537 | DEBUG | Appelant le gestionnaire d'appareil domestique pour le type: domoticzDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.538 | DEBUG | doHttpRequest avec url: http://192.168.2.240 : 9000 / json.htm? type = command & param = switchlight & idx = 143 & switchcmd = On avec http commande: null avec corps: null | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.538 | DEBUG | Faire un appel sortant dans doHttpRequest: <<>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.579 | DEBUG | GET execute (0) sur l'URL a répondu: 200 | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.581 | DEBUG | Réponse réussie - La réponse http est <<< {"status": "OK", "title": "SwitchLight"} >>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.684 | DEBUG | Décodez Json pour les éléments d'url: [{"item": " http://192.168.2.240 : 9000 / json.htm? Type = command & param = switchlight & idx = 143 & switchcmd = On", "type": "domoticzDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.684 | DEBUG | Appelant le gestionnaire d'appareil domestique pour le type: domoticzDevice | com.bwssystems.HABridge.hue.HueMulator
01-09-2018 17: 13: 13.685 | DEBUG | doHttpRequest avec url: http://192.168.2.240 : 9000 / json.htm? type = command & param = switchlight & idx = 143 & switchcmd = On avec http commande: null avec corps: null | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.686 | DEBUG | Faire un appel sortant dans doHttpRequest: <<>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.731 | DEBUG | GET execute (0) sur l'URL a répondu: 200 | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.734 | DEBUG | Réponse réussie - La réponse http est <<< {"status": "OK", "title": "SwitchLight"} >>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-09-2018 17: 13: 13.741 | DEBUG | La réponse est erronée: null | com.bwssystems.HABridge.hue.HueMulator

Oh? Eh bien, un symptôme que j'ai avec 3 commandes envoyées est que la commande domoticz envoyée exécute en fait un script. Ainsi, avec 3 commandes identiques envoyées, le script est cyclé 3 fois.

Idée:
Si "On with first dim" est sélectionné et que Harmony envoie une commande avec xy, on et bri, alors elle sera simplement traitée comme une seule commande "on". Après cela, les commandes devraient être décomposées. Ainsi, lorsque le prochain xy, on et bri est envoyé, habridge sait que l'état de ce périphérique est déjà `` on '', ce qui peut être ignoré, si `` xy '' vaut 0,0, cela peut être ignoré, le `` bri '' pourrait être comparé au précédent 'bri' et s'il est différent , alors traiter comme "dim" (car on peut supposer que l'interrupteur à bascule haut / bas est enfoncé sur la télécommande d'harmonie ou dans l'application) et si le processus est

Pensées?

@gohamstergo Cela a du sens lorsque cette sélection est faite. Mettra à jour.

@xPRozAcx Comme dans ma demande précédente, j'ai besoin que vous activiez DBUG pour plusieurs choses. La capture d'écran m'en dit très peu. Règles de test: J'ai besoin que DEBUG soit activé pour votre système particulier com.bwssystems.HABridge.plugins. (fibaro, FHEM, etc.) et com.bwssystems.HABridge.plugins.http afin que vous puissiez publier votre sortie de journal de ligne de commande.

C'est un plaisir pour moi de lire que vous intégrez le support FHEM, puisque tous les autres outils de domeautomation "célèbres" sont déjà à bord. En fait, je n'ai pas trouvé de Wiki ou quelque chose pour tester RC3 par rapport à mon installation FHEM. Comment peut-il être intégré? Comment interagit-il avec FHEM? Et qu'est-ce qui sera possible?

BR
Stefan

@bwssytems :)

Je vous remercie

Nouvelle version candidate 5.2.0RC4, téléchargez à partir du lien en haut de l'article.

Correction de problèmes de test RC pour:
Décodage de périphérique FHEM
allumé pour la première dim
Port OpoenHab par défaut
Amélioration du débogage des requêtes Fibaro

je pense que nous nous rapprochons! ainsi, quand l'état est activé et qu'un nouveau niveau bri est appelé, habridge le détecte correctement, mais s'exécute toujours "on" qui est la commande domoticz. Voici le journal et en bas est une capture d'écran de mon on / dim / off juste pour plus de clarté.

01-12-2018 16: 36: 28.884 | DEBUG | HueMulator PUT a appelé api / * avec la requête << >>, et le corps <<< {"xy": [0,0], "on": true, "bri": 229} >>> | com.bwssystems.HABridge.hue.HueMulator
- | - | - | -
01-12-2018 16: 36: 28.885 | DEBUG | changement d'état de teinte demandé: 8d93f0339d524fd28d1f13f44a2eeba3 à partir de 192.168.2.10 corps: {"xy": [0,0], "on": true, "bri": 229} | com.bwssystems.HABridge.hue.HueMulator
01-12-2018 16: 36: 28.886 | DEBUG | Appel dim comme demandé. | com.bwssystems.HABridge.hue.HueMulator
01-12-2018 16: 36: 28.887 | DEBUG | Décodez Json pour les éléments d'url: [{"item": " http://192.168.2.240 : 9000 / json.htm? Type = command & param = switchlight & idx = 143 & switchcmd = On", "type": "domoticzDevice"}] | com.bwssystems.HABridge.hue.HueMulator
01-12-2018 16: 36: 28.888 | DEBUG | Appelant le gestionnaire d'appareil domestique pour le type: domoticzDevice | com.bwssystems.HABridge.hue.HueMulator
01-12-2018 16: 36: 28.889 | DEBUG | doHttpRequest avec url: http://192.168.2.240 : 9000 / json.htm? type = command & param = switchlight & idx = 143 & switchcmd = On avec http commande: null avec corps: null | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-12-2018 16: 36: 28.889 | DEBUG | Faire un appel sortant dans doHttpRequest: <<>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-12-2018 16: 36: 28.944 | DEBUG | GET execute (0) sur l'URL a répondu: 200 | com.bwssystems.HABridge.plugins.http.HTTPHandler
01-12-2018 16: 36: 28.946 | DEBUG | Réponse réussie - La réponse http est <<< {"status": "OK", "title": "SwitchLight"} >>> | com.bwssystems.HABridge.plugins.http.HTTPHandler

Après avoir installé RC4 et mis com.bwssystems.HABridge.plugins.fibaro et com.bwssystems.HABridge.plugins.fibaro.http au niveau DEBUG, j'obtiens les mêmes mauvaises informations pour vous.
Mais quand j'ai défini com.bwssystems.HABridge.plugins.fibaro.FibaroInfo sur DEBUG, il semble qu'il ait lu mes scènes mais elles n'apparaîtront pas @ scènes fibaro et je reçois à nouveau l'erreur 500.
Je dois diviser les captures d'écran car il y a trop de choses à l'écran :)

@xPRozAcx il suffit de copier / coller comme je le suis. il devrait enregistrer le formatage.

edit: comme recommandé ci-dessous, affichera la sortie du terminal dans le fichier la prochaine fois :)

Je préférerais que vous preniez la sortie de la ligne de commande et que vous la publiez sous forme de lien de fichier. Ce serait le meilleur.

@xPRozAcx si vous pouviez également publier votre fichier ha-bridge.conf

Le deuxième écran sont les scènes de fibaro qui sont accessibles par l'utilisateur habridge

Existe-t-il déjà un moyen de contourner le délai d'attente de ~ 5 secondes sur Alexa? Je voudrais donc envoyer plusieurs commandes avec des délais d'attente, ce qui fonctionne, mais Alexa renvoie toujours un "périphérique ne répond pas".

btw. super logiciel, merci :)

Quelques problèmes

Avec la version 5.2, j'ai eu des problèmes pour conserver l'état réel des lumières dans Harmony. Après quelques secondes après avoir allumé une lumière, elle est revenue à "off" sur la télécommande. -La lumière est toujours allumée.
-Configuré qu'Harmony avait des problèmes pour lire les "éléments de couleur", que je n'ai pas / n'utilise pas. -En définissant l'élément de couleur sur un message MQTT factice (rubrique «ignorer», valeur «ignorer»), la télécommande est capable de conserver l'état.

Serait-il possible d'ignorer les éléments de couleur lorsqu'ils ne sont pas configurés? -Et même pouvoir supprimer correctement les éléments configurés?

Le deuxième problème est lié à bridgeupdatestate.
Lorsque vous envoyez à la fois "on" et "bri", alors seul "bri" change. La réponse de PUT indique ok pour les deux, mais "on" n'est pas mis à jour. -Si j'envoie "on" seulement, alors il est mis à jour.

Mise à jour: On a observé que le réglage du "bri" mettra toujours "on" sur true. -Est-ce par conception? -Si oui, je suppose que mon défi avec le réglage des deux est résolu .. -Le défi avec mes lumières est que la luminosité 0 signifie que la lumière est éteinte (KNX avec LogicMachine comme contrepartie ici)

@xPRozAcx J'ai toujours besoin de vos journaux de ligne de commande (pas des copies d'écran) pour b être publiés. De plus, je ne suis pas sûr de ce que vous entendez par utilisateur du pont ha.

@ sneaker8650 Il n'y a pas d'API pour modifier le délai d'expiration de la commande Alexa. Le habridge terminera toujours la commande donc c'est plus un ennui.

@ spiff972 Jettera un œil à vos problèmes. Il y a une nouvelle fonctionnalité dans la version 5.2.0 qui configurera un appareil pour qu'il ne s'allume qu'à certains moments sans envoyer de gradation ou de couleur. De plus, cela devrait être bon si l'url de la couleur est vide, elle ne doit pas être envoyée.

@gohamstergo Je pense que la logique est de faire ce que vous avez demandé. Seule la demande dim a été envoyée dans votre demande et aucune URL sur a été envoyée.

Edit: Qu'à cela ne tienne, j'ai trouvé l'erreur logique .... une vérification stupide pour onFirstDim a été laissée.

Merci pour vos commentaires. J'ai réussi à "contourner" le problème dans mon script dans LM, en gros, envoyer "on": false quand nécessaire, et utiliser "bri" autrement. Mes lumières s'allumeront lorsque la luminosité est> 0.
Cela fonctionne pleinement maintenant, le seul problème est la couleur (et peut-être faible ??) là où je n'en ai pas besoin.

Je suis nouveau dans votre outil ... Mais j'aimerais vraiment que le hub Harmony reconnaisse chaque lumière comme ce qu'elle est configuré (par exemple, si la luminosité et la couleur ne sont pas configurées, alors n'autorisez que l'activation / la désactivation). Je ne sais pas si cela appartient à Logitech, si c'est le cas, je vais bien, mais s'il existe différents types de HUE qui pourraient être utilisés, je préférerais que ha-bridge se réfère en conséquence.

Une observation. -Est-il possible de déplacer les activités / périphériques Harmony hors de la liste des lumières? Je ne vois pas l'intérêt de ma Harmony de les prendre. (sous les lumières, j'obtiens un mélange de lumières et d'éléments d'harmonie, sur mon harmonie ..) -Comment les déplacer vers une section séparée de l'API REST? Par exemple / api / noname / harmonie // état, ou quelque chose comme ça?

ok - démarrer avec la vérification de l'appareil Fhem. - tout d'abord, j'ai supprimé tous les anciens appareils créés avec RC3

1. défini un nouveau serveur Fhem avec une pièce où se trouvent 2 appareils (wifi_steckdose, steckdose3)

1. Problème - dans Habridge TAB «Fhem device» - les deux appareils sont affichés, mais lorsque je pousse le bouton «build item» dans la première ligne, le nom de l'appareil dans la ligne suivante est affiché / sélectionné
2. Problème - après avoir construit un nouvel appareil - l'appareil n'a pas été affiché dans la liste «Appareils Fhem déjà configurés»
3. Problème - si j'ai testé le périphérique fhem avec (Test ON / OFF), les deux URL ne fonctionnent pas.
   {"url": " http://192.168.178.26 : 8083 / fhem? cmd = set% 20steckdose3% 20", "command": "on"}
   {"url": " http://192.168.178.26 : 8083 / fhem? cmd = set% 20steckdose3% 20", "command": "off"}
   Voici la syntaxe correcte:
   http://192.168.178.26 : 8083 / fhem? cmd = set% 20steckdose3% 20off
   Si vous avez besoin de plus d'informations ou d'un journal de débogage, dites-moi.

@bwssytems J'ai besoin de contrôler les choses sur le hub Harmony. -Je veux utiliser ha-bridge comme "intermédiaire" entre LogicMachine (LM) / KNX et Harmony hub, et j'ai besoin d'une communication bidirectionnelle. -Par exemple, je veux ajouter «regarder la télévision», «jeux PS4» et «PowerOff» au pont, afin que je puisse intégrer cela dans ma visualisation LM. -Ou même ajouter "PowerOff" à mes scènes "Leaving home" et "Goodnight" (activées par les boutons poussoirs KNX, qui déclenchent un script pour parler à ha-bridge).

Je vois que vous avez une harmonie reposante qui pourrait faire le travail, mais il serait préférable de la combiner en ha-bridge. -Je comprends que ce n'est pas la version dans laquelle l'inclure, mais si je pouvais créer des dispositifs / activités d'harmonie comme "harmonie" au lieu de "lumières", ou au moins avoir un filtre pour restreindre ce que le hub peut voir, ce serait génial .

@bwssytems

Donc, pour les lumières, nous renvoyons un type qui est une lumière de couleur afin que dans tous les cas, tout le contrôle soit disponible.

Ce n'est en fait pas entièrement vrai. Dans le cas de vraies ampoules Hue passthru, nous retournons le type de lumière réel, cela signifie "Lumière de couleur étendue", "Lumière à intensité variable" ou "Unité enfichable marche / arrêt".
Si ce n'est pas un périphérique de relais, nous renvoyons la lumière de couleur uniquement si colorUrl n'est pas vide, si elle est vide, nous renvoyons une lumière dimmable.

Merci les gars, j'ai ajouté le filtre sur les éléments d'harmonie. Ils ne sont désormais visibles que pour LM et mon ordinateur de bureau. - Bien sûr, ce serait génial d'avoir un filtre inversé, bloquant simplement le moyeu.

J'ai également créé un nouvel élément léger à partir de zéro et en ajoutant uniquement les éléments marche / arrêt. Maintenant, la télécommande ne montre que la lumière et le gradateur. -Donc, le code fonctionne, sauf que ce serait bien d'exclure également la partie du gradateur. -Pas de problème à court terme pour moi car je vais principalement déclencher des lumières dimmables.

Pour mon problème de couleur, cela peut être reproduit en mettant quelque chose dans l'élément de couleur, puis en essayant de supprimer cet élément. -Il disparaît, MAIS après "enregistrer" il revient avec [] (crochets) comme élément cible, tous les autres champs sont vides.

À ce propos

Existe-t-il déjà un moyen de contourner le délai d'attente de ~ 5 secondes sur Alexa?

Une possibilité serait de créer l'option pour définir une lumière comme "exécution asynchrone", ce qui entraînerait son exécution dans un thread séparé et renvoyer immédiatement un message "succès". (Bien sûr, les erreurs se perdraient de cette façon)

_ (Dans ma propre configuration, j'ai une file d'attente où le traitement de chaque appel est ajouté et exécuté séquentiellement dans un thread séparé. J'ai donc décidé de tout exécuter de manière asynchrone, car je ne veux pas attendre si longtemps pour alexas "OK" et parce que mes séquences de cinéma durent toutes plus de 5 secondes et Alexa est même si stupide de l'essayer une deuxième fois après le premier timeout. Cette nouvelle tentative a provoqué des ennuis avec mes séquences de cinéma ..) _

J'ai essayé la création et ON / OFF d'un appareil Fhem.

1. La création de l'appareil à partir du menu des appareils Fhem a réussi
2. Allumer / éteindre le périphérique FHEM depuis Habridge / BridgeDevice Afficher le test d'URL vert, mais le périphérique ne montre aucune réaction.

Le journal de débogage arrive par courrier.

@essera Donc, il appelle le FHEM et obtient une réponse réussie. Ceci est la commande du journal http://192.168.178.26:8083/fhem?cmd=set%20steckdose3%20/on

Edit: Eh bien, ignorez ce dernier élément. Il semble que je mets une barre oblique avant la commande, cela devrait être juste l'espace.

Nouveau pot RC6 disponible au lien ci-dessus!

Correction de FHEM mineur, OpenHAB et ajout du support Broadlink

@bwssytems J'utilise un utilisateur "ha-bridge" séparé @ Fibaro HomeCenter pour sélectionner les scènes et les appareils qui seront vus par ha-bridge. Je ne veux pas offrir ma serrure à Alexa.

Et avec RC6, j'obtiens toujours la même erreur "indéfini avec statut: Erreur serveur - 500".
Mais comme je peux le voir dans le journal: le pont peut voir mes scènes correctement.
J'espère que mon journal est meilleur pour vous cette fois :)

20/01/2018 16: 47: 49.143 | DEBUG | consolidation de scènes pour fibaros | com.bwssystems.HABridge.plugins.fibaro.FibaroHome
- | - | - | -
20/01/2018 16: 47: 49.133 | DEBUG | dispositifs de consolidation pour fibaros | com.bwssystems.HABridge.plugins.fibaro.FibaroHome
20/01/2018 16: 47: 49.182 | DEBUG | Réponse de getRooms: <<< [{"id": 4, "name": "Dachboden", "sectionID": 4, "icon": "room_bedroom", "defaultSensors": {"temperature": 0, "humidité" : 0, "light": 0}, "defaultThermostat": 0, "sortOrder": 1}, {"id": 5, "name": "Badezimmer", "sectionID": 5, "icon": "room_wanna "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 2}, {" id ": 6," name ": "Büro", "sectionID": 5, "icon": "room_office", "defaultSensors": {"temperature": 0, "humidité": 0, "light": 0}, "defaultThermostat": 0, "sortOrder ": 3}, {" id ": 7," name ":" Flur "," sectionID ": 5," icon ":" room_schody2 "," defaultSensors ": {" temperature ": 0," humidité ": 0 , "light": 0}, "defaultThermostat": 0, "sortOrder": 4}, {"id": 8, "name": "Schlafzimmer", "sectionID": 5, "icon": "room_bedroom", "defaultSensors": {"temperature": 0, "humidité": 0, "light": 0}, "defaultThermostat": 0, "sortOrder": 5}, {"id": 9, "name": "Emelie "," sectionID ": 5," icon ":" room_wardrobe "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 6}, {"id": 10, "name": "Mino", "sectionID": 5, "ic on ":" room_garage "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 7}, {" id ": 11 , "name": "Flur", "sectionID": 6, "icon": "room_drzwiwejsciowe", "defaultSensors": {"temperature": 181, "humidité": 0, "light": 182}, "defaultThermostat" : 0, "sortOrder": 8}, {"id": 12, "name": "Wohnzimmer", "sectionID": 6, "icon": "room_sofa", "defaultSensors": {"temperature": 0, "humidité": 0, "lumière": 0}, "defaultThermostat": 0, "sortOrder": 9}, {"id": 13, "name": "Küche", "sectionID": 6, "icon" : "room_dining", "defaultSensors": {"température": 0, "humidité": 0, "lumière": 0}, "defaultThermostat": 0, "sortOrder": 10}, {"id": 14, " name ":" Esszimmer "," sectionID ": 6," icon ":" room_jadalnia "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0 , "sortOrder": 11}, {"id": 15, "name": "HWR", "sectionID": 6, "icon": "room_laundry", "defaultSensors": {"temperature": 0, "humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 12}, {" id ": 16," name ":" Gäste WC "," sectionID ": 6," icon ": "room_toilet", "defaultSensors": {"temperature": 0 , "humidité": 0, "lumière": 0}, "defaultThermostat": 0, "sortOrder": 13}, {"id": 17, "name": "Haus", "sectionID": 7, "icon ":" room_bedroom "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 14}, {" id ": 18, "name": "Terrasse", "sectionID": 7, "icon": "room_bedroom", "defaultSensors": {"temperature": 0, "humidité": 0, "light": 0}, "defaultThermostat": 0, "sortOrder": 15}] >>> | com.bwssystems.HABridge.plugins.fibaro.FibaroInfo
20/01/2018 16: 47: 49.183 | DEBUG | Réponse de getRooms: <<< [{"id": 4, "name": "Dachboden", "sectionID": 4, "icon": "room_bedroom", "defaultSensors": {"temperature": 0, "humidité" : 0, "light": 0}, "defaultThermostat": 0, "sortOrder": 1}, {"id": 5, "name": "Badezimmer", "sectionID": 5, "icon": "room_wanna "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 2}, {" id ": 6," name ": "Büro", "sectionID": 5, "icon": "room_office", "defaultSensors": {"temperature": 0, "humidité": 0, "light": 0}, "defaultThermostat": 0, "sortOrder ": 3}, {" id ": 7," name ":" Flur "," sectionID ": 5," icon ":" room_schody2 "," defaultSensors ": {" temperature ": 0," humidité ": 0 , "light": 0}, "defaultThermostat": 0, "sortOrder": 4}, {"id": 8, "name": "Schlafzimmer", "sectionID": 5, "icon": "room_bedroom", "defaultSensors": {"temperature": 0, "humidité": 0, "light": 0}, "defaultThermostat": 0, "sortOrder": 5}, {"id": 9, "name": "Emelie "," sectionID ": 5," icon ":" room_wardrobe "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 6}, {"id": 10, "name": "Mino", "sectionID": 5, "ic on ":" room_garage "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 7}, {" id ": 11 , "name": "Flur", "sectionID": 6, "icon": "room_drzwiwejsciowe", "defaultSensors": {"temperature": 181, "humidité": 0, "light": 182}, "defaultThermostat" : 0, "sortOrder": 8}, {"id": 12, "name": "Wohnzimmer", "sectionID": 6, "icon": "room_sofa", "defaultSensors": {"temperature": 0, "humidité": 0, "lumière": 0}, "defaultThermostat": 0, "sortOrder": 9}, {"id": 13, "name": "Küche", "sectionID": 6, "icon" : "room_dining", "defaultSensors": {"température": 0, "humidité": 0, "lumière": 0}, "defaultThermostat": 0, "sortOrder": 10}, {"id": 14, " name ":" Esszimmer "," sectionID ": 6," icon ":" room_jadalnia "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0 , "sortOrder": 11}, {"id": 15, "name": "HWR", "sectionID": 6, "icon": "room_laundry", "defaultSensors": {"temperature": 0, "humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 12}, {" id ": 16," name ":" Gäste WC "," sectionID ": 6," icon ": "room_toilet", "defaultSensors": {"temperature": 0 , "humidité": 0, "lumière": 0}, "defaultThermostat": 0, "sortOrder": 13}, {"id": 17, "name": "Haus", "sectionID": 7, "icon ":" room_bedroom "," defaultSensors ": {" temperature ": 0," humidité ": 0," light ": 0}," defaultThermostat ": 0," sortOrder ": 14}, {" id ": 18, "name": "Terrasse", "sectionID": 7, "icon": "room_bedroom", "defaultSensors": {"temperature": 0, "humidité": 0, "light": 0}, "defaultThermostat": 0, "sortOrder": 15}] >>> | com.bwssystems.HABridge.plugins.fibaro.FibaroInfo
20/01/2018 16: 47: 49.220 | INFO | Trouvé: 15 pièces | com.bwssystems.HABridge.plugins.fibaro.FibaroInfo
20/01/2018 16: 47: 49.246 | DEBUG | Réponse de getScenes: <<< [{"id": 33, "name": "Fernsehlicht aus", "type": "com.fibaro.luaScene", "roomID": 12, "iconID": 6, "runConfig" : "MANUAL_ONLY", "alexaProhibited": true, "autostart": true, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 4, "runningInstances": 0, "instances" : [], "runningManualInstances": 0, "visible": true, "isLua": true, "properties": "", "triggers": {"properties": [], "globals": [], "events ": []," météo ": []}," actions ": {" appareils ": []," scènes ": []," groupes ": []}," liliStartCommand ":" "," liliStopCommand " : "", "sortOrder": 17}, {"id": 68, "name": "Rollos runterfahren", "type": "com.fibaro.luaScene", "roomID": 14, "iconID": 6 , "runConfig": "MANUAL_ONLY", "alexaProhibited": true, "autostart": false, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 2, "runningInstances": 0 , "instances": [], "runningManualInstances": 0, "visible": true, "isLua": true, "properties": "", "triggers": {"properties": [], "globals": [ ], "événements": [], "météo": []}, "actions": {"appareils": [], "scène s ": []," groups ": []}," liliStartCommand ":" "," liliStopCommand ":" "," sortOrder ": 8}, {" id ": 69," name ":" Rollos hochfahren " , "type": "com.fibaro.luaScene", "roomID": 14, "iconID": 6, "runConfig": "MANUAL_ONLY", "alexaProhibited": true, "autostart": false, "protectedByPIN": false , "killable": true, "killOtherInstances": false, "maxRunningInstances": 2, "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": true, "isLua": true, "properties": "", "triggers": {"properties": [], "globals": [], "events": [], "weather": []}, "actions": {"devices": [], "scènes": [], "groupes": []}, "liliStartCommand": "", "liliStopCommand": "", "sortOrder": 9}, {"id": 93, "nom": "Alles aus Haus", "type": "com.fibaro.magicScene", "roomID": 12, "runConfig": "TRIGGER_AND_MANUAL", "alexaProhibited": false, "autostart": false, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 2, "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": false, "properties": "{\ "conditionDeviceId \": 163, \ "conditionObjectType \": \ "périphérique \", \ "conditionId \": \ "condition_centralSceneEvent1HeldDown_163 \", \ "conditionLua \": \ "true \", \ "conditionValue \": \ "\", \ "conditionRooms \": [], \ "trigger \": \ "163 CentralSceneEvent 1 HeldDown \ n163 CentralSceneEvent 1 Released \", \ "actionDeviceId \": 92, \ "actionObjectType \": \ "scene \", \ "actionId \": \ "action_runScene_92 \", \ "actionLua \" : \ "fibaro: startScene (92); \", \ "actionValue \": \ "\", \ "actionRooms \": [], \ "looping \": false} "," triggers ": {" propriétés ": []," globals ": []," events ": [{" deviceId ": 163," eventName ":" CentralSceneEvent "," args ": [" 1 "," Released "]}]," météo ": []}," actions ": {" appareils ": []," scènes ": [92]," groupes ": []}," liliStartCommand ":" "," liliStopCommand ":" "," sortOrder ": 18}, {" id ": 94," name ":" Fernsehlicht an "," type ":" com.fibaro.blockScene "," roomID ": 12," iconID ": 5," runConfig ":" MANUAL_ONLY "," alexaProhibited ": false," autostart ": true," protectedByPIN ": false," killable ": true," killOtherInstances ": false," maxRunningInstances ": 2," runningInstances ": 0," instances ": [ ], "runningManualInstances": 0, "visible": true, "isLua": false, "properti es ":" "," triggers ": {" propriétés ": []," globals ": []," events ": []," weather ": []}," actions ": {" devices ": [ 112,114], "scènes": [], "groupes": []}, "liliStartCommand": "", "liliStopCommand": "", "sortOrder": 10}, {"id": 95, "nom": "Fernsehlicht + aus", "type": "com.fibaro.blockScene", "roomID": 12, "iconID": 5, "runConfig": "MANUAL_ONLY", "alexaProhibited": false, "autostart": true, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 2, "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": true, " isLua ": false," properties ":" "," triggers ": {" properties ": []," globals ": []," events ": []," weather ": []}," actions ": {"devices": [7,10,11,12,13,14,57,60,74,77,97,112,114], "scènes": [], "groups": []}, "liliStartCommand": "" , "liliStopCommand": "", "sortOrder": 19}, {"id": 96, "name": "Fernsehlicht Wohnzim", "type": "com.fibaro.magicScene", "roomID": 12, " runConfig ":" TRIGGER_AND_MANUAL "," alexaProhibited ": false," autostart ": false," protectedByPIN ": false," killable ": true," killOtherInstances ": false," maxRunningInstanc es ": 2," runningInstances ": 0," instances ": []," runningManualInstances ": 0," visible ": false," properties ":" {\ "conditionDeviceId \": 163, \ "conditionObjectType \": \ "device \", \ "conditionId \": \ "condition_centralSceneEvent2Pressed_163 \", \ "conditionLua \": \ "true \", \ "conditionValue \": \ "\", \ "conditionRooms \": [], \ "trigger \": \ "163 CentralSceneEvent 2 Pressed \", \ "actionDeviceId \": 94, \ "actionObjectType \": \ "scene \", \ "actionId \": \ "action_runScene_94 \", \ "actionLua \ ": \" fibaro: startScene (94); \ ", \" actionValue \ ": \" \ ", \" actionRooms \ ": [], \" looping \ ": false}", "triggers": { "properties": [], "globals": [], "events": [{"deviceId": 163, "eventName": "CentralSceneEvent", "args": ["2", "Pressed"]}], "météo": []}, "actions": {"appareils": [], "scènes": [94], "groupes": []}, "liliStartCommand": "", "liliStopCommand": "", "sortOrder": 20}, {"id": 98, "name": "Fersehlicht blau", "type": "com.fibaro.blockScene", "roomID": 12, "iconID": 5, "runConfig" : "MANUAL_ONLY", "alexaProhibited": false, "autostart": true, "protectedByPIN": false, "killable": true, "killOtherInstances": false , "maxRunningInstances": 2, "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": true, "isLua": false, "properties": "", "triggers": { "propriétés": [], "globaux": [], "événements": [], "météo": []}, "actions": {"appareils": [112,114], "scènes": [], " groupes ": []}," liliStartCommand ":" "," liliStopCommand ":" "," sortOrder ": 11}, {" id ": 99," name ":" Fernsehlicht blau + au "," type ": "com.fibaro.blockScene", "roomID": 12, "iconID": 5, "runConfig": "MANUAL_ONLY", "alexaProhibited": false, "autostart": true, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 2, "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": true, "isLua": false, "properties": " "," triggers ": {" propriétés ": []," globals ": []," events ": []," weather ": []}," actions ": {" devices ": [7,10, 11,12,13,14,112,114], "scènes": [], "groupes": []}, "liliStartCommand": "", "liliStopCommand": "", "sortOrder": 21}, {"id": 100, "name": "Fernsehlicht blau + au", "type": "com.fibaro.magicScene", "roomID": 12, "runConfig": "TRIGGER_AND_MANUAL", "alexaProhib ited ": false," autostart ": false," protectedByPIN ": false," killable ": true," killOtherInstances ": false," maxRunningInstances ": 2," runningInstances ": 0," instances ": []," runningManualInstances ": 0," visible ": false," properties ":" {\ "conditionDeviceId \": 163, \ "conditionObjectType \": \ "périphérique \", \ "conditionId \": \ "condition_centralSceneEvent3HeldDown_163 \", \ " conditionLua \ ": \" true \ ", \" conditionValue \ ": \" \ ", \" conditionRooms \ ": [], \" trigger \ ": \" 163 CentralSceneEvent 3 HeldDown \ n163 CentralSceneEvent 3 Released \ ", \ "actionDeviceId \": 99, \ "actionObjectType \": \ "scene \", \ "actionId \": \ "action_runScene_99 \", \ "actionLua \": \ "fibaro: startScene (99); \", \ "actionValue \": \ "\", \ "actionRooms \": [], \ "looping \": false} "," triggers ": {" properties ": []," globals ": []," événements ": [{" deviceId ": 163," eventName ":" CentralSceneEvent "," args ": [" 3 "," Released "]}]," weather ": []}," actions ": {" devices ": []," scènes ": [99]," groupes ": []}," liliStartCommand ":" "," liliStopCommand ":" "," sortOrder ": 22}, {" id ": 101," nom ":" Fersehlicht blau Woh "," type ":" com.fibaro.magicScene " , "roomID": 12, "runConfig": "TRIGGER_AND_MANUAL", "alexaProhibited": false, "autostart": false, "protectedByPIN": false, "killable": true, "killOtherInstances": false, "maxRunningInstances": 2 , "runningInstances": 0, "instances": [], "runningManualInstances": 0, "visible": false, "properties": "{\" conditionDeviceId \ ": 163, \" conditionObjectType \ ": \" périphérique \ ", \" conditionId \ ": \" condition_centralSceneEvent3Pressed_163 \ ", \" conditionLua \ ": \" true \ ", \" conditionValue \ ": \" \ ", \" conditionRooms \ ": [], \" trigger \ ": \" 163 CentralSceneEvent 3 Pressed \ ", \" actionDeviceId \ ": 98, \" actionObjectType \ ": \" scene \ ", \" actionId \ ": \" action_runScene_98 \ ", \" actionLua \ ": \ "fibaro: startScene (98); \", \ "actionValue \": \ "\", \ "actionRooms \": [], \ "looping \": false} "," triggers ": {" propriétés ": [], "globals": [], "events": [{"deviceId": 163, "eventName": "CentralSceneEvent", "args": ["3", "Pressed"]}], "weather": []}, "actions": {"appareils": [], "scènes": [98], "groupes": []}, "liliStartCommand": "", "liliStopCommand": "", "sortOrder": 23}] >>> | com.bwssystems.HABridge.plugins.fibaro.FibaroInfo
20/01/2018 16: 47: 49.259 | DEBUG | Réponse de getDevices: <<< [{"id": 7, "name": "Deckenspots", "roomID": 12, "type": "com.fibaro.FGD212", "baseType": "com.fibaro.multilevelSwitch "," enabled ": true," visible ": true," isPlugin ": false," parentId ": 5," remoteGatewayId ": 0," viewXml ": false," configXml ": false," interfaces ": [" deviceGrouping "," energy "," levelChange "," light "," power "," zwave "," zwaveAlarm "," zwaveMultiChannelAssociation "," zwaveProtection "," zwaveSceneActivation "]," properties ": {" pollingTimeSec ": 0 , "zwaveCompany": "Fibargroup", "zwaveInfo": "3,4,5", "zwaveVersion": "3.5", "RFProtectionState": "0", "RFProtectionSupport": "3", "alarmLevel": " 0 "," alarmType ":" 0 "," configured ": true," dead ":" false "," deviceControlType ":" 23 "," deviceGroup ":" [] "," deviceGroupMaster ":" 0 ", "deviceIcon": "15", "emailNotificationID": "0", "emailNotificationType": "0", "endPointId": "1", "energy": "7.20", "isLight": "true", "liliOffCommand ":" "," liliOnCommand ":" "," localProtectionState ":" 0 "," localProtectionSupport ":" 5 "," log ":" "," logTemp ":" "," fabricant ":" "," markAsDead ":" true "," model ":" "," nodeId ":" 2 "," parametersTemplate ":" 796 "," power ":" 0.00 "," productInfo ":" 1,15,1,2,16,0,3,5 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ":" false "," pushNotificationID ":" 0 "," pushNotificationType ":" 0 "," remoteGatewayId ":" 0 " , "saveLogs": "true", "sceneActivation": "25", "serialNumber": "h'000000000001c1b4", "showEnergy": "true", "smsNotificationID": "0", "smsNotificationType": "0" , "useTemplate": "true", "userDescription": "", "value": "0"}, "actions": {"reconfigure": 0, "reset": 0, "sceneActivationSet": 0, "setValue ": 1," startLevelDecrease ": 0," startLevelIncrease ": 0," stopLevelChange ": 0," turnOff ": 0," turnOn ": 0}," created ": 1516410078," modified ": 1516410078," sortOrder " : 1}, {"id": 13, "name": "Licht Küche", "roomID": 13, "type": "com.fibaro.binarySwitch", "baseType": "com.fibaro.actor", "enabled": true, "visible": true, "isPlugin": false, "parentId": 10, "remoteGatewayId": 0, "viewXml": false, "configXml": false, "interfaces": ["deviceGrouping" , "énergie", "lumière", "p ower "," zwave "," zwaveMultiChannelAssociation "," zwaveProtection "]," properties ": {" pollingTimeSec ": 0," zwaveCompany ":" Fibargroup "," zwaveInfo ":" 3,4,5 "," zwaveVersion " : "3.2", "RFProtectionState": "0", "RFProtectionSupport": "3", "configured": true, "dead": "false", "deviceControlType": "2", "deviceGroup": "[] "," deviceGroupMaster ":" 0 "," deviceIcon ":" 2 "," emailNotificationID ":" 0 "," emailNotificationType ":" 0 "," endPointId ":" 1 "," energy ":" 9.39 ", "isLight": "true", "liliOffCommand": "", "liliOnCommand": "", "localProtectionState": "0", "localProtectionSupport": "5", "log": "", "logTemp": " "," fabricant ":" "," markAsDead ":" true "," model ":" "," nodeId ":" 3 "," parametersTemplate ":" 781 "," power ":" 0.00 "," productInfo ":" 1,15,2,3,16,0,3,2 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ":" false "," pushNotificationID ":" 0 "," pushNotificationType ":" 0 "," remoteGatewayId ":" 0 "," saveLogs ":" true "," serialNumber ":" h'000000000000450d "," showEnergy ":" true "," s msNotificationID ":" 0 "," smsNotificationType ":" 0 "," useTemplate ":" true "," userDescription ":" "," value ":" false "}," actions ": {" reconfigure ": 0, "reset": 0, "turnOff": 0, "turnOn": 0}, "created": 1516410079, "modified": 1516410079, "sortOrder": 2}, {"id": 14, "name": " Lampe Tisch "," roomID ": 14," type ":" com.fibaro.binarySwitch "," baseType ":" com.fibaro.actor "," enabled ": true," visible ": true," isPlugin ": false, "parentId": 10, "remoteGatewayId": 0, "viewXml": false, "configXml": false, "interfaces": ["deviceGrouping", "energy", "light", "power", "zwave" , "zwaveMultiChannelAssociation", "zwaveProtection"], "properties": {"pollingTimeSec": 0, "zwaveCompany": "Fibargroup", "zwaveInfo": "3,4,5", "zwaveVersion": "3.2", " RFProtectionState ":" 0 "," RFProtectionSupport ":" 3 "," configured ": true," dead ":" false "," deviceControlType ":" 2 "," deviceGroup ":" [] "," deviceGroupMaster ": "0", "deviceIcon": "2", "emailNotificationID": "0", "emailNotificationType": "0", "endPointId": "2", "energy": "29.06", "isLight": "true "," liliOffCommand ":" "," liliOnCommand ":" "," localProtectionState ":" 0 ", "localProtectionSupport": "5", "log": "", "logTemp": "", "Manufacturer": "", "markAsDead": "true", "model": "", "nodeId": "3 "," parametersTemplate ":" 781 "," power ":" 0.00 "," productInfo ":" 1,15,2,3,16,0,3,2 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ":" false "," pushNotificationID ":" 0 "," pushNotificationType ":" 0 "," remoteGatewayId ": "0", "saveLogs": "true", "serialNumber": "h'000000000000450d", "showEnergy": "true", "smsNotificationID": "0", "smsNotificationType": "0", "useTemplate": "true", "userDescription": "", "value": "false"}, "actions": {"reconfigure": 0, "reset": 0, "turnOff": 0, "turnOn": 0}, "créé": 1516410079, "modifié": 1516410079, "sortOrder": 3}, {"id": 18, "name": "Licht", "roomID": 16, "type": "com.fibaro.binarySwitch "," baseType ":" com.fibaro.actor "," enabled ": true," visible ": true," isPlugin ": false," parentId ": 15," remoteGatewayId ": 0," viewXml ": false, "configXml": false, "interfaces": ["deviceGrouping", "energy", "light", "power", "zwave" , "zwaveMultiChannelAssociation", "zwaveProtection"], "properties": {"pollingTimeSec": 0, "zwaveCompany": "Fibargroup", "zwaveInfo": "3,4,5", "zwaveVersion": "3.2", " RFProtectionState ":" 0 "," RFProtectionSupport ":" 3 "," configuré ": true," dead ":" false "," deviceControlType ":" 2 "," deviceGroup ":" [] "," deviceGroupMaster ": "0", "deviceIcon": "2", "emailNotificationID": "0", "emailNotificationType": "0", "endPointId": "1", "energy": "2.70", "isLight": "true "," liliOffCommand ":" "," liliOnCommand ":" "," localProtectionState ":" 0 "," localProtectionSupport ":" 5 "," log ":" "," logTemp ":" "," fabricant ": "", "markAsDead": "true", "model": "", "nodeId": "4", "parametersTemplate": "781", "power": "0.00", "productInfo": "1,15 , 2,3,16,0,3,2 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ": "false", "pushNotificationID": "0", "pushNotificationType": "0", "remoteGatewayId": "0", "saveLogs": "true", "serialNumber": "h'00000000000044b4", "showEnergy": "vrai", "sms nID ":" 0 "," smsNotificationType ":" 0 "," useTemplate ":" true "," userDescription ":" "," value ":" false "}," actions ": {" reconfigure ": 0, "reset": 0, "turnOff": 0, "turnOn": 0}, "created": 1516410079, "modified": 1516410079, "sortOrder": 4}, {"id": 26, "name": " Licht "," roomID ": 5," type ":" com.fibaro.FGD212 "," baseType ":" com.fibaro.multilevelSwitch "," enabled ": true," visible ": true," isPlugin ": false , "parentId": 24, "remoteGatewayId": 0, "viewXml": false, "configXml": false, "interfaces": ["deviceGrouping", "energy", "levelChange", "light", "power", "zwave", "zwaveAlarm", "zwaveMultiChannelAssociation", "zwaveProtection", "zwaveSceneActivation"], "properties": {"pollingTimeSec": 0, "zwaveCompany": "Fibargroup", "zwaveInfo": "3,4,5 "," zwaveVersion ":" 3.5 "," RFProtectionState ":" 0 "," RFProtectionSupport ":" 3 "," alarmLevel ":" 0 "," alarmType ":" 0 "," configured ": true," dead ":" false "," deviceControlType ":" 23 "," deviceGroup ":" [] "," deviceGroupMaster ":" 0 "," deviceIcon ":" 15 "," emailNotificationID ":" 0 "," emailNotificationType " : "0", "endPointId": "1", "energy": "27.95", "isLight": "tr ue "," liliOffCommand ":" "," liliOnCommand ":" "," localProtectionState ":" 0 "," localProtectionSupport ":" 5 "," log ":" "," logTemp ":" "," fabricant " : "", "markAsDead": "true", "model": "", "nodeId": "7", "parametersTemplate": "796", "power": "0.00", "productInfo": "1, 15,1,2,16,0,3,5 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport " : "false", "pushNotificationID": "0", "pushNotificationType": "0", "remoteGatewayId": "0", "saveLogs": "true", "sceneActivation": "0", "serialNumber": " h'0000000000001fec "," showEnergy ":" true "," smsNotificationID ":" 0 "," smsNotificationType ":" 0 "," useTemplate ":" true "," userDescription ":" "," value ":" 0 "}," actions ": {" reconfigure ": 0," reset ": 0," sceneActivationSet ": 0," setValue ": 1," startLevelDecrease ": 0," startLevelIncrease ": 0," stopLevelChange ": 0, "turnOff": 0, "turnOn": 0}, "created": 1516410079, "modified": 1516410079, "sortOrder": 5}, {"id": 57, "name": "Fenster rechts", "roomID ": 14," type ":" com.fibaro.FGRM222 "," baseType ":" co m.fibaro.FGR "," enabled ": true," visible ": true," isPlugin ": false," parentId ": 56," remoteGatewayId ": 0," viewXml ": false," configXml ": false," interfaces ": [" energy "," levelChange "," power "," zwave "," zwaveMultiChannelAssociation "," zwaveProtection "," zwaveSceneActivation "]," properties ": {" pollingTimeSec ": 0," zwaveCompany ":" Fibargroup "," zwaveInfo ":" 3,3,52 "," zwaveVersion ":" 25.25 "," RFProtectionState ":" 0 "," RFProtectionSupport ":" 3 "," configured ": true," dead ":" false "," deviceControlType ":" 54 "," deviceIcon ":" 87 "," emailNotificationID ":" 0 "," emailNotificationType ":" 0 "," endPointId ":" 0 "," energy ":" 0.77 ", "liliOffCommand": "", "liliOnCommand": "", "localProtectionState": "0", "localProtectionSupport": "5", "log": "", "logTemp": "", "fabricant": "" , "markAsDead": "true", "model": "", "nodeId": "19", "parametersTemplate": "721", "power": "0.00", "productInfo": "1,15,3 , 2,16,0,25,25 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionLocal ":" 0 "," protectionLocalSupport ":" 5 "," protectionRF ":" 0 "," protectionRFSupport ": "3", "protectionState": "0", "protectionTimeout": "0", "protectionTimeoutSupport": "false", "pushNotificationID": "0", "pushNotificationType": "0", "remoteGatewayId": "0 "," saveLogs ":" true "," sceneActivation ":" 0 "," serialNumber ":" "," showEnergy ":" true "," smsNotificationID ":" 0 "," smsNotificationType ":" 0 "," useTemplate ":" true "," userDescription ":" "," value ":" 99 "," value2 ":" 0 "}," actions ": {" close ": 0," open ": 0," reconfigurer ": 0," reset ": 0," sceneActivationSet ": 0," setValue ": 1," setValue2 ": 1," startLevelDecrease ": 0," startLevelIncrease ": 0," stop ": 0," stopLevelChange ": 0}, "created": 1516410080, "modified": 1516410080, "sortOrder": 12}, {"id": 60, "name": "Fenster mitte", "roomID": 14, "type": "com .fibaro.FGRM222 "," baseType ":" com.fibaro.FGR "," enabled ": true," visible ": true," isPlugin ": false," parentId ": 59," remoteGatewayId ": 0," viewXml ": false," configXml ": false," interfaces ": [" energy "," levelChange "," power "," zwave "," zwaveMultiChannelAssociation "," zwaveProtection "," zwaveSceneActivation "]," properties ": {" pollingTimeSec ": 0," zwaveCompany ":" Fibargroup "," zwaveInfo ":" 3,3,52 "," zwaveVersion ":" 25.25 "," RFProtectionState ":" 0 "," RFProtectionSupport ":" 3 "," configuré ": true," dead ":" false "," deviceControlType ":" 54 "," deviceIcon ":" 87 "," emailNotificationID ":" 0 "," emailNotificationType ":" 0 "," endPointId ":" 0 "," energy ":" 0.70 "," liliOffCommand " : "", "liliOnCommand": "", "localProtectionState": "0", "localProtectionSupport": "5", "log": "", "logTemp": "", "fabricant": "", "markAsDead ":" true "," model ":" "," nodeId ":" 20 "," parametersTemplate ":" 721 "," power ":" 0.00 "," productInfo ":" 1,15,3,2, 16,0,25,25 "," protectionExclusiveControl ":" 0 "," protectionExclusiveControlSupport ":" false "," protectionLocal ":" 0 "," protectionLocalSupport ":" 5 "," protectionRF ":" 0 "," protectionRFSupport ":" 3 "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ":" false "," pushNotificationID ":" 0 "," pushNotificationType ":" 0 "," remoteGatewayId " : "0", "saveLogs": "true", "sceneActivation": "16", "serialNumber": "", "showEnergy": "true", "smsNotificationID": "0", "smsNotificationType": "0 "," useTemplate ":" true "," userDes cription ":" "," value ":" 99 "," value2 ":" 0 "}," actions ": {" close ": 0," open ": 0," reconfigure ": 0," reset ": 0, "sceneActivationSet": 0, "setValue": 1, "setValue2": 1, "startLevelDecrease": 0, "startLevelIncrease": 0, "stop": 0, "stopLevelChange": 0}, "created": 1516410080 , "modified": 1516410080, "sortOrder": 13}, {"id": 74, "name": "Fenster links", "roomID": 14, "type": "com.fibaro.FGRM222", "baseType ":" com.fibaro.FGR "," enabled ": true," visible ": true," isPlugin ": false," parentId ": 73," remoteGatewayId ": 0," viewXml ": false," configXml ": false, "interfaces": ["energy", "levelChange", "power", "zwave", "zwaveMultiChannelAssociation", "zwaveProtection", "zwaveSceneActivation"], "properties": {"pollingTimeSec": 0, "zwaveCompany" : "Fibargroup", "zwaveInfo": "3,3,52", "zwaveVersion": "25.25", "RFProtectionState": "0", "RFProtectionSupport": "3", "configured": true, "dead" : "false", "deviceControlType": "54", "deviceIcon": "87", "emailNotificationID": "0", "emailNotificationType": "0", "endPointId": "0", "energy": " 0.63 "," liliOffCommand ":" "," liliOnCommand ":" "," localProtectionState ":" 0 "," localProtectionSupport ":" 5 "," log ":" "," logTemp ":" "," fabricant ":" "," markAsDead ":" true "," model ":" ", "nodeId": "21", "parametersTemplate": "721", "power": "0.00", "productInfo": "1,15,3,2,16,0,25,25", "protectionExclusiveControl": "0", "protectionExclusiveControlSupport": "false", "protectionLocal": "0", "protectionLocalSupport": "5", "protectionRF": "0", "protectionRFSupport": "3", "protectionState": "0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ":" false "," pushNotificationID ":" 0 "," pushNotificationType ":" 0 "," remoteGatewayId ":" 0 "," saveLogs ":" true ", "sceneActivation": "0", "serialNumber": "", "showEnergy": "true", "smsNotificationID": "0", "smsNotificationType": "0", "useTemplate": "true", "userDescription" : "", "value": "99", "value2": "0"}, "actions": {"close": 0, "open": 0, "reconfigure": 0, "reset": 0, "sceneActivationSet": 0, "setValue": 1, "setValue2": 1, "startLevelDecrease": 0, "startLevelIncrease": 0, "stop": 0, "stopLevelChange": 0}, "created": 1516410080, " modifié ": 1516410080," sortOrder ": 14}, {" id ": 77," name ":" Fenster Sideboard ", "roomID": 14, "type": "com.fibaro.FGRM222", "baseType": "com.fibaro.FGR", "enabled": true, "visible": true, "isPlugin": false, "parentId ": 76," remoteGatewayId ": 0," viewXml ": false," configXml ": false," interfaces ": [" energy "," levelChange "," power "," zwave "," zwaveMultiChannelAssociation "," zwaveProtection " , "zwaveSceneActivation"], "properties": {"pollingTimeSec": 0, "zwaveCompany": "Fibargroup", "zwaveInfo": "3,3,52", "zwaveVersion": "25.25", "RFProtectionState": " 0 "," RFProtectionSupport ":" 3 "," configured ": true," dead ":" false "," deviceControlType ":" 54 "," deviceIcon ":" 87 "," emailNotificationID ":" 0 "," emailNotificationType ":" 0 "," endPointId ":" 0 "," energy ":" 0.62 "," liliOffCommand ":" "," liliOnCommand ":" "," localProtectionState ":" 0 "," localProtectionSupport ":" 5 "," log ":" "," logTemp ":" "," fabricant ":" "," markAsDead ":" true "," model ":" "," nodeId ":" 22 "," parametersTemplate " : "721", "power": "0.00", "productInfo": "1,15,3,2,16,0,25,25", "protectionExclusiveControl": "0", "protectionExclusiveControlSupport": "false" , "protectionLocal": "0", "protectionLocal Support ":" 5 "," protectionRF ":" 0 "," protectionRFSupport ":" 3 "," protectionState ":" 0 "," protectionTimeout ":" 0 "," protectionTimeoutSupport ":" false "," pushNotificationID " : "0", "pushNotificationType": "0", "remoteGatewayId": "0", "saveLogs": "true", "sceneActivation": "0", "serialNumber": "", "showEnergy": "true "," smsNotificationID ":" 0 "," smsNotificationType ":" 0 "," useTemplate ":" true "," userDescription ":" "," value ":" 98 "," value2 ":" 0 "}, "actions": {"close": 0, "open": 0, "reconfigure": 0, "reset": 0, "sceneActivationSet": 0, "setValue": 1, "setValue2": 1, "startLevelDecrease" : 0, "startLevelIncrease": 0, "stop": 0, "stopLevelChange": 0}, "created": 1516410081, "modified": 1516410081, "sortOrder": 15}, {"id": 112, "name ":" Stehlampe "," roomID ": 12," type ":" com.fibaro.multilevelSwitch "," baseType ":" com.fibaro.binarySwitch "," enabled ": true," visible ": true," isPlugin ": false," parentId ": 111," remoteGatewayId ": 0," viewXml ": false," configXml ": false," interfaces ": [" deviceGrouping "," fibaroFirmwareUpdate "," levelChange "," light "," zwave "," zwaveSwitchAll "]," properties ": {" p ollingTimeSec ": 0," zwaveCompany ":" Domitech Products "," zwaveInfo ":" 3,4,5 "," zwaveVersion ":" 5.14 "," configured ": true," dead ":" false "," deviceControlType ":" 23 "," deviceGroup ":" [] "," deviceGroupMaster ":" 0 "," deviceIcon ":" 15 "," emailNotificationID ":" 0 "," emailNotificationType ":" 0 "," endPointId " : "0", "firmwareUpdate": "{\" info \ ": \" \ ", \" progress \ ": 0, \" status \ ": \" UpToDate \ ", \" updateVersion \ ": \" 5.14 \ "}", "isLight": "true", "liliOffCommand": "", "liliOnCommand": "", "log": "", "logTemp": "", "fabricant": "", " markAsDead ":" true "," model ":" "," nodeId ":" 27 "," parametersTemplate ":" 807 "," productInfo ":" 2,14,76,66,49,52,5,14 "," pushNotificationID ":" 0 "," pushNotificationType ":" 0 "," remoteGatewayId ":" 0 "," saveLogs ":" true "," serialNumber ":" "," smsNotificationID ":" 0 "," smsNotificationType ":" 0 "," switchAllMode ":" SWITCH_ALL_INCLUDED_IN_THE_ALL_ON_ALL_OFF_FUNCTIONALITY "," updateVersion ":" "," useTemplate ":" true "," userDescription ":" "," value ":" 0 "}," actions ": {"abortUpdate": 1, "reconfigure": 0, "retryUpdate": 1, "setValue": 1, "startLevelDecrease": 0, "start LevelIncrease ": 0," startUpdate ": 1," stopLevelChange ": 0," turnOff ": 0," turnOn ": 0," updateFirmware ": 1}," créé ": 1516410082," modifié ": 1516410082," sortOrder ": 6}, {" id ": 114," name ":" RGBW "," roomID ": 12," type ":" com.fibaro.FGRGBW441M "," baseType ":" com.fibaro.colorController ", "enabled": true, "visible": true, "isPlugin": false, "parentId": 113, "remoteGatewayId": 0, "viewXml": false, "configXml": false, "interfaces": ["deviceGrouping" , "energy", "fibaroFirmwareUpdate", "levelChange", "light", "power", "zwave", "zwaveSwitchAll"], "properties": {"pollingTimeSec": 0, "zwaveCompany": "Fibargroup", " zwaveInfo ":" 3,3,52 "," zwaveVersion ":" 26.25 "," associationMode ":" 0 "," bright ":" 0 "," buttonType ":" 0 "," color ":" 0, 0,0,0 "," configuré ": true," currentProgram ":" 0 "," currentProgramID ":" 0 "," dead ":" false "," deviceControlType ":" 50 "," deviceGroup ":" [] "," deviceGroupMaster ":" 0 "," deviceIcon ":" 15 "," emailNotificationID ":" 0 "," emailNotificationType ":" 0 "," endPointId ":" 0 "," energy ":" 1,70 "," favoriteProgram ":" 0 "," firmwareUpdate ":" {\ "info \": \ "\", \ "progress \": 0, \ "sta tus\":\"UpToDate\",\"updateVersion\":\"26.25\"}","isLight":"true","lastColorSet":"0,5,23,0","liliOffCommand":"","liliOnCommand":"","log":"","logTemp":"","manufacturer":"","markAsDead":"true","mode":"0","model":"","nodeId":"28","parametersTemplate":"231","power":"0.00","productInfo":"1,15,9,0,16,0,26,25","programsSortOrder":"1,2,3,4,5","pushNotificationID":"0","pushNotificationType":"0","rememberColor":"false","remoteGatewayId":"0","saveLogs":"true","serialNumber":"","showEnergy":"true","smsNotificationID":"0","smsNotificationType":"0","switchAllMode":"SWITCH_ALL_INCLUDED_IN_THE_ALL_ON_ALL_OFF_FUNCTIONALITY","updateVersion":"","useTemplate":"true","userDescription":"","value":"0"},"actions":{"abortUpdate":1,"reconfigure":0,"reset":0,"retryUpdate":1,"setB":1,"setBrightness":1,"setColor":1,"setFavoriteProgram":2,"setG":1,"setR":1,"setValue":1,"setW":1,"startLevelDecrease":0,"startLevelIncrease":0,"startProgram":1,"startUpdate":1,"stopLevelChange":0,"turnOff":0,"turnOn":0,"updateFirmware": 1},"created":1516410082,"modified":1516410082,"sortOrder":7},{"id":122,"name":"Fenster","roomID":12,"type":"com.fibaro.FGRM222","baseType":"com.fibaro.FGR","enabled":true,"visible":true,"isPlugin":false,"parentId":121,"remoteGatewayId":0,"viewXml":false,"configXml":false,"interfaces":["energy","fibaroFirmwareUpdate","levelChange","power","zwave","zwaveConfiguration","zwaveProtection","zwaveSceneActivation"],"properties":{"pollingTimeSec":0,"zwaveCompany":"Fibargroup","zwaveInfo":"3,3,52","zwaveVersion":"24.24","RFProtectionState":"0","RFProtectionSupport":"3","configured":true,"dead":"false","deviceControlType":"54","deviceIcon":"87","emailNotificationID":"0","emailNotificationType":"0","endPointId":"0","energy":"0.16","firmwareUpdate":"{\"info\":\"\",\"progress\":0,\"status\":\"UpToDate\",\"updateVersion\":\"24.24\"}","liliOffCommand":"","liliOnCommand":"","localProtectionState":"0","localProtectionSupport":"5","log":"","logTemp":"","manufacturer":"","markAsDead":"true","model":"","no deId":"29","parametersTemplate":"249","power":"0.00","productInfo":"1,15,3,1,16,1,24,24","protectionExclusiveControl":"0","protectionExclusiveControlSupport":"false","protectionState":"0","protectionTimeout":"0","protectionTimeoutSupport":"false","pushNotificationID":"0","pushNotificationType":"0","remoteGatewayId":"0","saveLogs":"true","sceneActivation":"0","serialNumber":"","showEnergy":"true","smsNotificationID":"0","smsNotificationType":"0","updateVersion":"","useTemplate":"true","userDescription":"","value":"0","value2":"0"},"actions":{"abortUpdate":1,"close":0,"getParameter":1,"open":0,"reconfigure":0,"reset":0,"retryUpdate":1,"sceneActivationSet":0,"setParameter":2,"setValue":1,"setValue2":1,"startLevelDecrease":0,"startLevelIncrease":0,"startUpdate":1,"stop":0,"stopLevelChange":0,"updateFirmware":1},"created":1516410083,"modified":1516410083,"sortOrder":16}] >>> | com.bwssystems.HABridge.plugins.fibaro.FibaroInfo
01-20-2018 16:47:49.291 | ERROR | | spark.http.matching.GeneralError
01-20-2018 16:47:49.384 | INFO | Found: 12 devices | com.bwssystems.HABridge.plugins.fibaro.FibaroInfo

@bwssytems
OK - J'ai testé à nouveau la commutation de l'appareil Fhem one

1. Rechercher et trouver l'appareil dans la pièce définie - OK
2. La commutation de l'appareil Fhem défini sur "Bridge Device" fonctionne (ON / OFF) - OK
3. La liste des "périphériques déjà définis contient le bon périphérique - OK

1. Problème - Mais si j'allume / éteins un appareil, je reçois un message d'avertissem*nt dans le journal
   Voici le journal de débogage:
   Le message est:
   Le code de réponse HTTP n'était pas une réponse réussie attendue entre 200 et 299, le code était: HTTP / 1.1 302 Trouvé avec le contenu de <<< >>>

Journal de débogage de la mise hors tension de l'appareil:
20/01/2018 23: 22: 54.356 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 0; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool
- | - | - | -
20/01/2018 23: 22: 59.359 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 0; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool
20/01/2018 23: 23: 02.848 | DEBUG | HueMulator PUT appelé sur api / * avec requête <<

>> et corps << >> | com.bwssystems.HABridge.hue.HueMulator
20/01/2018 23: 23: 02.850 | DEBUG | matchedPart:: userid = a9TykGSkLQX7qlH7BEUEHQCiALsTLa5jHkZl6qBA | étincelle.
20/01/2018 23: 23: 02.851 | DEBUG | matchedPart:: id = 17 | étincelle.
20/01/2018 23: 23: 02.852 | DEBUG | changement d'état de teinte demandé: a9TykGSkLQX7qlH7BEUEHQCiALsTLa5jHkZl6qBA de 192.168.178.35 corps: {"on": false} | com.bwssystems.HABridge.hue.HueMulator
20/01/2018 23: 23: 02.852 | DEBUG | validateWhitelistUser: trouvé un utilisateur

>>, et corps <<< >>> | com.bwssystems.HABridge.hue.HueMulator
20/01/2018 23: 23: 03.031 | DEBUG | matchedPart:: userid = a9TykGSkLQX7qlH7BEUEHQCiALsTLa5jHkZl6qBA | étincelle.
20/01/2018 23: 23: 03.032 | DEBUG | matchedPart:: id = 17 | étincelle.
20/01/2018 23: 23: 03.033 | DEBUG | hue light demandé: 17 pour l'utilisateur: a9TykGSkLQX7qlH7BEUEHQCiALsTLa5jHkZl6qBA de 192.168.178.35 | com.bwssystems.HABridge.hue.HueMulator
20/01/2018 23: 23: 03.034 | DEBUG | validateWhitelistUser: trouvé un utilisateur| com.bwssystems.HABridge.BridgeSecurity
20/01/2018 23: 23: 03.034 | DEBUG | appareil trouvé nommé: Esszimmer Licht | com.bwssystems.HABridge.hue.HueMulator
20/01/2018 23: 23: 04.360 | DEBUG | Statistiques: [loué: 0; en attente: 0; disponible: 1; max: 200] | com.bwssystems.HABridge.plugins.http.HttpClientPool
20/01/2018 23: 23: 07.874 | DEBUG | Obtenez logmsgs. | com.bwssystems.HABridge.SystemControl

1. Demande - je mets un appareil capable de diminuer la luminosité dans la pièce avec tous les autres appareils FHEM que j'aime travailler avec HaBridge. . Lorsque le périphérique a été créé par HABridge, l'entrée de la fonction DIM était vide.
   Mais quand je l'ai rempli manuellement, cela fonctionnait.

-> BTW - Excellent travail jusqu'à maintenant - je pense que le reste est des cacahuètes pour vous :-)

@essera Une question, lorsque vous avez testé la commande off et que vous voyez l'erreur ci-dessus, le FHEM a-t-il réellement éteint l'appareil?

@essera Pour votre question n ° 5, vous devez sélectionner le type de contrôle dim avant de construire. Cette liste déroulante est au-dessus de la liste.

@bwssytems Ok merci, la conversion que je comprends, mais la chaîne de données que j'ai ressemble à ceci:
(raccourci pour plus de lisibilité)
{"data": "6d00b001000", "mac": "34: be: 34: c7: 91: 3c", "name": "AllLightsOn"}
est-ce que j'inclurais l'adresse et le nom mac?
qu'est-ce que je convertis pour envoyer?

serait-ce juste "6d00b001000" avec les guillemets?

@bwssytems Ceci est le journal de / var / log / syslog

22 janvier 16:45:09 ha-bridge java [2588]: 2018-01-22 16: 45: 09,219 [qtp25999886-13] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroInfo - Trouvé: 15 chambres
22 janvier 16:45:09 ha-bridge java [2588]: 2018-01-22 16: 45: 09,318 [qtp25999886-16] ERREUR spark.http.matching.GeneralError -
22 janvier 16:45:09 ha-bridge java [2588]: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Attendu une chaîne mais BEGIN_OBJECT à la ligne 1 colonne 2436 chemin $ [3] .triggers.events [ 0]
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory $ Adapter.read (ReflectiveTypeAdapterFactory.java:220)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory $ 1.read (ReflectiveTypeAdapterFactory.java:116)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory $ Adapter.read (ReflectiveTypeAdapterFactory.java:216)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read (TypeAdapterRuntimeTypeWrapper.java:40)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ArrayTypeAdapter.read (ArrayTypeAdapter.java:72)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.Gson.fromJson (Gson.java:879)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.Gson.fromJson (Gson.java:844)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.Gson.fromJson (Gson.java:793)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.Gson.fromJson (Gson.java:765)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.bwssystems.HABridge.plugins.fibaro.FibaroInfo.getScenes (FibaroInfo.java:154)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.bwssystems.HABridge.plugins.fibaro.FibaroHome.getScenes (FibaroHome.java:60)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.bwssystems.HABridge.plugins.fibaro.FibaroHome.getItems (FibaroHome.java:82)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.bwssystems.HABridge.devicemanagmeent.DeviceResource.lambda $ setupEndpoints $ 11 (DeviceResource.java:244)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at spark.ResponseTransformerRouteImpl $ 1.handle (ResponseTransformerRouteImpl.java:47)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at spark.http.matching.Routes.execute (Routes.java:61)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at spark.http.matching.MatcherFilter.doFilter (MatcherFilter.java:130)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at spark.embeddedserver.jetty.JettyHandler.doHandle (JettyHandler.java:50)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.server.session.SessionHandler.doScope (SessionHandler.java:1568)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.server.handler.ScopedHandler.handle (ScopedHandler.java:141)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.server.Server.handle (Server.java:564)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.server.HttpChannel.handle (HttpChannel.java:317)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.server.HttpConnection.onFillable (HttpConnection.java:251)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.io.AbstractConnection $ ReadCallback.succeeded (AbstractConnection.java:279)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.io.FillInterest.fillable (FillInterest.java:110)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.io.ChannelEndPoint $ 2.run (ChannelEndPoint.java:124)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:673)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at org.eclipse.jetty.util.thread.QueuedThreadPool $ 2.run (QueuedThreadPool.java:591)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at java.lang.Thread.run (Thread.java:745)
22 janvier 16:45:09 ha-bridge java [2588]: Causé par: java.lang.IllegalStateException: une chaîne attendue mais BEGIN_OBJECT à la ligne 1 colonne 2436 chemin $ [3] .triggers.events [0]
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.stream.JsonReader.nextString (JsonReader.java:831)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.TypeAdapters $ 16.read (TypeAdapters.java:422)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.TypeAdapters $ 16.read (TypeAdapters.java:410)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read (TypeAdapterRuntimeTypeWrapper.java:40)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ArrayTypeAdapter.read (ArrayTypeAdapter.java:72)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory $ 1.read (ReflectiveTypeAdapterFactory.java:116)
22 janvier 16:45:09 ha-bridge java [2588]: # 011at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory $ Adapter.read (ReflectiveTypeAdapterFactory.java:216)
22 janvier 16:45:09 ha-bridge java [2588]: # 011 ... 28 images communes omises
22 janvier 16:45:09 ha-bridge java [2588]: 2018-01-22 16: 45: 09,599 [qtp25999886-13] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroInfo - Trouvé: 12 appareils
22 janvier 16:45:11 ha-bridge java [2588]: 2018-01-22 16: 45: 11,463 [Thread-20] DEBUG com.bwssystems.HABridge.plugins.http.HttpClientPool - Statistiques: [loué: 0; en attente: 0; disponible: 0; max: 200]
22 janvier 16:45:16 ha-bridge java [2588]: 2018-01-22 16: 45: 16.469 [Thread-20] DEBUG com.bwssystems.HABridge.plugins.http.HttpClientPool - Statistiques: [loué: 0; en attente: 0; disponible: 0; max: 200]

@tuicemen Ce serait la chaîne sans les guillemets dans le champ de commande ir.

@xPRozAcx Vous n'avez pas de débogage et j'ai besoin de l'extrait du fichier lui-même. Modifiez le fichier syslog et enregistrez-le sous un autre nom. Téléchargez ce fichier sur un site Web avec un lien

débogage plugins.fibaro et plugins.http activé

Lien vers le fichier syslog:
https://workupload.com/file/J7DtQAq

@bwssytems

L'interrupteur marche / arrêt fonctionne correctement - je n'ai reçu le message d'erreur que dans le journal.

au point 5: je ne sais pas ce que vous voulez dire par "vous devrez sélectionner le type de contrôle de gradation avant de créer.

J'ai sélectionné le pourcentage décimal et appuyé sur "Build Item", mais dans l'appareil créé, l'option dim était toujours vide.
Mais je ne sais pas si c'est ce que tu veux dire.

RC7 a corrigé "l'erreur de serveur - 500" mais les scènes ne s'affichent toujours pas @ liste des scènes fibaro

Débogage Syslog à partir de RC7
https://workupload.com/file/Xm2s8vx

@bwssystems
Le périphérique FHEM n'a pas de préférences DIM mais il existe le paramètre PCT. PCT de 1 à 100 pour «atténuer» l'appareil. Peut-être que c'est le déclencheur pour le convertir en $ (intensité.pourcentage).

aussi: Petit problème - Dans la liste des périphériques FHEM, j'ai 4 périphériques. Si je coche les cases à cocher en haut de la rangée, tous les 4 appareils sélectionneront - Ajout en bloc de spectacles (4) (c'est ok). Si je ne sélectionne qu'un seul appareil, tous les autres appareils seront également sélectionnés (c'est faux), mais l'ajout en bloc indique correct (1)

Installé RC9.

Maintenant, je reçois beaucoup de réponses "L'appareil ne répond pas" (ma langue est réglée sur l'allemand, donc j'obtiens en fait: Das Gerät reagiert gerade nicht). La commande est exécutée correctement, cependant.
J'ai remarqué que cela semble se produire surtout si les commandes vocales n'ont pas été exécutées pendant une période plus longue (1 heure, peut-être). Si je dis la même commande juste après "l'appareil ne répond pas", Alexa me dit simplement "OK". Les commandes suivantes produisent alors également: "OK". Alors peut-être que cela a à voir avec les nouveaux paramètres de synchronisation dans HA Bridge?

De plus, j'ai encore de sérieux problèmes de découverte.
Si j'ajoute un nouvel appareil dans HA Bridge et que j'essaie de le rechercher, «Alexa, trouve de nouveaux appareils» ne fonctionne jamais. ("Il n'y a pas de nouveaux appareils"). L'effacement de tous les appareils sur https://alexa.amazon.de et le démarrage de la découverte sur le site Web mettent parfois à jour correctement la liste des appareils sur le site Web Alexa, mais pas toujours. Mais Alexa ne reconnaît alors aucune de mes commandes vocales ("Appareil non trouvé"). Je dois ensuite effacer les appareils sur le site Web encore et encore et commencer la découverte dans l'application Alexa soit sur mon Fire 10 (2017) ou l'application alexa sur mon téléphone mobile. Après plusieurs découvertes (parfois plus de 10), les commandes vocales recommencent enfin à fonctionner.

En raison de ce comportement, j'ai vraiment peur d'ajouter de nouveaux périphériques à mon HABridge ;-)
J'ai 1 Echo dot (acheté en mai 2017), 1 Echo dot (acheté en novembre 2017), 1 Echo Show (acheté en novembre 2017) et 2 échos de taille moyenne (pas plus) (acheté en novembre 2017).

Concernant l'intégration FHEM:
Ne serait-il pas plus facile de saisir simplement une URL comme http: // adresseip : 8050 / webname au lieu de l'adresse IP et du port?
En fait, il n'est pas possible de se connecter à une instance de nom Web non standard de FHEMweb.

Au lieu de la zone de texte de la salle FHEM, la syntaxe de la liste (https://wiki.fhem.de/wiki/List) aurait du sens.
Cela rendrait le filtrage beaucoup plus facile.

@ heikoh81 Alors, quel type de commandes exécutez-vous et que l'Alexa dit ne répond pas. C'est une indication que la commande a pris trop de temps. En ce qui concerne vos problèmes de découverte, cela dépendra du périphérique qui effectue la découverte. Vous avez des appareils de première génération qui fonctionnent, mais votre émission ne sera jamais découverte et les derniers échos sont de la génération 2 qui est déjà connue pour avoir des problèmes. Ne découvrez que sur vos anciens appareils de génération 1.

@ t0th0mas L'élément de salle est une demande basée sur l'auteur original de l'intégration FHEM. Sur l'autre élément, nous devrons ajouter un nom de site Web que je vois pour les cas non standard.

@tuicemen Je ne suis pas sûr du fonctionnement des éléments RF dans l'API, je vais y jeter un œil. En outre, il ne doit y avoir aucun espace dans vos chaînes de données hexadécimales.

Commentaires Broadlink:

• Configuration initialisée
• L'onglet est apparu avec les deux appareils Broadlink que j'ai (mini + pro)
• Séquences saisies depuis mon BlackBeanControl pour mon téléviseur
• Le test On / Off n'a pas fonctionné - aucune activité de Broadlink (la LED du téléviseur scintille au cas où elle recevrait des signaux IR)

Les séquences ressemblent à ceci 26007800581c111b0f0f0e0f2b2b100e0f0f100d0f0f0e0f100d0f0f0e0f100e1d0f0e100e0f0e1e1f000add571c111b0f0f110c2c2b100e0e0f100e0e0f0e0f100e0e0f0e0f110d1d100e0f0e0f0e1e1f000add571d0f1c100e100d2c2c0e0f0e0f0f0f0e0f0e0f110d0f0e100d100f1c100e0f0f0e0f1e1d000d05 et 26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000

J'ai refait quelques commandes marche / arrêt simples En utilisant l'adresse Broadlinks actuelle, les anciennes commandes sont toujours dans le pont mais avec la mauvaise adresse IP si naturellement qu'elles ne fonctionnent pas.
En utilisant les nouvelles commandes, j'obtiens un succès d'envoi de pop-up mais mes appareils ne répondent jamais.
intéressant si je vais modifier l'appareil dans le champ de nom de l'élément cible est "RM 2 Pro Plus"
{"id": "192.168.0.18-272a", "name": "RM 2 Pro Plus", "command": "ircommand", "data": "2600 .........
Dois-je modifier le nom?

De plus, j'ai fait une analyse complète des ports et mon Broadlink Pro n'utilise que les ports 25,110,119,143,465,563,587,993 & 995, il ne voit pas 40000 comme étant utilisé (j'ai scanné jusqu'au port 65535)

@tuicemen et @hphde Il semble que j'aurai besoin de regarder dans la bibliothèque que j'utilise pour Broadlink.

En outre, si vous pouviez activer le débogage pour les plugins Broadlink, cela pourrait également aider.

@bwssytems :
Comment puis-je contrôler quel écho fait la recherche?
Si je lance la recherche vocale sur mon tout premier point d'écho (mai 2017), il ne détecte toujours aucun appareil sur RC9 (ou les précédents).
J'ai remarqué qu'au démarrage de la recherche avec mon application Alexa sur le Fire HD 10, les LED de mes deux échos clignotent simultanément.
J'ai beaucoup de chance de trouver de nouveaux appareils sur mon téléphone portable. Là, j'ai installé l'application Alexa lors de l'achat de mon tout premier point Echo (mai 2017). Il semble que l'application soit connectée à l'un de mes échos, bien qu'ils soient tous dans le même compte. Peut-être une coïncidence, cependant. Aucune LED ne clignote lors de la recherche sur mon téléphone portable.

Le "pas de découverte avec Echo show" est-il uniquement un problème HABridge ou un problème général?

Concernant le "pas de réaction":
J'émets toujours exactement une requête http. J'appelle une URL FHEM qui active ou désactive un mannequin.
Cela devrait toujours prendre le même temps. Après cela, FHEM gère ce que je veux faire avec ma commande vocale.

OK maintenant le HA-Bridge ne trouve même pas de Broadlink

29/01/2018 21: 29: 29.176 | INFO | Création de FHEM Home. Aucun FHEM configuré. | com.bwssystems.HABridge.plugins.fhem.FHEMHome
- | - | - | -
29/01/2018 21: 29: 29.176 | INFO | Création de Broadlink Home. | com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
29/01/2018 21: 29: 29.176 | INFO | Broadlink découvrir .... | com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
29/01/2018 21: 29: 29.179 | WARN | Impossible de découvrir Broadlinks, avec une exception IO | com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
29/01/2018 21: 29: 29.181 | WARN | Erreur de lecture du fichier: data \ group.db - n'existe pas ou n'est pas lisible. continue ... | com.bwssystems.HABridge.dao.GroupRepository
29/01/2018 21: 29: 29.181 | INFO | Démarrage du service de gestion des périphériques HABridge .... | com.bwssystems.HABridge.devicemanagmeent.DeviceResource

Ok pense que je le comprends.

C:\Alex10>java -jar ha-bridge.jar2018-01-30 13:05:32,088 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config2018-01-30 13:05:32,463 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.0RC10) initializing....2018-01-30 13:05:32,478 [main] INFO spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public2018-01-30 13:05:32,488 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....2018-01-30 13:05:32.509:INFO::Thread-0: Logging initialized <strong i="6">@665ms</strong> to org.eclipse.jetty.util.log.StdErrLog2018-01-30 13:05:32,510 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...2018-01-30 13:05:32,513 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Seocket initialized to: 500002018-01-30 13:05:32,515 [main] INFO com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.2018-01-30 13:05:32,518 [main] INFO com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.2018-01-30 13:05:32,519 [main] INFO com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.2018-01-30 13:05:32,519 [main] INFO com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.2018-01-30 13:05:32,520 [main] INFO com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.2018-01-30 13:05:32,521 [main] INFO com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.2018-01-30 13:05:32,522 [main] INFO com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.2018-01-30 13:05:32,523 [main] INFO com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.2018-01-30 13:05:32,523 [main] INFO com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.2018-01-30 13:05:32,523 [main] INFO com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.2018-01-30 13:05:32,523 [main] INFO com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.2018-01-30 13:05:32,523 [main] INFO com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.2018-01-30 13:05:32,523 [main] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.2018-01-30 13:05:32,528 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.2018-01-30 13:05:32,528 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.2018-01-30 13:05:32,528 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-01-30 13:05:32,528 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-01-30 13:05:32,528 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-01-30 13:05:32,533 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-01-30 13:05:32,533 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 13:05:32,543 [Thread-0] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...2018-01-30 13:05:32,543 [Thread-0] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:802018-01-30 13:05:32.548:INFO:oejs.Server:Thread-0: jetty-9.4.z-SNAPSHOT2018-01-30 13:05:32.568:INFO:oejs.session:Thread-0: DefaultSessionIdManager workerName=node02018-01-30 13:05:32.568:INFO:oejs.session:Thread-0: No SessionScavenger set, using defaults2018-01-30 13:05:32.573:INFO:oejs.session:Thread-0: Scavenging every 660000ms2018-01-30 13:05:32.653:INFO:oejs.AbstractConnector:Thread-0: Started ServerConnector@539fc{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-01-30 13:05:32.653:INFO:oejs.Server:Thread-0: Started <strong i="7">@812ms</strong>2018-01-30 13:05:37,545 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-01-30 13:05:37,545 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-01-30 13:05:37,560 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-01-30 13:05:37,570 [main] INFO com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.0.100-useIface:false on web server: 0.0.0.0:802018-01-30 13:05:37,570 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-01-30 13:05:37,631 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-01-30 13:05:37,676 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.12018-01-30 13:05:37,681 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set.2018-01-30 13:05:37,681 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: eth2 valid usable IP address: /192.168.0.1002018-01-30 13:05:37,681 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth2 to our upnp join interface set.2018-01-30 13:05:37,681 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....

C'est drôle maintenant que le pont revoie le Broadlink.

Encore une fois, je ne vois aucune activité sur l'appareil (la LED clignote lorsque vous faites quelque chose)

2018-01-30 20:18:19,021 [qtp15713626-20] DEBUG com.bwssystems.HABridge.hue.HueMulator - HueMulator PUT called on api/* with request <<</api/f51cc6bb85024e12874492be0456f3c5/lights/27/state>>>, and body <<<{"on":true}>>>2018-01-30 20:18:19,023 [qtp15713626-20] DEBUG spark.Request - matchedPart: :userid = f51cc6bb85024e12874492be0456f3c52018-01-30 20:18:19,024 [qtp15713626-20] DEBUG spark.Request - matchedPart: :id = 272018-01-30 20:18:19,024 [qtp15713626-20] DEBUG com.bwssystems.HABridge.hue.HueMulator - hue state change requested: f51cc6bb85024e12874492be0456f3c5 from 2001:16b8:2470:e300:1828:240c:42ed:24fd body: {"on":true}2018-01-30 20:18:19,025 [qtp15713626-20] DEBUG com.bwssystems.HABridge.BridgeSecurity - validateWhitelistUser: found a user <f51cc6bb85024e12874492be0456f3c5>2018-01-30 20:18:19,025 [qtp15713626-20] DEBUG com.bwssystems.HABridge.hue.HueMulator - Calling on-off as requested.2018-01-30 20:18:19,025 [qtp15713626-20] DEBUG com.bwssystems.HABridge.hue.HueMulator - Decode Json for url items: [{"item":"{\"id\":\"192.168.112.129-2737\",\"name\":\"RM Mini\",\"command\":\"ircommand\",\"data\":\"26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000\"}","type":"broadlinkDevice"}]2018-01-30 20:18:19,038 [qtp15713626-20] DEBUG com.bwssystems.HABridge.hue.HueMulator - Calling Home device handler for type : broadlinkDevice2018-01-30 20:18:19,039 [qtp15713626-20] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.112.129-2737\",\"name\":\"RM Mini\",\"command\":\"ircommand\",\"data\":\"26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000\"}"2018-01-30 20:18:19,041 [qtp15713626-20] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM Mini2018-01-30 20:18:19,041 [qtp15713626-20] DEBUG com.bwssystems.HABridge.hue.DeviceDataDecode - Request <<26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000>>, not done: false2018-01-30 20:18:19,042 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Authentication method starts2018-01-30 20:18:19,045 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Constructing AuthCmdPayload2018-01-30 20:18:19,046 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Sending CmdPacket with AuthCmdPayload: cmd=65 len=802018-01-30 20:18:19,052 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Constructor CmdPacket starts2018-01-30 20:18:19,053 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running checksum for headers2018-01-30 20:18:19,054 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypting payload2018-01-30 20:18:19,060 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running whole packet checksum2018-01-30 20:18:19,060 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - End of CmdPacket constructor2018-01-30 20:18:19,062 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 192.168.112.1292018-01-30 20:18:19,069 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 802018-01-30 20:18:19,070 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Received datagram2018-01-30 20:18:19,071 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Getting encrypted data from 0x38 to the end2018-01-30 20:18:19,071 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - encDataLen=322018-01-30 20:18:19,073 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Creating AES instance with initial iv, key2018-01-30 20:18:19,082 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Decrypting encrypted data2018-01-30 20:18:19,090 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Decrypted. len=322018-01-30 20:18:19,091 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Packet received payload bytes: 6F0CBA90F6F5F6A2557E046B7D75490FEAB61CE8D9F80A88E7B88E58FD4E8AC62018-01-30 20:18:19,092 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Getting key from 0x04 to 0x142018-01-30 20:18:19,099 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Packet received key bytes: F6F5F6A2557E046B7D75490FEAB61CE82018-01-30 20:18:19,099 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Getting ID from 0x00 to 0x042018-01-30 20:18:19,100 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - Packet received id bytes: 6F0CBA902018-01-30 20:18:19,100 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - ID len=42018-01-30 20:18:19,109 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - End of authentication method2018-01-30 20:18:19,110 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Constructor CmdPacket starts2018-01-30 20:18:19,113 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running checksum for headers2018-01-30 20:18:19,114 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypting payload2018-01-30 20:18:19,124 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running whole packet checksum2018-01-30 20:18:19,125 [qtp15713626-20] DEBUG com.github.mob41.blapi.pkt.CmdPacket - End of CmdPacket constructor2018-01-30 20:18:19,132 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 192.168.112.1292018-01-30 20:18:19,134 [qtp15713626-20] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 80

Je vois cela btw lors de l'exécution on / off la première fois sur l'appareil mais je ne vois rien de approprié dans les journaux.

La première requête défectueuse va à /api//lights/28/state tout après passe à /api/f51cc6bb85024e12874492be0456f3c5/lights/28/state

OK réinitialisé

2018-01-30 15:55:56,466 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener - ended, restart found2018-01-30 15:55:56,466 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.0RC10) reinitialization requessted....2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HABridge - Going to close all homes2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Manager close homes called....2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.tcp.TCPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.NestBridge.NestHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.NestBridge.NestHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.lifx.LifxHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.somfy.SomfyHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.openhab.OpenHABHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.fhem.FHEMHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.udp.UDPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.exec.CommandHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hass.HassHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.harmony.HarmonyHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hal.HalHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.udp.UDPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.hue.HueHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.harmony.HarmonyHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.tcp.TCPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.mqtt.MQTTHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.domoticz.DomoticzHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.exec.CommandHome2018-01-30 15:55:56,471 [main] INFO com.bwssystems.HABridge.HomeManager - Closing home: com.bwssystems.HABridge.plugins.http.HTTPHome2018-01-30 15:55:56,471 [Thread-38] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >>> Spark shutting down ...2018-01-30 15:55:56.476:INFO:oejs.AbstractConnector:Thread-38: Stopped ServerConnector@16cedd0{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-01-30 15:55:56.476:INFO:oejs.session:Thread-38: Stopped scavenging2018-01-30 15:55:56,476 [Thread-38] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - done2018-01-30 15:56:01,473 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config2018-01-30 15:56:01,508 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.0RC10) initializing....2018-01-30 15:56:01,508 [main] INFO spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public2018-01-30 15:56:01,508 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....2018-01-30 15:56:01,514 [Thread-40] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...2018-01-30 15:56:01,514 [Thread-40] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:802018-01-30 15:56:01,514 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...2018-01-30 15:56:01.514:INFO:oejs.Server:Thread-40: jetty-9.4.z-SNAPSHOT2018-01-30 15:56:01,514 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Seocket initialized to: 500002018-01-30 15:56:01,514 [main] INFO com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.2018-01-30 15:56:01.515:INFO:oejs.session:Thread-40: DefaultSessionIdManager workerName=node02018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.2018-01-30 15:56:01.515:INFO:oejs.session:Thread-40: No SessionScavenger set, using defaults2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.2018-01-30 15:56:01.515:INFO:oejs.session:Thread-40: Scavenging every 600000ms2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-01-30 15:56:01,515 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-01-30 15:56:01,516 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-01-30 15:56:01,516 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-01-30 15:56:01,516 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 15:56:01,517 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, with IO Exceptionjava.net.BindException: Address already in use: Cannot bind at java.net.TwoStacksPlainDatagramSocketImpl.bind0(Native Method) at java.net.TwoStacksPlainDatagramSocketImpl.bind0(Unknown Source) at java.net.AbstractPlainDatagramSocketImpl.bind(Unknown Source) at java.net.TwoStacksPlainDatagramSocketImpl.bind(Unknown Source) at java.net.DatagramSocket.bind(Unknown Source) at java.net.DatagramSocket.<init>(Unknown Source) at java.net.DatagramSocket.<init>(Unknown Source) at com.github.mob41.blapi.BLDevice.discoverDevices(BLDevice.java:656) at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.createHome(BroadlinkHome.java:71) at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.<init>(BroadlinkHome.java:50) at com.bwssystems.HABridge.HomeManager.buildHomes(HomeManager.java:128) at com.bwssystems.HABridge.HABridge.main(HABridge.java:78)2018-01-30 15:56:01.517:INFO:oejs.AbstractConnector:Thread-40: Started ServerConnector@190b2b3{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-01-30 15:56:01.517:INFO:oejs.Server:Thread-40: Started <strong i="6">@468859ms</strong>2018-01-30 15:56:01,519 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-01-30 15:56:01,519 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-01-30 15:56:01,520 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-01-30 15:56:01,520 [main] INFO com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.0.100-useIface:false on web server: 0.0.0.0:802018-01-30 15:56:01,520 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-01-30 15:56:01,554 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-01-30 15:56:01,589 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.12018-01-30 15:56:01,589 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set.2018-01-30 15:56:01,594 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: eth2 valid usable IP address: /192.168.0.1002018-01-30 15:56:01,594 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth2 to our upnp join interface set.2018-01-30 15:56:01,594 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....2018-01-30 15:56:02,094 [qtp3295843-55] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: 127.0.0.1:80 filled in with address: 192.168.0.100:80

Aucun Broadlink trouvé

2018-01-30 17:47:44,735 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-01-30 17:47:44,735 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:47:44,745 [Thread-0] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...2018-01-30 17:47:44,750 [Thread-0] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:802018-01-30 17:47:44.750:INFO:oejs.Server:Thread-0: jetty-9.4.z-SNAPSHOT2018-01-30 17:47:44.770:INFO:oejs.session:Thread-0: DefaultSessionIdManager workerName=node02018-01-30 17:47:44.776:INFO:oejs.session:Thread-0: No SessionScavenger set, using defaults2018-01-30 17:47:44.778:INFO:oejs.session:Thread-0: Scavenging every 600000ms2018-01-30 17:47:44.840:INFO:oejs.AbstractConnector:Thread-0: Started ServerConnector@2e18d2{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-01-30 17:47:44.840:INFO:oejs.Server:Thread-0: Started <strong i="5">@753ms</strong>2018-01-30 17:47:49,752 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:47:49,752 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:47:49,752 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:47:54,752 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:47:54,753 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:47:54,753 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:47:59,756 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:47:59,757 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:47:59,757 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:04,762 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:04,763 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:04,763 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:09,766 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:09,767 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:09,767 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:14,770 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:14,770 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:14,770 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:19,771 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:19,771 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:19,771 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:24,775 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:24,775 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:24,775 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:29,778 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:29,778 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:29,778 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:34,780 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:34,780 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:34,780 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:39,781 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-30 17:48:40,242 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-30 17:48:40,258 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-01-30 17:48:40,258 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-01-30 17:48:40,267 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-01-30 17:48:40,277 [main] INFO com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.0.100-useIface:false on web server: 0.0.0.0:802018-01-30 17:48:40,277 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-01-30 17:48:40,292 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-01-30 17:48:40,332 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.12018-01-30 17:48:40,332 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set.2018-01-30 17:48:40,332 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: eth2 valid usable IP address: /192.168.0.1002018-01-30 17:48:40,332 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth2 to our upnp join interface set.2018-01-30 17:48:40,332 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....

L'interface utilisateur du pont signale 1 lien large trouvé alors que les commandes ne sont pas reçues par le lien large

2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.2018-01-31 11:07:32.418:INFO:oejs.session:Thread-16: No SessionScavenger set, using defaults2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:32.418:INFO:oejs.session:Thread-16: Scavenging every 660000ms2018-01-31 11:07:32,418 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:07:32,418 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:32.418:INFO:oejs.AbstractConnector:Thread-16: Started ServerConnector@81e45f{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-01-31 11:07:32.423:INFO:oejs.Server:Thread-16: Started <strong i="5">@148039ms</strong>2018-01-31 11:07:32,688 [qtp25724169-27] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:36,685 [qtp25724169-33] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:37,419 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:37,419 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:07:37,419 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:40,700 [qtp25724169-34] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:42,422 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:42,422 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:07:42,422 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:44,698 [qtp25724169-27] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:47,425 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:47,425 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:07:47,425 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:48,694 [qtp25724169-28] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:52,427 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:52,427 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:07:52,427 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:52,687 [qtp25724169-30] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:56,698 [qtp25724169-32] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:07:57,429 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:07:57,429 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:07:57,429 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:00,694 [qtp25724169-31] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:08:02,432 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:02,432 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:08:02,432 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:04,690 [qtp25724169-27] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:08:07,434 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:07,435 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:08:07,435 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:08,687 [qtp25724169-28] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:08:12,437 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:12,438 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:08:12,439 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:12,698 [qtp25724169-30] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:08:16,694 [qtp25724169-32] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:08:17,444 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:17,445 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:08:17,446 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:20,690 [qtp25724169-31] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 11:08:22,448 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 11:08:22,449 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 11:08:22,453 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-01-31 11:08:22,453 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-01-31 11:08:22,456 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-01-31 11:08:22,457 [main] INFO com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.0.100-useIface:false on web server: 0.0.0.0:802018-01-31 11:08:22,457 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-01-31 11:08:22,473 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-01-31 11:08:22,508 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.12018-01-31 11:08:22,508 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set.2018-01-31 11:08:22,513 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: eth2 valid usable IP address: /192.168.0.1002018-01-31 11:08:22,513 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth2 to our upnp join interface set.2018-01-31 11:08:22,513 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....2018-01-31 11:08:24,701 [qtp25724169-27] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: 127.0.0.1:80 filled in with address: 192.168.0.100:80

Je ne sais pas quels ports il essaie, mais selon un scanner de port, ce sont les ports ouverts sur le Broadlink:
Un service
Port 25 (TCP)
Port 110 (TCP)
Port 119 (TCP)
Port 143 (TCP)
Port 465 (TCP)
Port 563 (TCP)
Port 587 (TCP)
Port 993 (TCP)
Port 995 (TCP)

J'ai regardé le mini mais je me suis dit que j'avais beaucoup d'appareils RF, alors j'ai choisi le RM Pro.
voici la nouvelle sortie

2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.2018-01-31 13:50:01.168:INFO:oejs.session:Thread-13: No SessionScavenger set, using defaults2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.2018-01-31 13:50:01.168:INFO:oejs.session:Thread-13: Scavenging every 660000ms2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-01-31 13:50:01.168:INFO:oejs.AbstractConnector:Thread-13: Started ServerConnector@c0711f{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 13:50:01.168:INFO:oejs.Server:Thread-13: Started <strong i="7">@82511ms</strong>2018-01-31 13:50:01,168 [main] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Could not discover Broadlinks, Port in use, increasing by 112018-01-31 13:50:01,168 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-01-31 13:50:02,019 [qtp24864698-24] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 13:50:06,010 [qtp24864698-27] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-01-31 13:50:06,175 [main] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Adding Device to Map - host: 192.168.0.18, device Type: RM 2 Pro Plus, mac: 34:ffffffea:34:ffffffc7:ffffff91:3b2018-01-31 13:50:06,175 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-01-31 13:50:06,175 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-01-31 13:50:06,180 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-01-31 13:50:06,180 [main] INFO com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: 192.168.0.100-useIface:false on web server: 0.0.0.0:802018-01-31 13:50:06,180 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-01-31 13:50:06,195 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-01-31 13:50:06,230 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: lo valid usable IP address: /127.0.0.12018-01-31 13:50:06,230 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding lo to our upnp join interface set.2018-01-31 13:50:06,230 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: eth2 valid usable IP address: /192.168.0.1002018-01-31 13:50:06,230 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding eth2 to our upnp join interface set.2018-01-31 13:50:06,230 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....2018-01-31 13:50:10,036 [qtp24864698-31] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: 127.0.0.1:80 filled in with address: 192.168.0.100:80

Toujours le même - aucune activité visible sur le RM2 mini

2018-01-31 20:34:43,021 [qtp1659618-49] DEBUG com.bwssystems.HABridge.hue.DeviceDataDecode - Request <<26007800581c111b0f0f0e0f2b2b100e0f0f100d0f0f0e0f100d0f0f0e0f100e1d0f0e100e0f0e1e1f000add571c111b0f0f110c2c2b100e0e0f100e0e0f0e0f100e0e0f0e0f110d1d100e0f0e0f0e1e1f000add571d0f1c100e100d2c2c0e0f0e0f0f0f0e0f0e0f110d0f0e100d100f1c100e0f0f0e0f1e1d000d05>>, not done: false2018-01-31 20:34:43,021 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Authentication method starts2018-01-31 20:34:43,021 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Constructing AuthCmdPayload2018-01-31 20:34:43,022 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Sending CmdPacket with AuthCmdPayload: cmd=65 len=802018-01-31 20:34:43,023 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Constructor CmdPacket starts2018-01-31 20:34:43,023 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running checksum for headers2018-01-31 20:34:43,023 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypting payload2018-01-31 20:34:43,036 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running whole packet checksum2018-01-31 20:34:43,036 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - End of CmdPacket constructor2018-01-31 20:34:43,037 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 192.168.112.1292018-01-31 20:34:43,038 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 802018-01-31 20:34:43,039 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Received datagram2018-01-31 20:34:43,040 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Getting encrypted data from 0x38 to the end2018-01-31 20:34:43,040 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - encDataLen=322018-01-31 20:34:43,040 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Creating AES instance with initial iv, key2018-01-31 20:34:43,040 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Decrypting encrypted data2018-01-31 20:34:43,041 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Decrypted. len=322018-01-31 20:34:43,042 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Packet received payload bytes: 24A2D13AF8E0F075A22BEE015850EB91728CC6A395E9CD5D7F985468027E84C92018-01-31 20:34:43,042 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Getting key from 0x04 to 0x142018-01-31 20:34:43,042 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Packet received key bytes: F8E0F075A22BEE015850EB91728CC6A32018-01-31 20:34:43,042 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Getting ID from 0x00 to 0x042018-01-31 20:34:43,042 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - Packet received id bytes: 24A2D13A2018-01-31 20:34:43,043 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - ID len=42018-01-31 20:34:43,043 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - End of authentication method2018-01-31 20:34:43,044 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Constructor CmdPacket starts2018-01-31 20:34:43,044 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running checksum for headers2018-01-31 20:34:43,044 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypting payload2018-01-31 20:34:43,046 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running whole packet checksum2018-01-31 20:34:43,047 [qtp1659618-49] DEBUG com.github.mob41.blapi.pkt.CmdPacket - End of CmdPacket constructor2018-01-31 20:34:43,056 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 192.168.112.1292018-01-31 20:34:43,057 [qtp1659618-49] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 802018-01-31 20:34:43,058 [qtp1659618-49] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA5500000000000000000000000000000000000000000000000089CDF9FF2A27E9033C5334EA34E3C0F024A2D13AA1C300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

également aucune activité du RM Pro

2018-01-31 15:13:34,738 [qtp24864698-25] INFO spark.http.matching.MatcherFilter - The requested route [/HNAP1/] has not been mapped in Spark for Accept: [*/*]2018-01-31 15:16:15,764 [qtp24864698-31] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.0.18-272a\",\"name\":\"RM 2 Pro Plus\",\"command\":\"ircommand\",\"data\":\"260058000001289015101511143514111411141114111411143614351510153514351535143614351510151015101535141114111411141114351535143614111435153514351535140005160001284814000c490001284715000d05\"}"2018-01-31 15:16:15,764 [qtp24864698-31] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM 2 Pro Plus2018-01-31 15:16:15,769 [qtp24864698-31] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA550000000000000000000000000000000000000000000000007FDB00002A27E9034AAC34EA34C7913B06000000C6C40000E179EDB3525AC696E76A5DAEDF6C94376C25EADAF90C867B9ACD86D1623717EF000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

a également essayé un envoi RF et obtenez ceci:

2018-01-31 15:30:59,078 [qtp24864698-28] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - consolidating devices for Broadlink2018-01-31 15:33:15,477 [qtp24864698-24] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.0.18-272a\",\"name\":\"RM 2 Pro Plus\",\"command\":\"ircommand\",\"data\":\"6e006e010d042800014f00011a8b12111234113511121b0811121e051112123312111211123412331234123412331212111212111112123312121211111212341134113412341211113511341135110004db00011a8c11121134123412111112111212111212113411121112113511341135113511341112111211121112123411121112121111351135113412331212113412341135110004db00011a8c11121135113412111211111211131112113411121211123411351134123411341211121112111212113411121212111211341135113412341112113511341234110004dc0001198d11121134113511121112111211121112113511121112113511341135113412341112111212111211123411121112111211351134123411341212113412341134120004db00011a8c11121135113411121112121211111211123411121112123411341234123411341211121112111212113412111211121112341234113412341112113511341234110005dc00000000000000000000\"}"2018-01-31 15:33:15,478 [qtp24864698-24] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM 2 Pro Plus2018-01-31 15:33:15,484 [qtp24864698-24] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA55000000000000000000000000000000000000000000000000C0CCF9FF2A27EE034DAC34EA34C7913B4EE14A724BC700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

Ok a activé le débogage pour le Broadlink, puis a envoyé le faux IR. Ce qui suit est ce qui est signalé dans la ligne de commande

2018-02-02 10:29:13,629 [qtp29459721-31] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.0.18-272a\",\"name\":\"RM 2 Pro Plus\",\"command\":\"ircommand\",\"data\":\"0000006D00220002015500AA0016001500160015001600400016001500160015001600150016001500160015001600400016004000160015001600400016004000160040001600400016004000160015001600150016001500160040001600150016001500160015001600150016004000160040001600400016001500160040001600400016004000160040001605E50155005500160E3C\"}"2018-02-02 10:29:13,630 [qtp29459721-31] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM 2 Pro Plus2018-02-02 10:29:13,660 [qtp29459721-31] ERROR com.github.mob41.blapi.pkt.CmdPacket - Cannot encrypt payload! Abortingjavax.crypto.IllegalBlockSizeException: Input length not multiple of 16 bytes at com.sun.crypto.provider.CipherCore.finalNoPadding(CipherCore.java:1042) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:1010) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:847) at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) at javax.crypto.Cipher.doFinal(Cipher.java:2164) at com.github.mob41.blapi.pkt.auth.AES.encrypt(AES.java:53) at com.github.mob41.blapi.pkt.CmdPacket.<init>(CmdPacket.java:139) at com.github.mob41.blapi.BLDevice.sendCmdPkt(BLDevice.java:551) at com.github.mob41.blapi.BLDevice.sendCmdPkt(BLDevice.java:501) at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.deviceHandler(BroadlinkHome.java:243) at com.bwssystems.HABridge.hue.HueMulator.callUrl(HueMulator.java:1465) at com.bwssystems.HABridge.hue.HueMulator.changeState(HueMulator.java:1220) at com.bwssystems.HABridge.hue.HueMulator.lambda$39(HueMulator.java:444) at spark.RouteImpl$1.handle(RouteImpl.java:72) at spark.http.matching.Routes.execute(Routes.java:61) at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:130) at spark.embeddedserver.jetty.JettyHandler.doHandle(JettyHandler.java:50) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1568) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:564) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:317) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:128) at org.eclipse.jetty.util.thread.Invocable$InvocableExecutor.invoke(Invocable.java:222) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:294) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:199) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:673) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:591) at java.lang.Thread.run(Unknown Source)2018-02-02 10:29:13,665 [qtp29459721-31] ERROR spark.http.matching.GeneralError -com.github.mob41.blapi.ex.BLApiRuntimeException: Cannot encrypt payload at com.github.mob41.blapi.pkt.CmdPacket.<init>(CmdPacket.java:145) at com.github.mob41.blapi.BLDevice.sendCmdPkt(BLDevice.java:551) at com.github.mob41.blapi.BLDevice.sendCmdPkt(BLDevice.java:501) at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.deviceHandler(BroadlinkHome.java:243) at com.bwssystems.HABridge.hue.HueMulator.callUrl(HueMulator.java:1465) at com.bwssystems.HABridge.hue.HueMulator.changeState(HueMulator.java:1220) at com.bwssystems.HABridge.hue.HueMulator.lambda$39(HueMulator.java:444) at spark.RouteImpl$1.handle(RouteImpl.java:72) at spark.http.matching.Routes.execute(Routes.java:61) at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:130) at spark.embeddedserver.jetty.JettyHandler.doHandle(JettyHandler.java:50) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1568) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:564) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:317) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:128) at org.eclipse.jetty.util.thread.Invocable$InvocableExecutor.invoke(Invocable.java:222) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:294) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:199) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:673) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:591) at java.lang.Thread.run(Unknown Source)Caused by: javax.crypto.IllegalBlockSizeException: Input length not multiple of 16 bytes at com.sun.crypto.provider.CipherCore.finalNoPadding(CipherCore.java:1042) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:1010) at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:847) at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446) at javax.crypto.Cipher.doFinal(Cipher.java:2164) at com.github.mob41.blapi.pkt.auth.AES.encrypt(AES.java:53) at com.github.mob41.blapi.pkt.CmdPacket.<init>(CmdPacket.java:139) ... 26 common frames omitted

J'espère que ça t'as aidé!

http://www.mbroadlink.com/docs/manual_sp2.pdf

Salut, je vois les mêmes symptômes ad quadhammer. il semble que les commandes passent, mais il n'y a aucune indication de Broadlink que quelque chose s'est passé.
Voici quelques résultats du cli:

2018-02-06 11: 17: 09,745 [qtp17738985-22] INFO spark.http.matching.MatcherFilter - La route demandée [/ api // lights / 34 / state] n'a pas été mappée dans Spark pour Accept: [application / json, text / plain, / ]

la commande que j'envoie est la suivante:

{"id": "172.16.0.24-2712", "name": "RM 2", "command": "ircommand", "data": ""}

J'ai un autre système qui envoie ces commandes avec succès mais le format json est:

{"api_id": 134,
"commande": "rm2_send",
"mac": "xx: xx: xx: xx: xx: xx",
"Les données":""
}

Je ne sais pas si la structure fait une différence.

@peadard Quel système utilisez-vous qui fonctionne. Il peut encore y avoir des problèmes dans java api impl

@quadhammer Le RF devrait être

Je n'arrive toujours pas à configurer ma RM mini 3 avec l'application. J'ai entendu dire que certaines de ces unités sont défectueuses et sont généralement renvoyées pour une neuve.

J'utilise toujours ce https://github.com/hphde/BlackBeanControl en raison de sa simplicité - peut-être que vous aurez un coup d'oeil @bwssytems

./BlackBeanControl.py -c DISCOVERScanning network for Broadlink devices ... Found 2 broadlink device(s)Device 1:IPAddress = 192.168.112.129Port = 80MACAddress = 34:ea:34:e3:c0:xyDevice 2:IPAddress = 192.168.112.128Port = 80MACAddress = 34:ea:34:e7:e2:xy

BlackBeanControl.ini

[General]IPAddress = 192.168.112.128Port = 80MACAddress = 34:ea:34:e7:e2:xyTimeout = 6[mini]IPAddress = 192.168.112.129Port = 80MACAddress = 34:ea:34:e3:c0:xyTimeout = 6[Commands]

@bwssytems J'utilise RM Commander Builder Tools qui peut être utilisé pour générer la commande à envoyer. http://leffab.wixsite.com/domo-assist

Ok doit faire quelque chose de mal activé le débogage Broadlink mais il n'affiche aucune information de débogage:

2018-02-07 17:17:27,855 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-02-07 17:17:27,855 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-02-07 17:17:27,855 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-02-07 17:17:27,871 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-02-07 17:17:27.871:INFO:oejs.session:Thread-13: Scavenging every 600000ms2018-02-07 17:17:27,886 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-02-07 17:17:27,886 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....

a fait un ajout en bloc même si aucun appareil n'a été trouvé et a obtenu ceci:

2018-02-07 17:25:34,618 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....2018-02-07 17:39:13,062 [qtp9740210-39] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - consolidating devices for Broadlink2018-02-07 17:39:13,097 [qtp9740210-39] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-02-07 17:39:18,228 [qtp9740210-39] WARN com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Did not discover any Broadlinks.

C'est avec une nouvelle installation totale de Bridge créant une nouvelle base de données et différents Broadlink rm pro Je suis à mon chalet ramènera ce Broadlink chez moi afin que je puisse tester avec deux.

Avec RC15, j'obtiens:

TODO: Décryptage incompatible avec plusieurs octets non 16. Forcer à avoir 2048 octets

Aucune autre action.

Ok, j'ai trouvé quelques choses dans la configuration Broadlink dans le ha-bridge. En outre, correction du dernier élément AES en suspens dans la bibliothèque api. Ajout d'un bouton d'actualisation pour Broadlink et Lifx car il s'agit de systèmes basés sur la diffusion.

RC16 est sorti et est disponible à partir du lien ci-dessus

Avec Broadlink non activé:

Exception in thread "main" java.lang.NullPointerException at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.broadlinkDiscover(BroadlinkHome.java:324) at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.createHome(BroadlinkHome.java:64) at com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome.<init>(BroadlinkHome.java:53) at com.bwssystems.HABridge.HomeManager.buildHomes(HomeManager.java:128) at com.bwssystems.HABridge.HABridge.main(HABridge.java:79)

Juste après le démarrage - puis en ouvrant l'interface utilisateur

2018-02-08 23:35:53,484 [qtp25770640-17] INFO spark.http.matching.MatcherFilter - The requested route [/api/devices/map/types] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-08 23:35:53,610 [qtp25770640-28] INFO spark.http.matching.MatcherFilter - The requested route [/api/devices] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-08 23:35:53,613 [qtp25770640-27] INFO spark.http.matching.MatcherFilter - The requested route [/api/devices/backup/available] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-08 23:35:53,760 [qtp25770640-14] INFO spark.http.matching.MatcherFilter - The requested route [/api] has not been mapped in Spark for Accept: [application/json, text/plain, */*]

Aucun appareil n'est répertorié. L'actualisation de l'onglet Broadlink produit des 404:
Get broadlink Devices Error: undefined with status: Not Found - 404 et Refresh devices request Error: undefined with status: Not Found - 404

Ok doit faire quelque chose de mal activé le débogage Broadlink mais il n'affiche aucune information de débogage:

J'ai eu la même chose jusqu'à ce que je réinitialise le pont avec le débogage, et non la trace.

RC16 ne trouve aucun de mes appareils (même erreur que @hphde), mais il peut trouver le Broadlink.

@quadhammer Le lien est en haut de cet article

J'utilisais ce fichier et j'ai reçu l'avertissem*nt de: TODO: Décryptage incompatible avec plusieurs octets non 16. Forcer à avoir 2048 octets

http://rm-bridge.fun2code.de/downloads/RMBridge-APIDocumentation.pdf est ce que j'utilise en ce moment, et il semble avoir une documentation qui pourrait être utile.

Aujourd'hui mis à jour de 5.2.0 RC9 -> 5.2.0 RC16, mon pont HA n'affiche plus aucun périphérique.
J'ai 124 appareils dans mon fichier de données.
Au lieu de cela, j'obtiens ces messages d'erreur:

Erreur d'obtention de mapTypes: non défini avec le statut: introuvable - 404
Impossible d'obtenir les périphériques de habridge: indéfini avec l'état: introuvable - 404
Impossible d'obtenir les périphériques de habridge: indéfini avec l'état: introuvable - 404
Impossible d'obtenir les périphériques de habridge: non défini avec l'état: introuvable - 404

Revenu à RC9, 124 appareils sont à nouveau affichés dans HA Bridge.

Cependant, j'ai toujours le problème qu'Alexa avec 5.2.0 RC * renvoie parfois (pas toujours) chaque commande avec:"L'appareil XY ne répond pas pour le moment" (allemand: Das Gerät reagiert gerade nicht)
La commande est exécutée correctement, cependant.

Dans les versions antérieures, j'avais rarement cette réponse.
Une solution pour ça?

Ok, il est resté ouvert assez longtemps cette fois.
J'ai créé et envoyé une commande mais aucune action à partir du lien large

2018-02-13 18:46:15,019 [main] INFO com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.2018-02-13 18:46:15,020 [main] INFO com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.2018-02-13 18:46:15,020 [main] INFO com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.2018-02-13 18:46:15,020 [main] INFO com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.2018-02-13 18:46:15,020 [main] INFO com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.2018-02-13 18:46:15,021 [main] INFO com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.2018-02-13 18:46:15,021 [main] INFO com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.2018-02-13 18:46:15,021 [main] INFO com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.2018-02-13 18:46:15,021 [main] INFO com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.2018-02-13 18:46:15.021:INFO:oejs.session:Thread-11: DefaultSessionIdManager workerName=node02018-02-13 18:46:15,021 [main] INFO com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.2018-02-13 18:46:15.022:INFO:oejs.session:Thread-11: No SessionScavenger set, using defaults2018-02-13 18:46:15,022 [main] INFO com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.2018-02-13 18:46:15.022:INFO:oejs.session:Thread-11: Scavenging every 660000ms2018-02-13 18:46:15,022 [main] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.2018-02-13 18:46:15,023 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.2018-02-13 18:46:15,023 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.2018-02-13 18:46:15,023 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-02-13 18:46:15,023 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-02-13 18:46:15,024 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-02-13 18:46:15,024 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-02-13 18:46:15.025:INFO:oejs.AbstractConnector:Thread-11: Started ServerConnector@1123279{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-02-13 18:46:15.026:INFO:oejs.Server:Thread-11: Started <strong i="7">@85391ms</strong>2018-02-13 18:46:15,961 [qtp4187960-22] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-13 18:46:17,970 [qtp4187960-25] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-13 18:46:19,980 [qtp4187960-29] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-13 18:46:20,026 [main] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Adding Device to Map - host: 192.168.0.3, device Type: RM 2 Pro Plus, mac: 34:ffffffea:34:ffffffc7:ffffff91:3b2018-02-13 18:46:20,026 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-02-13 18:46:20,044 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-02-13 18:46:20,044 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-02-13 18:46:20,045 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-02-13 18:46:20,046 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-02-13 18:46:20,070 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-02-13 18:46:20,137 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....2018-02-13 18:46:49,590 [qtp4187960-23] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - consolidating devices for Broadlink2018-02-13 18:47:19,807 [qtp4187960-25] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - consolidating devices for Broadlink2018-02-13 18:48:38,515 [qtp4187960-25] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - consolidating devices for Broadlink2018-02-13 18:49:00,981 [qtp4187960-22] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.0.3-272a\",\"name\":\"RM 2 Pro Plus\",\"command\":\"ircommand\",\"data\":\"260050000001279214111312143613121411131213121411143514361312143514361436143514361411141114111435141114111510141115351436143514111436133614361435150005160001274814000d050000000000000000\"}"2018-02-13 18:50:13,958 [qtp4187960-22] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM 2 Pro Plus2018-02-13 18:50:14,040 [qtp4187960-22] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA5500000000000000000000000000000000000000000000000081D700002A27E903019334EA34C7913B000000001CC5000062483975D636AC99DD8197BC7572B859156B56FAF274FE7C18A34F3325353A6C000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

J'ai essayé RC 17 et j'ai obtenu les mêmes résultats que @tuicemen.
j'obtiens un msg de succès mais pas de lumières sur le Broadlink.
Voici quelques-uns des journaux:

>
2018-02-14 10: 12: 37,959 [qtp15791280-19] DEBUG com.bwssystems.HABridge.hue.HueMulator - HueMulator PUT appelé sur api / * avec requête <<

>> et corps << >>
2018-02-14 10: 12: 37,963 [qtp15791280-19] DEBUG spark.Request - matchedPart:: userid = 062e799a3d3a462c8c46b8ac677c2c2f
2018-02-14 10: 12: 37,975 [qtp15791280-19] DEBUG spark.Request - matchedPart:: id = 35
2018-02-14 10: 12: 37,978 [qtp15791280-19] DEBUG com.bwssystems.HABridge.hue.HueMulator - changement d'état de teinte demandé: 062e799a3d3a462c8c46b8ac677c2c2f à partir de 172.16.0.39 corps: {"on": true}
2018-02-14 10: 12: 37,981 [qtp15791280-19] DEBUG com.bwssystems.HABridge.BridgeSecurity - validateWhitelistUser: a trouvé un utilisateur <062e799a3d3a462c8c46b8ac677c2c2f>
2018-02-14 10: 12: 37,984 [qtp15791280-19] DEBUG com.bwssystems.HABridge.hue.HueMulator - Appel marche-arrêt comme demandé.
2018-02-14 10: 12: 37,987 [qtp15791280-19] DEBUG com.bwssystems.HABridge.hue.HueMulator - Décode Json pour les éléments d'url: [{"item": "{\" id \ ": \" 172.16. 0.24-2712 \ ", \" nom \ ": \" RM 2 \ ", \" command \ ": \" ircommand \ ", \" data \ ": \" \ "}", "type": "broadlinkDevice "}]
2018-02-14 10: 12: 37,992 [qtp15791280-19] DEBUG com.bwssystems.HABridge.hue.HueMulator - Gestionnaire d'appareil d'appel pour le type: broadlinkDevice
2018-02-14 10: 12: 38,005 [qtp15791280-19] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - exécution de la demande de l'API HUE pour envoyer un message à BroadlinkDevice: "{\" id \ ": \" 172.16. 0,24-2712 \ ", \" nom \ ": \" RM 2 \ ", \" commande \ ": \" ircommand \ ", \" data \ ": \" \ "}"
2018-02-14 10: 12: 38 012 [qtp15791280-19] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - appel BroadlinkDevice: RM 2
2018-02-14 10: 12: 38,015 [qtp15791280-19] DEBUG com.bwssystems.HABridge.hue.DeviceDataDecode - Request << >>, not done: false
2018-02-14 10: 12: 38,027 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - La méthode d'authentification démarre
2018-02-14 10: 12: 38,029 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Construction d'AuthCmdPayload
2018-02-14 10: 12: 38,031 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Envoi de CmdPacket avec AuthCmdPayload: cmd = 65 len = 80
2018-02-14 10: 12: 38,046 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - printBytes: 000000003131313131313131313131313131313100000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000
2018-02-14 10: 12: 38 050 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Le constructeur CmdPacket démarre
2018-02-14 10: 12: 38 053 ​​[qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - count = 27820 cmdPayload.cmd = 65 payload.len = 80
2018-02-14 10: 12: 38,055 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Nouveau décompte: 27821 (ajouté par 1)
2018-02-14 10: 12: 38,058 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Création d'un tableau d'octets avec des données
2018-02-14 10: 12: 38,060 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Exécution de la somme de contrôle pour la charge utile non chiffrée
2018-02-14 10: 12: 38,063 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Somme de contrôle de la charge utile non chiffrée: c3a1
2018-02-14 10: 12: 38,075 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Création d'une instance AES avec la clé fournie [-45, -21, 73, 68, -22, 80, -84, 64, -124, 127, 127, 125, -27, 86, -65, -92], iv [86, 46, 23, -103, 109, 9, 61, 40, -35, -77 , -70, 105, 90, 46, 111, 88]
2018-02-14 10: 12: 38,078 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Chiffrement de la charge utile
2018-02-14 10: 12: 38.084 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - printBytes: 851739B35D15C0614B39AA0B0DDC5DC837E8160FDC216DA1229E3655A2FDE8A1806A436EF8ACC87A874FF86FC61E6652E6537B0190DD2A240DE735C6156D7D5474CC5A8513FEEAB89A9559E2F540643616DA720E534723A25D89B5413E1D18D0
2018-02-14 10: 12: 38,087 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Chiffré. len = 96
2018-02-14 10: 12: 38,095 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Exécution de la somme de contrôle du paquet entier
2018-02-14 10: 12: 38,097 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Somme de contrôle du paquet entier: c414
2018-02-14 10: 12: 38,100 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Fin du constructeur CmdPacket
2018-02-14 10: 12: 38.102 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - printBytes: 5AA5AA555AA5AA5500000000000000000000000000000000000000000000000014C400002A276500AD6CB4430D391560DDD74C5BA1C30000851739B35D15C0614B39AA0B0DDC5DC837E8160FDC216DA1229E3655A2FDE8A1806A436EF8ACC87A874FF86FC61E6652E6537B0190DD2A240DE735C6156D7D5474CC5A8513FEEAB89A9559E2F540643616DA720E534723A25D89B5413E1D18D0
2018-02-14 10: 12: 38,115 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 172.16.0.24
2018-02-14 10: 12: 38,117 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 80
2018-02-14 10: 12: 38,121 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Datagramme reçu
2018-02-14 10: 12: 38,124 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - printBytes:
2018-02-14 10: 12: 38,129 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Récupération des données chiffrées de 0x38 à la fin
2018-02-14 10: 12: 38,134 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - encDataLen = 1992
2018-02-14 10: 12: 38,145 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Création d'une instance AES avec la clé iv initiale
2018-02-14 10: 12: 38,148 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - printBytes:
2018-02-14 10: 12: 38,152 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Décryptage des données cryptées
2018-02-14 10: 12: 38,175 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Décrypté. len = 2000
2018-02-14 10: 12: 38,178 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Paquet reçu des octets de charge utile:
2018-02-14 10: 12: 38,186 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Obtention de la clé de 0x04 à 0x14
2018-02-14 10: 12: 38,189 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Paquet reçu octets clés: F8E0F075A22BEE015850EB91728CC6A3
2018-02-14 10: 12: 38,195 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Obtention de l'ID de 0x00 à 0x04
2018-02-14 10: 12: 38,197 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Paquet reçu octets d'identification: 24A2D13A
2018-02-14 10: 12: 38,200 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - ID len = 4
2018-02-14 10: 12: 38,215 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - Fin de la méthode d'authentification
2018-02-14 10: 12: 38,218 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Le constructeur CmdPacket démarre
2018-02-14 10: 12: 38,221 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - count = 27821 cmdPayload.cmd = 6a payload.len = 464
2018-02-14 10: 12: 38,223 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Nouveau décompte: 27822 (ajouté par 1)
2018-02-14 10: 12: 38,226 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Création d'un tableau d'octets avec des données
2018-02-14 10: 12: 38,228 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Exécution de la somme de contrôle pour la charge utile non chiffrée
2018-02-14 10: 12: 38,231 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Somme de contrôle de la charge utile non chiffrée: dd0e
2018-02-14 10: 12: 38,234 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Création d'une instance AES avec la clé fournie [-8, -32, -16, 117, -94, 43 , -18, 1, 88, 80, -21, -111, 114, -116, -58, -93], iv [86, 46, 23, -103, 109, 9, 61, 40, -35, -77, -70, 105, 90, 46, 111, 88]
2018-02-14 10: 12: 38,237 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Chiffrement de la charge utile
2018-02-14 10: 12: 38,249 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - printBytes:
2018-02-14 10: 12: 38,255 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Chiffré. len = 480
2018-02-14 10: 12: 38,263 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Exécution de la somme de contrôle du paquet entier
2018-02-14 10: 12: 38,266 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Somme de contrôle du paquet entier: be30
2018-02-14 10: 12: 38,269 [qtp15791280-19] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Fin du constructeur CmdPacket
2018-02-14 10: 12: 38,271 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - printBytes:
2018-02-14 10: 12: 38,275 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 172.16.0.24
2018-02-14 10: 12: 38,277 [qtp15791280-19] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 80
2018-02-14 10: 12: 38,281 [qtp15791280-19] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Retour de données de l'appareil RM2: <<< >>>
2018-02-14 10: 12: 43,184 [main] DEBUG com.bwssystems.HABridge.upnp.UpnpListener - sendUpnpNotify notifyTemplate est <<

HÔTE: 239.255.255.250:1900
CACHE-CONTROL: âge max = 100
LIEU: http://172.16.0.17 : 80 / description.xml
SERVEUR: Linux / 3.14.0 UPnP / 1.0 IpBridge / 1.19.0
NTS: ssdp: vivant
teinte-bridgeid:
NT: uuid: 2f402f80-da50-11e1-9b23-b827eb4ad5b1
USN: uuid: 2f402f80-da50-11e1-9b23-b827eb4ad5b1

>

2018-02-14 17:19:42,761 [qtp3715863-35] DEBUG com.bwssystems.HABridge.hue.HueMulator - HueMulator PUT called on api/* with request <<</api/4b672858de25495da1ec3530b00bd160/lights/27/state>>>, and body <<<{"on":true}>>>2018-02-14 17:19:42,762 [qtp3715863-35] DEBUG spark.Request - matchedPart: :userid = 4b672858de25495da1ec3530b00bd1602018-02-14 17:19:42,763 [qtp3715863-35] DEBUG spark.Request - matchedPart: :id = 272018-02-14 17:19:42,763 [qtp3715863-35] DEBUG com.bwssystems.HABridge.hue.HueMulator - hue state change requested: 4b672858de25495da1ec3530b00bd160 from 192.168.112.21 body: {"on":true}2018-02-14 17:19:42,764 [qtp3715863-35] DEBUG com.bwssystems.HABridge.BridgeSecurity - validateWhitelistUser: found a user <4b672858de25495da1ec3530b00bd160>2018-02-14 17:19:42,765 [qtp3715863-35] DEBUG com.bwssystems.HABridge.hue.HueMulator - Calling on-off as requested.2018-02-14 17:19:42,766 [qtp3715863-35] DEBUG com.bwssystems.HABridge.hue.HueMulator - Decode Json for url items: [{"item":"{\"id\":\"192.168.112.129-2737\",\"name\":\"RM Mini\",\"command\":\"ircommand\",\"data\":\"26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000\"}","type":"broadlinkDevice"}]2018-02-14 17:19:42,768 [qtp3715863-35] DEBUG com.bwssystems.HABridge.hue.HueMulator - Calling Home device handler for type : broadlinkDevice2018-02-14 17:19:42,768 [qtp3715863-35] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.112.129-2737\",\"name\":\"RM Mini\",\"command\":\"ircommand\",\"data\":\"26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000\"}"2018-02-14 17:19:42,769 [qtp3715863-35] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM Mini2018-02-14 17:19:42,770 [qtp3715863-35] DEBUG com.bwssystems.HABridge.hue.DeviceDataDecode - Request <<26008400581d0e1e0f0e0f0f0f1c1c0f0f0e100e0f0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f1d100e1d100d10000acf571d0f1d0f0e0f0f0f1d1c0e100e0f0f0e0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e1d100e1e0f0f0e000ad0561d101c0f0e0f0f101c1c0f0f0f0e0f0e0f0f0f0e0f0f0e0f0f0f0e100e0f0e0f0f1d0f0f1d0f0f0e000d0500000000>>, not done: false2018-02-14 17:19:42,771 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Authentication method starts2018-02-14 17:19:42,771 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Constructing AuthCmdPayload2018-02-14 17:19:42,771 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Sending CmdPacket with AuthCmdPayload: cmd=65 len=802018-02-14 17:19:42,771 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth AuthPayload initial bytes to send: 00000000313131313131313131313131313131000000000000000000000001000000000000000000000000000001000054657374202031000000000000000000000000000000000000000000000000002018-02-14 17:19:42,772 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Constructor CmdPacket starts2018-02-14 17:19:42,772 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - count=32540 cmdPayload.cmd=65 payload.len=802018-02-14 17:19:42,773 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - New count: 32541 (added by 1)2018-02-14 17:19:42,773 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Creating byte array with data2018-02-14 17:19:42,773 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running checksum for un-encrypted payload2018-02-14 17:19:42,773 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Un-encrypted payload checksum: c3a12018-02-14 17:19:42,773 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Creating AES instance with provided key [-8, -32, -16, 117, -94, 43, -18, 1, 88, 80, -21, -111, 114, -116, -58, -93], iv [86, 46, 23, -103, 109, 9, 61, 40, -35, -77, -70, 105, 90, 46, 111, 88]2018-02-14 17:19:42,774 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypting payload2018-02-14 17:19:42,780 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - printBytes: 2E88BCE3858A1A70893FCB792171D8B466E2E3658B7C40E73A8FCE4090C9A7AFEF5F42106985C6FE3BB6B324CD8B3B7ED8691547F426B7DB8EB7D0C6215FC67031860C59869F2354945F07837632606E1372046F1D47250CEF2A7B6678C7E9222018-02-14 17:19:42,781 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypted. len=962018-02-14 17:19:42,781 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running whole packet checksum2018-02-14 17:19:42,781 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Whole packet checksum: c0f42018-02-14 17:19:42,781 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - End of CmdPacket constructor2018-02-14 17:19:42,782 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - printBytes: 5AA5AA555AA5AA55000000000000000000000000000000000000000000000000F4C000002A2765001D7F34EA34E3C0F024A2D13AA1C300002E88BCE3858A1A70893FCB792171D8B466E2E3658B7C40E73A8FCE4090C9A7AFEF5F42106985C6FE3BB6B324CD8B3B7ED8691547F426B7DB8EB7D0C6215FC67031860C59869F2354945F07837632606E1372046F1D47250CEF2A7B6678C7E9222018-02-14 17:19:42,784 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 192.168.112.1292018-02-14 17:19:42,784 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 802018-02-14 17:19:42,785 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Received initial datagram2018-02-14 17:19:42,785 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth recv data bytes after initial req: 5AA5AA555AA5AA5500000000000000000000000000000000000000000000000084CDF9FF2A27E903177F34EA34E3C0F06F0CBA90A1C300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002018-02-14 17:19:42,786 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Getting encrypted data from 0x38 to the end2018-02-14 17:19:42,786 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth encDataLen=19922018-02-14 17:19:42,787 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth padded encoded bytes from initial req: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002018-02-14 17:19:42,787 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Creating AES instance with initial iv, key2018-02-14 17:19:42,787 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Decrypting encrypted data2018-02-14 17:19:42,793 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Decrypted. len=20002018-02-14 17:19:42,793 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Packet received payload bytes: 24A2D13AF8E0F075A22BEE015850EB91728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C9728CC6A395E9CD5D7F985468027E84C92018-02-14 17:19:42,794 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Getting key from 0x04 to 0x142018-02-14 17:19:42,794 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Packet received key bytes: F8E0F075A22BEE015850EB91728CC6A32018-02-14 17:19:42,794 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Getting ID from 0x00 to 0x042018-02-14 17:19:42,794 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth Packet received id bytes: 24A2D13A2018-02-14 17:19:42,795 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth ID len=42018-02-14 17:19:42,795 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - auth End of authentication method2018-02-14 17:19:42,795 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Constructor CmdPacket starts2018-02-14 17:19:42,796 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - count=32541 cmdPayload.cmd=6a payload.len=1442018-02-14 17:19:42,802 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - New count: 32542 (added by 1)2018-02-14 17:19:42,803 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Creating byte array with data2018-02-14 17:19:42,803 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running checksum for un-encrypted payload2018-02-14 17:19:42,803 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Un-encrypted payload checksum: c70e2018-02-14 17:19:42,804 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Creating AES instance with provided key [-8, -32, -16, 117, -94, 43, -18, 1, 88, 80, -21, -111, 114, -116, -58, -93], iv [86, 46, 23, -103, 109, 9, 61, 40, -35, -77, -70, 105, 90, 46, 111, 88]2018-02-14 17:19:42,804 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypting payload2018-02-14 17:19:42,806 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - printBytes: 73D40E65DE1CC77B3E725FF8613AB84B1CE3FDDB1AA9328F27BF43C2C144A683C8999942857947E1D9275348996691493C2E09B93AA8F7E0E98D66C14D7039C6F19666A1296F5D5ED9ACD1FDA975D2A3B1C587BFBC5870526C7FD59C8A329317EF20CC16B5AA43C39C097D803B8360A6D09AE898F75F1167F374588C5F2223C69ECE2258C77D28787E1A4D44F4ECBD8F5DF07A2EB3BBFF13FB515C42FD4C39852018-02-14 17:19:42,806 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Encrypted. len=1602018-02-14 17:19:42,806 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Running whole packet checksum2018-02-14 17:19:42,807 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - Whole packet checksum: c17a2018-02-14 17:19:42,807 [qtp3715863-35] DEBUG com.github.mob41.blapi.pkt.CmdPacket - End of CmdPacket constructor2018-02-14 17:19:42,807 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - printBytes: 5AA5AA555AA5AA550000000000000000000000000000000000000000000000007AC100002A276A001E7F34EA34E3C0F024A2D13A0EC7000073D40E65DE1CC77B3E725FF8613AB84B1CE3FDDB1AA9328F27BF43C2C144A683C8999942857947E1D9275348996691493C2E09B93AA8F7E0E98D66C14D7039C6F19666A1296F5D5ED9ACD1FDA975D2A3B1C587BFBC5870526C7FD59C8A329317EF20CC16B5AA43C39C097D803B8360A6D09AE898F75F1167F374588C5F2223C69ECE2258C77D28787E1A4D44F4ECBD8F5DF07A2EB3BBFF13FB515C42FD4C39852018-02-14 17:19:42,807 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - DESTIP: 192.168.112.1292018-02-14 17:19:42,808 [qtp3715863-35] DEBUG com.github.mob41.blapi.BLDevice - DESTPORT: 802018-02-14 17:19:42,808 [qtp3715863-35] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA5500000000000000000000000000000000000000000000000084CDF9FF2A27E903177F34EA34E3C0F06F0CBA90A1C300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

> 2018-02-14 11:31:48,173 [Thread-10] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - done> 2018-02-14 11:31:53,163 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.0RC18) initializing....> 2018-02-14 11:31:56,689 [main] INFO spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...> 2018-02-14 11:31:56,689 [Thread-11] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...> 2018-02-14 11:31:56,689 [Thread-11] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:80> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 50000> 2018-02-14 11:31:56.689:INFO:oejs.Server:Thread-11: jetty-9.4.z-SNAPSHOT> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.> 2018-02-14 11:31:56,689 [main] INFO com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.> 2018-02-14 11:31:56.694:INFO:oejs.session:Thread-11: DefaultSessionIdManager workerName=node0> 2018-02-14 11:31:56.694:INFO:oejs.session:Thread-11: No SessionScavenger set, using defaults> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.> 2018-02-14 11:31:56.694:INFO:oejs.session:Thread-11: Scavenging every 660000ms> 2018-02-14 11:31:56,694 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....> 2018-02-14 11:31:56.694:INFO:oejs.AbstractConnector:Thread-11: Started ServerConnector@15b99c6{HTTP/1.1,[http/1.1]}{0.0.0.0:80}> 2018-02-14 11:31:56.694:INFO:oejs.Server:Thread-11: Started <strong i="5">@105428ms</strong>> 2018-02-14 11:31:58,201 [qtp6417098-22] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]> 2018-02-14 11:32:00,222 [qtp6417098-25] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]> 2018-02-14 11:32:01,694 [main] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Adding Device to Map - host: 192.168.0.3, device Type: RM 2 Pro Plus, mac: 34:ffffffea:34:ffffffc7:ffffff91:3b> 2018-02-14 11:32:01,694 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.> 2018-02-14 11:32:01,709 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...> 2018-02-14 11:32:01,709 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....> 2018-02-14 11:32:01,709 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....> 2018-02-14 11:32:01,714 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....> 2018-02-14 11:32:01,739 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....> 2018-02-14 11:32:01,800 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....> 2018-02-14 11:33:10,621 [qtp6417098-28] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.0.3-272a\",\"name\":\"RM 2 Pro Plus\",\"command\":\"ircommand\",\"data\":\"260096006f6d1d521d511e1b1d511d521d511e511d521d1b1d1b1d1b1d1b1d1a1d521d1b1d1b1d1b1d1b1d1b1d511d521d521d0004cd6f6d1e511d521d1b1d511d521d521d511d521d1b1d1b1d1b1d1b1d1b1c521d1b1d1b1d1b1d1b1d1b1d511d521d521d0004cd706c1d521d521d1b1d511d521d521d511d521d1b1d1b1d1b1d1b1d1b1d511d1b1d1b1d1b1d1b1d1b1d521d511d521d000d050000\"}"> 2018-02-14 11:33:10,626 [qtp6417098-28] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM 2 Pro Plus> 2018-02-14 11:33:10,741 [qtp6417098-28] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA5500000000000000000000000000000000000000000000000098CAF9FF2A27EE03621B34EA34C7913B0600000075D600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

J'ai fait un tcpdump pour une demande en utilisant BlackBeanControl et une avec HA-Bridge. Les deux étaient censés envoyer exactement la même demande. Vous pouvez les ouvrir dans Wireshark.

Ce qui saute aux yeux immédiatement, c'est qu'il semble que HA-Bridge envoie deux requêtes au lieu d'une seule.

J'ai fait un autre tcpdump avec BlackBeanControl, même demande, juste pour montrer ce qui peut varier avec chaque demande.

tcpdump.zip

tcpdump et débogage de la même requête
tcpdump-debuglog.zip

2018-02-16 17:58:11,145 [main] INFO com.bwssystems.HABridge.BridgeSettings - reading from config file: data/habridge.config2018-02-16 17:58:11,219 [main] INFO com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.0RC19) initializing....2018-02-16 17:58:11,219 [main] INFO spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public2018-02-16 17:58:11,220 [main] INFO com.bwssystems.HABridge.SystemControl - System control service started....2018-02-16 17:58:11,221 [Thread-16] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ...2018-02-16 17:58:11,221 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket...2018-02-16 17:58:11,221 [Thread-16] INFO spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on 0.0.0.0:802018-02-16 17:58:11,221 [main] INFO com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 500002018-02-16 17:58:11,221 [main] INFO com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created.2018-02-16 17:58:11,221 [main] INFO com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured.2018-02-16 17:58:11.221:INFO:oejs.Server:Thread-16: jetty-9.4.z-SNAPSHOT2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created.2018-02-16 17:58:11,222 [main] INFO com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. No Domoticz devices configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured.2018-02-16 17:58:11,223 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink discover....2018-02-16 17:58:11.224:INFO:oejs.session:Thread-16: DefaultSessionIdManager workerName=node02018-02-16 17:58:11.224:INFO:oejs.session:Thread-16: No SessionScavenger set, using defaults2018-02-16 17:58:11.224:INFO:oejs.session:Thread-16: Scavenging every 660000ms2018-02-16 17:58:11.226:INFO:oejs.AbstractConnector:Thread-16: Started ServerConnector@231e3d{HTTP/1.1,[http/1.1]}{0.0.0.0:80}2018-02-16 17:58:11.226:INFO:oejs.Server:Thread-16: Started <strong i="5">@92738ms</strong>2018-02-16 17:58:12,498 [qtp9968991-27] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-16 17:58:14,507 [qtp9968991-30] INFO spark.http.matching.MatcherFilter - The requested route [/description.xml] has not been mapped in Spark for Accept: [application/json, text/plain, */*]2018-02-16 17:58:16,225 [main] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Adding Device to Map - host: 192.168.0.3, device Type: RM 2 Pro Plus, mac: 34:ffffffea:34:ffffffc7:ffffff91:3b2018-02-16 17:58:16,225 [main] INFO com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created.2018-02-16 17:58:16,245 [main] WARN com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data\group.db - Does not exist or is not readable. continuing...2018-02-16 17:58:16,246 [main] INFO com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....2018-02-16 17:58:16,247 [main] INFO com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started....2018-02-16 17:58:16,248 [main] INFO com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started....2018-02-16 17:58:16,272 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting....2018-02-16 17:58:16,340 [main] INFO com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready....2018-02-16 17:58:50,485 [qtp9968991-34] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - executing HUE api request to send message to BroadlinkDevice: "{\"id\":\"192.168.0.3-272a\",\"name\":\"RM 2 Pro Plus\",\"command\":\"ircommand\",\"data\":\"260096006f6d1d521d511e1b1d511d521d511e511d521d1b1d1b1d1b1d1b1d1a1d521d1b1d1b1d1b1d1b1d1b1d511d521d521d0004cd6f6d1e511d521d1b1d511d521d521d511d521d1b1d1b1d1b1d1b1d1b1c521d1b1d1b1d1b1d1b1d1b1d511d521d521d0004cd706c1d521d521d1b1d511d521d521d511d521d1b1d1b1d1b1d1b1d1b1d511d1b1d1b1d1b1d1b1d1b1d521d511d521d000d050000\"}"2018-02-16 17:58:50,486 [qtp9968991-34] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - calling BroadlinkDevice: RM 2 Pro Plus2018-02-16 17:58:50,651 [qtp9968991-34] DEBUG com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - RM2 Device data return: <<<5AA5AA555AA5AA5500000000000000000000000000000000000000000000000098CBF9FF2A27EE038FEE34EA34C7913B0600000075D600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>>>

Rien n'est envoyé depuis Broadlink. Aucune lumière LED ne scintille non plus.

tcpdump-debuglog.zip
Même procédure que chaque année James

Pas de chance pour moi sur le front RM. Pas de message d'erreur, mais pas de travailleur non plus. J'ai remarqué sur mon autre pont qu'une adresse MAC est utilisée, pas seulement IP. Je ne sais pas de quoi je parle, mais je pensais juste que je le mentionnerais.

À votre santé.

@hphde Quelque chose doit avoir changé dans vos paramètres. Cela n'aurait pas dû changer.

Jusqu'à présent, dans mon débogage et en utilisant la bibliothèque python comme base de test. Il semble que le message de datagramme de Java ne soit pas également répondu même s'il est configuré de la même manière que l'appel python. Faire beaucoup de traçage du réseau pour résoudre.

Je peux confirmer un succès partiel. Les commandes IR fonctionnent maintenant pour moi. Avec RF, j'ai eu un succès partiel. L'un fonctionnait, l'autre non. Celui qui ne fonctionnait pas n'a montré aucune erreur sur l'interface utilisateur. Ensuite, j'ai réalisé que la requête JSON avait reçu un 500.

2018-03-06 09:46:48,794 [qtp12509699-14] ERROR com.github.mob41.blapi.pkt.CmdPacket - Cannot encrypt payload! Abortingjavax.crypto.IllegalBlockSizeException: Input length not multiple of 16 bytes

Les codes de travail avaient une longueur de 728 = 45 16 + 8, les codes

Pour le truc utilisateur / mot de passe, je suis revenu à 5.1.0 qui ne m'a donné aucun utilisateur, puis j'ai ajouté un utilisateur. Après cela, j'ai pu utiliser RC23 avec un utilisateur et un mot de passe. Après avoir supprimé l'utilisateur, tout allait bien à nouveau.

Après quelques débogages aujourd'hui, je crois que tout fonctionne.

Pour vous assurer que la nouvelle version fonctionne correctement, vous devrez supprimer et recréer vos appareils avec le générateur. Plus d'informations sont nécessaires dans les URL de l'appareil pour garantir qu'il fonctionne.

RC24 est en place

@bwssytems donc le remplissage ne fonctionne pas. La bonne chose: une erreur apparaît dans l'interface graphique au lieu de seulement 500 en arrière-plan.

Pour la découverte, j'ai le même que @quadhammer - le périphérique nouvellement ajouté n'apparaît pas

ha-bridge.jar.log

L'onglet Broadlink a disparu, mais Alexa peut à nouveau découvrir les appareils du Bridge. J'ai réglé le délai d'envoi UPNP sur «500».

»

INFO | Broadlink découvrir .... | com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
- | - | -
08/03/2018 10: 32: 42.817 | INFO | La route demandée [/description.xml] n'a pas été mappée dans Spark pour Accept: [application / json, text / plain, / ] | spark.http.matching.MatcherFilter
08/03/2018 10: 32: 44.839 | INFO | La route demandée [/description.xml] n'a pas été mappée dans Spark pour Accept: [application / json, text / plain, / ] | spark.http.matching.MatcherFilter
08/03/2018 10: 32: 46.854 | INFO | La route demandée [/description.xml] n'a pas été mappée dans Spark pour Accept: [application / json, text / plain, / ] | spark.http.matching.MatcherFilter
03-08-2018 10: 32: 47.601 | INFO | Broadlink découvrir a trouvé 1 clients. | com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome
03-08-2018 10: 32: 47.601 | INFO | Création de Broadlink Home. Aucun Broadlinks configuré. | com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome

»

@quadhammer Dans votre onglet 'Bridge Control', avez-vous coché "Broadlink Support"?

Il semble que j'ai oublié de mettre dans la validation pour ne pas découvrir si elle n'a pas été cochée. L'onglet Broadlink est également contrôlé par ce paramètre.

Cette page vous a été utile?

0 / 5 - 0 notes