Skip to content

Conversation

@Garfonso
Copy link
Contributor

This depends on PR in iobroker.docs repo: ioBroker/ioBroker.docs#621
I will update this PR, if we change something in the other PR.

The discussion about the role should happen in the docs-PR.

This one is mostly straightforward. One might debate if all of them "need" the effect state. There could be a flash effect on a simple on/off light. I am not sure if there is. Zigbee offers effects for dimmer lights (like breath, candle, ...).

might debate if all of them "need" the effect state. There could be a flash effect on simple on/off light.. not sure if there is.
Zigbee offers effects for dimmer lights.
Garfonso added a commit to ioBroker/ioBroker.lovelace that referenced this pull request Oct 1, 2025
needs type-detector PR to be merged:
ioBroker/ioBroker.type-detector#136

But won't do much harm until then.
Copy link
Contributor

@GermanBluefox GermanBluefox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@GermanBluefox
Copy link
Contributor

@Apollon77 what do you mean?

@Apollon77
Copy link
Collaborator

As discussed makes sense, but we should only find it even with the role when also "common.states" exist. I have no clue if we can define this already in Type detector but would make sense to have (and then also maybe use for others that only make sense with states?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants