Oh gosh! Super complicated! Thank you for your work an motivation! The LED fancy blinking personally isnt the most important feature for me, as long the speach recognition gets way better than VP, I am more than happy.
1 Like
There should already be a configuration for this ready for Homeassistant…
what do you think about it?
At this point I think it’s necessary to open a separate topic for this too…
Let me know how it goes… and how the voice recognition works. I hope you also have a Respeaker Lite for comparison.
That config you posted is based on my old config for Respeaker Lite.
Yes, XVF3800 should have dedicated thread.
It goes well, I’m progressing with components and effects. It’s 90% ready for public testing, I’d say.
1 Like
So… it’s not good?
or is it not using the HW type well?
It’s just first bare try to verify I2C is working. There’s no DAC code, no LED code, just small PoC by Seeed. It’s not in any way working code. 
1 Like
Right now I have XVF3800 running with Seeeds Solution.
Voice is working as intended but the LED handling is super annoying. its blinking all the time to indicate from which direction it detects incoming sound. Voice handling itself there is no LED indication ^^
From the voice quality I would say its working better but still need to test more.
1 Like
2 Likes
Thank you so much. I just installed it. I really like how the LEDs are now behaving! I will test it and report back if I run into issues.
1 Like
I’ve created dedicated thread.
2 Likes
what do you advise: the model with or without the XIAO ESP32-S3?
Depends on what you need. The kit with S3 is easier to start (like, very easy, you basically just need to jump-solder mute and user buttons to the pads, and it works). But if you want a bit of customizability like adding LEDs, buttons/knob for volume etc. - then you need your own ESP32 chip, to get those free GPIO pins.
2 Likes
Just a question: Can I add an LD2410 to the Respeaker Lite? The KoalaProject is definitely more suitable… but since I now have two Respeaker Lites, I would like to know if and where I can solder the TX and RX pins of the LD2410.
EXIT: I saw what the TX and RX pins of the XIAO ESP32S3 are… but I don’t understand if they are already used or not… or at least I don’t understand it from the YAML configuration
All pins there are used.
If you want to use at least something, you will have to unsolder mute and usr from d2/d3 (thus losing their functionality), and use them as Rx and Tx for 2410…
1 Like
Perfect!
very helpful thanks!
1 Like
just a question…
I have a few Assistant devices at home… and automations:
The microphone will activate and deactivate if someone is in the room:
“If someone is in the room, turn off mic mute.”
“if no one is in the room, activate MIC MUTE”
alias: TEST1
description: ""
triggers:
- type: occupied
device_id: cd5f0675a5f043fb274deda216c970d8
entity_id: 8766a705421c9b435a3a584814fdd5ba
domain: binary_sensor
trigger: device
conditions: []
actions:
- type: turn_off
device_id: 3ba1737037b54ee48e5087480e23c65f
entity_id: ad49aeadf9b5fec9b4a4fa9c5023fca9
domain: switch
mode: single
but it doesn’t work properly.
The problem is that the “deactivate MIC MUTE” (or activate) option works like a toggle, not like an “on/off” switch.
If the action “deactivate MIC MUTE” is performed 2 times… it will activate again it doesn’t stay off
this is the action:
type: turn_off
device_id: 3ba1737037b54ee48e5087480e23c65f
entity_id: ad49aeadf9b5fec9b4a4fa9c5023fca9
domain: switch
(This doesn’t happen on other ESP32S3-based Home Assistant devices. Only on Respeaker)
Do you know what this problem depends on?
Thank you
I have similar automations and they work great.
The rule of thumb (always!): don’t use those “device” actions. They’re flaky and unreliable.
Use regular calls like “Switch: turn off”.
Like this:
- action: switch.turn_off
target:
entity_id: <your_mute_switch_like_switch.my_satellite_mute_microphone>
is mine not regular?
I use the visual configuration to create Automations…
No, you use action “Device”. Use action “Switch: Turn off”.
alias: Test1
description: ""
triggers:
- trigger: state
entity_id:
- binary_sensor.presenza_esp32c3_letto_presence
to: "on"
conditions: []
actions:
- action: switch.turn_off
target:
entity_id: switch.respeaker_mic_mute
data: {}
mode: single
still working as a tougle and not like a switch ON/OFF… if I repeat the action 2 times it will switch ON instead of staying OFF
Geez, you’re right!
I NEVER noticed this. Both turn_on and turn_off work like toggle.
I will see what I can do to fix this. So far you can check before action. Like - if state is on, turn off.
1 Like