What is the manufacturer ID for this device ?
Isn't it the best choice for mounting on a wall
1 Like
- endpointId: 01
- model: TS0601
- application: 41
- manufacturer: _TZE200_ztc6ggyl
You can put it on the wall or on the ceiling.
If you don't want to make a hole in the ceiling, I think you can put it up.
1 Like
Perhaps, there will be no problem with double-sided tape.
1 Like
There is a company that develops counter sensors in Korea.
Not perfect yet.
I has a first generation of improvements.
Season 1 counter sensor will be upgraded free of charge to Super Dual Motion Sensor (DMS-300ZB), which can set the detection time per second.
For reference, the dual motion sensor uses a case with a wide initial detection angle, provides three motion sensor functions: inner, outer, and integrated, and is available for ST (edge) and HA (z2m).
Hello, I'm Shihas.
It's already been a year since we released a counter sensor (season 1) using dual PIR.
Season 1, the first generation of counter sensors, used two PIR sensors to handle counting, but the wide range of detection caused many errors in the beginning, and later modified the mold to enhance detection range masking and reduce errors, but the PIR signal itself was based on temperature change, long detection signal, and sensitivity differences between the two sensors.
Season 2, the second generation of counter sensors, is configured to handle counting with PIR+ToF, unlike the first generation, which is PIR+PIR. In Season 2, the PIR is used only as a prior detection for battery power saving, and the actual counting is handled only by the ToF sensor.
Therefore, there are no errors counted when there are no people like in season 1 and errors due to changes in ambient temperature. In addition, the high-speed laser-based ToF sensor has improved the counting error due to fast counting and slow hesitation, and entering and leaving immediately.
Like the first-generation season 1, the cafe test group (13 people) was pre-tested for about a month. Through the test, not only the ST environment but also the HA environment was improved. Nevertheless, season 2 is also a sensor, so there may be some errors depending on the usage environment.
Depending on the user's environment, the optimization setting of the installation height, installation direction, and counting transaction time can be minimized.
** Key features of the season 2 counter sensor include:
- Function: Improvement of counting function by PIR+ToF sensor
- Support platform: ST edge driver, HA z2m (OTA support)
- Power: USB-C type rechargeable lithium-ion battery (2000mA), used for about 1 year when detecting every 10 minutes
- Size: Smaller and Slim compared to Season 1, 55W×74H×16D (including bracket) Unit: mm
- Automatic environment setting according to installation location with distance measurement adjustment function according to use environment (maximum distance of 2.4m)
- Provides a Seahas Button-type Switch (SBM-300 Series) and fast RF integration
- Provide quick counting function for initial check-in (0->1) and last check-out (1->0)
- Translation interval setting function for continuous access optimization (0-1 second, step 6)
- Provision of counting stop (freeze) function for selecting usage conditions when automating ST by counter value 10. Provide various setting functions (set by button, set by counter value, set by ST app)
- Support for installation of ST edge driver (V2) and instruction manual through QR code
Link to purchase page (not available on Naver Pay) 무선 재실 카운터 센서 CSM-300-ZB시즌2
1 Like
This device looks very interesting!
Are there any plans to add a Zigbee interface to it (instead of WiFi) ?
1 Like
No, 'battery unknown' means that the currently implemented OFFLINE detection logic in the driver does not work very well for these particular devices. Can you post the devices Manufacturer IDs?
The issue is that every device has a different implementation of the check-in / heartbeat mechanism to announce it is alive. I suppose these 'battery unknown' events are observed after long periods of inactivity?
"counter sensor" is a Zigbee product.
1 Like
Then it shouldn’t be a problem to add full support for it in HE as well.
Can you obtain some documentation?
1 Like
I have a first-generation product at home. I'll try to connect to HE when I get home. I will give you feedback when I get the information from there.
1 Like
The contents of the sensor.
People usually use it a lot for the automation of toilets.
I use it at the entrance, but the gown is not accurate, so I used it only for entrance and exit checking.
It is said that the second-generation product has improved accuracy by using PIR + Top sensor.
1 Like
Information for the device.
I am a member of the best smart home community in the Republic of Korea.
The president of Sihaas, who makes counter sensors, is also a member of the community.
He is very passionate and has good feedback.
If you ask for information, I will ask him for the data.
Device pairing info
| Manufacturer: | ShinaSystem |
|---|---|
| Endpoint 01 application: | 03 |
| Endpoint 01 endpointId: | 01 |
| Endpoint 01 idAsInt: | 1 |
| Endpoint 01 inClusters: | 0000,0004,0003,0001,000C |
| Endpoint 01 initialized: | true |
| Endpoint 01 manufacturer: | ShinaSystem |
| Endpoint 01 model: | CSM-300Z |
| Endpoint 01 outClusters: | 0000,0004,0003,0019,0006 |
| Endpoint 01 profileId: | 0104 |
| Endpoint 01 stage: | 4 |
Summary
dev:3282022-09-18 10:24:56.060 am debugCountSen pollPresence()
dev:3282022-09-18 09:24:56.035 am debugCountSen pollPresence()
dev:3282022-09-18 08:24:56.006 am debugCountSen pollPresence()
dev:3282022-09-18 07:24:55.929 am debugCountSen pollPresence()
dev:3282022-09-18 06:24:55.886 am warnCountSen forced motion to 'inactive
dev:3282022-09-18 06:24:55.883 am infoCountSen Motion reset to inactive after 14400s
dev:3282022-09-18 06:24:55.862 am warnCountSen is not present!
dev:3282022-09-18 06:24:55.847 am debugCountSen pollPresence()
dev:3282022-09-18 05:24:55.818 am debugCountSen pollPresence()
dev:3282022-09-18 04:24:55.788 am debugCountSen pollPresence()
dev:3282022-09-18 03:24:55.763 am debugCountSen pollPresence()
dev:3282022-09-18 03:10:05.654 am infoCountSen reported Power source 03
dev:3282022-09-18 03:10:05.651 am debugCountSen parse(ShinaSystem) descMap = [raw:7C080100001007003003FEFF86, dni:7C08, endpoint:01, cluster:0000, size:10, attrId:0007, encoding:30, command:01, value:03, clusterInt:0, attrInt:7, additionalAttrs:[[status:86, attrId:FFFE, attrInt:65534]]]
dev:3282022-09-18 03:10:04.835 am debugCountSen sendZigbeeCommands (cmd=[he raw 0x7C08 1 0x01 0x0000 {10 00 00 07 00 FE FF}, delay 200])
dev:3282022-09-18 03:10:04.833 am debugCountSen refresh()...
dev:3282022-09-18 02:25:35.861 am infoCountSen preferencies updates are sent to the device...
dev:3282022-09-18 02:25:35.858 am debugCountSen sendZigbeeCommands (cmd=[])
dev:3282022-09-18 02:25:35.857 am debugCountSen sending the changed AdvancedOptions
dev:3282022-09-18 02:25:35.849 am debugCountSen Config parameters changed! old=2424320913d37f1d813fbd new=2424320913d37f1d813fbd
dev:3282022-09-18 02:25:35.841 am infoCountSen Debug logging is will be turned off after 24 hours
dev:3282022-09-18 02:25:35.807 am infoCountSen Debug logging is true; Description text logging is true
dev:3282022-09-18 02:25:35.804 am infoCountSen Updating CountSen (Device) model CSM-300Z manufacturer ShinaSystem
dev:3282022-09-18 02:25:05.383 am debugCountSen write attribute response is FAILURE
dev:3282022-09-18 02:25:05.380 am debugCountSen parse(ShinaSystem) descMap = [raw:catchall: 0104 0000 01 01 0040 00 7C08 00 00 0000 04 01 86DEFF, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:7C08, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[86, DE, FF]]
dev:3282022-09-18 02:25:05.373 am infoCountSen Tuya device manufacturer is ShinaSystem
dev:3282022-09-18 02:25:05.365 am debugCountSen parse(ShinaSystem) descMap = [raw:7C080100005E0400420B5368696E6153797374656D00000020020100002003050000420843534D2D3330305A0700003003FEFF86, dni:7C08, endpoint:01, cluster:0000, size:5E, attrId:0004, encoding:42, command:01, value:ShinaSystem, clusterInt:0, attrInt:4, additionalAttrs:[[value:02, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:03, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:CSM-300Z, encoding:42, attrId:0005, consumedBytes:11, attrInt:5]]]
dev:3282022-09-18 02:24:57.444 am infoCountSen Received bind response, data=[A4, 00] (Sequence Number:A4, Status: Success)
dev:3282022-09-18 02:24:57.441 am debugCountSen parse(ShinaSystem) descMap = [raw:catchall: 0000 8021 00 00 0040 00 7C08 00 00 0000 00 00 A400, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7C08, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A4, 00]]
dev:3282022-09-18 02:24:57.416 am infoCountSen Received bind response, data=[A3, 00] (Sequence Number:A3, Status: Success)
dev:3282022-09-18 02:24:57.412 am debugCountSen parse(ShinaSystem) descMap = [raw:catchall: 0000 8021 00 00 0040 00 7C08 00 00 0000 00 00 A300, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7C08, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A3, 00]]
dev:3282022-09-18 02:24:57.312 am infoCountSen Received bind response, data=[A2, 00] (Sequence Number:A2, Status: Success)
dev:3282022-09-18 02:24:57.308 am debugCountSen parse(ShinaSystem) descMap = [raw:catchall: 0000 8021 00 00 0040 00 7C08 00 00 0000 00 00 A200, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7C08, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[A2, 00]]
dev:3282022-09-18 02:24:56.932 am infoCountSen Received device announcement, data=[C3, 08, 7C, 78, D8, 36, 07, 00, 8D, 15, 00, 80] (Sequence Number:C3, Device network ID: 7C08, Capability Information: 80)
dev:3282022-09-18 02:24:56.924 am debugCountSen parse(ShinaSystem) descMap = [raw:catchall: 0000 0013 00 00 0040 00 7C08 00 00 0000 00 00 C3087C78D83607008D150080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7C08, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[C3, 08, 7C, 78, D8, 36, 07, 00, 8D, 15, 00, 80]]
dev:3282022-09-18 02:24:55.784 am debugCountSen sendZigbeeCommands (cmd=[he raw 0x7C08 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x7C08 0x01 0x0000 0xFFDE 0x20 {13} {}, delay 200, delay 200, zdo bind 0x7C08 0x02 0x01 0x0402 {00158D000736D878} {}, delay 200, zdo bind 0x7C08 0x02 0x01 0x0405 {00158D000736D878} {}, delay 200, zdo bind 0x7C08 0x03 0x01 0x0400 {00158D000736D878} {}])
dev:3282022-09-18 02:24:55.738 am infoCountSen configure()..
dev:3282022-09-18 02:18:55.576 am infoCountSen reported Power source 03
dev:3282022-09-18 02:18:55.564 am debugCountSen parse(ShinaSystem) descMap = [raw:606C0100001007003003FEFF86, dni:606C, endpoint:01, cluster:0000, size:10, attrId:0007, encoding:30, command:01, value:03, clusterInt:0, attrInt:7, additionalAttrs:[[status:86, attrId:FFFE, attrInt:65534]]]
dev:3282022-09-18 02:18:55.250 am debugCountSen sendZigbeeCommands (cmd=[he raw 0x606C 1 0x01 0x0000 {10 00 00 07 00 FE FF}, delay 200])
dev:3282022-09-18 02:18:55.249 am debugCountSen refresh()...
dev:3282022-09-18 02:17:35.793 am infoCountSen preferencies updates are sent to the device...
dev:3282022-09-18 02:17:35.789 am debugCountSen sendZigbeeCommands (cmd=[])
dev:3282022-09-18 02:17:35.787 am debugCountSen sending the changed AdvancedOptions
dev:3282022-09-18 02:17:35.778 am debugCountSen Config parameters changed! old=bdbdbdbdbdbdbdbdbdbdbd new=2424320913d37f1d813fbd
dev:3282022-09-18 02:17:35.764 am infoCountSen Debug logging is will be turned off after 24 hours
dev:3282022-09-18 02:17:35.732 am infoCountSen Debug logging is true; Description text logging is true
dev:3282022-09-18 02:17:35.729 am infoCountSen Updating CountSen (Device) model CSM-300Z manufacturer ShinaSystem
dev:3282022-09-18 02:13:54.746 am infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0004,0003,0001,000C", outClusters:"0000,0004,0003,0019,0006", model:"CSM-300Z", manufacturer:"ShinaSystem"
dev:3282022-09-18 02:13:53.745 am traceZCL version:02
dev:3282022-09-18 02:13:53.743 am traceSoftware Build Id:4000-0001
dev:3282022-09-18 02:13:53.742 am traceModel:CSM-300Z
dev:3282022-09-18 02:13:53.741 am traceManufacturer:ShinaSystem
dev:3282022-09-18 02:13:52.933 am debuggetting info for unknown Zigbee device...
dev:3282022-09-18 02:13:50.914 am debugconfigure() called...
[/details]
1 Like
Hey @jw970065 , thank you for the info!
I've found the SmartThings driver code for an older version of the device here, so I may have all the information needed.
With the approaching winter season and the increasing costs of energy here in Europe, I suppose that will be rather busy improving my drivers related to energy savings in the next few months.. So I can come back to this device probably in the beginning of the next year.
1 Like
This first-generation device will be eliminated and the second-generation version will be in operation. Of course, the structure will be the same.
Instead, the first generation device will be changed to a dual motion sensor.
If there is a change, I will tell you the relevant news.
I am also concerned about the situation in Europe. I hope you have a safe winter.
1 Like
Hi there. Can anyone please clarify that these links referred to at the top of this thread are actually 2 different devices please? They have different prices and the Moes device seems to have the additional luminance and PIR sensor. But apart from that they are the same (eg. same frequency and so similar range and functionality in terms of motion sensing).
Is there any benefit of using the other devices mentioned with a higher frequency radar? Better range? Better sensitivity? They are more expensive. Worth it?
I’m thinking to use these devices in indoor ceilings for motion lighting, and use the ones with luminance sensing for outdoors on my terrace so that I can evaluate the light level too for auto mode setting (I currently use Xiaomi luminance sensors for that which work well but are battery operated, which is a pain). I currently use PIR sensors and cameras with tinyCAM person detection to keep lights on with no motion but I think these should be better/simpler.
Basically just looking for the “state of the art” for motion and presence detection please.
Thank you for any advice.
Is it possible to automatically change the setting value of the presence detection sensor from a specific situation or mode to a program?
You didn't leave a link.
Probably the same product. If the presence sensor has the same picture, it's generally likely that it's the same product. It's just assumed that the brand is different.
These two products perform best.
https://blog.naver.com/ispark0114/222832624821
This goes back a bit
Manufacturer IDs:
_TZ3000_mcxw5ehu
_TZ3000_msl6wxk9
_TZ3210_zmy9hjay
I have not noticed missed events from these sensors. They do seem to report power source unknown during periods of time long inactivity.
Thank you so much for this! I purchased a "Smart ZIGBEE Motion Sensor" from Amazon which showed up with ID TS0202 and it seems to work, prior using this driver, the Generic Zigbee Motion Sensor driver was not working, it only showed the power.
1 Like
It’s a screen shot from the OP. The links are in there (top of this thread).
Definitely not the same product.
I went into the link. Two are different products.
MOES:(link) products are the best.
But it is very expensive. You can buy a cheap product among the same shape. However, it is necessary to check whether the power supply line is supported.
In this case, it is more convenient to quote than to take a picture.
