-
Notifications
You must be signed in to change notification settings - Fork 11
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
Shelly Plus Wall Dimmer #17
Comments
You are the first. So no. |
I have one as well that I would like to convert. I have the boot loader up and running but still no GPIO mapping? |
Since no feedback from users which have the device how the GPIOs are assigned, I can't add them. |
I know this is probably more involved, but I'm not a complete noob... can you guide me on how to check GPIO and maybe I can help provide a map? I have a temporary rig setup for this already, i have a serial over USB connector I can hook on to it... I just don't know how to proceed to map the pin sets. |
Without open the device this can be a useless attempt. If dimming is done via a second MCU the train stops here. |
So if i crack the case and take some photos, that would be helpful? I know shelly has stated that this is very different than the original dimmers... so (just an assumption) i think it might do everything from the ESP32 now. |
Yes, photos will help. So no guessing about "who" does the dimming. Maybe it can be seen which GPIOs goes to the FETs (when the ESP32 does everything) |
Hope that helps! |
It is an STM32S003. Best way is to use a logic analyzer to read UART communication between ESP32 and it, with the original Shelly firmware loaded, of course. |
I am attempting to migrate a Shelly Plus Wall Dimmer to Tasmota (I know it's untested!). I don't see any GPIO mapping after autoconfig. Is the template known / defined somewhere?
The text was updated successfully, but these errors were encountered: