[RELEASE] Tuya Zigbee Multi-Sensor 4 In 1 (PIR motion sensors) w/ healthStatus

tim.ocallag · July 3, 2022, 3:52am

I just received 1 of the $7 Tuya motion sensors with the following (below) ...it wouldn't work with the generic zigbee motion sensor so I used your latest driver and it worked. I read above where you told someone to try the generic zigbee motion sensor (no temp), so I did and it worked.

Q1. is one recommended over the other
Q2. is there any configuration for this motion sensor in either driver?
Thanks for a great job creating a driver to allow us to use these very inexpensive sensors !!

endpointId: 01
application: 46
softwareBuild:
inClusters: 0001,0500,0003,0000
outClusters: 1000,0006,0019,000A
model: TS0202
manufacturer: _TZ3000_msl6wxk9

kkossev · July 5, 2022, 5:28am

This driver sends specific initialization commands required by some (not all!) Tuya devices during the initial pairing process.

This is another Tuya phenomena - once a device is initialized in a similar way the Tuya Zigbee gateway does it, from this time on the device can be used with the 'standard' zigbe drivers.

An advantage over the inbuilt driver is the possibility to adjust the sensor sensitivity and the device internal 'keep time'. I find useful reducing the sensitivity for my two motion sensors in the kitchen that activate some spotlights only when a person approaches really close to that particular area of the room.

When changing the motion sensor parameters, you need to press the pair/reset button at the same time when you click on the 'Save Preferences' button.

Gr0sh · July 7, 2022, 4:01pm

Hi @kkossev did you have chance to add 'keep time' configuration of this device to the driver?

kkossev · July 9, 2022, 7:29pm

Not yet, but it comes on the top of my TODO list now.

The decoding of the sensitivity and the 'keep time' was already added in this driver version 1.0.5, but not the configuration of these settings.

BTW, have you tried using this sensor ( _TZE200_3towulqd ) illuminance reading in a RM 5.1 or other HE lighting automation?
When the rule or the app gets triggered because of motion active event, is the illuminance reading correct (the illum. value that was seen in the info logs together with the motion active event), or it may be the previous illuminance value?

kkossev · July 9, 2022, 7:51pm

@Gr0sh checking the code now, I see that I have actually implemented the setting of the sensitivity and the 'keep time' for your device in version 1.0.5, I have just forgotten to announce and document it ...

Can you try changing these 2 parameters? Remember, you need to shortly press the sensor button at the same time when you click on Save Preferences button. If it doesn't work, copy/paste the logs that follow the change preferences operation.

kkossev · July 17, 2022, 7:09pm

The development branch version 1.0.7 now provides full functionality for the Tuya ZigBee Smart Ceiling-mounted Human Presence Sensor (w/ distance measurement). Many thanks to @jw970065 for the tests and the feedback!

Next on my radar is the Human Presence AIR (the ugly looking one). The behavior of this device seems to be rather different than the first one. The Chinese site mentions that it uses some kind of "MFAI Intelligent Algorithm" to "accurately identify the presence of people in the room". if MFAI stands for Mathematical Foundations of Artificial Intelligence (Australian National University, Canberra, Australia), then it could be really interesting... What I like in this device is that it does not send every second distance or other useless (for now) information, like the first sensor does. It provides the option for 3 different operational modes : "General Model", "Temporay Stay", "Basic Detecton" ( plus PIR sensor only test mode). The AIR model has 2 different tuning parameters : V-Sensitivity ["Speed Priority", "Standard", "Accuracy Priority"] and O-Sensitivity ["Sensitive", "Normal", "Cautious" ]. The 'Vacancy Delay' can be set in the range 0..1000 seconds.

jw970065 · July 18, 2022, 9:37am

I'm leaving a short message because I don't have time now.
You've worked so hard, and I'm really grateful.
I switched one Tuya switch used in the fishing cafe to Hubitat
I filmed a test video.
It looks very successful. The rest of Tuya's use will also be moved to Hubitat, and we will leave a more normal video later.
It's a noisy environment, so FP1 is a difficult place to use.
https://blog.naver.com/ispark0114/222815443522

jw970065 · July 18, 2022, 1:58pm

I ordered this sensor, too.
I don't know, but I'm interested in the combination of "mmWave" + "MFAI Intelligent Algorithm".
And I'm also interested in being able to respond to noise by choosing a variety of options, whether it will be enough or not.
I have two important things in the presence sensor
I think it is an option that can handle and respond to sensing speed and noise.

kkossev · July 18, 2022, 4:26pm

With HE you could easily change the radar operational parameters from the inbuilt Rule Machine app:

With most sensors, the parameters are usually changed once in the Preference section. But these parameters, which really make sense to be changed dynamically can be exposed as custom commands.

jw970065 · July 19, 2022, 5:05am

Today, the switch connected to all presence sensors in the urban fisherman's fishing cafe has been changed to Hubitat.
In the process, I found that using Hubitat now reacts much more sensitively.
I wonder why.
In fact, I had to change the sensitivity of all sensors from 9 to 7~8.
I will upload the final applied values and videos on the last link.

I will study about the parameters. Thank you.

jw970065 · July 19, 2022, 7:12am

이 모델이 지원되고 있는지 궁금하다.
내가 연결을 했는데, 나는 움직임을 볼 수가 없다.
아래에 로그파일이 있다.

endpointId: 01
model: TS0202
application: 46
manufacturer: _TZ3000_msl6wxk9

dev:46802022-07-19 04:04:07.360 pm info수관리실외부MotS preferencies updates are sent to the device...
dev:46802022-07-19 04:04:07.355 pm debug수관리실외부MotS sendZigbeeCommands (cmd=[he wattr 0xCF54 0x01 0x0500 0x0013 0x20 {01} {}, delay 200, he wattr 0xCF54 0x01 0x0500 0xF001 0x20 {00} {}, delay 200])
dev:46802022-07-19 04:04:07.354 pm debug수관리실외부MotS sending the changed AdvancedOptions
dev:46802022-07-19 04:04:07.347 pm debug수관리실외부MotS changing IAS Keep Time to : 30
dev:46802022-07-19 04:04:07.346 pm debug수관리실외부MotS sending sensitivity : 30 (0)
dev:46802022-07-19 04:04:07.343 pm debug수관리실외부MotS changing IAS sensitivity to : medium
dev:46802022-07-19 04:04:07.342 pm debug수관리실외부MotS sending sensitivity : medium (1)
dev:46802022-07-19 04:04:07.337 pm debug수관리실외부MotS Config parameters changed! old=bd24320921d37f1d8121bd new=bd24320913d37f1d813fbd
dev:46802022-07-19 04:04:07.329 pm info수관리실외부MotS Debug logging is will be turned off after 24 hours
dev:46802022-07-19 04:04:07.297 pm info수관리실외부MotS Debug logging is true; Description text logging is true
dev:46802022-07-19 04:04:07.296 pm info수관리실외부MotS Updating 수관리실외부MotS (Tuya Multi Sensor 4 In 1) model TS0202 manufacturer _TZ3000_msl6wxk9
dev:46802022-07-19 04:03:57.446 pm info수관리실외부MotS preferencies updates are sent to the device...
dev:46802022-07-19 04:03:57.441 pm debug수관리실외부MotS sendZigbeeCommands (cmd=[])
dev:46802022-07-19 04:03:57.440 pm debug수관리실외부MotS sending the changed AdvancedOptions
dev:46802022-07-19 04:03:57.433 pm debug수관리실외부MotS changing IAS Keep Time to : No selection
dev:46802022-07-19 04:03:57.432 pm warn수관리실외부MotS Keep Time No selection is not supported for your model:TS0202 manufacturer:_TZ3000_msl6wxk9
dev:46802022-07-19 04:03:57.430 pm debug수관리실외부MotS changing IAS sensitivity to : No selection
dev:46802022-07-19 04:03:57.429 pm warn수관리실외부MotS sensitivity No selection is not supported for your model:TS0202 manufacturer:_TZ3000_msl6wxk9
dev:46802022-07-19 04:03:57.427 pm debug수관리실외부MotS Config parameters changed! old=bd24320921d37f1d8121bd new=bd24320921d37f1d8121bd
dev:46802022-07-19 04:03:57.419 pm info수관리실외부MotS Debug logging is will be turned off after 24 hours
dev:46802022-07-19 04:03:57.388 pm info수관리실외부MotS Debug logging is true; Description text logging is true
dev:46802022-07-19 04:03:57.386 pm info수관리실외부MotS Updating 수관리실외부MotS (Tuya Multi Sensor 4 In 1) model TS0202 manufacturer _TZ3000_msl6wxk9

dev:46802022-07-19 03:53:44.890 pm info수관리실입구MotS preferencies updates are sent to the device...
dev:46802022-07-19 03:53:44.887 pm debug수관리실입구MotS sendZigbeeCommands (cmd=[])
dev:46802022-07-19 03:53:44.886 pm debug수관리실입구MotS sending the changed AdvancedOptions
dev:46802022-07-19 03:53:44.879 pm debug수관리실입구MotS changing IAS Keep Time to : No selection
dev:46802022-07-19 03:53:44.877 pm warn수관리실입구MotS Keep Time No selection is not supported for your model:TS0202 manufacturer:_TZ3000_msl6wxk9
dev:46802022-07-19 03:53:44.876 pm debug수관리실입구MotS changing IAS sensitivity to : No selection
dev:46802022-07-19 03:53:44.875 pm warn수관리실입구MotS sensitivity No selection is not supported for your model:TS0202 manufacturer:_TZ3000_msl6wxk9
dev:46802022-07-19 03:53:44.872 pm debug수관리실입구MotS Config parameters changed! old=bdbdbdbdbdbdbdbdbdbdbd new=bd24320921d37f1d8121bd
dev:46802022-07-19 03:53:44.860 pm info수관리실입구MotS Debug logging is will be turned off after 24 hours
dev:46802022-07-19 03:53:44.832 pm info수관리실입구MotS Debug logging is true; Description text logging is true
dev:46802022-07-19 03:53:44.831 pm info수관리실입구MotS Updating 수관리실입구MotS (Tuya Multi Sensor 4 In 1) model TS0202 manufacturer _TZ3000_msl6wxk9
dev:46802022-07-19 03:53:21.168 pm infoTuya Multi Sensor 4 In 1 Motion reset to inactive after 9s
dev:46802022-07-19 03:53:21.165 pm debugTuya Multi Sensor 4 In 1 Zone status: zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:46802022-07-19 03:53:21.164 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [:]
dev:46802022-07-19 03:53:12.284 pm infoTuya Multi Sensor 4 In 1 Detected motion
dev:46802022-07-19 03:53:12.260 pm debugTuya Multi Sensor 4 In 1 Zone status: zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:46802022-07-19 03:53:12.258 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [:]
dev:46802022-07-19 03:53:11.349 pm debugTuya Multi Sensor 4 In 1 NOT PARSED : descMap = [raw:CF540100001605004206545330323032, dni:CF54, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0202, clusterInt:0, attrInt:5]
dev:46802022-07-19 03:53:11.346 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [raw:CF540100001605004206545330323032, dni:CF54, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0202, clusterInt:0, attrInt:5]
dev:46802022-07-19 03:53:11.128 pm debugTuya Multi Sensor 4 In 1bind response, data=[16, 82] (Sequence Number:16, Status: FAILURE)
dev:46802022-07-19 03:53:11.125 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [raw:catchall: 0000 8021 00 00 0040 00 CF54 00 00 0000 00 00 1682, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:CF54, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[16, 82]]
dev:46802022-07-19 03:53:10.988 pm debugTuya Multi Sensor 4 In 1bind response, data=[15, 82] (Sequence Number:15, Status: FAILURE)
dev:46802022-07-19 03:53:10.985 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [raw:catchall: 0000 8021 00 00 0040 00 CF54 00 00 0000 00 00 1582, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:CF54, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[15, 82]]
dev:46802022-07-19 03:53:10.613 pm debugTuya Multi Sensor 4 In 1bind response, data=[14, 82] (Sequence Number:14, Status: FAILURE)
dev:46802022-07-19 03:53:10.609 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [raw:catchall: 0000 8021 00 00 0040 00 CF54 00 00 0000 00 00 1482, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:CF54, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[14, 82]]
dev:46802022-07-19 03:53:10.252 pm debugTuya Multi Sensor 4 In 1 write attribute response is success
dev:46802022-07-19 03:53:10.248 pm debugTuya Multi Sensor 4 In 1 parse(_TZ3000_msl6wxk9) descMap = [raw:catchall: 0104 0000 01 01 0040 00 CF54 00 00 0000 04 01 00, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:CF54, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:46802022-07-19 03:53:09.828 pm infoTuya Multi Sensor 4 In 1 installed()

kkossev · July 19, 2022, 7:52am

Yes. it is supported and I see in the logs, that motion was detected and reset to inactive after 9 seconds.

Have in mind, that changing battery-powered devices parameters is a bit tricky. They 'sleep' most of the time for the purpose of battery saving, so if you change a parameter and press ''Save' the sensor may miss the parameters change command, except the device was 'awake' at that time. Contrary, the mains / DC-powered devices (like Tuya radars) accept commands at any time.

You need to wake up the battery-powered sensor at the same time as you click on the Save button. The most effective way to wake it up is to press shortly the pair button. Most battery devices will accept parameter change also at the time when there is a movement, illuminance, or temperature/humidity change.

jw970065 · July 19, 2022, 8:09am

I tested with two sensors. But neither of them worked properly.
But because I trust you, I went through several pairs again, and now it's working well.
I don't think this is a very good sensor.
You'd better guide others to repeat it over and over again if they ask you not to do well.

kkossev · July 19, 2022, 8:38am

This is exactly what I was going to propose to you as 'plan B' ..

However, I also noticed a possible change in the latest HE platform versions, the newly paired Zigbee devices do not have the inClusters list filled in the device Data section anymore. Honestly, I don't remember if this is a platform change or I have always tried the inbuilt 'device' driver in the past, which fills in the supported/declared clusters list.
And because this driver aim is to support many different motion sensors, part of the code logic relies on whether the device supports the Zigbee standard IAS cluster (0x0500) or not. And your device is IAS reporting device, but on your screenshot the inClusters are missing. The driver should still work correctly because of the device model TS0202 being identified , but I should review the current logic and do not rely on the inClusters data.

Here I disagree, from the big variety of cheap Tuya motion sensors, _TZ3000_msl6wxk9 is probably the best one. It is one of the few models that support changing the sensitivity and the 'keep time', usually these settings are available for the more expensive models.

Beware of the battery that comes with these sensors, often the original battery is not in a good condition! The battery reporting level for many devices (not just Tuya) is not always very reliable..

I had also cases when one battery was almost depleted, and another cheap sensor had bad contact with the cell battery, You may need to examine the metal contacts and bend them a little to ensure good contact with the battery cell.

jw970065 · July 19, 2022, 8:47am

I agree. " " It is one of the few models that support changing the sensitivity and the 'keep time', usually these settings are available for the more expensive models."
In fact, another developer put a sensitivity control function in the SmartThings Hub, and I tried it.
From the developer's point of view, these sensors will be good.

Battery problems often affect sensors a lot.
As you advised, I will check the battery right away if there is a problem.

I have five of these sensors. I will use it well as you advise.

jw970065 · July 20, 2022, 12:27am

Dear kkossev
I put the sensor horizontally and conducted the test by distance. Given that the recognition varies over time depending on the distance, the distance detection ability is somewhat accurate.
I will put the video related to this in the link you know
In this way, it is possible to overcome and use an environment in which sensors are difficult to use due to the high noise.

If you place the sensor horizontally, can you recognize that it is coming from far away and that it is going from near and that it is used as a trigger?

In practice, 'aqara-fp1' uses this method.

There is a man. There are no people.
- enter, enter left/right, leave leave left/right, approhing, absenting, unknown8, unknown9
Temperature (Step 3)
Signal Strength (Stage 6)

I suggest this because I think it will be a beneficial challenge for you.

I bought the same sensor in 3 places, and all the manufacturers were the same regardless of the brand (my favorite sensor)
The only thing that's wrong is whether you give the price and the power supply.
If you have a purchase plan, please refer to it

bptworld · July 20, 2022, 10:03pm

Does anyone have this sensor?

Mine arrived today but I can't get it to pair at all (or do anything). When I plug it in, there are no flashing light, beep or other sign of life.

I've tried pluging it in and pressing the button (once, three times, five times)
I've tried holding the button ( 3 seconds, 5 seconds, even 30 seconds)

Still no flashing light or any signs of like.

jw970065 · July 21, 2022, 3:05am

I have this sensor.

It is important for the presence detection sensor to change the setting value that solves the noise, which does not have such a function. Moreover, the sensor is not "mmWave".
So I dealt with this dispute,
To pair, you have to press with a pin.

If you press the pin to make a sound (It is important to make a sound.)and wait a little, the light flashes.

![photo_2022-07-21_14-01-58|666x500]

(upload://r8RnSZW74SSnTUdkBNOsjOxL5qD.jpeg)
Pairing works in Hubitat. But the sensor doesn't seem to work.

kkossev · July 21, 2022, 5:59am

What is the Manufacturer from the device Data section when paired to Hubitat?

Looking at the picture, I see two mmWave antennas on the PCB… but with these manufacturers you never know if it is really functional or just a place holder.

jw970065 · July 21, 2022, 6:06am

There seems to be no information from the manufacturer, and it is paired with Xiaomi products.
It doesn't actually work.

dev:47692022-07-21 03:09:29.003 pm infoReset button pressed/message requested by hourly checkin - description:read attr - raw: 37EF0100001605004206545330363031, dni: 37EF, endpoint: 01, cluster: 0000, size: 16, attrId: 0005, encoding: 42, command: 01, value: 06545330363031 | parseMap:[raw:37EF0100001605004206545330363031, dni:37EF, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0601, clusterInt:0, attrInt:5] 1

dev:47692022-07-21 03:09:29.001 pm infomsgMap: [raw:37EF0100001605004206545330363031, dni:37EF, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0601, clusterInt:0, attrInt:5]

dev:47692022-07-21 03:09:26.996 pm infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 37EF 00 00 0000 00 00 7F82, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:37EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[7F, 82]]

dev:47692022-07-21 03:09:26.030 pm infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 37EF 00 00 0000 00 00 7D00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:37EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[7D, 00]]

dev:47692022-07-21 03:09:26.014 pm infoReset button pressed/message requested by hourly checkin - description:read attr - raw: 37EF0100001605004206545330363031, dni: 37EF, endpoint: 01, cluster: 0000, size: 16, attrId: 0005, encoding: 42, command: 01, value: 06545330363031 | parseMap:[raw:37EF0100001605004206545330363031, dni:37EF, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0601, clusterInt:0, attrInt:5] 1

dev:47692022-07-21 03:09:26.012 pm infomsgMap: [raw:37EF0100001605004206545330363031, dni:37EF, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0601, clusterInt:0, attrInt:5]

dev:47692022-07-21 03:09:25.940 pm infoReset button pressed/message requested by hourly checkin - description:read attr - raw: 37EF0100001605004206545330363031, dni: 37EF, endpoint: 01, cluster: 0000, size: 16, attrId: 0005, encoding: 42, command: 01, value: 06545330363031 | parseMap:[raw:37EF0100001605004206545330363031, dni:37EF, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0601, clusterInt:0, attrInt:5] 1

dev:47692022-07-21 03:09:25.938 pm infomsgMap: [raw:37EF0100001605004206545330363031, dni:37EF, endpoint:01, cluster:0000, size:16, attrId:0005, encoding:42, command:01, value:TS0601, clusterInt:0, attrInt:5]

dev:47692022-07-21 03:09:24.114 pm infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 37EF 00 00 0000 00 00 7F82, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:37EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[7F, 82]]

dev:47692022-07-21 03:09:23.923 pm infoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...

dev:47692022-07-21 03:09:23.914 pm infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 37EF 00 00 0000 00 00 7D00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:37EF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[7D, 00]]

dev:47692022-07-21 03:09:23.899 pm infoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...

dev:47692022-07-21 03:09:23.856 pm infoRecovery feature ENABLED

dev:47692022-07-21 03:09:23.758 pm infogetDriverVersion() = v1.0.1.1123

dev:47692022-07-21 03:09:23.745 pm infoinstalled()

I don't know if the log file will help.

I don't understand, but the content seems to have changed.

I changed it to the driver you made, and I saw the log again.
It is recognized as a Presence sensor, not a motion sensor.
22072103

search

dev:47692022-07-21 03:21:15.572 pm errororg.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'null' with class 'null' to class 'int'. Try 'java.lang.Integer' instead on line 948 (method updated)

dev:47692022-07-21 03:21:15.560 pm debug도플러 레이더 Config parameters changed! old=bd24320921d37f1d8121bd new=bd24320921d37f1d8121bd

dev:47692022-07-21 03:21:15.554 pm info도플러 레이더 Debug logging is will be turned off after 24 hours

dev:47692022-07-21 03:21:15.521 pm info도플러 레이더 Debug logging is true; Description text logging is true

dev:47692022-07-21 03:21:15.519 pm info도플러 레이더 Updating 도플러 레이더 (Zigbee - Xiaomi/Aqara Motion Sensor) model TS0601 manufacturer null

dev:47692022-07-21 03:21:15.518 pm debug도플러 레이더 state.hashStringPars = bd24320921d37f1d8121bd

dev:47692022-07-21 03:21:15.506 pm info도플러 레이더 InitializeVars( fullInit = false )...

dev:47692022-07-21 03:21:15.504 pm debug도플러 레이더 updating the settings from the current driver version null to the new version 1.0.7 2022/07/17 9:02 PM

dev:47692022-07-21 03:21:01.048 pm errororg.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'null' with class 'null' to class 'int'. Try 'java.lang.Integer' instead on line 948 (method updated)

Summary

This text will be hidden