-
Notifications
You must be signed in to change notification settings - Fork 223
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
feat(esp32): ✨ add esp32 support #831
Conversation
This looks awesome! When you're ready I should be able to run the test suite |
@sidoh, its ready for a review. i didnt had a esp8266 to test if there is any regression :/ |
That's okay! I have an automated test suite I can run against both the esp32 and esp8266. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I left a few comments -- need to make some minor changes to fix the esp8266 build.
Was able to verify that the integration test suite for ESP8266 is still working with these changes!
One additional request:
Can you update the README with the pin mappings for the ESP32 + nrf24l01? A new section around here is fine:
https://github.com/sidoh/esp8266_milight_hub?tab=readme-ov-file#nrf24l01
Doesn't need to be super detailed. Just the raw mapping is fine.
I haven't run the integration tests against ESP32 yet (will wait on the pin mappings so I'm not guessing), but if that works should be able to merge this pretty quickly!
Alright, I'll look at it after my workday :) |
@sidoh, thx for the review, changes made |
Got it working! Had to add this line to
but I think that's because the board I used was at some point flashed with a non-default partition table. Probably still worth including this since it seems like SPIFFS maybe doesn't work with non-default partition table. I ran the integration tests. There were some failures, but I think only 4 of them are real. Here are the full results:
I think we can ignore the MQTT error. The backup route failures are real. Looks like the issue is we need to make The first UDP failure looks like it was transient -- probably just a flaky test. The UDP discovery failures seem real. Not the most important thing in the world -- the UDP server probably isn't used very much, but worth looking into. I'm out of time for tonight and will probably be a few days before I can look again, but suspect there's something extra we need to do for the ESP32 to allow receiving broadcast packets? The ruby code that sends the broadcast packets is here in case it's helpful: https://github.com/sidoh/esp8266_milight_hub/blob/master/test/remote/spec/udp_spec.rb#L119 |
(I should mention that tons of tests pass -- the important stuff seems to be working just fine) |
Going to merge this into a branch in this repo so I can make the last few changes to get it over the line. tyvm for the PR <3 |
No description provided.