Zigbee For Domoticz plugin - presence sensors settings

[pipiche]

Done.
I have merged the changes on the 'tuya-motion-radar-parameters '

the parameters to play on the SonOff are:

Code: Select all

{
"UltrasonicOccupiedToUnoccupiedDelay": 60,
"UltrasonicOccupancySensibility": 1.    ( can be 1, 2 or 3)
}

You can use the debug parameter

Code: Select all

occupancySettings

to get a bit more log.

To debug the On/Off every 15 minutes, can you enable trackZclClustersIn to see if we are not getting other information which impact that.

[JanZorz]

Code: Select all

{
    "TuyaFadingTime": 2,
    "SmallDetectionSensitivity": 1,
    "MediumMotionDetectionSensitivity": 1,
    "LargeMotionDetectionSensitivity": 1,
    "SmallDetectionDistance": 0,
    "MediumMotionDetectionDistance": 8,
    "LargeMotionDetectionDistance": 1
}

Do you have any idea what the ranges of those parameters might be?

I'm experimenting with them and the TuyaFadingTime must be 60, otherwise if it's 1 or 2 the internal siren starts to scream when it detects motion. I scared the hell out of everyone in the house

Is there a way to switch off the internal siren/sound completely?

Cheers, Jan

[JanZorz]

Done.
I have merged the changes on the 'tuya-motion-radar-parameters '

the parameters to play on the SonOff are:

Code: Select all

{
"UltrasonicOccupiedToUnoccupiedDelay": 60,
"UltrasonicOccupancySensibility": 1.    ( can be 1, 2 or 3)
}

You can use the debug parameter

Code: Select all

occupancySettings

to get a bit more log.

To debug the On/Off every 15 minutes, can you enable trackZclClustersIn to see if we are not getting other information which impact that.

Updated the plugin, removed the SNZB-06P and added it again. This is the log:

Code: Select all

2024-02-01 15:10:23,704 INFO    :b'--> Adding device 1c4c in self.DevicesInPairingMode'
2024-02-01 15:10:23,704 INFO    :b"--> ['1c4c']"
2024-02-01 15:10:23,704 INFO    :b'[None] NEW OBJECT: 1c4c None'
2024-02-01 15:10:24,319 INFO    :b'Decode8046 - Match Descriptor response: SQN: 00 Status: 00 Nwkid: 1c4c Lenght: 01 List: 01'
2024-02-01 15:10:24,319 INFO    :b'Decode8046 - Match Descriptor response Nwkid: 1c4cfound Ep: 01 Matching 0500'
2024-02-01 15:10:24,423 INFO    :b'[-] NEW OBJECT: 1c4c Active Endpoint Response Ep: 01 LQI: 108'
2024-02-01 15:10:24,426 INFO    :b'[-] NEW OBJECT: 1c4c Request Simple Descriptor for Ep: 01'
2024-02-01 15:10:24,547 INFO    :b'[-] NEW OBJECT: 1c4c Simple Descriptor Response EP: 0x01 LQI: 108'
2024-02-01 15:10:24,547 INFO    :b'[-]    NEW OBJECT: 1c4c ProfileID 0104'
2024-02-01 15:10:24,547 INFO    :b'[-]    NEW OBJECT: 1c4c ZDeviceID 0107'
2024-02-01 15:10:24,548 INFO    :b'[-]    NEW OBJECT: 1c4c Application Version 0001'
2024-02-01 15:10:24,548 INFO    :b'[-]    NEW OBJECT: 1c4c Cluster IN Count: 06'
2024-02-01 15:10:24,549 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster In 1: 0000 (Basic)'
2024-02-01 15:10:24,553 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster In 2: 0003 (Identify)'
2024-02-01 15:10:24,554 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster In 3: 0406 (Occupancy Sensing)'
2024-02-01 15:10:24,554 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster In 4: 0500 (IAS Zone)'
2024-02-01 15:10:24,555 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster In 5: fc57'
2024-02-01 15:10:24,556 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster In 6: fc11'
2024-02-01 15:10:24,556 INFO    :b'[-]    NEW OBJECT: 1c4c Cluster OUT Count: 02'
2024-02-01 15:10:24,557 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster Out 1: 0003 (Identify)'
2024-02-01 15:10:24,557 INFO    :b'[-]       NEW OBJECT: 1c4c Cluster Out 2: 0019 (Over-the-Air Upgrade)'
2024-02-01 15:10:24,768 INFO    :b'[-] NEW OBJECT: 1c4c Active Endpoint Response Ep: 01 LQI: 108'
2024-02-01 15:10:25,678 INFO    :b'Decode8046 - Match Descriptor response: SQN: 00 Status: 00 Nwkid: 1c4c Lenght: 01 List: 01'
2024-02-01 15:10:25,678 INFO    :b'Decode8046 - Match Descriptor response Nwkid: 1c4cfound Ep: 01 Matching 0500'
2024-02-01 15:10:26,103 INFO    :b'[0] NEW OBJECT: 1c4c Model Name: SNZB-06P'
2024-02-01 15:10:26,104 INFO    :b'[0] NEW OBJECT: 1c4c Manufacturer Name: SONOFF'
2024-02-01 15:10:29,946 INFO    :b'process_cluster_attribute_response - 1c4c/01 0406 - 0022 DataType: 20 miss-match with expected 21'

