Read the statement by Michael Teeuw here.
Kalliope assistant + MM
-
@marcnlx why are you trying to reach the URL from your browser? It’s an API. It should be accessed from a script only.
-
@sispheor said in Kalliope assistant + MM:
@marcnlx why are you trying to reach the URL from your browser? It’s an API. It should be accessed from a script only.
The CURL example gave me this output on the CLI. I was only using my browser to make sure I was able to reach the API.
Any idea what configuration mistake I could have made?
-
@marcnlx @marcnlx you’ve set http://127.0.0.1:8080/kalliope for the neuron but the mirror up is 192.168.1.16. doesn’t it?
Also, notification and payload are not needed in the config of the module.
-
@sispheor said in Kalliope assistant + MM:
@marcnlx @marcnlx you’ve set http://127.0.0.1:8080/kalliope for the neuron but the mirror up is 192.168.1.16. doesn’t it?
Also, notification and payload are not needed in the config of the module.
@sispheor 127.0.0.1 is the localhost IP, 192.168.1.16 is the external IP…the Magic Mirror is available on every IP in use on the RPi (listening address is set to 0.0.0.0).
I just commented out the notification and payload and thing are now showing on the Mirror! This is really cool! :)
Okay…now I need to figure out how to build the whole virtual assistant…on to “phase #2”.
In your demo video I saw a basically complete brain…is there any place where I can find that one? ;) -
@marcnlx take a look to starter kits. It contains example. Also there is an example of usage of each neuron on the website.
Have fun ! -
@sispheor said in Kalliope assistant + MM:
@marcnlx take a look to starter kits. It contains example. Also there is an example of usage of each neuron on the website.
Have fun !I will! I’m going to check everything out later today, thanks!
-
I tested Kalliope yesterday night and once you know how it works, it’s pretty sweet! ;)
Unfortunately I noticed some bugs/issues which are discussed multiple times on Github, so for now I think I will wait until a later release since I need to restart Kalliope multiple times after 2-3 phrases because of pulseaudio issues which I can’t seem to fix:
2018-03-18 12:42:27 :: kalliope-0.5.1b :: File found in /home/pi/kalliope_starter_en/trigger/kalliope-EN-12samples.pmdl Exception in thread Thread-2: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run()File "/usr/local/lib/python2.7/dist-packages/kalliope-0.5.1b0-py2.7.egg/kalliope/trigger/snowboy/snowboydecoder.py", line 98, in __init__ stream_callback=audio_callback) File "build/bdist.linux-armv7l/egg/pyaudio.py", line 750, in open stream = Stream(self, *args, **kwargs) File "build/bdist.linux-armv7l/egg/pyaudio.py", line 441, in __init__ self._stream = pa.open(**arguments) IOError: [Errno -9985] Device unavailable -
@marcnlx Uninstall pulse audio and work only with alsa.
We’ve remove pulseaudio from our doc. -
Kalliope v0.5.1 has been released with all stuff needed to integrate Magic Mirror.
-
@sispheor kalliope uses the Google Speech recognition?
-
@maxbachmann google is the default, but you can select others https://kalliope-project.github.io/kalliope/settings/settings/#speech-to-text-configuration
-
@maxbachmann Yes you can choose your STT and TTS engine. Some are cloud based and some can be self hosted.
-
@sispheor I am interested in duplicating your work for a different AI. So I figured the best place to start is to install your module and get it working before I make changes to suit my needs with the other AI. I have installed the MMM-Kalliope module, but the curl commands do not display on my mirror. I am not sure what I am doing wrong. Here’s my entry in config.js
{ module: "MMM-kalliope", position: "upper_third", config: { max: "5", keep_seconds: "8", title: "Kalliope" } },I do receive a json response indicating success, however, nothing gets displayed on the mirror.
Here’s the curl command:
curl -H "Content-Type: application/json" -X POST -d '{"notification":"KALLIOPE", "payload": "my message"}' http://localhost:8080/kalliopeHere’s the response:
{"status": "success"}Yet nothing gets displayed. Do you have any suggestions?
-
@dmwilsonkc seems good anyway.
I don’t see any errors. Maybe test another position. This one is not already used by another module? -
@sispheor I’ve tried multiple positions for the module, still nothing gets displayed. Not sure why though. I’ve tried refresh, reboot etc. still nothing. Maybe I should delete the module and try a fresh install. The curl should work with just the module installed right?
-
@sispheor trying to help, I installed the module on my mirror… but… curl notifications don’t work…
is there an install step missing? or a package.json that defines the install process for the dependencies?
cut paste from the module readme…
~/MagicMirror/modules$ curl -H "Content-Type: application/json" -X POST -d '{"notification":"KALLIOPE", "payload": "my message"}' http://localhost:8080/kalliope curl: (7) Failed to connect to localhost port 8080: Connection refusednetstat shows nothing listening on 8080
so, my mirror is NOT on 8080, but 8086, due to other components on the normal MM ports…
you should update the instructions to say use the MM port on the curl…
now… I got the notification, and see the debug log (ctrl-shft-i) say
MMM-kalliope received a socket notification: KALLIOPE Payload: my messageand the content shows for the configured amount of time (8 seconds per the above config settings)
-
@sispheor So using the ctrl-shift-i I was able to find the error that it is throwing.
Uncaught TypeError: console.log is not a functionThis error is repeated in the log each time it receives the post request.
What are your suggestions?
-
@dmwilsonkc edit the MM/modules/MMM-kalliope/MMM-kalliope.js and change all console. to Log.
console.log is ONLY allowed in the node_helper.js and Log.log is ONLY allowed in the module.js
-
@sispheor So… I figured out how to get rid of the error. I deleted line 86 of MMM-kalliope.js .
console.log(this.name + " received a socket notification: " + notification + " - Payload: " + payload);Everything works fine for now. Not sure why this is, but I’m assuming the chromium browser does not like the console.log code, but I could be wrong.
-
@sdetweil huumm… yes it is obvious that you have to call your magic mirror url. Including the port if you changed it.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login