Aucunes actions jeedom


#1

Bonjour.

J’essaye d’activer le mode cinéma sur jeedom depuis snips mais je n’y arrive pas.

Ma structure :

  • snips server sur VM debian
  • snips satellite “salon” sur rpi3 avec respeacker pi hat 2

J’ai pris l’app de valf que j’ai fork et j’ai rajouté “active le mode cinéma” comme training example pour TurnOnJeedom avec “cinéma” comme device_name.

Quand je dis “active le mode cinéma”, dans la console de snips (avec sam watch) j’ai bien TurnOnJeedom avec device_name = cinéma.

Dans les logs de jeedom j’ai :

[2018-11-25 14:58:05][DEBUG] : [logmq] code: 16 : Client mosq/rxAgv0FOnPV5]ntBoM received PUBLISH (d0, q0, r0, m0, ‘hermes/hotword/default/detected’, … (151 bytes))
[2018-11-25 14:58:05][DEBUG] : [message] Received message. Topic:hermes/hotword/default/detected
[2018-11-25 14:58:06][DEBUG] : [logmq] code: 16 : Client mosq/rxAgv0FOnPV5]ntBoM received PUBLISH (d0, q0, r0, m0, ‘hermes/dialogueManager/sessionStarted’, … (119 bytes))
[2018-11-25 14:58:06][DEBUG] : [message] Received message. Topic:hermes/dialogueManager/sessionStarted
[2018-11-25 14:58:17][DEBUG] : [logmq] code: 16 : Client mosq/rxAgv0FOnPV5]ntBoM received PUBLISH (d0, q0, r0, m0, ‘hermes/dialogueManager/sessionEnded’, … (122 bytes))
[2018-11-25 14:58:17][DEBUG] : [message] Received message. Topic:hermes/dialogueManager/sessionEnded

Je ne sais pas ce que sa veut dire mais à priori la communication se fait bien.

Dans le plugin snips, je suis allez dans TurnOnJeedom et j’ai attaché un scenario en callback. Je n’ai rien touché d’autre.

Ce scénario est juste un envoi de notification pushover pour tester. Bien sûr si je test le scénario, sa fonctionne bien.

Je n’ai pas rajouté d’action binding (j’avais test mais ça ne fonctionnait pas plus).

Normalement je n’ai rien oublié mais il ne se passe rien. Rien dans les logs snips, rien dans les logs jeedom (à part ceux ci-dessus) et pas de notification.

Il y a t’il quelque chose que j’ai oublié ? Ou peut-on debug un peu plus ce que reçois jeedom de la part de snips ?

Merci pour votre aide.

Édit : jeedom est installé sur cubieboard2 et non sur rpi. Le problème peut il venir de la ?


#2

Pareil, mes actions ne sont pas récupérées par jeedom, pourtant les logs jeedom semblent dire que la comm entre le “maitre” et le satellite se fait bien.
pour info les logs côté jeedom :
[2019-01-02 19:41:16][DEBUG] : [logmq] code: 16 : Client mosq/]>rl^t3jo63X?T_Zmreceived PUBLISH (d0, q0, r0, m0, 'hermes/hotword/default/detected', ... (173 bytes)) [2019-01-02 19:41:16][DEBUG] : [message] Received message. Topic:hermes/hotword/default/detected [2019-01-02 19:41:16][DEBUG] : [logmq] code: 16 : Client mosq/]>rl^t3jo63X?T_Zm received PUBLISH (d0, q0, r0, m0, ‘hermes/dialogueManager/sessionStarted’, … (123 bytes))
[2019-01-02 19:41:16][DEBUG] : [message] Received message. Topic:hermes/dialogueManager/sessionStarted
[2019-01-02 19:41:16][DEBUG] : [logmq] code: 16 : Client mosq/]>rl^t3jo63X?T_Zmreceived PUBLISH (d0, q0, r0, m0, 'hermes/dialogueManager/sessionStarted', ... (123 bytes)) [2019-01-02 19:41:16][DEBUG] : [message] Received message. Topic:hermes/dialogueManager/sessionStarted [2019-01-02 19:41:21][DEBUG] : [logmq] code: 16 : Client mosq/]>rl^t3jo63X?T_Zm received PUBLISH (d0, q0, r0, m0, ‘hermes/intent/valf:CloseCoverJeedom’, … (1167 bytes))
[2019-01-02 19:41:21][DEBUG] : [message] Received message. Topic:hermes/intent/valf:CloseCoverJeedom
[2019-01-02 19:41:21][DEBUG] : [message] Find a snips device which is not in the list:satellite
[2019-01-02 19:41:21][DEBUG] : [postSave] post saved
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Intent:valf:CloseCoverJeedom siteId:satellite sessionId:63bf772e-d8f0-4ad0-bab0-2336b9e3dab2
[2019-01-02 19:41:22][DEBUG] : [extractSlotsValues] Checking slots: window_devices
[2019-01-02 19:41:22][DEBUG] : [extractSlotsValues] No, this does not exist in the array :window_devices
[2019-01-02 19:41:22][DEBUG] : [extractSlotsValues] Checking slots: house_room
[2019-01-02 19:41:22][DEBUG] : [extractSlotsValues] No, this does not exist in the array :house_room
[2019-01-02 19:41:22][DEBUG] : [setSlotsCmd] Set slots cmd values
[2019-01-02 19:41:22][DEBUG] : [setSlotsCmd] Slots name is :window_devices
[2019-01-02 19:41:22][DEBUG] : [setSlotsCmd] Slots name is :house_room
[2019-01-02 19:41:22][DEBUG] : [executeCallbackScenario] Intent: valf:CloseCoverJeedom
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Cur binding name : Fermer volets salle à manger
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Binding count is : 1
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Snips count is : 2
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Cur binding name : fermer volets cuisine
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Binding count is : 1
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Snips count is : 2
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Cur binding name : fermer volets salon
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Binding count is : 1
[2019-01-02 19:41:22][DEBUG] : [findAndDoAction] Snips count is : 2
[2019-01-02 19:41:22][DEBUG] : [generateFeedback] Generating feedback text
[2019-01-02 19:41:22][DEBUG] : [generateFeedback] The 0 variable cmd is not set
[2019-01-02 19:41:22][DEBUG] : [playTTS] Player: #[Snips-Intents][Snips-TTS-satellite][say]# Message: Désolé maître, je ne suis qu’un puits de sottise… Title: default
[2019-01-02 19:41:22][DEBUG] : [execute] cmd: say
[2019-01-02 19:41:22][DEBUG] : [execute] siteId: satellite asked to say :Désolé maître, je ne suis qu’un puits de sottise…
[2019-01-02 19:41:22][DEBUG] : [sayFeedback] Publish: Désolé maître, je ne suis qu’un puits de sottise…
[2019-01-02 19:41:22][DEBUG] : [publish] published message: {“text”:“D\u00e9sol\u00e9 ma\u00eetre, je ne suis qu’un puits de sottise…”,“sessionId”:“63bf772e-d8f0-4ad0-bab0-2336b9e3dab2”} to topic: hermes/dialogueManager/endSession
[2019-01-02 19:41:23][DEBUG] : [resetSlotsCmd] Reset all the slots
[2019-01-02 19:41:27][DEBUG] : [logmq] code: 16 : Client mosq/]>rl^t3jo63X?T_Zmreceived PUBLISH (d0, q0, r0, m0, 'hermes/dialogueManager/sessionEnded', ... (126 bytes)) [2019-01-02 19:41:27][DEBUG] : [message] Received message. Topic:hermes/dialogueManager/sessionEnded [2019-01-02 19:41:33][DEBUG] : [logmq] code: 16 : Client mosq/]>rl^t3jo63X?T_Zm received PUBLISH (d0, q0, r0, m0, ‘hermes/dialogueManager/sessionEnded’, … (126 bytes))
[2019-01-02 19:41:33][DEBUG] : [message] Received message. Topic:hermes/dialogueManager/sessionEnded

