Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.15k stars 1.68k forks source link

Gledopto GU10 Spot Bulbs not turning on from Home Assistant Automation or light.turn_on service call #19225

Open stumain opened 1 year ago

stumain commented 1 year ago

What happened?

Discovered that Gledopto GU10 Spot bulbs (GL-S-003z and GL-S-007z) fail to turn on when triggered by HA automation or via a light.turn_on service call for the device in Home Assistant. They do turn on and off when done manually on the device in HA or in Z2M (HA Add-on).

Using a simple automation to turn on specific bulbs when motion detected (or any other trigger, e.g. Time). The MQTT message is issued to Z2M and shows in the logs. The bulbs do not turn on, but initially their state in Z2M GUI is reported as on. Click refresh on the bulb in Z2M and it immediately reports as OFF. The bulbs can be manually turned on/off via both Z2M and HA directly as specific device, just doesn't work when being triggered from an automation or via the service call.

Test performed with Gledopto GU10 and other bulbs (Hue) in single automation. Hue bulbs turn on correctly only the Gledopto GU10 bulbs stay off but initially report as turned on until refresh in Z2M.

What did you expect to happen?

Bulbs to turn on.

How to reproduce it (minimal and precise)

Use Gledopto GU10 (GL-S-003z or GL-S-007z) bulbs as device to turn on based on simple HA automation trigger (e.g. at time, turn on device GU10. Or when Sensor.Door=Open turn on device.GU10Bulb. Z2M and HA device state report device as on, but bulb is off. Refresh device in Z2M and state immediately changes to off. Or leave until next device ping/refresh and device status eventually updates to off.

Zigbee2MQTT version

1.33.1-1

Adapter firmware version

20230507

Adapter

TubesZB C2652 PoE 2022

Debug log

Screenshot 2023-10-09 at 3 48 10 PM

log.txt

stumain commented 1 year ago

Some additional trial and error and I see some odd behaviour.

Using the device in HA Turn bulb on to 50% - bulb turns on. Turn off Turn bulb on to 40% - bulb stays off Turn off Turn bulb on to 30% - bulb stays off Turn off Turn on to 30% or higher than 30% value - bulb turns on Turn off Turn on to new value lower than previous - bulb stays off Turn off Turn on to new value same or higher than previous (no matter if bulb turned on or not) then the bulb will turn on. Leave Bulb on Change brightness level with bulb already on both up and down works correctly every time.

I tested the above with 4 different GU10 bulbs to be sure it wasn't a faulty bulb.

Seems almost like the automation may be failing to turn on the lights because it's passing a value that is 1 lower than the prior manual setting (e.g. Brightness_Value 253 from Z2M logs instead of BrightnessPercent 100). But I am at the end of my knowledge on what might be happening here.

github-actions[bot] commented 7 months ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

stumain commented 7 months ago

This is issue is still happening.