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

Lidl (Silvercrest/Tuya) Light not working in automation #49825

Closed
1800Zeta opened this issue Apr 28, 2021 · 3 comments
Closed

Lidl (Silvercrest/Tuya) Light not working in automation #49825

1800Zeta opened this issue Apr 28, 2021 · 3 comments

Comments

@1800Zeta
Copy link

The problem

Attempting to use automation with a Lidl (Silvercrest/Tuya) zigbee bulb. When using automation, HA & ZHA show the light as being on, but the light has not actually turned on. From discussions on Discord, It doesn't appear that it supports the move_to_level_with_on_off command. They respond to the simple on_off command.

From the logs, this works:
2021-04-28 16:41:19 DEBUG (MainThread) [homeassistant.components.zha.entity] light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'on_off': [1, <Status.SUCCESS: 0>]}

This does not work:
2021-04-28 16:43:25 DEBUG (MainThread) [homeassistant.components.zha.entity] light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off: turned on: {'move_to_level_with_on_off': [4, <Status.SUCCESS: 0>]}

This issue came up when I tried to convert from using the device.on method to making use of the light.on service, after changing I have been unable to revert back to using the device.on method, it has the same result.
Using a toggle on the Lovelace dashboard, I am able to switch the light on and off without issue. I can do this after the automation has run to turn the light on. The light works via manual intervention. The automation to turn the light off works fine.

Device profile:
TS0505A
by _TZ3000_dbou1ap4
Zigbee Coordinator
Zigbee info
IEEE: 58:8e:81:ff:fe:d1:88:44
Nwk: 0x9d07
Device Type: Router
LQI: 54
RSSI: Unknown
Last Seen: 2021-04-28T19:18:15
Power Source: Mains

What is version of Home Assistant Core has the issue?

core-2021.4.6

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

Zigbee Home Automation

Link to integration documentation on our website

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

Example YAML snippet

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
id: '1619558086627'
alias: Hall Light - Activate
description: Activate Hall Light on Motion
trigger:
  - type: motion
    platform: device
    device_id: fd70cb3e073998f7542c3ea12c65b2cc
    entity_id: binary_sensor.lumi_lumi_sensor_motion_aq2_ias_zone
    domain: binary_sensor
condition:
  - condition: numeric_state
    entity_id: sensor.lumi_lumi_sensor_motion_aq2_illuminance
    below: '40'
action:
  - type: turn_on
    device_id: dea548277fae4f7077191131cbb686bd
    entity_id: light.tz3000_dbou1ap4_ts0505a_4488d1fe_level_light_color_on_off
    domain: light
  - service: timer.start
    data:
      duration: '0'
    target:
      entity_id: timer.hall_light_timer
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

No response

@probot-home-assistant
Copy link

Hey there @dmulcahey, @Adminiuga, mind taking a look at this issue as its been labeled with an integration (zha) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@1800Zeta
Copy link
Author

Device Signature (sorry I missed this off)

{
  "node_descriptor": "NodeDescriptor(byte1=1, byte2=64, mac_capability_flags=142, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False, *is_valid=True, *logical_type=<LogicalType.Router: 1>, *user_descriptor_available=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x010d",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0300",
        "0x1000"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "_TZ3000_dbou1ap4",
  "model": "TS0505A",
  "class": "zigpy.device.Device"
}

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 27, 2021
@github-actions github-actions bot closed this as completed Aug 3, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Sep 2, 2021
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

3 participants