Anyone by chance tried one of these with HA?
RGBgenie ZigBee 3.0 RGBW Remote and Dimmer, 4 zones with 3 Scenes, On/Off, Color and Brightness Control. Works with Philips Hue. ZB-5008 https://www.amazon.com/dp/B07KBF9GMS/ref=cm_sw_r_cp_api_glt_fabc_ZXSY1FEAPM57P6YYNT1R
1 Like
I have played with one of these, they will join to HA, but you won’t get any events/entities ( a quirk is likely needed) but you can bind them to lights or zigbee groups and they work fine that way. its is pretty powerful as it has 4 different endpoints for control, so you can join 4 different groups, and you select them by the 1 2 3 4 on the remote.
The remote does power down (completely off) when not in use so it can take a few seconds to wake up and rejoin.
Hi Gunther, I have asked for this device to be added to ZHA on Github, nobody has yet picked it up so maybe if you could add a comment to the request on Github, someone on the team might help us out.
Does anyone use this Tuya Water leak sensor with ZHA?
Just want to know if its working fine or not. Thanks
Hi Jason,
I would love to add a few Zigbee remote controls to the zha quirks, but is the information which I supplied enough to add a control? I got about 4 remote controls that I would love to use with Home Assistant.
Where on Github should I report thisfor zha-quirks? Here: GitHub - zigpy/zha-device-handlers ? And do I need to include more information or is that info sufficient to work with?
I think you misunderstood that a little. 
You can/have to do that and submit it to the repository you linked in your post, when you got it working.
Take a look here
and here
I have had multiple battery devices drop off and fail to rejoin recently some times hitting the pairing button a few times will wake them some times I need to put them in to pairing mode and re join them
I’m posting again here because it seems as if my problem has returned. I bought a brand new Hue outdoor motion sensor to rule out the sensor. It seemed as if everything was working for a while, but then noticed recently that things were not. Looking closer I have the same behavior again. I had not added new devices, or changed my configuration in quite a while. It seems to me that this is a the most common scenario
- State change in motion
- Motion detected or cleared
- Then device goes unavailable foe 30-60 seconds
- Then seems to work until the next state change
it does not go unavailable after every state change, just seems to correlate often.
For example sitting there with no motion detected. I walk outside, trigger motion, walk back inside to check state and find it had detected motion, went unavailable, and then back to available after a bit.
Same behavior with both the new and the older sensor. I dont feel like my other zha devices are having issues like this, or at least not enough to notice. I have 43 ZHA devices, maybe I’m just getting to my limit of devices??
Trying to get MOSZB-140 to work with home assistant. It already is supported by zigbee2mqtt. (https://www.zigbee2mqtt.io/devices/MOSZB-140.html).
In home assistant it does not import the sensors correctly.
I think it should expose occupancy, battery_low, tamper, temperature, illuminance_lux, linkquality.
Here is a pastebin log from pair: https://pastebin.com/VNbSQSpH
Here is link to develco’s technical manual for this device: https://www.develcoproducts.com/media/1697/moszb-130-14x-technical-manual-motion-sensor-040721.pdf
This is how the sensor looks imported:
Zigbee device signature from home assistant.
{
"node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=0, manufacturer_code=4117, maximum_buffer_size=80, maximum_incoming_transfer_size=80, server_mask=0, maximum_outgoing_transfer_size=80, descriptor_capability_field=0, *allocate_address=False, *complex_descriptor_available=False, *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, *is_valid=True, *logical_type=<LogicalType.EndDevice: 2>, *user_descriptor_available=False)",
"endpoints": {
"1": {
"profile_id": 49353,
"device_type": "0x0001",
"in_clusters": [
"0x0003",
"0x0005",
"0x0006"
],
"out_clusters": []
},
"34": {
"profile_id": 260,
"device_type": "0x0107",
"in_clusters": [
"0x0000",
"0x0003",
"0x0406"
],
"out_clusters": []
},
"35": {
"profile_id": 260,
"device_type": "0x0402",
"in_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x000f",
"0x0020",
"0x0500"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"38": {
"profile_id": 260,
"device_type": "0x0302",
"in_clusters": [
"0x0000",
"0x0003",
"0x0402"
],
"out_clusters": [
"0x0003"
]
},
"39": {
"profile_id": 260,
"device_type": "0x0106",
"in_clusters": [
"0x0000",
"0x0003",
"0x0400"
],
"out_clusters": []
},
"40": {
"profile_id": 260,
"device_type": "0x0107",
"in_clusters": [
"0x0000",
"0x0003",
"0x0406"
],
"out_clusters": []
},
"41": {
"profile_id": 260,
"device_type": "0x0107",
"in_clusters": [
"0x0000",
"0x0003",
"0x0406"
],
"out_clusters": []
}
},
"manufacturer": "Develco Products A/S",
"model": "MOSZB-140",
"class": "zigpy.device.Device"
}
1 Like
I’ve successfully added the Sonoff SNZB-04 Wireless Door/Window Sensor to ZHA without any issues.
I’m able to see it in Node-Red and Lovelace just like I had hoped and wanted to.
I’m quite please with it so far.
I know this is a bit late, but I was able to configure it and I was able to integrate it with the Alarm Control Panel and setup some flows in NodeRed that allow me to arm the virtual alarm panel and that will arm the physical keypad and vice versa. Happy to share if you are interested.
I’ve successfully added the MOES 4 Scene Remot to ZHA without any issues.
I’m able to see it in Node-Red just like I had hoped and wanted to.
I’m quite please with it so far.
Trying to get the “Third Reality” water leak sensor to work with zha. I was able to add it successfully but no device is created. Any idea?
Signature is
{
"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=4659, 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",
"0x0500"
],
"out_clusters": [
"0x0006",
"0x0019"
]
}
},
"manufacturer": "Third Reality, Inc",
"model": "3RWS18BZ",
"class": "zigpy.device.Device"
}
Lots of lines like these ones in the log (it keeps changing the class in the second log line):
[zigpy.quirks.registry] Fail because endpoint list mismatch: {232, 230} {1}
[zigpy.quirks.registry] Considering <class ‘zhaquirks.smartthings.tag_v4.SmartThingsTagV4’>
And then
2021-11-01 10:07:02 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x94E1: completed configuration
2021-11-01 10:07:02 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x94E1: stored in registry: ZhaDeviceEntry(name=‘unk_manufacturer unk_model’, ieee=‘28:2c:02:bf:ff:e7:29:21’, last_seen=1635786422.3793445)
2021-11-01 10:07:02 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x94E1: started initialization
2021-11-01 10:07:02 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] 0x94E1:ZDO: ‘async_initialize’ stage succeeded
2021-11-01 10:07:02 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendUnicast: (<EmberOutgoingMessageType.OUTGOING_DIRECT: 0>, 0x94E1, EmberApsFrame(profileId=0, clusterId=4, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY|APS_OPTION_RETRY: 320>, groupId=0, sequence=4), 5, b’\x04\xe1\x94\x01’)
2021-11-01 10:07:02 DEBUG (bellows.thread_0) [bellows.uart] Sending: b’6684219c54cb81b259904a25aa1593499c4a22afe92ff38a32a27e’
2021-11-01 10:07:02 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x94E1: power source: Battery or Unknown
2021-11-01 10:07:02 DEBUG (MainThread) [homeassistant.components.zha.core.device] 0x94E1: completed initialization
2021-11-01 10:07:02 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py”, line 569, in async_device_initialized
device_info = zha_device.zha_device_info
File “/usr/src/homeassistant/homeassistant/components/zha/core/device.py”, line 505, in zha_device_info
ATTR_NAME: f"unknown {endpoint.device_type} device_type "
TypeError: unsupported format string passed to NoneType.format
2021-11-01 10:07:02 DEBUG (MainThread) [zigpy.appdb] Error handling ‘_save_device’ event with (,) params: NOT NULL constraint failed: endpoints_v6.profile_id
Got the Moes TV01 TRV: Tuya ZigBee3.0 New Mini Radiator Actuator Valve Smart Programmable The – Moes
{
"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=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=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": "0x0301",
"in_clusters": [
"0x0000",
"0x0001",
"0x0004",
"0x0005",
"0x0201",
"0x0204",
"0xef00"
],
"out_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZE200_e9ba97vf",
"model": "TS0601",
"class": "zhaquirks.tuya.ts0601_trv.ZonnsmartTV01_ZG"
}
Seems to be working as it should except for the built-in temp sensor:
-
Temp values are static and way above actual room temp (26,2C). Using the built-in temp offset feature I’m able to affect the temp reading but it’s still static and still wrong (also the offset value is not 1:1 to the temp reading)
-
I was not too concerned as I was planning on using an external temp sensor anyways, using a script and automation based on this principle: Danfoss Ally TRV working with remote temp sensor
Unfortunately I’m unable to send any temp value to the Zigbee cluster. Target temp, mode, etc. works without any issue but no success with temp. I’m using the following settings:
Cluster: ZONNSMARTManufCluster (Endpoint id: 1, Id: 0xef00, Type: in)
Cluster attribute: ZONNSMARTManufCluster (Endpoint id: 1, Id: 0xef00, Type: in)
Any ideas?
If anybody has similar problem with TV01 TV02 TV05, the code for this device was extended in HA 2022.3 and the not changing current temperature is known power saving feature. Read this [Device Support Request] TS0601 _TZE200_hue3yfsn / TV02 Zigbee TRV · Issue #1027 · zigpy/zha-device-handlers · GitHub
I have a zigbee bathroom mirror cabinet from Villeroy & Boch (My View Now) and it can’t connect at all with ZHA.
Pairs easily with Hue bridge and shows as color temperature light.
https://www.home-assistant.io/integrations/zha#how-to-add-support-for-new-and-unsupported-devices
Consider reporting as a new “Device support request” to ZHA Device Handlers (a.k.a. zha-quirks) repo:
https://github.com/zigpy/zha-device-handlers/issues
Be sure to search there for using the Zigbee device signature to see if there are any existing requests.
Read these ZHA documentation sections relative to understanding why such “quirks” are needed:
https://www.home-assistant.io/integrations/zha#knowing-which-devices-are-supported
https://www.home-assistant.io/integrations/zha#how-to-add-support-for-new-and-unsupported-devices
https://www.home-assistant.io/integrations/zha#reporting-issues
https://www.home-assistant.io/integrations/zha#debug-logging
Hi, I saw this an wondered if you had any problems with your doorbell triggering the sensor. It’s setup and recognised in ZHA. I can trigger in HA buy using the “Press” button. But the doorbell doesnt make any registered change.
Added an IKEA PILSKOTT LED floor lamp. Steps:
- Put ZHA in pairing mode
- Pushed the pairing button on the base of the lamp
- Configured the lamp in the UI
Now everything works:
have you tried this sensor near gas stove? I’ve seen a lot of negative reviews about this item.