The newly created switch in Domoticz now behaves like it should and switches on when the person is in the room and switches off when there is no motion detected anymore.

Is there any other information that we can extract from the presence sensor?

Cheers, Jan

[pipiche]

That is a good news.
There is an attribute that sonoff named Illumination, but I don’t what it is.
Can we get de device illuminated when presence ?

[JanZorz]

That is a good news.
There is an attribute that sonoff named Illumination, but I don’t what it is.
Can we get de device illuminated when presence ?

Yup, got some light on the device now - what type of export do you need?

Cheers, Jan

[pipiche]

I guess this is a parameter to configure.
I’ll see if I can update the code tonight

[pipiche]

just pushed an update on the that branch

you can try the following parameter

"SonOffUltrasonicIllumination": 1 bright, 0 dim


As usall, when you change the parameter value and you validate twice ( once on the pop-up window, and then once in the page top-right), it could take couple of seconds to minutes (depending on the network/plugin load)

[JanZorz]

just pushed an update on the that branch

you can try the following parameter

"SonOffUltrasonicIllumination": 1 bright, 0 dim


As usall, when you change the parameter value and you validate twice ( once on the pop-up window, and then once in the page top-right), it could take couple of seconds to minutes (depending on the network/plugin load)

I set this but I see no difference. Should the sensor emit some light when it detects a motion?

Cheers, Jan

[pipiche]

I have no clue. Don’t you have any documentation with the device

[pipiche]

I have no clue. Don’t you have any documentation with the device

Kindly check that there is no error in the logs

[pipiche]

Code: Select all

{
    "TuyaFadingTime": 2,
    "SmallDetectionSensitivity": 1,
    "MediumMotionDetectionSensitivity": 1,
    "LargeMotionDetectionSensitivity": 1,
    "SmallDetectionDistance": 0,
    "MediumMotionDetectionDistance": 8,
    "LargeMotionDetectionDistance": 1
}

Do you have any idea what the ranges of those parameters might be?

I'm experimenting with them and the TuyaFadingTime must be 60, otherwise if it's 1 or 2 the internal siren starts to scream when it detects motion. I scared the hell out of everyone in the house

Is there a way to switch off the internal siren/sound completely?

Cheers, Jan

Sorry, didn't see your post. Ok, I'll set the Fading Time to 60 by default. For the others I do not have any documentation. I set the default as the one I got from you (after the pairing).

If that is find for you I would push this branch onto the Release Candidate for 7.1.009.

Let me know what you think ?

[edit] I'll see if I have some budget to purchase one , so I can test it on the Tuya gateway and reverse-engineer the values

[JanZorz]

Sorry, didn't see your post. Ok, I'll set the Fading Time to 60 by default. For the others I do not have any documentation. I set the default as the one I got from you (after the pairing).

If that is find for you I would push this branch onto the Release Candidate for 7.1.009.

Let me know what you think ?

[edit] I'll see if I have some budget to purchase one , so I can test it on the Tuya gateway and reverse-engineer the values

Please, don't push this branch to RC yet. Something weird is happening with Sonoff presence sensor. The moment I updated to latest in the branch and this 'SonOffUltrasonicIllumination': 1 was added to the code - strange thing started to happen and I can repeat the issue.

I also have 3 other motion sensors, lumi.sensor_motion.aq2. When you added to the code that Illumination option - one of them went mad (just one of them). When it switches On then it doesn't switch back off when there is no presence in the room and keeps flooding the Zigbee network with data.

If I disable SNZB-06P presence sensor in ZFD web admin panel, then that lumi.sensor_motion.aq2 goes back to normal operation. If I enable it - it starts acting weird again.

I removed the lumi.sensor_motion.aq2 from config and re-added it, not hing changed. I removed the SNZB-06P from config and re-paired it - and still the same issue.

Then I removed all the additional config for SNZB-06P (apparently it was added by default when re-added) and the lumi.sensor_motion.aq2 started working again, but now SNZB-06P doesn't work (the switch doesn't go to On of Off when presence).

It started the moment I got the code with 'SonOffUltrasonicIllumination': 1 option. I can send you plugin logs, if you wish, but I can't see anything useful in them - but maybe I'm wrong.

I would suggest that you roll back to the code before you added this illumination option and I can test again.

Cheers, Jan

[pipiche]

I have disabled the SonOffUltrasonicIllumination in the recent push
can you try how does it behave ?

[JanZorz]

I have disabled the SonOffUltrasonicIllumination in the recent push
can you try how does it behave ?

Testing...

Cheers, Jan

[pipiche]

@janzorz , I got confirmation Illumination is in fact device -> gateway. This simply tells the illumination when presence is detected.

[JanZorz]

I have disabled the SonOffUltrasonicIllumination in the recent push
can you try how does it behave ?

Same problem... and it's clashing/affecting just just one other motion sensor, not all of them. I have a feeling that we pushed something into the SNZB-06P that is causing problems. Is there any way how I could completely factory-reset the SNZB-06P?

Even if I add just "'UltrasonicOccupiedToUnoccupiedDelay': 60" to the SNZB-06P - the other sensor stops working - and SNZB-06P doesn't work anyway.

Weird...

If you tell me which debug modules to switch on in plugin debug page - I can send you the plugin log when everything is ok and then when I add the SNZB-06P sensor.

Cheers, Jan

[pipiche]

What's happen if you press for more than. 10s

[pipiche]

I got the documentation, and they are mentioning that you need to be carreful when 2 Presence sensors are in the same room are close to each other, because they can impact the other one.

If you switch off all and you keep only one, do you still see strange behaviour ?

[JanZorz]

I got the documentation, and they are mentioning that you need to be carreful when 2 Presence sensors are in the same room are close to each other, because they can impact the other one.

If you switch off all and you keep only one, do you still see strange behaviour ?

I took the Sonoff presence sensor into a different room where there are no other sensors, so I had only 1 sensor in the room - but that was during precious version. Let me try again.

If I switch off (disconnect) Sonoff sensor but do not disable it in the Z4D web admin panel - the Aquara sensor still doesn't work. I'll do more tests today.

Cheers, Jan

[pipiche]

If I switch off (disconnect) Sonoff sensor but do not disable it in the Z4D web admin panel - the Aquara sensor still doesn't work. I'll do more tests today.

Cheers, Jan

Hum, the fact that the Aqara sensor doesn't work, as nothing to do with the Sonoff presence sensor.
Did you try to put the plugin in pairing mode and re-pair the Aqara sensor ?