-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
SM2135: Support 15W bulbs using higher current #10634
Comments
This comment has been minimized.
This comment has been minimized.
Add support for SM2135 current selection using GPIO ``SM2135 DAT`` index (#10634)
The fix makes limited SM2135 current selection possible by using an index to GPIO
Be careful NOT TO SELECT higher currents on devices which do not support this based on their power supply. |
It would appear the bulb I am working on (Arlec Smart 10W 830lm RGBCCT Bulb GLD320HA) is configured as a GBR rather than any of the options above. Is it possible to update the SM2135 options to include this configuration as well? |
I don't think it is going to be possible to update the list of index without a breaking change @arendst |
Great hack @asozio! |
Turns out I had to do another, so tested that one with the above SetOption37 suggestion. Looks like GLD130HA and potentially GLD320HA both would work with SetOption37 7 (as detailed in https://tasmota.github.io/docs/SetOption37/ |
Are these also based on SM2135 ? I was under the impression that the SM2135 was not using SetOption37 |
I thought I had updated the GLD320HA page, but must have not committed it. For the GLD132HA (Edison Screw version of the GLD130HA I believe) I am using: |
I have 3 models of RGBCCT light bulbs (5W, 13W and 15W) that use SM2135 LED driver.
Found out that I had to modify the current setting for these light bulbs in order to output the correct brigtness.
It would be good if the current setting for component SM2135 can be altered using command instead of compiling custom firmwares for each type, with the lowest current as the default.
Originally posted by @VaThInK in #10570
The text was updated successfully, but these errors were encountered: