Replies: 9 comments 30 replies
-
|
tuya is using 0xEF00 (61184) for there DP commands to TS0601 devices (tunneling MQTT commands to there cloud) and some hybrid devices that using normal Zigbee cluster for commands and DP for advanced config. "Normal" tuya Zigbee devices:Manufactur cluster:
Known DP commands for
Extra "custom" commands and attribute added to ZCL cluster:Commands:
Attributes:
Looks like the dim min and max can having different attribute (combined 0xfc00 or spate 0xFC03/0xFC04) on different devices.
✅ = Implanted in tuya INIT. |
Beta Was this translation helpful? Give feedback.
-
|
@miit86 i have found some functions of your first tuya PITA cluster Like trying defining it and look if your device is responding on it ? |
Beta Was this translation helpful? Give feedback.
-
|
0xE001 Switch mode cluster: How to you want me to define them? Im always available for testing Tuya Pita devices |
Beta Was this translation helpful? Give feedback.
-
|
Try do it like the power on state you was doing but with one new cluster. PS: I have adding back light to tuya OnOff cluster (and renamed it) and its looks working but my power strip is not having any back light but its reporting the attribute OK. zigpy/zha-device-handlers#1105. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts0201_neo.py is defining attributes and also making one new custom cluster !! |
Beta Was this translation helpful? Give feedback.
-
|
Zigbee is having one 0x0007 clster OnOff configuration that is very rear used but it good. Its supporting monetary (2 stable state) toggle (2 states 1 stable) and multi function (OnOff Dimmer). I think 2 of the tuya attributes i compatible but the last not ;-(( |
Beta Was this translation helpful? Give feedback.
-
Some interesting findings in new updated tuya ZCL R8 docksLevel control clusterlevel control cluster(0x0008) Private cluster
Special instructions: 0xFC00 is used to store the current maximum and minimum brightness values. On/Off clusterAttributes
Over-current alerts (2) Turn off the relay that is being turned on, and immediately report the overcurrent alarm status Over Current Alarm to the gateway. IAS WD Cluster0xF000 Private attribute: a custom private attribute used to display prompts on the app. int8 -0x20 true/false Special instructions:
|
Beta Was this translation helpful? Give feedback.
-
|
@miit86 Over current alarm attribute found on OnOff cluster but not tested.
|
Beta Was this translation helpful? Give feedback.
-
|
I have a couple of this Tuya switches (Moes branding): They (as others tuya switches) are using a DP for controlling the
The freeze value sets the backlight to the current state and only can be tested with a double switch device. The strange thing is that on the product website it is announced that the I don't know if those settings are specific to Moes devices or other Tuya devices are using them. Grettings. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for information and feedback that is very interesting for our users and devs !! Moes is only one "German brand" or somthing like that that is buying all kinds of tuya products and branding them. They have doing it with nearly all TRVs but behind is always one manufacture with one name. I my thinking all tuya devices is belonging in the tuya quirk folder and not being splitted as Z2M have doing (ZHA is having one LIDL but its only for fixing some lights). Back too attribute / commands !!! If you is finding some Zigbee Cluster Library (ZCL) compliment commands like power on default on / off / last i think its best way is putting them on the same attribute as the ZCL ones then ZHA devs is starting implanting GUI elements for ZCL functions and then its possible getting them in GUI without making any changes in the quirk and in ZHA. tuya scene switches is also having some special for reporting how many gangs they is having on startup with DP but its not the normal DP that is used for other devices but you can finding them in tuya dev decks then you is needing them. One thing that is little discussed in the background is moving tuya DP things one level higher (ZHA or one "tuya DP module" in HA) for getting better implementation in HA that is one great PITA with TRVs and only need adding one quirks that is piping the DP to the module and all is done in zigbee layer and the upper is doing the rest. The same can being used for ZHA, Tasmota Z2M and more if they is liking that and being much free implanting the GUI element in HA. I dont knowing if its being done but i think its the best way getting good functions on tuya DP devices in (Z)HA. Great thanks for your work done with switches and dimmers and hope you is getting more great code in our systems that making all working better in the end !! |
Beta Was this translation helpful? Give feedback.
-
|
I have to say that I have mixed feelings with everything related to Tuya devices. On the one hand I can understand and share the need to make the devices work in HA (or any other ecosystem). But on the other hand, I feel like Tuya is doing a great business selling non-standard 'things' as Zigbee devices. And that we are doing the dirty work saying "it does not matter, we will make it work as standard". That causes people to keep buying and complaining to HA, Zigpy, whoever that his new devices are not working, diverting the pressure from the manufacturer to the developers/maintainers. I don't know, maybe we should give a different message and say "if you want it to work, don't buy Tuya devices, buy from manufacturers who care about following the Zigbee standard" |
Beta Was this translation helpful? Give feedback.
-
|
It was the same with IKEA was not working so well with other Zigbee system in the beginning but thy was fixing most of there issues and being one of the heavy board members of Zigbee Alliance. tuya "normal Zigbee" is not so bad then they is mostly using Silabs SDK that is working OK and getting bug fixed (but IKEA is not rolling the latest so still having bad bugs in there devices like battery draining in remotes). tuya is being board member in Zigbee Alliance and that is very heavy in the market but they is only certifying device if the customer is demanding it like LIDL have done. The DP device is little different then the same tuya MCU can using WiFi, BT, 433 or Zigbee and only need changing the radio module and its working out of the box. tuya is having 2 hardware for Zigbee DP devices and 2 software one for sleeping end device and one for router devices so its pretty basic. tuya is having some very nice touch dimmer but then its DP devices its not possible making binding i Zigbee so they is not working if the host system is not on line = one no go for my production system. Ony "Zigbee" side its good and bad then tuya is implanting som things no standard way like power on state with different attribute that is not needed and can being dome with the standard ones maped OK and adding some with extended manufacturer attributes and all was 110% better. The same with power metering and switch configuration as you can see in the first posting. One bad with tuya is Zigbee updates /certificat is not working well. LIDL was seling one 3 plug power strip with 4 USB and was certificated and new ones have getting one updated firmware that is not certificated and its only having one end point and switching all 3 plugs so waiting for some user is sniffing it for see what magic they have doing (hidden end points or using unknown commands). And i agree tuya is so large so they is the number one in IOT for us then Xiaomi is behind and no one can comparing with the gigant. Hopefully they is doing better products in the future that is working with our system without making tons of extra code and revers engineering there devices. The problem is getting cheap devices for our systems is not easy to finding like light switches, buch jäger its great devices but is costing 10 times one tuya switch so its out of range for most user. IKEA is cheap and normally working good but is not having wall switches only remotes. tuya TRVs is very problematic in ZHA then they is having so much functions that is not possible squeezing thru ZCL commands and also on the scheduling side 3 or more different implementations so its no tuya standard that can helping on the road. Z2M is having great time then they is only throwing tuya commands thru MQTT and dont need the ZCL for getting the functions in HA. deCONZ have completely freeing all PR then reworking there device base for getting user adding there device with file editing in GUI (no tuya DP device for 1/2 year = ver bad for the system). At least we have getting most DP blind controller, TRVs and switches up and running but i have guíving up the TRVs then no devs can helping getting the working quirks merged then we cant writing the tests for it. But one the good side tuya is not making the life boring and always finding new interesting things with them !!! |
Beta Was this translation helpful? Give feedback.
-
|
I have found the Child Lock on the OnOff cluster in Z2M but i cant finding witch data type its using. @javicalle can you see if its one t.enum8 or it somthing else ? |
Beta Was this translation helpful? Give feedback.
-
|
The OnOff attribute 0x8000 is for "normal" tuya Zigbee device and as you knowing tuya very "flexible" then its coming to coding there things. The MCU / DP for TRV is one other large mess and is all you can do without Zigbee standard. The user have start making code for testing it and we will knowing very son i think. 👍 |
Beta Was this translation helpful? Give feedback.
-
|
ZigBee type 0x10 check the specs. |
Beta Was this translation helpful? Give feedback.
-
|
I was looking for somewhere where value types were declared, similar to what is in I haven't found where this posible types are declarated in |
Beta Was this translation helpful? Give feedback.
-
|
Check zcl specification, it defines the types and corresponding type between type_id and python class is defined in zigpy/zcl/foundation.py |
Beta Was this translation helpful? Give feedback.
-
|
Caught: 0x10: ("Boolean", t.Bool, Discrete),Thanks for guiding me! |
Beta Was this translation helpful? Give feedback.
-
|
Have found the command used for hybrid devices with 0xEF00 tuya DP cluster:
Known DP commands for
Can being of interest for @javicalle and our HB friend @kkossev Edit: Looks one more command is being found but i think i have wrong with the DPs then its more ones and is grouped that i need finding out.
Link to Z2M PR Koenkk/zigbee-herdsman#519 I have seen somthing in tuya dev docks but i must finding it agen then its lost in the storm ;-(( |
Beta Was this translation helpful? Give feedback.
-
|
Need feeding the DPs being used but was finding little more interesting things in https://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty. Its possible subscribing reporting from the MCU for one or more DP !!! If have interest look little more of the commands they is using so getting little more knowledge if there protocol |
Beta Was this translation helpful? Give feedback.
-
|
One Norwegian brand have released some interesting information how they is faking tuya ZBGW and have released one PDF with our tuya magic sequence dresden-elektronik/deconz-rest-plugin#6198 (comment). Also is tuya calling the unknown attribute If some TRVs is needing it i thinking it is needed for more or less all tuya MCU device but it need being tested on many before assign it "globally" but i think its making more good in the future if we start adding it for all new tuya MCU and "normal Zigbee" devices. Holla @javicalle some interesting reading for you in the PDF attached from the above issue Connecte Smart Thermostat.pdf. By the way is Valencia not liking my and have bad weather then im visiting on my Holiday ;-( |
Beta Was this translation helpful? Give feedback.
-
|
I am also convinced that most of the hacks could be applied by default to all Tuya devices (the spell cast, the In the PDF are collected most of our adventures. Looks like someone else has been through the same thing (they mention integration with Homey) Offtopic: I'm sorry for your bad experience (I'm sure the bad weather didn't help). Valencia has some very nice places to visit (the Old City, the "Ciudad de las ciencias"...), but like anywhere your experience will depend on where you were 🤷🏻♂️ |
Beta Was this translation helpful? Give feedback.
-
|
Then im back for Gandia i like trying updating the TS004F Quirk so its using the spell for all device classes then we is having 2 devices plus one "general" and one upcoming that is working (need the spell) then i have 2 of the device and the user for the new one is good tester but the only problem is how to do it general for more classes without duplicating the code all the time. For MCU devices is only implanting it on the tuya cluster but most normal devices dont have that and one dev was trying using the basic cluster but it was not working then paring device and need it very early in the paring. Off topic: IKEA VLC was having the Styrbar in stainless steel for good price and 2 large BLACK (not the coding check tool !!!) Coffey cups so only 30€ for 2 of each and the holiday is great also then its raining :-))). Shall taking one more look on the old city in VLC then have doing it one time but its very nice and i like what i have seen !! |
Beta Was this translation helpful? Give feedback.
-
The def __init__(self, *args, **kwargs):
"""Initialize with task."""
super().__init__(*args, **kwargs)
self._init_device_task = asyncio.create_task(self.spell())The spell its just reading from the cluster (the async def spell(self) -> None:
"""Initialize device so that all endpoints become available."""
attr_to_read = [4, 0, 1, 5, 7, 0xFFFE]
basic_cluster = self.endpoints[1].in_clusters[0]
await basic_cluster.read_attributes(attr_to_read)Maybe, we can put that call just in the My proposal, a new class EnchantedBasicCluster(Basic):
"""Class for enchanted Tuya devices which needs to be unlocked by casting a 'spell'."""
def __init__(self, endpoint, is_server: bool = True):
"""Initialize with task."""
super().__init__(endpoint, is_server)
self._init_device_task = asyncio.create_task(self.spell())
async def spell(self) -> None:
"""Initialize device so that all endpoints become available."""
attr_to_read = [4, 0, 1, 5, 7, 0xFFFE]
await self.read_attributes(attr_to_read)Not sure if will work because tha call is inside the init method, so cluster would not be initialized yet to read the attributes. Now in the rogue device, define the quirk replacement with the new Basic cluster, like that: signature = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Time.cluster_id,
.../...
],
OUTPUT_CLUSTERS: [Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
INPUT_CLUSTERS: [
EnchantedBasicCluster,
Time.cluster_id,
.../...
],
OUTPUT_CLUSTERS: [Ota.cluster_id],
}
}
}Pingme when you are going to test the code and I will try to assist you. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Matt, I would like to know how you infer the payload of these commands in these manufacture-specific clusters. For example, you can know that the 0x0006 (OnOFF cluster) has a command 0xFC (Rotate) which payload 0x00/0x01/0x02. I am curious how you know the payload. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if they will help, but FYI, there's more links in the README.md from zha-device-handlers repo (including Tuya-specific ones): https://github.com/zigpy/zha-device-handlers/blob/dev/README.md https://github.com/zigpy/zha-device-handlers/blob/dev/README.md#what-are-these-specifications https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html |
Beta Was this translation helpful? Give feedback.
-
Hi Matt, sorry to bother you again. I reviewed your sentences, and I think you mentioned two methods for the command payload identification.
I am still confused about one question: You mentioned "scanning the devices with ZHA-Toolkit", what is the ZHA-Toolkit? Any link for it? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your info. I will check the referred Tuya documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Its utility that can making many extra things that is not implanted in ZHA and one is scanning all / selected endpoints of one device for attributes its supporting )only working on good Zigbee 3 devices) and you is getting the list of them in the HA log. Look on the devs git. Number 2 can being done with wire shark but then its very low level data but can being great. |
Beta Was this translation helpful? Give feedback.
-
Also check out related discussion about zha-toolkit here:
|
Beta Was this translation helpful? Give feedback.
-
ManufacturerSpecificCluster is used in Zigbee then one manufacture is implanting no Zigbee standard functions that can being used in one Zigbee system.
IKEA is using one and sending commands then adding scenes in there lights to making the scenes ignoring the light level and only changing the color of the light.
Some known ManufacturerSpecificCluster is:
tuya: 0xef00 (is used for sending DPs), 0xe000 and 0xe001 (locks being used for changing device propitiates) both is not in zigbee range for ZMC !!
IKEA: 0xFC7C, 0xFC57.
Philips: 0xfc00, 0xfc01, 0xfc02 and 0xfc03 Looks like last firmware is using the last one and the other is outdated).
I think some function can in the future being implanted in the system that is using some of theis without quirk is they is being percent on the device for adding more standard functions from common used devices.
Knowing more one ? Pleas adding them to the list then ZHA dont have one.
Beta Was this translation helpful? Give feedback.
All reactions