Open itsolon opened 2 years ago
Most implementation extracted from the info in:
Proposed quirk:
The device is a low power device and reading/setting values can be difficult:
Thank you for your answer, but i do not really know what to do with this code.. i assume i should copy it into a file and upload it to HA? but i already have TS601 switch you wrote a quirk for me already .. the question is.. how do i know if i can remove that "hand made quirks" because its now in HA zha integration itself? Best regards Markus
One approach is just configure a zha local quirk folder. This is a guide of the steps to follow:
Copy the propposed file in the local folder and restart. If everything is fine, the device signature will change and maybe some new entities will show up in HA.
ok. it seems that every device i buy at the moment is ts0601 and additionally has issues.
i made file but corrected from ts0601_swicth.py to ts0601_switch.py
and copied your suggest into that file. after restart
{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, allocate_address=True, is_alternate_pan_coordinator=False, is_coordinator=False, is_end_device=True, is_full_function_device=False, is_mains_powered=False, is_receiver_on_when_idle=False, is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0402", "in_clusters": [ "0x0000", "0x0001", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "_TZE200_3towulqd", "model": "TS0601", "class": "ts0601_switch.PirMotion" }
good news.. the battery with 100% is reporting. but no entities movement or brightness :-(
{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2022.6.2", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.9.12", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "5.15.41", "supervisor": "2022.05.3", "host_os": "Home Assistant OS 8.1", "docker_version": "20.10.14", "chassis": "vm", "run_as_root": true }, "custom_components": { "ecowitt": { "version": "0.7", "requirements": [ "pyecowitt==0.14" ] }, "frigate": { "version": "2.3", "requirements": [] }, "hacs": { "version": "1.25.5", "requirements": [ "aiogithubapi>=22.2.4" ] }, "sonoff": { "version": "3.0.5", "requirements": [ "pycryptodome>=3.6.6" ] }, "alarmo": { "version": "v1.9.4", "requirements": [] }, "remote_homeassistant": { "version": "3.6", "requirements": [] }, "ble_monitor": { "version": "8.8.0", "requirements": [ "pycryptodomex>=3.14.1", "janus>=1.0.0", "aioblescan>=0.2.12", "btsocket>=0.2.0", "pyric>=0.1.6.3" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.30.0", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.75", "zigpy-deconz==0.16.0", "zigpy==0.45.1", "zigpy-xbee==0.14.0", "zigpy-zigate==0.7.4", "zigpy-znp==0.7.0" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "2652", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "10C4", "pid": "EA60", "description": "sonoffplus", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "tubeszb", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "tubeszb", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "zigstar", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "conbee", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "zigbee", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "zigate", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "zigate", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "bv 2010/10", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "zigate" } ], "after_dependencies": [ "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "REDACTED", "nwk": 10480, "manufacturer": "_TZE200_3towulqd", "model": "TS0601", "name": "_TZE200_3towulqd TS0601", "quirk_applied": true, "quirk_class": "ts0601_switch.PirMotion", "manufacturer_code": 4417, "power_source": "Battery or Unknown", "lqi": 40, "rssi": null, "last_seen": "2022-06-06T11:03:06", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, allocate_address=True, is_alternate_pan_coordinator=False, is_coordinator=False, is_end_device=True, is_full_function_device=False, is_mains_powered=False, is_receiver_on_when_idle=False, is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0402", "in_clusters": [ "0x0000", "0x0001", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] } } }, "entities": [ { "entity_id": "sensor.galerie_bewegung_power", "name": "_TZE200_3towulqd TS0601" } ], "neighbors": [], "endpoint_names": [ { "name": "IAS_ZONE" } ], "user_given_name": "Galerie Bewegung", "device_reg_id": "7410af9d59c022ac8863daf829516868", "area_id": "galerie" } }
Is the 'normal' behaviour for most of the Tuya devices (not only yours). If you don't like troubles I would suggest you that avoid them.
The device is loading the quirk, but maybe the DP mapping is not good. Please, enable the debug logs and attach the relevant info (formatted inside ``` please). For enabling the logs: https://www.home-assistant.io/integrations/zha/#debug-logging
corrected from ts0601_swicth.py to ts0601_switch.py
Ouch π
Hi i could successfully activate logs. but dont know how to filter the relevant info for you.. the log is so big only zigpy interesting?
Usually looking at the logs while interacting with the device and copying the generated logs. There's not an easy way to do.
I'm not sure in this case, but with some devices you can look for the device identifier, the most right left number (456789 1234) from [1234:1:456789]
in the logs.
hi, javicalle, i have installed new intance with few modules.. for test and enabled logging. for your interest here you can see everything
The device signature is telling us that the quirk has been applied:
"class": "ts0601_switch.PirMotion"
But logs complains that can't find the DP definition:
2022-06-13 18:48:53 WARNING (MainThread) [zigpy.zcl] [0x4269:1:0xef00]
No 'handle_set_data_response' tuya handler found for set_data_response(
data=TuyaCommand(
status=0,
tsn=87,
dp=12, <--- *
data=TuyaData(dp_type=<TuyaDPType.VALUE: 2>,
function=0,
raw=b'\xaa\x02\x00\x00',
*payload=682)
)
)
2022-06-13 18:48:54 WARNING (MainThread) [zigpy.zcl] [0x4269:1:0xef00]
No 'handle_set_data_response' tuya handler found for set_data_response(
data=TuyaCommand(
status=0,
tsn=88,
dp=1, <--- *
data=TuyaData(dp_type=<TuyaDPType.ENUM: 4>,
function=0,
raw=b'\x01',
*payload=<enum8.undefined_0x01: 1>)
)
)
@itsolon, I have updated the replacement part of the quirk, can you test the new version?:
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
TuyaPowerConfigurationCluster,
PirMotionManufCluster,
TuyaOccupancySensing,
TuyaIlluminanceMeasurement,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
}
}
}
yes i will please give me 20 min
maybe the missing entity is old and can be removed? it seems the occupancy reports very fast
maybe the missing entity is old and can be removed?
Yes, probably it is.
Please, look at the logs for any device related errors.
does this device have iaszone which means occupation.. and second entity motion which means motion
like aquara motion sensor has?
You should be able to set the sensitivity_level
and keep_time
attributes from the PirMotionManufCluster
cluster.
Accepted values would be:
class SensitivityLevel(t.enum8):
"""Sensitivity level enum."""
LOW = 0x00
MEDIUM = 0x01
HIGH = 0x02
class OnTimeValues(t.enum8):
"""Sensitivity level enum."""
_10_SEC = 0x00
_30_SEC = 0x01
_60_SEC = 0x02
_120_SEC = 0x03
For setting the value, just write the numeric value (0, 1, 2, ...) and push the "SET ZIGBEE ATTRIBUTE". To check if value is setted, just push the "GET ZIGBEE ATTRIBUTE".
at the moment it works like this
The device is reporting just a boolean value at DP_1. We can implement it like an IasZone Motion_Sensor or like an OccupancySensing, but not both. According to the manufacturer, it would be a "Human Motion Sensor":
Probably if the device signature already has a IasZone would be better implement as a IasZone Motion_Sensor π€·π»ββοΈ
i try to use your code and test what i can find out.
The IasZone alternative woud be like:
add a new MotionSensorCluster
class:
class MotionSensorCluster(IasZone, TuyaLocalCluster):
"""Tuya Motion_Sensor Sensor."""
_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Motion_Sensor}
2. replace the `dp_to_attribute` mapping in `PirMotionManufCluster` class:
```python
1: DPToAttributeMapping(
MotionSensorCluster.ep_attribute,
"zone_status",
dp_type=TuyaDPType.BOOL,
converter=lambda x: IasZone.ZoneStatus.Alarm_1 if x else 0,
),
replacement
part in PirMotion
class:
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
TuyaPowerConfigurationCluster,
PirMotionManufCluster,
MotionSensorCluster,
TuyaIlluminanceMeasurement,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
}
}
}
This would replace the OccupancySensing
with an IasZone
cluster.
Does this sensor now work without custom files in HA? Because I have the same and it doesnt seem to work
Does this sensor now work without custom files in HA? Because I have the same and it doesnt seem to work
HI KrOnAsk i have to tell you that this device didnt work with zha for me.. that was (mainly) the reason to switch over to zigbee2mqtt where it is supported even with a small picture of it.. there it works like a charm. even other devices i had to fight for were supported out of the box there. as far as i can say i do not regret to quit zha for the moment. possible that i come back some time but this was it for now Thank you to the great support javicalle and matt west ,, they always gave their best.! trying get things to work but for this device i decided to switch over to zigbee2mqtt, reason:? i counted how many devices are supported there and how many at zha, i dont remember the correct number but it was 3 times more like 500 to 1500 devices .. no question about it. Best regards Markus
ZHA is supporting all devices that is Zigbee (ZCL) compatible out of the box and not making strange things like most tuya and Xiaomi devises id doing and is not working as standard Zigbee devices.
If you is baying one new model Philips HUE bulb that is not added to Z2M its not working but in ZHA is working with all ground functions and can needing some patching for getting some extras Philips have putting in so in the end all system have good and bad sides.
Hello, I bought the same motion sensor from aliexpress and had the same problems as the originator of this ticket.
@javicalle - thanks a lot for you advises and your code. I was able to get the motion sensor working after following all you recommended changes from the original python file. Just 1 thing I still noticed:
The motion sensor state was inverted.
I changed the following in dp_to_attribute
converter=lambda x: IasZone.ZoneStatus.Alarm_1 if not x else 0,
Maybe there is a better way to fix this, but I'm quite new on ZHA.
For all the others who want to use:
"""BlitzWolf IS-3/Tuya motion rechargeable occupancy sensor."""
import math
from typing import Dict
from zigpy.profiles import zha
from zigpy.quirks import CustomDevice
import zigpy.types as t
from zigpy.zcl.clusters.general import Basic, Ota, Time
from zigpy.zcl.clusters.measurement import IlluminanceMeasurement, OccupancySensing
from zigpy.zcl.clusters.security import IasZone
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
ZONE_TYPE,
)
from zhaquirks.tuya import TuyaLocalCluster
from zhaquirks.tuya.mcu import (
DPToAttributeMapping,
TuyaDPType,
TuyaMCUCluster,
TuyaPowerConfigurationCluster,
)
class TuyaOccupancySensing(OccupancySensing, TuyaLocalCluster):
"""Tuya local OccupancySensing cluster."""
class TuyaIlluminanceMeasurement(IlluminanceMeasurement, TuyaLocalCluster):
"""Tuya local IlluminanceMeasurement cluster."""
class SensitivityLevel(t.enum8):
"""Sensitivity level enum."""
LOW = 0x00
MEDIUM = 0x01
HIGH = 0x02
class OnTimeValues(t.enum8):
"""Sensitivity level enum."""
_10_SEC = 0x00
_30_SEC = 0x01
_60_SEC = 0x02
_120_SEC = 0x03
class MotionSensorCluster(IasZone, TuyaLocalCluster):
"""Tuya Motion_Sensor Sensor."""
_CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Motion_Sensor}
class PirMotionManufCluster(TuyaMCUCluster):
"""Neo manufacturer cluster."""
attributes = TuyaMCUCluster.attributes.copy()
attributes.update({0xEF09: ("sensitivity_level", SensitivityLevel)})
attributes.update({0xEF0A: ("keep_time", OnTimeValues)})
dp_to_attribute: Dict[int, DPToAttributeMapping] = {
1: DPToAttributeMapping(
MotionSensorCluster.ep_attribute,
"zone_status",
dp_type=TuyaDPType.BOOL,
converter=lambda x: IasZone.ZoneStatus.Alarm_1 if not x else 0,
),
4: DPToAttributeMapping(
TuyaPowerConfigurationCluster.ep_attribute,
"battery_percentage_remaining",
dp_type=TuyaDPType.VALUE,
),
9: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"sensitivity_level",
dp_type=TuyaDPType.ENUM,
converter=lambda x: SensitivityLevel(x),
),
10: DPToAttributeMapping(
TuyaMCUCluster.ep_attribute,
"keep_time",
dp_type=TuyaDPType.ENUM,
converter=lambda x: OnTimeValues(x),
),
12: DPToAttributeMapping(
TuyaIlluminanceMeasurement.ep_attribute,
"measured_value",
dp_type=TuyaDPType.VALUE,
converter=lambda x: (10000 * math.log10(x) + 1 )/ 10,
),
}
data_point_handlers = {
1: "_dp_2_attr_update",
4: "_dp_2_attr_update",
9: "_dp_2_attr_update",
10: "_dp_2_attr_update",
12: "_dp_2_attr_update",
}
class PirMotion(CustomDevice):
"""Tuya PIR motion sensor."""
signature = {
MODELS_INFO: [("_TZE200_3towulqd", "TS0601")],
ENDPOINTS: {
# endpoints=1 profile=260 device_type=0x0402
# in_clusters=[0x0000, 0x0001, 0x0500],
# out_clusters=[0x000a, 0x0019]
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
TuyaPowerConfigurationCluster.cluster_id,
IasZone.cluster_id,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
}
},
}
replacement = {
ENDPOINTS: {
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.IAS_ZONE,
INPUT_CLUSTERS: [
Basic.cluster_id,
TuyaPowerConfigurationCluster,
PirMotionManufCluster,
MotionSensorCluster,
TuyaIlluminanceMeasurement,
],
OUTPUT_CLUSTERS: [
Time.cluster_id,
Ota.cluster_id,
],
}
}
}
Can we reopen this issue?
I've just got one of these sensors and it would be great to get it supported in ZHA than need to use a quirk.
I would love that too
Just because there is a lot going on in this thread, the current solution to this is as follows:
Create a folder for your custom quirks (I created /config/zha_quirks/)
Create a quirk/file in this directory (I followed the guide above and called it "ts0601_pirmotion.py"). This file should contain the quirk from this post - https://github.com/zigpy/zha-device-handlers/issues/1599#issuecomment-1146852599
Add the following to your config.yaml
zha:
custom_quirks_path: /config/zha_quirks/
Another user has submitted a pull request here - https://github.com/home-assistant/home-assistant.io/pull/23884
I used the quirk at
Hello, I bought the same motion sensor from aliexpress and had the same problems as the originator of this ticket.
@javicalle - thanks a lot for you advises and your code. I was able to get the motion sensor working after following all you recommended changes from the original python file. Just 1 thing I still noticed:
The motion sensor state was inverted. I changed the following in dp_to_attribute
converter=lambda x: IasZone.ZoneStatus.Alarm_1 if not x else 0,
Maybe there is a better way to fix this, but I'm quite new on ZHA.For all the others who want to use:
"""BlitzWolf IS-3/Tuya motion rechargeable occupancy sensor.""" import math from typing import Dict from zigpy.profiles import zha from zigpy.quirks import CustomDevice import zigpy.types as t from zigpy.zcl.clusters.general import Basic, Ota, Time from zigpy.zcl.clusters.measurement import IlluminanceMeasurement, OccupancySensing from zigpy.zcl.clusters.security import IasZone from zhaquirks.const import ( DEVICE_TYPE, ENDPOINTS, INPUT_CLUSTERS, MODELS_INFO, OUTPUT_CLUSTERS, PROFILE_ID, ZONE_TYPE, ) from zhaquirks.tuya import TuyaLocalCluster from zhaquirks.tuya.mcu import ( DPToAttributeMapping, TuyaDPType, TuyaMCUCluster, TuyaPowerConfigurationCluster, ) class TuyaOccupancySensing(OccupancySensing, TuyaLocalCluster): """Tuya local OccupancySensing cluster.""" class TuyaIlluminanceMeasurement(IlluminanceMeasurement, TuyaLocalCluster): """Tuya local IlluminanceMeasurement cluster.""" class SensitivityLevel(t.enum8): """Sensitivity level enum.""" LOW = 0x00 MEDIUM = 0x01 HIGH = 0x02 class OnTimeValues(t.enum8): """Sensitivity level enum.""" _10_SEC = 0x00 _30_SEC = 0x01 _60_SEC = 0x02 _120_SEC = 0x03 class MotionSensorCluster(IasZone, TuyaLocalCluster): """Tuya Motion_Sensor Sensor.""" _CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Motion_Sensor} class PirMotionManufCluster(TuyaMCUCluster): """Neo manufacturer cluster.""" attributes = TuyaMCUCluster.attributes.copy() attributes.update({0xEF09: ("sensitivity_level", SensitivityLevel)}) attributes.update({0xEF0A: ("keep_time", OnTimeValues)}) dp_to_attribute: Dict[int, DPToAttributeMapping] = { 1: DPToAttributeMapping( MotionSensorCluster.ep_attribute, "zone_status", dp_type=TuyaDPType.BOOL, converter=lambda x: IasZone.ZoneStatus.Alarm_1 if not x else 0, ), 4: DPToAttributeMapping( TuyaPowerConfigurationCluster.ep_attribute, "battery_percentage_remaining", dp_type=TuyaDPType.VALUE, ), 9: DPToAttributeMapping( TuyaMCUCluster.ep_attribute, "sensitivity_level", dp_type=TuyaDPType.ENUM, converter=lambda x: SensitivityLevel(x), ), 10: DPToAttributeMapping( TuyaMCUCluster.ep_attribute, "keep_time", dp_type=TuyaDPType.ENUM, converter=lambda x: OnTimeValues(x), ), 12: DPToAttributeMapping( TuyaIlluminanceMeasurement.ep_attribute, "measured_value", dp_type=TuyaDPType.VALUE, converter=lambda x: (10000 * math.log10(x) + 1 )/ 10, ), } data_point_handlers = { 1: "_dp_2_attr_update", 4: "_dp_2_attr_update", 9: "_dp_2_attr_update", 10: "_dp_2_attr_update", 12: "_dp_2_attr_update", } class PirMotion(CustomDevice): """Tuya PIR motion sensor.""" signature = { MODELS_INFO: [("_TZE200_3towulqd", "TS0601")], ENDPOINTS: { # endpoints=1 profile=260 device_type=0x0402 # in_clusters=[0x0000, 0x0001, 0x0500], # out_clusters=[0x000a, 0x0019] 1: { PROFILE_ID: zha.PROFILE_ID, DEVICE_TYPE: zha.DeviceType.IAS_ZONE, INPUT_CLUSTERS: [ Basic.cluster_id, TuyaPowerConfigurationCluster.cluster_id, IasZone.cluster_id, ], OUTPUT_CLUSTERS: [ Time.cluster_id, Ota.cluster_id, ], } }, } replacement = { ENDPOINTS: { 1: { PROFILE_ID: zha.PROFILE_ID, DEVICE_TYPE: zha.DeviceType.IAS_ZONE, INPUT_CLUSTERS: [ Basic.cluster_id, TuyaPowerConfigurationCluster, PirMotionManufCluster, MotionSensorCluster, TuyaIlluminanceMeasurement, ], OUTPUT_CLUSTERS: [ Time.cluster_id, Ota.cluster_id, ], } } }
I used this Quirk and its kinda working but the Luminance value doesnt show at all but the rest is working, could u maybe help why its not there
Can someone help me ? It looks like that for me and it just shows detected the whole time. I also just put in a new battery so the battery reading is wrong too
It has been working before? It is the device loading the quirk? Any relevant info in your logs?
I would try to pair the device again.
I deleted the quirk and added it again, but it still didnt work but then I changed some cluster setting (I dont know which one anymore cause I changed or tried to change allot) and now it reports Motion and that all works great but the Lux value is stuck at 1,9 lux which is for sure not true but it also doesnt change when I turn the light on.
I deleted the quirk and added it again, but it still didnt work but then I changed some cluster setting (I dont know which one anymore cause I changed or tried to change allot) and now it reports Motion and that all works great but the Lux value is stuck at 1,9 lux which is for sure not true but it also doesnt change when I turn the light on.
Hi, did you managed to find out what you changed to get the luminance sensor to work? I've added the quirk and motion is excellent but there is no luminance sensor present.
Also just to thank @javicalle also for getting me this far with this device quirk. Thought i'd bought a lemon when i first tried it in ZHA and it didn't detect anything, really appreciated.
I deleted the quirk and added it again, but it still didnt work but then I changed some cluster setting (I dont know which one anymore cause I changed or tried to change allot) and now it reports Motion and that all works great but the Lux value is stuck at 1,9 lux which is for sure not true but it also doesnt change when I turn the light on.
Hi, did you managed to find out what you changed to get the luminance sensor to work? I've added the quirk and motion is excellent but there is no luminance sensor present.
Also just to thank @javicalle also for getting me this far with this device quirk. Thought i'd bought a lemon when i first tried it in ZHA and it didn't detect anything, really appreciated.
No I definetly changed it for the worse, it doesnt work at all or just really flaky now.
I deleted the quirk and added it again, but it still didnt work but then I changed some cluster setting (I dont know which one anymore cause I changed or tried to change allot) and now it reports Motion and that all works great but the Lux value is stuck at 1,9 lux which is for sure not true but it also doesnt change when I turn the light on.
Hi, did you managed to find out what you changed to get the luminance sensor to work? I've added the quirk and motion is excellent but there is no luminance sensor present. Also just to thank @javicalle also for getting me this far with this device quirk. Thought i'd bought a lemon when i first tried it in ZHA and it didn't detect anything, really appreciated.
No I definetly changed it for the worse, it doesnt work at all or just really flaky now.
Argh, sorry to hear that.
Typical after i posted my question the sensor is now working as expected for me. I deleted everything i'd tried, recopied the code from @javicalle post, restarted HA and re-added the sensor. I've no idea what changed because i didn't do anything different than previous attempts and yet this time it worked.
I deleted the quirk and added it again, but it still didnt work but then I changed some cluster setting (I dont know which one anymore cause I changed or tried to change allot) and now it reports Motion and that all works great but the Lux value is stuck at 1,9 lux which is for sure not true but it also doesnt change when I turn the light on.
I share your problem. I've read through the discussion here and carefully followed the guidance. The Illuminance sensor is there but its range seems to be from 1.0 (darkness) to 2.0 (directly under a bulb.)
Looking at the 'measured_value' attribute seems to give actual useful numbers that are specific. It seems like that's what needs to be exposed as a sensor.
Holy cow it's fixed. Either through the many removals and restarts or because I changed line 92.
converter=lambda x: (10000.0 * math.log10(x) + 1.0 if x != 0 else 0),
I found that version in another device handler here. I now correctly see values peaking at 1000 in the sensor.
I'm pretty sure that the right expression must be:
converter=lambda x: 10000.0 * math.log10(x + 1.0)
This way for 0<x<1
values remains positive. With the current version for values 0<x<1
you can get negative values that don't make sense to me.
(Example with a 10 scale to see the behavior)
I can't see that quirk or similar in the code. Could anyone create the PR for that quirk?
something interesting i just found with my PIR.
the quirk works for motion detection and battery.....but illuminance is still buggy and doesn't seem correct just seems to stick between a value of 0 and 2
one other thing i noticed is that if it's too dark in an area, the motion sensor will detect motion (as evident by the red light flashing indicating motion detected) but it will not tell HA and instead will leave it in a stuck state
for example:
motion triggered + room dark = motion stays locked to triggered in ZHA
applying light to motion = motion resets and functions again
motion triggered + normal room light = motion triggers then un-triggers as per usual operation.
Curious as if anyone else has noticed this?
here's a diagnostic log
{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2022.11.4", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "x86_64", "timezone": "America/New_York", "os_name": "Linux", "os_version": "5.15.74", "supervisor": "2022.11.2", "host_os": "Home Assistant OS 9.3", "docker_version": "20.10.18", "chassis": "vm", "run_as_root": true }, "custom_components": { "nodered": { "version": "0.5.2", "requirements": [] }, "blueiris": { "version": "1.0.12", "requirements": [] }, "hacs": { "version": "1.28.4", "requirements": [ "aiogithubapi>=22.2.4" ] }, "nws_alerts": { "version": "2.5", "requirements": [] }, "truenas": { "version": "0.0.0", "requirements": [] }, "weatheralerts": { "version": "0.1.5", "requirements": [] }, "tesla_custom": { "version": "3.3.1", "requirements": [ "teslajsonpy==3.2.2" ] }, "zha_toolkit": { "version": "v0.8.26", "requirements": [ "packaging>=20.8" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.2", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.86", "zigpy-deconz==0.19.0", "zigpy==0.51.5", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.3", "zigpy-znp==0.9.1" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 36286, "manufacturer": "_TZE200_3towulqd", "model": "TS0601", "name": "_TZE200_3towulqd TS0601", "quirk_applied": true, "quirk_class": "ts0601_pirmotion.PirMotion", "manufacturer_code": 4417, "power_source": "Battery or Unknown", "lqi": 255, "rssi": -65, "last_seen": "2022-11-27T16:00:12", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0402", "in_clusters": [ "0x0000", "0x0001", "0x0400", "0x0500", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] } } }, "active_coordinator": false, "entities": [ { "entity_id": "binary_sensor.motion_by_bed_iaszone", "name": "_TZE200_3towulqd TS0601" }, { "entity_id": "sensor.motion_by_bed_battery", "name": "_TZE200_3towulqd TS0601" }, { "entity_id": "sensor.motion_by_bed_illuminance", "name": "_TZE200_3towulqd TS0601" } ], "neighbors": [], "endpoint_names": [ { "name": "IAS_ZONE" } ], "user_given_name": "Motion by bed", "device_reg_id": "c36b24b9479ad8f9d3442f87dd18499c", "area_id": null, "cluster_details": { "1": { "device_type": { "name": "IAS_ZONE", "id": 1026 }, "profile_id": 260, "in_clusters": { "0x0000": { "endpoint_attribute": "basic", "attributes": { "0x0004": { "attribute_name": "manufacturer", "value": "_TZE200_3towulqd" }, "0x0005": { "attribute_name": "model", "value": "TS0601" } }, "unsupported_attributes": {} }, "0x0001": { "endpoint_attribute": "power", "attributes": { "0x0021": { "attribute_name": "battery_percentage_remaining", "value": 200 } }, "unsupported_attributes": { "0x0020": { "attribute_name": "battery_voltage" }, "0x0021": { "attribute_name": "battery_percentage_remaining" }, "0x0031": { "attribute_name": "battery_size" }, "0x0033": { "attribute_name": "battery_quantity" } } }, "0xef00": { "endpoint_attribute": "tuya_manufacturer", "attributes": { "0xef09": { "attribute_name": "sensitivity_level", "value": 2 }, "0xef0a": { "attribute_name": "keep_time", "value": 0 } }, "unsupported_attributes": {} }, "0x0500": { "endpoint_attribute": "ias_zone", "attributes": { "0x0001": { "attribute_name": "zone_type", "value": 13 }, "0x0002": { "attribute_name": "zone_status", "value": 0 }, "0x0010": { "attribute_name": "cie_addr", "value": "00:0d:6f:00:17:20:6a:90" } }, "unsupported_attributes": { "0x0000": { "attribute_name": "zone_state" }, "0x0002": { "attribute_name": "zone_status" } } }, "0x0400": { "endpoint_attribute": "illuminance", "attributes": { "0x0000": { "attribute_name": "measured_value", "value": 1813.0133566428553 } }, "unsupported_attributes": {} } }, "out_clusters": { "0x000a": { "endpoint_attribute": "time", "attributes": {}, "unsupported_attributes": {} }, "0x0019": { "endpoint_attribute": "ota", "attributes": {}, "unsupported_attributes": {} } } } } } }
something interesting i just found with my PIR.
the quirk works for motion detection and battery.....but illuminance is still buggy and doesn't seem correct just seems to stick between a value of 0 and 2
one other thing i noticed is that if it's too dark in an area, the motion sensor will detect motion (as evident by the red light flashing indicating motion detected) but it will not tell HA and instead will leave it in a stuck state
for example:
motion triggered + room dark = motion stays locked to triggered in ZHA
applying light to motion = motion resets and functions again
motion triggered + normal room light = motion triggers then un-triggers as per usual operation.
Curious as if anyone else has noticed this?
here's a diagnostic log`
I experienced similar with my units and this quirk in ZHA. I found motion would often stick on for hours for seeming no reason and wouldn't clear until mounting / dismount the pir. This was across four different sensors. I'd pretty much given up on them as a poor devices but swapped to using zigbee2mqtt and (touch wood) they've been working perfectly since then.
I'm now tempted to order more because they are good value, compact, accurate and the luminance sensor is an added bonus.
something interesting i just found with my PIR. the quirk works for motion detection and battery.....but illuminance is still buggy and doesn't seem correct just seems to stick between a value of 0 and 2 one other thing i noticed is that if it's too dark in an area, the motion sensor will detect motion (as evident by the red light flashing indicating motion detected) but it will not tell HA and instead will leave it in a stuck state for example: motion triggered + room dark = motion stays locked to triggered in ZHA applying light to motion = motion resets and functions again motion triggered + normal room light = motion triggers then un-triggers as per usual operation. Curious as if anyone else has noticed this? here's a diagnostic log`
I experienced similar with my units and this quirk in ZHA. I found motion would often stick on for hours for seeming no reason and wouldn't clear until mounting / dismount the pir. This was across four different sensors. I'd pretty much given up on them as a poor devices but swapped to using zigbee2mqtt and (touch wood) they've been working perfectly since then.
I'm now tempted to order more because they are good value, compact, accurate and the luminance sensor is an added bonus.
Exactly same happening here. I thought myzigbee network is overcrowded and it is missing messages but seems yet again the ZHA is the culprit.
I also got the motion sensor to work using the quirk posted. However, now the Illuminance sensor doesn't work anymore (used to work out of the box without the quirk). It is now stuck at 1000 lx. Anyone else with the same problem? I use ZHA with a Conbee II stick.
I can really recommend using zigbee2mqtt There the sensor works like a charm I understand that you want to use the built in Standard ZigBee functionality of home assistant which is quite cool.. But for me β as i Have many different sensors and themostates β there was no way without going away from the Standard zha Give it a try and then you will be without those quirks.. Best Regards Markus
Gesendet von Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 fΓΌr Windows
Von: @.> Gesendet: Samstag, 17. Dezember 2022 12:29 An: @.> Cc: Markus @.>; @.> Betreff: Re: [zigpy/zha-device-handlers] _TZE200_3towulqd TS0601 Tuya Motion Sensor with illuminance sensor (Issue #1599)
I also got the motion sensor to work using the quirk posted. However, now the Illuminance sensor doesn't work anymore (used to work out of the box without the quirk). It is now stuck at 1000 lx. Anyone else with the same problem? I use ZHA with a Conbee II stick.
β Reply to this email directly, view it on GitHubhttps://github.com/zigpy/zha-device-handlers/issues/1599#issuecomment-1356214497, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPUKO66DSZYZHPGYNQQTHTWNWPZHANCNFSM5XZ35VCQ. You are receiving this because you were mentioned.Message ID: @.***>
Having the same issue with this sensor. Can someone recommend one that will work just fine with ZHA?
Having the same issue with this sensor. Can someone recommend one that will work just fine with ZHA?
I followed the suggestions in this thread (sounds much more complicated than it is... I got it to work without having deep knowledge of YAML or HA in general). I had to restart the system and bind the sensor again... since then it works for me without a problem for the last 3 weeks...
Having the same issue with this sensor. Can someone recommend one that will work just fine with ZHA?
I followed the suggestions in this thread (sounds much more complicated than it is... I got it to work without having deep knowledge of YAML or HA in general). I had to restart the system and bind the sensor again... since then it works for me without a problem for the last 3 weeks...
I installed also the quirk manually (not really complicated, I'm a dev myself) and it is indeed working but it still has this issue that it won't recognize motion when it's dark. Are you sure you're not having this problem as well?
I installed also the quirk manually (not really complicated, I'm a dev myself) and it is indeed working but it still has this issue that it won't recognize motion when it's dark. Are you sure you're not having this problem as well?
I just did a quick test (with my second sensor that I haven't mounted yet). I took it into my bathroom that has no window and gets pretty much 100 % dark. Mine works just fine. It had no issue detecting motion. I can shoot a video of it later if you want....
I installed also the quirk manually (not really complicated, I'm a dev myself) and it is indeed working but it still has this issue that it won't recognize motion when it's dark. Are you sure you're not having this problem as well?
I just did a quick test (with my second sensor that I haven't mounted yet). I took it into my bathroom that has no window and gets pretty much 100 % dark. Mine works just fine. It had no issue detecting motion. I can shoot a video of it later if you want....
Ah ok that's good. I'll try to configure it again from scratch to see if it works. Just a clarification: you're using ZHA and not zigbee2mqtt right? And if i may ask on which hardware?
I installed also the quirk manually (not really complicated, I'm a dev myself) and it is indeed working but it still has this issue that it won't recognize motion when it's dark. Are you sure you're not having this problem as well?
I just did a quick test (with my second sensor that I haven't mounted yet). I took it into my bathroom that has no window and gets pretty much 100 % dark. Mine works just fine. It had no issue detecting motion. I can shoot a video of it later if you want....
Ah ok that's good. I'll try to configure it again from scratch to see if it works. Just a clarification: you're using ZHA and not zigbee2mqtt right? And if i may ask on which hardware?
Yes... ZHA... Give me 5mins and I'll post a video... just to make sure I got the same sensor or there isn't some sort of miss-understanding...
Ah ok that's good. I'll try to configure it again from scratch to see if it works. Just a clarification: you're using ZHA and not zigbee2mqtt right? And if i may ask on which hardware?
Here it is.... didn't do a very good job filming because I had to dim the screen down to the point where I could hardly see what I was filming... However, you can clearly see the sensor triggering... https://youtu.be/5ldyrA5Ct-I
Hello, the device is possible to connect to ZHA integration but then it is not really recognized
the device is bought from here: https://de.aliexpress.com/item/1005004294995498.html?spm=a2g0o.productlist.0.0.7cff2ed9XwpAXp&algo_pvid=c25e2c8c-63d9-4cea-bb0c-5f190d010c75&aem_p4p_detail=202206032153431297942660195650067651185&algo_exp_id=c25e2c8c-63d9-4cea-bb0c-5f190d010c75-55&pdp_ext_f=%7B%22sku_id%22%3A%2212000028662981700%22%7D&pdp_npi=2%40dis%21EUR%21%2111.38%21%21%21%21%21%400b0a01f816543184230937794e1339%2112000028662981700%21sea
Device signature
```yaml { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```yaml { "home_assistant": { "installation_type": "Home Assistant OS", "version": "2022.6.1", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.9.12", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "5.15.41", "supervisor": "2022.05.3", "host_os": "Home Assistant OS 8.1", "docker_version": "20.10.14", "chassis": "vm", "run_as_root": true }, "custom_components": { "ecowitt": { "version": "0.7", "requirements": [ "pyecowitt==0.14" ] }, "frigate": { "version": "2.3", "requirements": [] }, "hacs": { "version": "1.25.5", "requirements": [ "aiogithubapi>=22.2.4" ] }, "sonoff": { "version": "3.0.5", "requirements": [ "pycryptodome>=3.6.6" ] }, "alarmo": { "version": "v1.9.3", "requirements": [] }, "remote_homeassistant": { "version": "3.6", "requirements": [] }, "ble_monitor": { "version": "8.8.0", "requirements": [ "pycryptodomex>=3.14.1", "janus>=1.0.0", "aioblescan>=0.2.12", "btsocket>=0.2.0", "pyric>=0.1.6.3" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.30.0", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.75", "zigpy-deconz==0.16.0", "zigpy==0.45.1", "zigpy-xbee==0.14.0", "zigpy-zigate==0.7.4", "zigpy-znp==0.7.0" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" } ], "after_dependencies": [ "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 46235, "manufacturer": "_TZE200_3towulqd", "model": "TS0601", "name": "_TZE200_3towulqd TS0601", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4417, "power_source": "Battery or Unknown", "lqi": 18, "rssi": null, "last_seen": "2022-06-03T19:40:04", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Additional logs
``` ```