I would LOVE to see 48kHz! 
Have no idea on JTAG pinout, but I think it’s worth trying to ask on Seeed Discord.
That’s the listen light LED. That’s why it’s not enabled by default. Even though my listen LED doesn’t work if I expose that and say the wake word “ok nabu” it turns on and changes colors as it progresses along with the voice pipeline. When the command ends it turns back on. Seems to emulate the on board LED but since mine doesn’t work then I can’t verify but pretty positive that’s all it does.
Are we all still on the same page? I didn’t expose the LED in config, dod you do it to test?
Yeah exactly what I was thinking.
Question: Does your perform poorly as well?
Doesnt seem like this is better than another one I built with esp32-s3-devkitc-1(N16R8).
It’s way better for me. I have 3 S3-based satellites with INMP mic.
Interesting. Could it be the host/VM spec?
I am on a 13th Gen 32GB no graphics card Win 11 Pro system.
Home Assistant on VM player with basic settings.
2 CPU/2 GB
I don’t think it matters really. Although STT can give difference. But it depends on where you have troubles: wake word, speech-to-text, or noise cancelling.
I received my ReSpeaker Lite Kit yesterday.
All is working, except the RGB LED isn’t, or barley.
When using the Arduino LED example, it shows the initial colour set (all colors work fine) but then only a power cycle helps to set a new color.
GND & VCC is fine, but I measure like 300 kOhms between GPIO1 and DI of the LED, seems a little high. There is activity on GPIO1 when the LED should be ON, will hook up my Oscilliscope later. Could anyone with working LEDS quickly verify what resistance is between GPIO1 and DI?
I measured mine and have pretty same value. ~400kOhm. My LED is working.
1 Like
However, i have another board, to which i soldered S3 myself. Has +5V across and working connection DIN-GPIO1 with same resistance. But LED doesn’t work.
I have no idea why but yes, using your yaml it shows up as disabled by default, If I enable it it goes through the voice pipeline colors in the UI but the LED still doesn’t work. I have zero idea why it’s but it does. I just cleaned the build files and installed after deleting the integration to be sure.
I like the new little on boarding process they have. Not sure when that was added. After saying the wake word twice, then the last pic comes up. After that it prompts you for the voice pipeline to use so it does everything you need, especially if you have multiple voice pipelines like I do. Since they removed the binary sensor it’s still there but hidden by default and “Assist Satellite” takes it’s place.
Personally, I think it works better then the S3 box when not using the touchscreen button on the S3 to hold and let go to stop listening. Not sure if that could be done with the USR button on the respeaker lite board or not but I would say it’s a close second to my dedicated speakerphone plugged into my HA server using Assist Microphone. To my understanding that add on is supposed to at least utilize some of the DSP tech in whatever USB device it’s plugged into. I would say it’s equal to a wyoming satellite with room to improve over time. Maybe not this particular model, but future versions, like nabu’s and others.
Yeah, it’s pretty cool device. Onboarding process is nice, but for some reason it removed my TTS from my pipeline after setup, so I had to set it again (after several minutes of confusion why my satellite does work but doesn’t speak).
I got 2x bare boards too, and tried to solder my own XIAO S3 to one of them. S3 works, Respeaker works via USB with Mac - but doesn’t work with board. Triple checked LED connection to GPIO1 and 5v/gnd - but LED doesn’t work too…
I’m trying to get to Seeed support, but they stopped responding… Shame. I’d gladly have 2 more good satellites for my home.
Hi Guys,
First of all forgive me for my ignorance I am new to all this stuff!
So from what I understand.
-
I have to build ESPHome for the S3, this then uses a YAML file to work out how to talk to the audio side of the board.
-
Currently it is only 16K in and 16K out, but it looks like there is the possibility of 48K out in the future.
Is the best YAML to use from @formatBCE : Create esphome-respeaker-lite.yaml · formatBCE/Random-snippets@5eef002 · GitHub ?
I’m guessing there is some kind of server needed somewhere as well (Home Assistant)? I also need to install this on a PI?
Am I on the right track here or am I hopelessly confused
Thanks
Andy
All you said is about to be right, but you’re starting from the end. For people here, HA is the goal, and Respeaker is the tool. If you gonna install HA and ESPHome solely to work with Respeaker - don’t. My YAML does one thing: connects Respeaker as satellite to HA voice assistant.
If you want to work with board, there are examples of Arduino IDE code for it, which will get you running much faster, and without dependency on HA server.
2 Likes
Everyone having troubles with getting kit to work - try flashing this firmware to XMOS. They’re updating Wiki as i write too.
1 Like
Also just confirmed, that soldering back pins isn’t necessary, just side ones.
Another news: mute state isn’t exposed as of now, but will be exposed in next XMOS firmware update. Great news, software mute will be available (REAL mute, not just wake word cut-off).
1 Like
Thanks for all the info @formatBCE
I’m after using it for a few things really.
- Controlling the bulbs in the house (Tapo and Phillips)
- Listening to the radio.
- Developing a decent white noise app.
- just a bit of learning!
I got HA installed and running on a PI4, had a bit of trouble with the MTU being too high which was fun to sort out!
I also managed to get HA so it is controlling one of the tapo bulbs for testing.
I can’t get the re speaker do do anything though, it connects correctly, but it’s not listening to a word I say
The log also contains these at intervals:
[06:09:34][W][api.connection:107]: : Reading failed: BAD_INDICATOR errno=11
I will give your firmware a go after a coffee and get back to you.
Once again thanks for the help
Andy
1 Like
Thanks for pointing that out.
On the wiki the changelog is also available:
Change log :
v1.0.7 : support i2c control speaker mute and output channels
v1.0.6 : change PRODUCT_STR to ReSpeaker Lite, fix ws2812 control bug
v1.0.5 : support i2c read vnr value
Anyways, this also fixed my LED issue, now the RGB Led is working.
Would be great to get the schematics, as the LED does not seem to be connected to the ESP directly.
3 Likes
It is connected directly. You can try with multimeter.
Case was that 1.0.5 had a bug, that prevented it from flashing to the board correctly, although it reported success in dfu output, but in reality it was still USB firmware. At least that’s what happened to both my boards.
We investigated and confirmed this with Seeed support, and they quickly made the patch.
I asked them about schematics. Not available at the moment, but they promised to arrange them for the community - all in all, dev kit without dev docs is a bummer…
1 Like
Hi Guys,
I got to the bottom of why mine didn’t work, it seems that the issue was using HA and the ESPHome page and possibly building on the host (which is a Pi4).
After another few wasted times I thought I would install ESPHome on the PC and get the debugger out to see what was going on, I removed the devices in HA, flashed the respeaker from the pc, it appeared as a device so I added it and bang it worked!
The wake word works well but the speech recognition is awful. I’m using the recommended setup with faster-whisper, is there a better solution?
Thanks
Andy
edit: Also is there a way of controlling the volume easily?