Read the statement by Michael Teeuw here.
Which Voice Control module is fit for me?
-
@Chris
You’d seemed to try to install python library for Google Assistant. Mine is a standalone node module with grpc API.So below has no relation with my module.
(env) $ googlesamples-assistant-devicetool register-model --manufacturer "Assistant SDK developer" \ --product-name "Assistant SDK light" --type LIGHT --model my-project-1505046981535-my-model1 -
@Peter said in Which Voice Control module is fit for me?:
I learned from this forum that Jessie works better with MM than Stretch, thats why I use Jessie.
I still have Jessie on my Pi mirror. There is no reason to change it. MM is very happy under Jessie. Why would I change it? Don’t fix it if it isn’t broken. :-)
But voice is still a problem …
There is no go-to voice module that works reliably and satisfies everyone’s desires. Whether it’s processing demands, privacy, accuracy, there is much to be improved upon. With that said, and not expecting too much, you might find one of them acceptable. Or, as is my case, I modified one to do what I wanted it to do.
-
@Peter said in Which Voice Control module is fit for me?:
@E3V3A I learned from this forum that Jessie works better with MM than Stretch, thats why I use Jessie.
Yeah, I never had any problem with Stretch, so I think that is just an artificial impression due to less info available, that is based on it. I haven’t seen any facts backing that up. Actually, as a distribution concerned, most stuff just works and what doesn’t is usually the problem of the user (me). No system works out-of-the-box unless you use some pre-compiled image. We hate those, don’t we!?
