-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Microphone not working on 4 boards #86
Comments
Did you take the file and flashed without any changes? And what version? What you should do is scale down to debug - test both the openWakeWord and microWakeWord edition. I hardly believe you've received 4 boards from PCBWay with defective mics (but who knows) |
Thanks. No, I compared my yaml with the original one, it's really only minor changes such as the webserver and network info. I've enabled debug logging too but didn't give extra info apart from the lack of voice. |
I suggest to use the official ESPHome firmware and tools as a test here. https://github.com/justLV/onju-voice if this fails, too then your only step helping here is reporting faulty boards over at PCBWay. I got my 5 boards from them, too and the only thing they are really bad at in my case are the LEDs. Looks like they don't survive the solder bath. I had to fix about 50% of them. Some did not work on one or two colors, some were completely dead. But the microphone never was a flaw here. Btw, the mic used is the one from the Google hardware. You sure that the ribbon cable is really sitting correctly? |
I will try the original yaml when I'm back home, though I dont think it will make much difference. About the mic, that's not the Google hardware, it's the 2 small holes in the print on both sides. The Google part is just the speaker. |
I had a weird mic problem that never got satisfactorily solved. It seems the issue was with the actual nest hardware - i swapped the same board to a different speaker housing and it worked fine. Put another board into the first speaker housing and it also didn't work. Couldn't for the life of me figure it out. Tried trimming the foil back, looked at the working and not working ones with a magnifying glass. Nothing! Gave up in frustration and binned the nest. |
Looks like you are right. There a parts with a M on both sides. Did not expect that the mics are that good and instead really thought the ribbon cable has enough contacts for a mic. Ok. Still I have none of these problems and really look forward to the test results. |
I just installed the yaml without the wake word. Only had to set a fixed ip and an api encryption key. It seems to a bit further but I doubt if it really notices my voice. I tested with "can you turn off the office lights" and then you get: A part of the logs:
|
Some testing firmware which records and plays back a sample would be nice for such cases... But everything sounds like the next step is reporting back to PCBWay and ask for support there... |
I will do that, lets make it their issue. Thanks all so far. |
Flavor
MicroWakeWord
Checklist
Describe the issue
It's most likely not related to the esphome config of onju voice but I can really use some help and hints. I ordered 5 boards, so far I've tried 4 of them. Flashed them, did the hardware switch, checked the yt movies 10 times.
Buttons work, speaker works, leds work, home assistant integration works but the microphone seems broken. When I use a wake word, nothing responds, leds remain the same and I dont see anything in the logs. Whenever I tap the top and initiate listening (I see that in the logs,) but nothing is received and it times out.
For me it's hard to believe there's a hardware issue in 4 boards and both microphones. Did I make some silly mistake or how can I test this?
Thanks in advance, if it's inappropriate filing an issue, let me know.
Edit: My config is almost identical, just some standard changes in the first part:
https://github.com/robsonke/hass-config/blob/master/esphome/onju-voice-satellite-3.yaml
Reproduction steps
Debug logs
No response
The text was updated successfully, but these errors were encountered: