-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
ESP8266 vs ESP32 with BBQKees Gateway - 1st experiences of differences #15
Comments
Thanks for the picture. Yes I was thinking about making cutouts as well .. Not having an endshield is fine for me. |
Thanks for the feedback. For most use cases the ESP8266 is still fine. There are actually very few customers who experience problems. |
@bbqkees: the esp32 D1mini is not from lolin/wemos, it's orginal from chinese MH-ET Live, but i don't know if this a sign for constant quality. |
I baught the gateway some 3-4 weeks before. I do have a Lolin D1 mini V3.1.0. But for stability and speed the ESP32 is the right choice. |
Yes it works. enclosure can now be closed but blue led is at different position and cannot been seen easyly anymore. Looking at the development of the ems-esp gateway software, I believe that the esp32 is a must in the future to secure stable operations. Not using the service jack, usb powering is in most cases a must as well. Better be prepared for both. |
we've incorporated some of this feedback into the ESP32 build. |
I am using / testing BBQKees Gateway Premium II since 2 weeks.
My Heating System: Buderus KB192i Boiler with integrated IP, RC310 thermostat and MM100 mixer.
I tried different versions of EMS-ESP: 2.1 and 2.1.1b5 and b6.
I had quite some stability problems with the gateway attached to my EMS-Bus. I tried different things and finally I bought a new D1 mini board with an ESP32. I want to comment on my first findings.
Original Wemos D1 Mini with ESP8266:
Newly bougth AZDelivery ESP32 D1 Mini NodeMCU board
The ESP8266 seems to be too limited. I would recommend to go for ESP32.
The text was updated successfully, but these errors were encountered: