TCL MS01 Motion Sensor

Hardware Home Automation
1

Hello all
I recently bought from a well known auction site a TCL LIFE Home automation kit (It was cheap) The App won’t install on my android system as it says it needs android v4. (Probably why it was cheap) So I thought i’d try installing OpenHAB as a learning exercise. I also have several Sonoff devices with Tasnota on them which were a breeze.
The Motion sensor though pairs and gets node discovery completed then shows several channels but these channels never seem to change.

image
image744×286 26.3 KB

image
image1000×398 23.4 KB

So I have obtained from OpenHAB the fingerprint here

openhab> zigbee fingerprint 00158D00017A2AEA
|>| Node Descriptor
| |> Logical Type               END_DEVICE
| |> MAC Capabilities           [REDUCED_FUNCTION_DEVICE]
| |> Stack Compliance           0
| |> Server Capabilities        []
| |> Buffer Size                127
| |> Incoming Transfer Size     100
| |> Outgoing Transfer Size     100
|
|>| Power Descriptor
| |> Available Power Sources    [DISPOSABLE_BATTERY]
| |> Current Power Source       DISPOSABLE_BATTERY
| |> Current Power Mode         RECEIVER_ON_IDLE
| |> Power Level                FULL
|
|>| ZDO
| |> ManagementBindRequest      TIMEOUT
| |> IeeeAddressRequest         UNKNOWN
| |> ManagementLqiRequest       TIMEOUT
| |> ManagementRoutingRequest   TIMEOUT
|
|>| Basic Information
| |> Generic Device Class       
| |> Generic Device Type        
| |> Manufacturer Name          TCL
| |> Model Indentifier          MS01
| |> Product Code               
| |> Product URL                
| |> Date Code                  00010025
| |> Application Version        1
| |> Software Build ID          
| |> Hardware Version           1
| |> Zcl Version                1
| |> Stack Version              2
| |
| |>| Endpoint 1
| | |> Profile                  0104  ZIGBEE_HOME_AUTOMATION
| | |> Device Type              0402  IAS_ZONE
| | |> Device Version           1
| | |
| | |>| Input Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster 0001 Power Configuration
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0009 Alarms
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0500 IAS Zone
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster FFFF 
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | |
| | |>| Output Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0004 Groups
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0005 Scenes
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally

However I’m stuck at this point.

I’m wondering if it only sends a presence on movement and I need to do something to reset it. The door contact that came in the package works fine as you can see the contact-portal changes when the door is opened and closed but the motion sensors channels never change… It also came with a Camera and Hub but as I couldn’t use the app I haven’t experimented with them.
I have replaced the batteries with new ones (twice to make sure)
So is there something obvious I have missed?

Martin.

2

That’s how I would assume it works. There might be some sort of internal logic to reset it but if not you can use the expire metadata to reset the Item back to off after a time.

Often (not always) what all the channels are and how they work are described in the manual. Maybe you can find a PDF online somewhere?

The only other thing to note is Zigbee devices are not always pure Zigbee. Hue, Xaiomi, Tradfri etc are notorious for adding proprietary stuff on top of the standard Zigbee meaning extra support needs to be programmed into the controllers (i.e. the Zigbee binding). Usually it’s the device is Zigbee certified there’s no problem so look for that.

Not that zigbee2mqtt had better support for these Zigbee(plus) type devices.

3

As an update, The Expire metadata seems to have done the job I used 1 minute as the reset time. I’m still puzzled about there being two channels “Motion Intrusion” and “Motion Presence” which appear to both change together and are opposite, i.e one sits idle at off and the other one on.Also although the expire metadata can SEND a command I assume that is moot as the device is probably sleeping and never receives it antway.

Martin