Nicolas Marcq

It is not usable with a playbook that use sudo with password. Beause the sudo password is never the same between our workstation and target servers You should document the...

Fell free to create you own neuron. Spotify is not available yet. And you can already talk to Home Assistant via the API (use the URI neuron)

Could be a nice feature. I don't know how to implement it, but it would be nice. The problem is, if we keep Kalliope listening for a new order while...

@LaMonF do we keep this opened? The fact also is that we will need to keep snowboy alive to handle this feature. And, as you know, this last is very...

The snowboy process is killed after matching a hotword because it cost too much resource on a RPI. We cannot keep it alive. And, in most of case, the speaker...

You cannot keep the STT (you wrote TTS but I suppose you are talking about the STT) process alive because this one need a start and a stop to know...

Yes the TTS could be placed in a thread. But this is not this issue here. Give a try if you want, on your RPI, just keep the snowboy process...

The current design doesn't allow that. The LIFO for processing orders is unique. You cannot have two execution in the mean time.

I like the idea, but I'm not sure about the implementation. Would it not be better to update the current "on_order_found" hook to receive the order and so call a...

Actually, it's even already possible to do it. With the master code, could you try something like this? Settings: ```yml hooks: on_order_not_found: "answer-of-everything-all" ``` Brain: ```yml - name: "answer-of-everything-all" signals:...