Skip to content
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

Insteon Micro Dimmer 2442-222 brightness settings ignored in scenes #81170

Open
philip7277 opened this issue Oct 29, 2022 · 2 comments
Open

Insteon Micro Dimmer 2442-222 brightness settings ignored in scenes #81170

philip7277 opened this issue Oct 29, 2022 · 2 comments

Comments

@philip7277
Copy link

The problem

I have set up 3 scenes, each containing one Insteon 2442-222 Micro Dimmer and 2 Insteon 2457D2 LampLinc Dimmers. The LampLinc devices behave correctly as set up in each scene, but the Micro Dimmer does not. Upon creating the scenes, in the first scene the 2442 device brightness is set to 100%, in the second scene it's set to 50%, and in the third it's set to 0%. After saving each scene after its creation, upon activating each of the three scenes in turn, the 2442 remained at 100% brightness instead of diminishing according to my settings.

After going back and reviewing each of the three scenes, I discovered that the 2442 brightness slider was at 100% in each scene, indicating that the different brightness settings in the other two were ignored or lost during the Save scene operation. I've edited and recreated the scenes several times and every 2442 brightness setting, other than 100%, continues to be ignored after saving the scene.

What version of Home Assistant Core has the issue?

2022.10.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Insteon

Link to integration documentation on our website

https://www.home-assistant.io/integrations/insteon/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @teharris1, mind taking a look at this issue as it has been labeled with an integration (insteon) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of insteon can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant unassign insteon Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


insteon documentation
insteon source
(message by IssueLinks)

@github-actions github-actions bot added the stale label Nov 28, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jan 4, 2023
@teharris1 teharris1 reopened this Jan 18, 2023
@teharris1
Copy link
Contributor

FYI, this is not an Insteon specific issue as I see it. Adding the scene tag. Can you edit the scene in YAML view and show the lines you are referring to?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants