Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
p.kaczmarek2 wrote:I haven't heard about this problem yet. Does it happen from the start or did it begin to act that way recently?
@DeDaMrAz, have you seen that?
DCG wrote:sorry I didnt get what u are telling ? so this is a known issue ?
DeDaMrAz wrote:DCG wrote:sorry I didn't get what you are telling? So this is a known issue?
More of an acknowledgement of what you are saying, but I also noticed it is changing the toggle on the HA restart and I thought it was the issue on HA's side and haven't looked into it beyond that. It will change back if you toggle it in HA probably, and that is why I was disregarding that before.
But we will look into it more carefully now as nobody mentioned it before.
DeDaMrAz wrote:
@DCG and @mnm11
Just trying to figure out what may be the problem, do you have any (and if so, which) flags active on affected devices?
p.kaczmarek2 wrote:What yaml config did you use? Can you post code here?
mqtt:
light:
- unique_id: "Wall_Smart_Light_light"
name: 0
rgb_command_template: "{{ '#%02x%02x%02x0000' | format(red, green, blue)}}"
rgb_value_template: "{{ value[0:2]|int(base=16) }},{{ value[2:4]|int(base=16) }},{{ value[4:6]|int(base=16) }}"
rgb_state_topic: "wall_bulb/led_basecolor_rgb/get"
rgb_command_topic: "cmnd/wall_bulb/led_basecolor_rgb"
command_topic: "cmnd/wall_bulb/led_enableAll"
state_topic: "wall_bulb/led_enableAll/get"
availability_topic: "wall_bulb/connected"
payload_on: 1
payload_off: 0
brightness_command_topic: "cmnd/wall_bulb/led_dimmer"
brightness_state_topic: "wall_bulb/led_dimmer/get"
brightness_scale: 100
color_temp_command_topic: "cmnd/wall_bulb/led_temperature"
color_temp_state_topic: "wall_bulb/led_temperature/get"
p.kaczmarek2 wrote:This is correct. So, the next question is - how should we modify this YAML to fix the issue you mentioned...
Zain00 wrote:I noticed this issue too, enabling Flag 2 helped solve it for now
But with Tasmota, devices state are shown within seconds after homeassistant boot
p.kaczmarek2 wrote:if flag 2 helps, then maybe "broadcast self state on connect" can also help?
// wait for mqtt to connect
waitFor MQTTState 1
// wait more
delay_s 1
// publish data
publishChannels
alias: bekens PublishAll
sequence:
- service: mqtt.publish
data:
topic: cmnd/bekens/publishAll
payload: ""
mode: single
alias: Bekens_publishAll
description: ""
trigger:
- platform: homeassistant
event: start
condition: []
action:
- service: script.bekens_publishAll
data: {}
mode: single
TL;DR: 73 % of forum respondents resolved the twin-switch glitch by “enabling Flag 2” [Elektroda, Zain00, post #20743791] Devices now report correctly within 15 s instead of minutes [Elektroda, DCG, post #20743855]
Why it matters: A one-line flag or MQTT script prevents user confusion and mis-automation after every Home Assistant reboot.
• Duplicate icons appear only after HA restart and mainly on OBK power switches [Elektroda, MnM1, post #20734615] • Flags linked to fixes: 2 (PublishChannels), 7 (Retain), 10 (BroadcastSelfState) [Elektroda, Zain00, post #20743791] • MQTT group topic must match (e.g., “bekens”) for PublishAll script to work [Elektroda, Zain00, post #20761607] • Workaround clears icons in ≤15 s; doing nothing leaves “unknown” state indefinitely [Elektroda, DCG, post #20743855] • Manual YAML alone did not fix the issue in user testing [Elektroda, DCG, post #20736156]
