Need driver for Neo Coolcam Temperature and Humidity Sensor

marcus.soderberg · July 19, 2021, 12:45pm

With fully understanding that this is being helped with "pro bono" (for which I am sooo greatful for), has there been any progress or are you expecting something from me at this time?
Only wondering so that I haven't misunderstood anything and am stuck with the ball in my court here!

I have checked the trace logs and despite being set to log every 5 minutes, it reports every 10 seconds or so, but only luminance.
Should I switch to Debug or Info and provide?

snell · July 19, 2021, 2:37pm

Trace actually provides the most info for my logging because it even gives logs for things "working as intended".

At this point I think we are a bit stuck if the device is not reporting anything further, but I owe you an update to enable the refresh and read device data commands. I will remove the reporting frequency. My own Tuya 5-in-1 ignores all that also.

If, after the changes, we get nothing more from the reporting it will likely be that the device (for whatever reason) is only reporting luminance and not the other fields.

EDIT:
New version 0.1.2 is now posted. All it does is remove the reporting interval (since the device does not appear to respond to it) and make it possible to ReadDevice (gets a variety of basic attributes from the device). Plus refresh SHOULD trigger the device to respond with data...

Let me know if anything special shows up or anything different (and the general ReadDevice info). After that you can probably switch to Debug so that it only lets you know if something it is NOT handling is received. Any ZigBee data it receives that does not have a handler function should be dumped to debug (meant so I CAN add a function for it). In this case I have also changed it to log temperature, humidity, and battery to the debug so we can see if those ever show up at this point.

snell · July 23, 2021, 10:28pm

Any new information from the updated driver? Or anything come across when you do a refresh or ReadDevice?

Usually new news is good news... but I doubt this driver is just "working" yet.

marcus.soderberg · July 24, 2021, 5:39am

Sorry, I didn't realize that the new patch had been released until now.
Just installed, but still just getting luminance readings after pressing both refresh and ReadDevice. Trying humidity, temp aor battery is still drawing a blank.
When pushing configure I did get this though:

snell · July 24, 2021, 11:39am

Still those same non-useful responses from that cluster and nothing else. It should not be a defective product but I wonder if they are REALLY not following the ZigBee protocols at all really and just using a ZigBee radio for communication. They do say it requires their hub.

As for the Configure, it really would not do much since it gets called when you Save Preferences so no real surprise there.

I ordered one of these myself. I do not like little mysteries like this one... Mine should arrive Monday. Then I can really do some bashing of commands to look for responses.

marcus.soderberg · July 24, 2021, 7:09pm

What can I say? You're above and beyond!

snell · July 24, 2021, 7:24pm

I would not celebrate yet. Even once I get it there will likely be a lot of work to try to figure out what it is doing. It may not even be possible without their hub. But, I am willing to try.

It feels like I get in these cycles of drivers that work out... and attempts that do not.

Jerry.Deux · July 26, 2021, 1:56pm

Just checking in. I think I’m finally caught up with much of what everybody else already knows. One observation I made after trying the YOUPOU driver is that the battery dropped from 100 to 6; which is definitely not right. The batteries are new.

After reviewing the details from zigpy/zha-device-handlers issue#862 on GitHub I still don’t understand exactly how @oscensores was able to get it working.

Let me know if there is anything I can do to help.

snell · July 26, 2021, 6:00pm

Ok... Can you send me a Trace sometime when it reports the battery? Not sure how it would get 6%... maybe it is meant to be something else. Cannot be voltage (some report voltage) as this does not have 4 batteries (5v) does it?

That humidity is also really messed up. Obviously I have to make a fix tonight. Although the fact that it even tried to report it should be a good sign.

marcus.soderberg · July 26, 2021, 7:04pm

The batteries used are two standard AA.

snell · July 26, 2021, 10:42pm

I have posted an updated version of the driver, but it has been renamed because I am pretty sure this is actually a Tuya-based device (mine was even labeled as such from where I bought it), so here are all the basics:
Tuya Multi Sensor.groovy = 0.1.3 REPLACES YOUPOU Multi Sensor

Features:

Receives illuminance reported (note: this is NOT the same as the lux it shows on the display and there is no easy conversion between the two)
Receives battery value reported (note: specific values are unknown at this time, mine seems to be reporting 82% and I have fixed why it was reporting 6% mistakenly)

Features NOT Working:

Temperature and Humidity do not seem to be reported by the device. I have not caught a single log entry with either in it. I have also not received any of the normal Tuya cluster (EF00) that would seem to be either. This device is also reporting another cluster (E002) but so far it only seems to have pushed a value that matches what has been sent for the battery value, nothing else.
Configuring a reporting rate using "normal" ZigBee commands does not seem to work. It is a very chatty device for illuminance and nothing else.

I am continuing to log everything from it in the hopes of figuring out more. I am also going to pop mine open some evening and take a look at the board (like I did with my 5-in-1 air sensor).

If I can get a bit more progress on this thing I will create a project thread for it. At this time it just feels too incomplete.

marcus.soderberg · July 27, 2021, 5:50am

