-
Notifications
You must be signed in to change notification settings - Fork 12
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
Lights return to 50% brightness and default color immediately after changing #25
Comments
Just tried controlling from my iPhone (previously using iPad Pro), and the behavior is different -- now, it keeps the changes, but subsequent changes don't happen at all, until yet another change is requested. E.g., turn on Here are some logs, it's many repeats of similar:
|
You are not alone in this problem; I have exactly the same behavior. If needed I can provide the logs but they are similar. |
I am unable to reproduce this issue. Can u share your config.json ? And picture of your RGB controller ? |
config.json is above (unless you want the whole thing, I can get that tonight). Here's the product: amazon, there's no pic of the controller there, but it's just a black oblong box with weatherproof light cord in and out. No markings on it at all. I can take a pic tonite if it helps |
Describe the bug
If I change brightness or color in Home App or via Siri, the lights make the change, then immediately return to 50% brightens and a light purple color
Expected behavior
Once changed, brightness/color remain until changed again
Config
{
"platform": "MagicHome-Platform",
"debug": true,
"lights": [
{
"name": "Roofdeck String",
"ip": "10.0.1.32",
"setup": "RGBWW",
"purewhite": false,
"timeout": 10000
}
]
}
I have tried each of RGB, RGBW, RGBWW, same behavior in all -- lights are actually RGB
Logs
Setting brightness, and then reverting:
Setting color and reverting:
Desktop (please complete the following information):
Additional context
controller is unlabelled, Magic Home setup says it is UCS1903, the lights are addressable bulbs along a string
The text was updated successfully, but these errors were encountered: