Closed Sku1ly closed 11 months ago
This is now happening with two more IKEA devices. I've rolled back Z2M version but no change.
Same problem here
Current version: 1.33.2-1 CC2652 (Electrolama zig-a-zig-ah! (zzh!)) CC2652R_coordinator_20221226
Very annoying, it happens with ALL my IKEA bulbs (+/- 25 bulbs, all kinds)
B
@bartplessers I've actually just fixed it. Even though transition is by default set to 0 I've had to set it again in the config.yaml file, now all my bulbs are working fine.
Give it a try
I've had to set it again in the config.yaml file
I can set this in an automation, i.e.
- id: '0x14b457fffe4fa583_action_on'
alias: '(R07) action on'
initial_state: true
trigger:
- entity_id: sensor.my_n00_p00_switch_r07_achterzijde_action
platform: state
to: 'on'
condition: []
action:
- data:
entity_id: light.group_n00_p00_plafond_bijkeuken
transition: 0
service: light.turn_on
But where can I set "transition: 0" as default value for all (IKEA) lights?
I noticed that you also work with lightgroups. Is this related?
I noticed that you also work with lightgroups. Is this related?
nope, just tested this. Indeed same problem when adressing bulb directly
Hi @bartplessers this is my zigbee2mqtt config.yaml example, it's still working after about 15 hours
friendly_name: Group - Kitchen Lights
devices:
- 0x000b57fffec1ec80/1
- 0x000b57fffebad38d/1
- 0x000b57fffec01ba2/1
- 0x000b57fffebb92c6/1
transition: 0
ah @Sku1ly ,
I see,. You defined your groups in Z2M config. I prefer having my group definitions in Home Assistant, but there I can not give a default transition to a group.... Can you reopen this issue as the solution you provided is only a workaround.
@Koenkk is this a bug or a feature? This behaviour came up few weeks ago, don't remember the exact update. I'm a bit reluctant to change the definition of all my IKEA lights in the config file because I have so many. And it's not a solution for new bulbs.
Putting
device_options:
legacy: false
transition: 0.7
in the global Z2M config file ("\HASSOS\share\zigbee2mqtt\configuration.yaml") does not work :-(
kind regards, Bart Plessers
@bartplessers what's the benefit for you grouping within Home Assistant?
If I group in Home Assistant lights turn on with delays in the group, if I group in Z2M they all come on at the same time.
@Sku1ly that's interesting! Maybe I have to reconsider my setup. However, I have a lot of groups with "mixed technology": zigbee + wifi. So I can't do this for everything.
PS: if putting something like this in the global config would work, it's also OK for me.
device_options:
transition: 0.7
Here that solution not working. My bulbs are 20% when i putting them on.
Slider says 100%
Looks the same as https://github.com/Koenkk/zigbee2mqtt/issues/19211#issuecomment-1849409528, please check the solution in that comment.
What happened?
Light not turning on at full brightness, even within Z2M control panel itself. Light shows full brightness in control panel and MQTT message but it isn't. Manually adjusting slider to 100% works. MQTT message shows exact same in both messages. I can't recall what version this started to happen in but it's a very recent problem.
TRADFRI bulb GU10 WS 400lm on 2.3.087
What did you expect to happen?
Light to turn on at full brightness
How to reproduce it (minimal and precise)
Turn light on via Z2M dashboard
Zigbee2MQTT version
1.33.2
Adapter firmware version
20211217
Adapter
Sonoff 3.0 Dongle Plus
Debug log