Not sure if you saw this. Not sure if anything has changed
Thankyou, I had spent a lot of time on that thread but for some reason missed that part, it's a shame there isn't very good support for mmwave multi sensors and while I appreciate all the effort that has gone into making all of these weird obscure sensors work at all its a bit of a cop out to just straight up offer little to no support for multi sensors and the solution is to just buy multiple devices.
Mine reports all parameters back just fine under the 4 in 1 driver and I dont even need the extra configuration of the mmwave sensor just active and inactive is enough but it doesn't work correctly and after some time of inactive motion it will just return to active and stay there until something passes by it again.
Most mmW devices available these days fall under the Tuya umbrella (one way or another). Tuya devices are generally pretty notorious for not adhering to standard zigbee implementations, so that makes them difficult to support at scale.
That's the main reason you don't see Tuya zigbee devices more widely supported - it's just a never-ending game of whack-a-mole.
@kkossev has bravely & tirelessly stepped up to fill this support gap for a lot of various Tuya-based zigbee products, but he'll be the first to tell you that it's a slog. But huge hat tip to him -- he does excellent work!
I think a more interesting question here is why aren't there mmW devices from any well-established players yet (e.g. Hue). Inoveli has a switch coming soon and there are some other non-Tuya players in this realm, but they are small or new players.
I find it interesting that mmW is still only available from cheap chinese manus or small/niche players.
Agreed!, kkossev does amazing work and cannot even begin to fathom how hard it must be to keep up with the million and one variations of these devices, his drivers have been instrumental for my use with the sensors I have.
You make a good point about larger brands not getting in on this market I wonder if its because the demand for this kind of thing in the west just isn't that great? or perhaps there are bigger reasons i.e compatibility, battery life, network traffic etc that the no name sensors just dont care about.
ikea have been getting into more sensors id love to see something like this from them.
I have been using device for some time now. I realized that it is reporting a very low value for illumination.
I have 2 other types of device which reports illumination and this one is reporting like 1/10 of the others.
So I tried to dig in to the code to see if there is a divider or any other manipulation/normalization. I could not find any.
I added a log line just after the "isAttribute" check in "processTuyaDPfromDeviceProfile" function.
logDebug "${value}"
The value here is the same as the one reported on UI and logs.
So can we say that this is the lack of capability of the device ? Or anything could be done in the code ? (maybe I'm missing some scale/manipulation)
The problem is that the device can not report really low illuminance. It shows 0 for non zero light conditions. That makes the illumination function unusable in some cases.
There is probably a requirement for certification around this that the Chinese ones don't have, and may be expensive/not worth it from a legit brand.
model: ZG-204ZV
manufacturer: HOBEIAN
inClusters: 0000,0003,0500,EF00,0001,0400. I have this device and no real idea what I am doing. I've used chat gpt to help, the hub is then flooded with readings according to chat gpt. Any help would be appreciated.
Is this a mmW sensor? If so, this is the wrong driver to use - this one's for PIR. The mmW driver is linked in first post.
Thanks for the reply. I tried that driver and got this, PM
error
com.hubitat.app.exception.LimitExceededException: Device 333 generates excessive hub load on line 3639 (method parse)
To be honest, I'm way out of my comfort zone but like to try!
Cheers.
I would suggest using one of the models identified as being recommended (not just supported) in the first post of these 2 threads. If you are seeking a PIR sensor, look at this thread's first post. If you are seeking a mmW sensor, look at the first post of the other thread.
Hi @kkossev .
I've purchased a mmWave Motion Sensor.
It was initially found but allocated 'Device' as the driver.
It's doesn't work correctly with your Tuya Zigbee mmWave driver but does with this one.
It does work OK with one small 'info' report in the logs.
I thought I'd post what I am seeing here in case you want to include it into this driver.
Here is the relevant information.
Here is the 'Get Info' logs.
Hi Bob,
This driver is for PIR sensors only, so it will not work with your mmWave devices. The logs that you see are due to random matching the standard ZCL cluster/attributes or Tuya ''Data Points' of other devices.
I will reply further on the mmWave sensor thread later on.
Just reading a bit more about this device, it looks like once motion is detected using an internal PIR sensor, it then activates the mmWave function.
Here is a paragraph from the spec.
The sensor is powered by battery and uses the PIR functions. Once motion is detected, the mm wave radar is activated.
Is it advertised to also measure temperature and humidity, as well as illuminance? I'm uncertain about how to classify it....it look more like a 4-in-1 sensor? The only difference seems to be that it contains both PIR and mmWave sensors.
Have you tried some of the 4 in 1 inbuilt HE drivers?
Not yet. I'll have a play.
Try the inbuilt 'Hue Motion Sensor'
Also, try this HE inbuilt driver :
Or this (also inbuilt/system!)
The last one is most promising ...
Seems there are two different HOBEIAN models - one is working with the mmWave driver, but your model - not ? See here : [FINAL RELEASE] Tuya Zigbee mmWave Sensors (code moved from the Tuya 4 In 1 driver) - #315 by mgk65
Here ? [New device support]: ZG-204ZM similar to ZG-204ZL · Issue #21919 · Koenkk/zigbee2mqtt · GitHub
All of the above drivers (apart from the HUE which does not work at all) reports lux only.
As does your 4 in 1 sensor.
Looks like I've bought a pup here. Maybe I'll play a bit more and send it back if I cannot use it.
Once again, thanks for your help.
The alternative is to wait a week or two or three, until I have the mmWave driver refactored and I can add more devices to it.