Sorry, my fault, I made a mistake and modified wrong driver…
Can you test the 1.9.3 new version :
You’ll need to remove then add again your device.
As previously, after testing, let it run for at least 30 minutes and then, send me another Diag report.
Regards,
SoPhos
Hi Serge,
Good news: the relay/switch function is now working correctly. I can switch the toilet light ON and OFF from Homey.
However, I still don’t see any presence detection/sensor capability for the device in Homey.
Regards,
Han
Hi ,
You can try 1.9.4 test version, maybe presence will be Ok regarding your previous Diagnostic report.
If not, let it run for at least 30 minutes and then, send me another Diag report.
Regards,
SoPhos
Hi SoPhos,
I tested version 1.9.4 and let it run for more than 30 minutes.
The switch on/off function now works correctly, and the presence trigger/condition cards are visible in Homey. However, presence itself still does not work. Homey shows the presence capability as alarm_presence: null, so no presence events are generated and a Flow based on presence does not trigger.
New Diagnostic Report ID: b1d408a0-88dd-4220-8b2f-af03b70f11e3
Regards,
Han
Hi all,
Thanks to 
Gabriel Machado advice and recommandations, a new Homey MOES App version has been published in test.
This new version adds compatibility for MOES Human Presence Sensor (ZSS-LP-HP02-MS).
This new test version is available in Homey store :
Thank you Gabriel Machado !!!
Regards,
SoPhos
Hi, I noticed version 1.9.5 and installed it, but no change…
Hi,
You can see changelog in Homey App store page.
Regards,
SoPhos
Hi SoPhos,
Thanks. I checked the changelog and I’m already running version 1.9.5.
The device became unavailable, so I removed it and paired it again. Switching the light on and off through Homey works, but the presence value remains at 0, even when I move directly in front of the sensor.
Is any additional configuration required? Please let me know if you need a diagnostic report.
Kind regards,
Han
Hi Han_Kamminga,
I could get one ZS Smart Presence Switch device but I need time to integer Presence Sensor in driver.
So, be patient, It will happen soon now.
Regards,
SoPhos
Ok, it would be nice to have it working as these things are all you need in a small room, if they function properly
HI Han_Kamminga,
Finaly, I could integer Presence Sensor in MOES Smart Presence Switch (ZS-S-EUx-*-MS) device (1,2 and 3 Gang).
You can new testing version of MOES App in Homey App Store :
You should be aware that I’ve done some testing, and it seems that MOES Smart Presence Switch is not actually a true presence sensor, but rather an enhanced motion sensor.
Regards,
SoPhos
Hé, I just went to the toilet and the light went on automatically 
Didnt try staying in there for long yet
Thanks a lot for the support!
Hi @SergeP
Please, could you add support for a MOES Smart Siren
Thank you for your support.
Device Name: MOES Smart Siren
Device Model: TS0601
ManufactoreName: “_TZE204_t1blo2bj”
https://pt.aliexpress.com/item/1005004420956694.html?gatewayAdapt=glo2bra
"ids": {
"modelId": "TS0601",
"manufacturerName": "_TZE204_t1blo2bj"
},
"endpoints": {
"ieeeAddress": "a4:c1:38:e0:3f:c8:31:08",
"networkAddress": 28525,
"modelId": "TS0601",
"manufacturerName": "_TZE204_t1blo2bj",
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 28525,
"_reserved": 20,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 81,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
4,
5,
61184,
0
],
"outputClusters": [
25,
10
]
},
{
"status": "SUCCESS",
"nwkAddrOfInterest": 28525,
"_reserved": 10,
"endpointId": 242,
"applicationProfileId": 41440,
"applicationDeviceId": 97,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [],
"outputClusters": [
33
]
}
],
"deviceType": "router",
"receiveWhenIdle": true,
"capabilities": {
"alternatePANCoordinator": false,
"deviceType": true,
"powerSourceMains": true,
"receiveWhenIdle": true,
"security": false,
"allocateAddress": true
},
"extendedEndpointDescriptors": {
"1": {
"clusters": {
"groups": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"dataTypeId": 24,
"name": "nameSupport",
"value": {
"type": "Buffer",
"data": [
0
]
},
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"dataTypeId": 33,
"name": "clusterRevision",
"value": 2,
"reportingConfiguration": {
"status": "NOT_FOUND",
"direction": "reported"
}
}
]
},
"scenes": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"dataTypeId": 32
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"dataTypeId": 32
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"dataTypeId": 33
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"dataTypeId": 16
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"dataTypeId": 24
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"dataTypeId": 33,
"name": "clusterRevision",
"value": 2
}
]
},
"basic": {
"attributes": [
{
"acl": [
"readable",
"reportable"
],
"id": 0,
"dataTypeId": 32,
"name": "zclVersion",
"value": 3
},
{
"acl": [
"readable",
"reportable"
],
"id": 1,
"dataTypeId": 32,
"name": "appVersion",
"value": 74
},
{
"acl": [
"readable",
"reportable"
],
"id": 2,
"dataTypeId": 32,
"name": "stackVersion",
"value": 0
},
{
"acl": [
"readable",
"reportable"
],
"id": 3,
"dataTypeId": 32,
"name": "hwVersion",
"value": 1
},
{
"acl": [
"readable",
"reportable"
],
"id": 4,
"dataTypeId": 66,
"name": "manufacturerName",
"value": "_TZE204_t1blo2bj"
},
{
"acl": [
"readable",
"reportable"
],
"id": 5,
"dataTypeId": 66,
"name": "modelId",
"value": "TS0601"
},
{
"acl": [
"readable",
"reportable"
],
"id": 6,
"dataTypeId": 66,
"name": "dateCode",
"value": ""
},
{
"acl": [
"readable",
"reportable"
],
"id": 7,
"dataTypeId": 48,
"name": "powerSource",
"value": "mains"
},
{
"acl": [
"readable",
"writable",
"reportable"
],
"id": 65502,
"dataTypeId": 32
},
{
"acl": [
"readable",
"reportable"
],
"id": 65533,
"dataTypeId": 33,
"name": "clusterRevision",
"value": 2
},
{
"acl": [
"readable",
"reportable"
],
"id": 65534,
"dataTypeId": 48,
"name": "attributeReportingStatus",
"value": "PENDING"
},
{
"acl": [
"readable",
"reportable"
],
"id": 65506,
"dataTypeId": 32
},
{
"acl": [
"readable",
"reportable"
],
"id": 65507,
"dataTypeId": 72
}
]
}
},
"bindings": {
"ota": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"dataTypeId": 240,
"name": "upgradeServerID",
"value": "ff:ff:ff:ff:ff:ff:ff:ff"
},
{
"acl": [
"readable"
],
"id": 1,
"dataTypeId": 35,
"name": "fileOffset",
"value": 4294967295
},
{
"acl": [
"readable"
],
"id": 2,
"dataTypeId": 35,
"name": "currentFileVersion",
"value": 74
},
{
"acl": [
"readable"
],
"id": 3,
"dataTypeId": 33,
"name": "currentZigBeeStackVersion",
"value": 2
},
{
"acl": [
"readable"
],
"id": 4,
"dataTypeId": 35,
"name": "downloadedFileVersion",
"value": 4294967295
},
{
"acl": [
"readable"
],
"id": 5,
"dataTypeId": 33,
"name": "downloadedZigBeeStackVersion",
"value": 65535
},
{
"acl": [
"readable"
],
"id": 6,
"dataTypeId": 48,
"name": "imageUpgradeStatus",
"value": "normal"
},
{
"acl": [
"readable"
],
"id": 7,
"dataTypeId": 33,
"name": "manufacturerID",
"value": 4417
},
{
"acl": [
"readable"
],
"id": 8,
"dataTypeId": 33,
"name": "imageTypeID",
"value": 65535
},
{
"acl": [
"readable"
],
"id": 9,
"dataTypeId": 33,
"name": "minimumBlockPeriod",
"value": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"dataTypeId": 33,
"name": "clusterRevision",
"value": 3
}
]
},
"time": {
"attributes": [
{
"acl": [
"readable"
],
"id": 65533,
"dataTypeId": 33,
"name": "clusterRevision",
"value": 1
}
]
}
}
},
"242": {
"clusters": {},
"bindings": {}
}
}
}
FYI: on 1.10.0 my Wall Switch Scene 4 Gang did not work anymore. After reinstalling 1.5.1 it did work again.
HI TKroon,
I don’t think v1.10.0 has changed anything on Wall Switch Scene 4 Gang device, its last driver update was earlier. Maybe there’s a problem elsewhere but I need more details to analyse.
Regards,
SoPhos
Hi SoPhos,
Thanks for your reply. I wanted to test it for you and send a diagnostics report, but after installing experimental 1.10.0 the buttons did work now. So case closed 
Kind regards,
Thomas
Hi SoPhos, I have been using your app for several months now with 1, 2 and 4 gang scene remote switches (from the ZT-SY-EU*S-**-MS series).
Specifically regarding the 2 gang version I noticed that sometimes a single press is executed twice. It is really random and incidental.
I am sure the press is executed twice as:
Due to its randomness it is difficult to reproduce, but I have noticed this several times over the past months on all the 2 button scene switches in use (I have 7 of them).
Prior to pairing them to your app, they were paired with the Tuya Zigbee app, which did not exhibit this behavior. As such I assume this is somehow related to the driver in the MOES app.
Have you got any idea what could be causing this? I am not sure whether and what info I can provide to troubleshoot this matter.
Hi SunBeech,
Could you please send me a Diagnostic Report just after a double event, please?
Regards,
SoPhos
Good morning. Could you create the drivers for the Smart Sliding Window Pusher?
Thank you very much for your work.
type: SMART SLIDING WINDOWS PUSHER ZC-LP01-MS
manufacturerName:_TZ3210_5rta89nj
productId: TS0601
