-
Notifications
You must be signed in to change notification settings - Fork 37
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
Enhance config options #332
Conversation
commit ea34708 Merge: e14877b 1dcef13 Author: Jan-Ole Schümann <j.o.schuemann@gmx.de> Date: Tue Mar 26 20:16:00 2024 +0700 Merge pull request technyon#328 from iranl/ha-fixes Multiple fixes (Nuki ID + README + ACL + DoorSensor/Keypad) commit 1dcef13 Author: iranl <iranl@users.noreply.github.com> Date: Sun Mar 24 22:28:44 2024 +0100 Add extra checks and auto retries commit 56d718b Author: iranl <iranl@users.noreply.github.com> Date: Sat Mar 23 19:52:50 2024 +0100 Remove Force options commit a3658bf Author: iranl <iranl@users.noreply.github.com> Date: Sun Mar 17 22:57:24 2024 +0100 Update README.md commit ef7fe75 Author: iranl <iranl@users.noreply.github.com> Date: Sun Mar 17 22:50:46 2024 +0100 Update WebCfgServer.cpp commit ac375df Author: iranl <iranl@users.noreply.github.com> Date: Sun Mar 17 22:47:42 2024 +0100 Redact Nuki ID commit 516af39 Author: iranl <iranl@users.noreply.github.com> Date: Sun Mar 17 22:40:22 2024 +0100 ACL Info WebCfg + Force Keypad/DoorSensor commit 3db4c06 Author: iranl <iranl@users.noreply.github.com> Date: Sun Mar 17 21:59:57 2024 +0100 Nuki ID + README + ACL fix
f511163
to
f8c8db7
Compare
ee2497a
to
2af1fbd
Compare
@technyon This PR needs the most recent changes in I-Connect/NukiBleEsp32. Can you sync nuki_ble with upstream? |
Hi, Sorry I didn't see your comment. nuki_ble is now updated. One more thing: Since there are breaking changes in this PR, could we have a discussion on discord? Not that I'm against it, I'd just like to hear some more opinions. |
47fc663
to
01a294b
Compare
Apologies if this is not the place to ask this but testing the 8.34pre4 release in a AtomS3 Lite + Atom PoE and configured as follows:
Same M5Stack Atom POE but with an Atom Lite (not S3 Lite) with 8.33 works fine (connectivity is done by ethernet if configured so) Based on this snap from their store Thanks! |
@katiuskt: I've pushed an update to the W5500 code to change the pinout for the AtomPOE on the S3 to 5/7/8/39 instead of 19/22/23/33 Can you try esp32-s3-assets.zip? |
Thanks @iranl . OTA updated to that new version but unfortunately, nothing changed: connectivity remains by wifi. Turned off/on PoE to restart (just in case it would be necessary) didn't help either. |
I've taken a good look at the pinouts and it seems the following pinouts translate to the different models:
In my first try I assumed the pinout G5/G6/G7/G8/G38/G39 translated to G19/G21/G22/G23/G25/G33. Please try esp32-s3-assets.zip You can try debugging using the serial console with a program like hterm |
Thanks @iranl , it worked now! A couple of "weird" things (not sure if expected):
Beyond those two observations (probably not relevant), S3 lite seems to be working fine. I'll do further tests next days, though, but really appreciated your work supporting the S3!! 🙌 UPDATE:
Wouldn't be a better choice to configure it as a "button" (https://www.home-assistant.io/integrations/button.mqtt/) rather than as a "switch"? |
Good to hear the Atom POE now works on the S3. As for the |
92744a0
to
e2ad4c0
Compare
NOTE: Breaking change as the existing configuration MQTT topics can not be used for changing settings if this is merged.
Closes #327