SmartHome-yourself/sonoff-tx-ultimate-for-esphome

ble proxy

pablogpr opened this issue ยท 10 comments

I want to use my tx for the bluetooth proxy functionality, but:
Error: The program size (1941981 bytes) is greater than maximum allowed (1835008 bytes)

How can inprove the size of the overall firmware?, I have 1 gang switch, nothing connected to the relay, but i want to know with part of the touchpanel is used.
I already try to comment some features like logger, but without success.

Yes, I've tried bt proxy too.
But unfortunately I had to leave it out for now. As soon as I see a way to free up enough space, I'll add the proxy back into the configuration as well.
What might work would be to omit the audio component. But I haven't tested it yet because I use the voice output of the TX.

how did you use the voice output of the TX? isnt it too noisy to be used?

how did you use the voice output of the TX? isnt it too noisy to be used?

Add following to the Media component Like in my current config.

    i2s_comm_fmt: lsb

Yes, I've tried bt proxy too. But unfortunately I had to leave it out for now. As soon as I see a way to free up enough space, I'll add the proxy back into the configuration as well. What might work would be to omit the audio component. But I haven't tested it yet because I use the voice output of the TX.

Just to confirm -> The ble proxy can be activated when omitting the audio component

Just to confirm -> The ble proxy can be activated when omitting the audio component

Thank you for confirm this

@pablogpr how dit you get BLE proxy working, so what code did u use?

@brotaxt can u please explain how you deleted the audio component?

@robbiedehand @yanirel IIRC I removed the following part of my configuration. Thus the audio component does not get included and there is enough free space for the ble proxy.

media_player:
- platform: i2s_audio
id: media_out
name: ${friendly_name} Player
dac_type: external
i2s_dout_pin: ${audio_sdata_pin}
i2s_audio_id: audio_i2s
i2s_comm_fmt: lsb
mode: mono
i2s_audio:
id: audio_i2s
i2s_lrclk_pin: ${audio_lrclk_pin}
i2s_bclk_pin: ${audio_bclk_pin}

I think with the answer of @brotaxt this issue can be closed