I now get a reasonable battery value (82%) that shows in the dashboard.
Will watch and see what happens in way of progress!

On another note, I saw Paul Hibbert going on about Tuya opening for localized access in the near future. I this doesn't work, maybe that will be the way?

snell · July 27, 2021, 11:07am

Probably not. Localized access would be more for their WiFi networked devices. ZigBee ones like this are already directly connected to the Hubitat, just they do not work like people expect ZigBee devices to.

Jerry.Deux · July 28, 2021, 2:10pm

Sorry for the delayed reply. For some reason I’m not getting notifications for activity on this thread.

After updating with the new driver the device reports as follows:

I realize it has already been noted that the battery is now reporting 82%, but to be sure I replaced them with brand new ones.

Here is some trace log data:

dev:842021-07-28 09:55:21.463 traceDiag enviro/Cal75 - Luminance is 12042 lx

dev:842021-07-28 09:55:13.397 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:55:05.342 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:58.730 debugDiag enviro/Cal75 - Battery at 82%

dev:842021-07-28 09:54:58.727 traceDiag enviro/Cal75 - Battery DescMap = [raw:catchall: 0104 0001 01 01 0040 00 F1BD 00 00 0000 0B 01 0682, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F1BD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

dev:842021-07-28 09:54:57.265 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:56.847 debugDiag enviro/Cal75 - Battery at 82%

dev:842021-07-28 09:54:56.844 traceDiag enviro/Cal75 - Battery DescMap = [raw:catchall: 0104 0001 01 01 0040 00 F1BD 00 00 0000 0B 01 0682, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F1BD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

dev:842021-07-28 09:54:49.701 traceDiag enviro/Cal75 - PowerSource = Battery

dev:842021-07-28 09:54:49.658 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:49.642 traceDiag enviro/Cal75 - ModelIdentifier = TS0201

dev:842021-07-28 09:54:49.623 debugDiag enviro/Cal75 - Battery at 82%

dev:842021-07-28 09:54:49.619 traceDiag enviro/Cal75 - Battery DescMap = [raw:catchall: 0104 0001 01 01 0040 00 F1BD 00 00 0000 0B 01 0682, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F1BD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

dev:842021-07-28 09:54:49.200 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:42.424 traceDiag enviro/Cal75 - ManufacturerName = _TZ3000_qaaysllp

dev:842021-07-28 09:54:41.607 traceDiag enviro/Cal75 - HardwareVersion = 01

dev:842021-07-28 09:54:41.498 traceDiag enviro/Cal75 - StackVersion = 00

dev:842021-07-28 09:54:41.472 traceDiag enviro/Cal75 - ApplicationVersion = 44

dev:842021-07-28 09:54:41.417 traceDiag enviro/Cal75 - ApplicationVersion = 44

dev:842021-07-28 09:54:41.141 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:38.869 traceDiag enviro/Cal75 - Sending request to read device attributes

dev:842021-07-28 09:54:38.860 infoDiag enviro/Cal75 - Refreshing device...

dev:842021-07-28 09:54:34.231 traceDiag enviro/Cal75 - ZCLVersion = 03

dev:842021-07-28 09:54:33.972 traceDiag enviro/Cal75 - Sending request for Basic cluster data

dev:842021-07-28 09:54:33.430 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:33.064 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:29.302 traceDiag enviro/Cal75 - Sending request to set ZigBee reporting

dev:842021-07-28 09:54:29.298 traceDiag enviro/Cal75 - Sending request to read device attributes

dev:842021-07-28 09:54:29.289 infoDiag enviro/Cal75 - Configuring device...

dev:842021-07-28 09:54:24.999 traceDiag enviro/Cal75 - Luminance is 12305 lx

dev:842021-07-28 09:54:16.933 traceDiag enviro/Cal75 - Luminance is 12042 lx

dev:842021-07-28 09:54:08.865 traceDiag enviro/Cal75 - Luminance is 12042 lx

dev:842021-07-28 09:54:00.850 traceDiag enviro/Cal75 - Luminance is 11762 lx

dev:842021-07-28 09:53:52.780 traceDiag enviro/Cal75 - Luminance is 11140 lx

dev:842021-07-28 09:53:44.667 traceDiag enviro/Cal75 - Luminance is 10793 lx

dev:842021-07-28 09:53:36.600 traceDiag enviro/Cal75 - Luminance is 10001 lx

dev:842021-07-28 09:53:30.789 traceDiag enviro/Cal75 - Luminance is 4772 lx

dev:842021-07-28 09:53:20.473 traceDiag enviro/Cal75 - Luminance is 4772 lx

dev:842021-07-28 09:53:12.402 traceDiag enviro/Cal75 - Luminance is 4772 lx

dev:842021-07-28 09:53:04.338 traceDiag enviro/Cal75 - Luminance is 4772 lx

dev:842021-07-28 09:52:56.269 traceDiag enviro/Cal75 - Luminance is 4772 lx

dev:842021-07-28 09:52:48.201 traceDiag enviro/Cal75 - Luminance is 3011 lx

dev:842021-07-28 09:52:40.136 traceDiag enviro/Cal75 - Luminance is 9543 lx

dev:842021-07-28 09:52:32.065 traceDiag enviro/Cal75 - Luminance is 15912 lx

dev:842021-07-28 09:52:24.004 traceDiag enviro/Cal75 - Luminance is 31352 lx

dev:842021-07-28 09:52:22.388 traceDiag enviro/Cal75 - Luminance is 29783 lx

dev:842021-07-28 09:52:22.268 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:52:15.314 traceDiag enviro/Cal75 - Luminance is 50 lx

dev:842021-07-28 09:52:15.084 traceDiag enviro/Cal75 - Device alive/awake

dev:842021-07-28 09:51:49.728 traceDiag enviro/Cal75 - Luminance is 6991 lx

dev:842021-07-28 09:51:41.673 traceDiag enviro/Cal75 - Luminance is 19032 lx

dev:842021-07-28 09:51:33.592 traceDiag enviro/Cal75 - Luminance is 11462 lx

dev:842021-07-28 09:51:29.046 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:51:17.457 traceDiag enviro/Cal75 - Luminance is 10001 lx

dev:842021-07-28 09:51:09.391 traceDiag enviro/Cal75 - Luminance is 14625 lx

dev:842021-07-28 09:51:01.324 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:53.260 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:45.187 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:37.119 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:29.054 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:20.986 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:12.918 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:50:04.856 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:56.834 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:48.719 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:40.648 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:32.591 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:24.846 traceDiag enviro/Cal75 - PowerSource = Battery

dev:842021-07-28 09:49:24.816 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:24.777 traceDiag enviro/Cal75 - PowerSource = Battery

dev:842021-07-28 09:49:24.525 traceDiag enviro/Cal75 - Luminance is 0 lx

dev:842021-07-28 09:49:23.953 debugDiag enviro/Cal75 - Battery at 82%

dev:842021-07-28 09:49:23.949 traceDiag enviro/Cal75 - Battery DescMap = [raw:catchall: 0104 0001 01 01 0040 00 F1BD 00 00 0000 0B 01 0682, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F1BD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

dev:842021-07-28 09:49:18.696 debugDiag enviro/Cal75 - Battery at 82%

Jerry.Deux · July 28, 2021, 2:25pm

Something I have seen from other threads that are reporting some successes with the humidity and temperature for this device is that these two parameters appear to report on endpoint-2 while other parameters report on endpoint-1. One thread suggested that the endpoint-2 was not identified during device discovery, but they did have some success after adding it with an init function.

We might be just beating our heads against a wall if Tuya has implemented some security feature that makes it work only with their own gateway.

Jerry.Deux · July 28, 2021, 4:41pm

Another oddity is that lux is a factor of illuminance, not luminance. In any case the value reported via zha does not seem to compute to the lux value seen on the display by any obvious conversion factor. The closest match I found was nox or millilux to lux, but even that is not close enough to be useful.

snell · July 28, 2021, 6:23pm

You are correct about the illuminance. They are performing some calculation on the device to determine what is displayed and it is very different from what is reported.

I am not sure on the battery value reported either. Mine ALSO report 82%. It is right in the log... But if that was converted from Hex it would be 126. Also not useful. Plus the batteries are used to provide 3v, so none of the battery related responses appear to be voltage either. So right now I am just hoping to monitor it.

This device definitely does NOT provide temperature and humidity in a normal manner. I am looking into the alternative you mentioned (also from the other thread) AND the method that they indicate in some Tuya documents to have the hub trigger a response. If I could take that maybe it would respond? Not sure though. Very annoying they could not just reuse very well-established methods everyone already handles.

Jerry.Deux · July 28, 2021, 7:04pm

Yeah, I’m not seeing any real rhyme or reason for the illuminance conversion factor

While experiment with other related drivers (user and built-in) the battery sometimes reported 100% or 3.0V, So some answers might be found in those drivers. I will look again and see if I can provide more specific examples.

Frankly I think they may deliberately be using obscure methods to encourage the use of their own gateway; which in-turn could lead to increased sales of their other proprietary devices. Personally I have no intention of ever buying any totally proprietary devices, so if that is the case I will certainly be returning this device and will not be looking at Tuya for any future purchases.

Battery test results:

It should also be noted that the value of Illuminance being reported by ZHA seems very high. While the device is reporting 15 lux on the display and 11762 via ZHA (indoors) the outdoors Illuminance reported by a weather station for my area is only 6690 on this bright sunny day.

For the sake of comparison I took the device outside for a few minutes. While the device display was showing a whopping 90278 lux my dashboard showed something very different:

Note the differences in lx on both Diag enviro and OWM Weather Device.

snell · July 28, 2021, 10:00pm

Yeah... definitely areas I need to figure out. It is not the worst looking hardware for a (relatively) cheap little sensor. I just wish they had made it easier to deal with. Still need to crack it open to take a look at the actual chipset also.

Jerry.Deux · July 28, 2021, 11:27pm

I can’t help but wonder if the endpoint-1 data might all just be a decoy