et logs sam sur le master :

[18:41:20] [Asr] captured text "ferme les volet de la cuisine" in 3.0s
[18:41:20] [Asr] was asked to stop listening on site satellite
[18:41:20] [AudioServer] was asked to play a wav of 93.1 kB with id '465bed91-89a3-4d09-a535-4c55ce7e4f5b' on site satellite
[18:41:21] [AudioServer] finished playing wav with id '465bed91-89a3-4d09-a535-4c55ce7e4f5b'
[18:41:21] [Nlu] was asked to parse input "ferme les volet de la cuisine"
[18:41:21] [Nlu] detected intent valf:CloseCoverJeedom with probability 1.000 for input "ferme les volet de la cuisine"
              Slots ->
                 window_devices -> volets (confidence: 0.500)
                     house_room -> cuisine (confidence: 1.000)
[18:41:21] [Dialogue] New intent detected valf:CloseCoverJeedom with probability 1.000
              Slots ->
                 window_devices -> volets (confidence: 0.500)
                     house_room -> cuisine (confidence: 1.000)
[18:41:22] [Dialogue] was ask to end session with id 63bf772e-d8f0-4ad0-bab0-2336b9e3dab2 by saying 'Désolé maître, je ne suis qu'un puits de sottise...'
[18:41:22] [Tts] was asked to say "Désolé maître, je ne suis qu'un puits de sottise..."
[18:41:22] [AudioServer] was asked to play a wav of 137.2 kB with id '469bd6cd-20d3-4d66-8b04-15f89edee048' on site satellite
[18:41:23] [AudioServer] was asked to play a wav of 137.2 kB with id '4e307dca-8f94-47d4-83eb-cbae7e289a38' on site satellite
[18:41:27] [AudioServer] finished playing wav with id '469bd6cd-20d3-4d66-8b04-15f89edee048'
[18:41:27] [Tts] finished speaking with id '130cf3c7-5fa6-478d-ac4f-b92f2acd8b49'
[18:41:27] [Dialogue] session with id '63bf772e-d8f0-4ad0-bab0-2336b9e3dab2' was ended on site satellite. The session ended as expected
[18:41:27] [Asr] was asked to stop listening on site satellite
[18:41:27] [Hotword] was asked to toggle itself 'on' on site satellite
[18:41:31] [AudioServer] finished playing wav with id '4e307dca-8f94-47d4-83eb-cbae7e289a38'
[18:41:31] [Tts] finished speaking with id '130cf3c7-5fa6-478d-ac4f-b92f2acd8b49'
[18:41:33] [Dialogue] session with id 'b1cc7a74-3d4c-43aa-a61d-7c683eb64b08' was ended on site satellite. The session was ended because one of the component didn't respond in a timely manner
[18:41:33] [Asr] was asked to stop listening on site satellite
[18:41:33] [Hotword] was asked to toggle itself 'on' on site satellite 

J’ai l’impression que c’est un pb similaire, non ?