Skip to content
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

LwIP Variant set to v1.4 Higher Bandwidth #227

Open
intouchrandb opened this issue Jun 27, 2022 · 2 comments
Open

LwIP Variant set to v1.4 Higher Bandwidth #227

intouchrandb opened this issue Jun 27, 2022 · 2 comments

Comments

@intouchrandb
Copy link

This project works great, thanks for everyones support. I know we are suppose to use LwIP Variant set to v1.4 Higher Bandwidth with the esp8266 and fauxmoESP , but the time.h library with Network Time Protocol does not work with v1.4 Higher Bandwidth but works fine with v2 Lower Memory. During my testing I find both time.h/NTP and fauxmoESP work good together with v2 Lower Memory, and have not found any issues with fauxmoESP running with v2 Lower Memory. So my question is how important is it to use v1.4 Higher Bandwidth with fauxmoESP? What issues might show up later? I’m using esp8266 12E core 2.74, fauxmoESP ver 3.4.

@pvint
Copy link
Member

pvint commented Jun 27, 2022

If it works for you right now, I would not expect any issues in the future.

It could be that there has been a change to LwIP and the current V2 Low Memory version now works fine, however I haven't tried recently.

I likely won't have any time to do testing for at least a week or two, so if any others can report back on this it would be greatly appreciated!

@mcspr
Copy link

mcspr commented Jun 28, 2022

Regarding v1 vs. v2, ESPurna builds with v2 for at least a year, and the only apparent issue is the inability to control more than 9 'devices' with the lib
https://github.com/xoseperez/espurna/blob/ad8e30fcda57b3ae591dbd6da270c308445ccc6d/code/platformio.ini#L94
If fauxmo still uses the lwip buffer directly (client->send() / client->add()), high bandwidth will definitely be a better choice. With low mem there's only 1kib of buffer available

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants