-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 or Eliminate SetOption51 #6969
Comments
Mike, you're too quick. I noticed some devices do not report the correct chip. Needs more time before abandoning SO51. |
Noted. Archive the request for now then. Thanks Mike P.S.
Hmmm, my wife said something similar the other night ;-) |
Ok. Let's reopen this issue if we can add this automatic selection. |
Add hardware detection to be overruled with SetOption51 (#6969)
It now automaticcaly selects the correct functionality based on hardware. User can still overrule wit SO51 1 |
Have you looked for this feature in other issues and in the wiki?
Yes
Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
As of this commit, Tasmota is able to query for the type of ESP chip in the device via
GetDeviceHardware()
. Currently,SetOption51
allows a user to "expose"GPIO9
andGPIO10
as available pins. This is provided since the ESP8285 frees these pins up. However, the option does not prevent a user for enablingSetOption51
if they have an ESP8266. Now that Tasmota is able to know the type of chip, it ought to prevent a user from enabling this feature if the device uses an ESP8266.Describe alternatives you've considered
GPIO9
andGPIO10
automatically.The text was updated successfully, but these errors were encountered: