-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Total conversion as Mycroft physical entry point #6
Comments
Humh, I realise that the effective question is: how is transported the recorded sound? |
That would be very elegant... The nabaztag will simply send and receive audio but is capabilities will be extended dramatically. |
This is also another way https://www.hackster.io/bastiaan-slee/nabaztag-gets-a-new-life-with-google-aiy-e9f2c8 |
I think creating a Frankenstein Nabaztag (replacing the "brain" with a raspberry pi) is much easier then patching the original firmware. Unfortunately the original hardware&firmware are not documented and it's quite difficult to debug. |
There is a project about porting the firmware to gcc and there are some audio functions in there so, this might be actually doable |
Hi,
I still have a working Nabaztag:tag. The Nabaztag was a good project, but it seems that its main idea is revived as the new movement of Home Assistants (Google Home, Amazon Echo...).
All this services are closed, all but one: Mycroft.
Do you think it is possible to continue your project in order to convert the Nabaztag as the physical device of the Mycroft project? I imagine we will need to:
Reading the status of the project, I think all of this seems possible. Do you see any difficulties?
The text was updated successfully, but these errors were encountered: