[Device Support Request] Mercator Ikuu 1 button Dimmer (SSWD01) #1463
Labels
stale
Issue is inactivate and might get closed soon
Comments
|
Your device need being added in one quirk for working in ZHA and we have getting its working with most tuya dimmers but its little more work getting all in the right place. |
|
I believe that you can simple change the class TuyaSingleSwitchDimmerPlus(TuyaDimmerSwitch):
"""Tuya touch switch device."""
signature = {
# "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0,
# reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>,
# manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82,
# descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *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)",
MODELS_INFO: [
("_TZE200_swaamsoy", "TS0601"),
],
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.DIMMER_SWITCH,
INPUT_CLUSTERS: [
Basic.cluster_id,
Identify.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
OnOff.cluster_id,
LevelControl.cluster_id,
Color.cluster_id,
TuyaManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
INPUT_CLUSTERS: [
Basic.cluster_id,
Identify.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaOnOffMCU,
TuyaInWallLevelControl,
# LevelControl.cluster_id,
TuyaLevelControlManufCluster,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
}
}The device also exposes 'normal' |
|
I've updated the file with your code above and get this error: |
|
Get all the from typing import Optional, Union
from zigpy.profiles import zha
from zigpy.quirks import CustomCluster
import zigpy.types as t
from zigpy.zcl import foundation
from zigpy.zcl.clusters.general import Basic, GreenPowerProxy, Groups, Identify, LevelControl, OnOff, Ota, Scenes, Time
from zigpy.zcl.clusters.lighting import Color
from zhaquirks.const import (
DEVICE_TYPE,
.../.... |
|
Thanks. That's getting closer. I have the light turning on and off, but the dimming functionality is missing. It's also introduced color and temperature controls, which this physical device doesn't control (but that doesn't matter much). |
|
It seems that the quirk does not fit the device. Please, without turning HA off, reboot the switch and attach any traces it generates. |
If not useful, the According to Koenkk/zigbee-herdsman-converters#3004 most of the DPs match with our definition, so is not clear why didn't work. In addition to the traces of the device restart (for example unplugging it and turning it back on), traces of when the physical device is operated would be very useful. Look at the logger config to get all the relevant traces: |
I restarted the device by cutting the power at the mains power / fuse box. It has now restarted and is working perfectly. I will keep testing it over the next few days, but thank you for your help @javicalle . I really appreciate it!
This worked as well. For anyone else with this device, here is the final ts0601_dimmer.py contents: |
|
I've tested this for a couple of days. Other than a warning in the logs, it is working perfectly, both through HA and physically. Are the warnings anything to worry about? |
|
The warnings are only informative that there is a config of the device (datapoint 6) that the implementation is not considering. It seems that device reports from datapoints 1, 2, 3 and 6. DP 1 and 2 are the But it is also, according to the vendor device have a 'backlight status' function, other tuya devices have it at datapoint 15 but yours don't report at this DP, so no sure how can be configured (maybe one of the already known DP?). Regards. |
|
Any ideas as to what might be happening with this device? When I select a brightness, it jumps around wildly. I can't see any pattern to it. Sequence.01.mp4I don't think it's a faulty device. I believe it's something happening within my Home Assitant/ConbeeII/ZHA setup because:
|
|
I can't say that would be the same behaviour, but some devices have a 'transition time' when you change the brightness.
Debug logs would give more information of what is happening here. |
|
I think your guess might be right. In instances where I make a large change (example: from 20% to 80%) and when it reverts back to the original value in the UI, the device's physical brightness does not change. So, it appears the UI updates itself to show the true current state reported by the device. I can force it to get to the desired brightness if I tap/click the brightness level twice, it jumps a bit, but seems to retain the second one. The device's behaviour is not erratic, just the UI. Debug log |
|
Sorry to contaminate the thread with a question to @ToastySefac , you mention that you have the hub that also integrates with this mech. I don't suppose you can check to see what the firmware version is reported as ? I seem to have an issue with coil whine and i'm wondering if there's a newer firmware that might solve this issue (since i don't have a hub to use with this). |
|
I bought the Mercator hub just to check if any of the devices I have had any updates, they don't 😁 It says the following for the dimmer: I've got a whining too, but the switch is far enough away that I don't hear it. Let me know if you need anything else checked with the hub |
|
@ToastySefac , Thank you for checking! |
Do you have the same issue as above with your dimmer? |
|
@ToastySefac , I do not have the same behaviour. It appears mine works as i would expect, however if my dimmer is in the "off" state and i adjust the brightness it does turn on (which is annoying). |
|
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 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. |
|
Hi Guys , a complete noob here ,so appreciate your help . i got the exact same light switch from Mercator Ikuu , and usinghome assitant OS , ZHA with Skyconnect , the switch interview comletes and i get a switch toggle which does nothing , also dont have any dimming options. i read through the whole discussion , but really dont know where to start and how to edit the device .py or even where to find it ! @ToastySefac appreciate your help since it seems like you got this working . thanks mate! |
|
Here's my memory of what I did...
To see if the quirk is being applied:
|
|
Hey mate , thanks a lot for your reply and step by step instructions. Logger: homeassistant.components.websocket_api.http.connection [546903718064] The system cannot restart because the configuration is not valid: Invalid config for [zha]: not a directory for dictionary value @ data['zha']['custom_quirks_path']. Got '/config/custom_zha_quirks/'. (See /config/configuration.yaml, line 17). |
|
I'm still a novice but I think it's an issue with your custom_zha_quirks folder. |
|
I think toasty is right, it needs to be in the right place.
For my installation, the quirk file lives in
"/usr/share/hassio/homeassistant/custom_zha_quirks"
…On Sat, 13 May 2023 at 16:45, ToastySefac ***@***.***> wrote:
I'm still a novice but I think it's an issue with your custom_zha_quirks
folder.
Check that you've created it in the right location. It should be:
/config/custom_zha_quirks/
—
Reply to this email directly, view it on GitHub
<#1463 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSSJG75OSI4FHRHOZMHLM3XF5CYXANCNFSM5SYMI5KA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Cheers,
Peter
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I have a Mercator Ikuu Light Dimmer (SSWD01) which identifies as a Tuya TS0601 Dimmer (_TZE200_swaamsoy). It interviews ok in ZHA, but once done, HA only gives a on/off option which doesn’t do anything.
Describe the solution you'd like
I'd like to have it identify correctly and have standard options, such an on/off, dimmer brightness up/down, etc
Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *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)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0104",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0008",
"0x0300",
"0xef00"
],
"out_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZE200_swaamsoy",
"model": "TS0601",
"class": "zigpy.device.Device"
}
Additional context
The model is in the Tuya "ts0601_dimmer.py" quirk file already. I've added the quirk to my custom folder and linked in configuration.yaml, but it doesn't seem to be helping.
Appreciate any help you could give. Thanks
The text was updated successfully, but these errors were encountered: