Repository navigation
Replies: 6 comments 2 replies
|
Hi, the media negotiation and ESP to ESP routing paths have changed substantially on the current development branches, and the compatibility problems behind this symptom appear to be addressed. Could you please rebuild and upload both devices with the maintained YAMLs pointing to the coordinated For this and future issues or discussions, please attach the complete sanitized YAML for every affected device, the ESPHome logs from both endpoints covering the entire call, the exact call direction, board models, component versions, and the negotiated SIP/SDP details when available. That evidence makes it possible to reproduce the actual configuration instead of guessing from the final Please let us know whether the rebuilt |
|
Hi, I updates my esp's the intercom-living.yaml is based on Waveshare ESP32-P4 Touch LCD, full JPEG videophone but adjusted with GitHub copilot to make it work |
|
sorry i dident try the dev yet |
|
Thanks for attaching both YAMLs. I found a specific mismatch, and the example your Inter3 configuration was based on also needed a correction. Sorry that my earlier suggestion to update alone did not explain it. Both devices send microphone audio at 16 kHz. Living accepts that, but Inter3 only advertises 48 kHz reception. A direct call needs a compatible format in both directions. Inter3 already uses the shared speaker resampler, so its physical speaker can stay at 48 kHz while accepting a 16 kHz call. Under rx_formats:
- sample_rate: 16000
pcm_format: s16le
channels: 1
frame_ms: 10Keep your existing microphone and speaker rates. Living already includes the matching 16 kHz/10 ms formats. The maintained Generic S3 Full Native example is now corrected on dev as well. Please rebuild both devices using the coordinated dev components and packages, with this addition in your custom Inter3 YAML. I tested direct WS3-to-Spotpear calls in both directions at 16 kHz/10 ms, and separately tested an incompatible PCM destination: the ESP retried through HA, which converted the audio and reported Please let me know whether calls now work in both directions. If not, attach the logs from both devices covering one complete attempt so we can see the negotiated formats and where it stops. |
|
Hi thanks for the information a small other question is it posible to let HA VoIP Stack card to remember to ringtone again thanks and nice work |
|
Thanks for confirming that switching to the coordinated components fixed calls in both directions, calls to HA and group calls. There is now a dedicated Waveshare ESP32-S3-Touch-LCD-1.85C-BOX V2 FULL profile, tested on my own V2 hardware and published with 2026.10.1. It includes the display/touch UI, dual-microphone AFE/AEC, voice features, media and VoIP, and remains experimental while we collect more real-world tests. If your Living device is the V2 / SKU 30684, please consider using this maintained FULL YAML instead of continuing to adapt the P4 profile. Keep the Freenove device on its own hardware-appropriate configuration. Use ESPHome 2026.9.0 or newer and the coordinated Could you retest Living -> Inter3, Inter3 -> Living, audio in both directions, and hangup followed by another call? Our WS3/Spotpear/BOX tests cover the shared implementation, but your Freenove and custom buttons still deserve their own check. Release notes and photographs | Board support and diagnostic checklist This update concerns the board firmware and call path. It does not establish a fix for the separate browser ringtone-setting question you raised. |
Uh oh!
There was an error while loading. Please reload this page.
Hi
I try to call from a freenove_esp32_s3_wroom with INMP441 mic and MAX98357A speaker to an ESP32-S3-Touch-LCD-1.85C
but that is not working
I can call from the devices to home but not to each other
in the log I see
'VoIP Last Reason' >> 'media_incompatible'
All reactions