Silvercrest Motion Sensor give Error whilst Detection is okay

[phkpr]

Hi,

Silvercrest Motion Sensor gives Error in Domoiticz (In Phoscon App everything okay)

Type identification: IAN 341805_1910 Bought recently in the Netherlands

Plugin version 1.0.22

-- In Domoticz log: Error line: 2022-02-22 20:40:51.199 Error: deCONZ: ###### Device with hardware default: {'e': 'changed', 'id': '20', 'r': 'sensors', 'state': {'lastupdated': '2022-02-22T19:40:51.158', 'lowbattery': False, 'presence': False, 'tampered': True}, 't': 'event', 'uniqueid': 'ec:1b:bd:ff:fe:94:5d:23-01-0500'}

-- On Domoticz Device page: Device turns RED.

-- Extra problem: Value 60 in DeConz page of Domoticz cannot be changed. (See screenprint)

Detection On and Off is okay,

Attachments:

• DeCONZ-domoticz.jpg
• DomoticzError.txt (pasted after JPG attachments)
• Phoscon-MotionDevice-OK.jpg
• Phoscon-ConbeeII-Ver.jpg
• Domoticz-RedDevice.jpg
• Domoticz-ParameterChangeErr.jpg

Regards Frits Koperdraat

On Github name = phkpr On Discord name = FK (FK#9113)

--------------DomoticzError.txt---

DOMOTICZ Log Line relevant to problem. error lines at the end.

Runnning on Raspberry PI 4

---

Domoticz log first lines STARTUP

2022-02-22 20:37:50.963 Status: Domoticz V2022.1 (c)2012-2022 GizMoCuz 2022-02-22 20:37:50.964 Status: Build Hash: c9526851b, Date: 2022-01-31 09:34:32 2022-02-22 20:37:50.964 Status: Startup Path: /home/pi/domoticz/ 2022-02-22 20:37:51.002 Sunrise: 07:40:00 SunSet: 18:05:00 2022-02-22 20:37:51.002 Day length: 10:25:00 Sun at south: 12:52:00 2022-02-22 20:37:51.002 Civil twilight start: 07:06:00 Civil twilight end: 18:39:00 2022-02-22 20:37:51.002 Nautical twilight start: 06:26:00 Nautical twilight end: 19:19:00 2022-02-22 20:37:51.002 Astronomical twilight start: 05:47:00 Astronomical twilight end: 19:58:00 2022-02-22 20:37:51.115 Status: PluginSystem: Started, Python version '3.7.3', 8 plugin definitions loaded. 2022-02-22 20:37:51.118 Error: : Auto Discovery Topic empty! 2022-02-22 20:37:51.126 Active notification Subsystems: email, pushbullet, telegram (3/13) 2022-02-22 20:37:51.128 Status: WebServer(HTTP) started on address: :: with port 8080 2022-02-22 20:37:51.181 Status: WebServer(SSL) started on address: :: with port 443 2022-02-22 20:37:51.185 Starting shared server on: :::6144 2022-02-22 20:37:51.185 Status: TCPServer: shared server started... 2022-02-22 20:37:51.186 Status: RxQueue: queue worker started... 2022-02-22 20:37:53.187 Status: RFXCOM: Worker started...

--------------------------------========== Domoticz log relevant deCONZ STARTUP LINES

root@raspberrypi:/home/pi/domoticz/plugins# grep deC /var/log/domoticz.log 2022-02-22 20:37:53.527 deCONZ: Worker thread started. 2022-02-22 20:37:53.527 Status: deCONZ: Entering work loop. 2022-02-22 20:37:53.527 Status: deCONZ: Started. 2022-02-22 20:37:56.493 Status: deCONZ: Initialized version 1.0.22, author 'Smanar' 2022-02-22 20:37:56.506 deCONZ: Domoticz and deCONZ are installed on the same machine. 2022-02-22 20:37:56.507 deCONZ: Adding banned device : 00:15:8d:00:02:36:c2:3f-01-0500

2022-02-22 20:38:56.742 deCONZ: ### Request config 2022-02-22 20:38:56.776 Status: deCONZ: Firmware version: 0x26660700 2022-02-22 20:38:56.776 Status: deCONZ: Websocketnotifyall: True 2022-02-22 20:38:56.776 Status: deCONZ: You have 62 API keys memorised, some of them are probably useless, can use the API_KEY.py tool or the Front end to clean them 2022-02-22 20:38:56.776 deCONZ: ### Request lights 2022-02-22 20:38:56.790 deCONZ: ### Device > 1 Name:Configuration tool 1 Type:Configuration tool Details:{'reachable': True} and [] 2022-02-22 20:38:56.790 deCONZ: Skipping Device (Useless) : 00:21:2e:ff:ff:06:51:61-01 2022-02-22 20:38:56.790 deCONZ: ### Device > 2 Name:Smart plug 2 Type:Smart plug Details:{'alert': 'none', 'on': True, 'reachable': True} and [] 2022-02-22 20:38:56.804 deCONZ: ### Device > 3 Name:Color temperature light 3 Type:Color temperature light Details:{'alert': 'none', 'bri': 130, 'colormode': 'ct', 'ct': 250, 'on': True, 'reachable': True} and [] 2022-02-22 20:38:56.827 deCONZ: ### Device > 4 Name:Lidle Color Type:Extended color light Details:{'alert': 'none', 'bri': 190, 'colormode': 'xy', 'ct': 153, 'on': False, 'reachable': True, 'xy': [0.323, 0.329]} and [] 2022-02-22 20:38:56.851 deCONZ: ### Device > 5 Name:On/Off plug-in unit 5 Type:On/Off plug-in unit Details:{'alert': 'none', 'on': False, 'reachable': True} and [] 2022-02-22 20:38:56.852 deCONZ: ### Request sensors 2022-02-22 20:38:56.870 deCONZ: ### Device > 1 Name:Daylight Type:Daylight Details:{'dark': True, 'daylight': False, 'lastupdated': '2022-02-22T19:16:38.785', 'status': 230, 'sunrise': '2022-02-22T06:42:26', 'sunset': '2022-02-22T17:05:20'} and {'configured': True, 'on': True, 'sunriseoffset': 30, 'sunsetoffset': -30} 2022-02-22 20:38:56.871 deCONZ: ### Device > 16 Name:Mi Magic Cube Type:ZHASwitch Details:{'buttonevent': -383, 'gesture': 8, 'lastupdated': '2022-02-03T09:33:34.741'} and {'battery': 100, 'on': True, 'reachable': False, 'temperature': 2100} 2022-02-22 20:38:56.893 deCONZ: ### Device > 17 Name:Switch 17 Rotate Type:ZHASwitch Details:{'buttonevent': 7000, 'gesture': 0, 'lastupdated': '2022-02-22T18:52:57.158'} and {'battery': 100, 'on': True, 'reachable': True, 'temperature': 2100} 2022-02-22 20:38:56.894 deCONZ: ### Device > 18 Name:Power 18 Type:ZHAPower Details:{'lastupdated': '2022-02-22T19:37:38.175', 'power': 0} and {'on': True, 'reachable': True, 'temperature': 3800} 2022-02-22 20:38:56.895 deCONZ: ### Device > 19 Name:Consumption 19 Type:ZHAConsumption Details:{'consumption': 24909, 'lastupdated': '2022-02-22T19:37:38.175'} and {'on': True, 'reachable': False, 'temperature': 3800} 2022-02-22 20:38:56.920 deCONZ: ### Device > 2 Name:Transmitter 2-gang Type:ZHASwitch Details:{'buttonevent': 1002, 'lastupdated': '2022-02-20T21:01:35.551'} and {'battery': 100, 'on': True, 'reachable': False, 'temperature': 3000} 2022-02-22 20:38:56.937 deCONZ: ### Device > 20 Name:Presence 20 Type:ZHAPresence Details:{'lastupdated': '2022-02-22T19:38:14.400', 'lowbattery': False, 'presence': True, 'tampered': True} and {'battery': None, 'duration': 60, 'enrolled': 1, 'on': True, 'pending': [], 'reachable': True} 2022-02-22 20:38:56.938 deCONZ: ### Device > 7 Name:TRÅDFRI remote control Type:ZHASwitch Details:{'buttonevent': 1002, 'lastupdated': '2021-11-10T17:16:11.248'} and {'alert': 'none', 'battery': 16, 'group': '6', 'on': True, 'reachable': False} 2022-02-22 20:38:56.953 deCONZ: ### Request groups 2022-02-22 20:38:56.970 deCONZ: ### Groupe > 11 Name:A 2022-02-22 20:38:56.970 deCONZ: ### Groupe > 12 Name:B 2022-02-22 20:38:56.970 deCONZ: ### Groupe > 13 Name:C 2022-02-22 20:38:56.971 deCONZ: ### Groupe > 6 Name:TRADFRI remote control 2022-02-22 20:38:56.971 Status: deCONZ: ### deCONZ ready 2022-02-22 20:38:56.971 Status: deCONZ: ### Found 4 Operators, 8 Sensors, 4 Groups, 0 Scenes and 0 others, with 0 Ignored 2022-02-22 20:38:56.971 Status: deCONZ: ### Device GROUP_All(deCONZ - All) Not in deCONZ ATM, the device is deleted or not ready. 2022-02-22 20:38:57.023 Status: deCONZ: Launching WebSocket on port 20877 2022-02-22 20:38:57.079 deCONZ: WebSocket Handshake : HTTP/1.1 101 Switching Protocols^MUpgrade: websocket^MConnection: Upgrade^MSec-WebSocket-Accept: V0htEbn5FhIA1xfQRyG3yU1aG9c=^MServer: deconz^MAccess-Control-Allow-Credentials: false^MAccess-Control-Allow-Methods: GET^MAccess-Control-Allow-Headers: content-type^MAccess-Control-Allow-Origin: http://127.0.0.1^M***Date: Tue, 22 Feb 2022 19:38:57 GMT^M^M 2 2022-02-22 20:40:08.293 Error: deCONZ: Websocket error, unknown device > 65520 (groups) 2022-02-22 20:40:08.312 deCONZ: ### Groupe > 65520 Name:All

---

Domoticz log ERROR LINES DECONZ (using SilverCrest Motion Detector name Presence 20"in Phoscon App)

2022-02-22 20:40:51.199 Error: deCONZ: ###### Device with hardware default: {'e': 'changed', 'id': '20', 'r': 'sensors', 'state': {'lastupdated': '2022-02-22T19:40:51.158', 'lowbattery': False, 'presence': False, 'tampered': True}, 't': 'event', 'uniqueid': 'ec:1b:bd:ff:fe:94:5d:23-01-0500'} 2022-02-22 20:42:21.165 Error: deCONZ: ###### Device with hardware default: {'e': 'changed', 'id': '20', 'r': 'sensors', 'state': {'lastupdated': '2022-02-22T19:42:21.125', 'lowbattery': False, 'presence': True, 'tampered': True}, 't': 'event', 'uniqueid': 'ec:1b:bd:ff:fe:94:5d:23-01-0500'} 2022-02-22 20:44:45.900 Error: deCONZ: ###### Device with hardware default: {'e': 'changed', 'id': '20', 'r': 'sensors', 'state': {'lastupdated': '2022-02-22T19:44:45.846', 'lowbattery': False, 'presence': False, 'tampered': True}, 't': 'event', 'uniqueid': 'ec:1b:bd:ff:fe:94:5d:23-01-0500'} 2022-02-22 20:46:02.869 Error: deCONZ: ###### Device with hardware default: {'e': 'changed', 'id': '20', 'r': 'sensors', 'state': {'lastupdated': '2022-02-22T19:46:02.813', 'lowbattery': False, 'presence': True, 'tampered': True}, 't': 'event', 'uniqueid': 'ec:1b:bd:ff:fe:94:5d:23-01-0500'} 2022-02-22 20:47:09.961 Error: deCONZ: ###### Device with hardware default: {'e': 'changed', 'id': '20', 'r': 'sensors', 'state': {'lastupdated': '2022-02-22T19:47:09.926', 'lowbattery': False, 'presence': False, 'tampered': True}, 't': 'event', 'uniqueid': 'ec:1b:bd:ff:fe:94:5d:23-01-0500'}

[phkpr]

---

Below the Device DATA available in Domoticz

{ "config": { "battery": null, "duration": 60, "enrolled": 1, "on": true, "pending": [], "reachable": true }, "ep": 1, "etag": "e71365d01b701d7efae90cd5e651cde9", "lastannounced": "2022-02-22T19:16:42Z", "lastseen": "2022-02-22T21:18Z", "manufacturername": "LIDL Silvercrest", "modelid": "TY0202", "name": "Presence 20", "state": { "lastupdated": "2022-02-22T21:18:21.681", "lowbattery": false, "presence": true, "tampered": true }, "type": "ZHAPresence", "uniqueid": "ec:1b:bd:ff:fe:94:5d:23-01-0500", "id": "20", "deviceclass": "sensors" }

[Smanar]

Hello, so first, why the parameter are not visible in capture n ° 2 ? it s because it's white text on white background ?

"tampered": true

You you didn't break the device, or have it open ? This setting is an alarm, it mean someone tamper the device. I m searching on deconz if this setting is not locked to true, but I don't find sample. I will ask if someone have it too to check if the value is normal, but it s for that the device is in alarm on domoticz.

Value 60 in DeConz page of Domoticz cannot be changed

It mean you set a value, refresh the page and the value return to 60 ? Are you trying with value > 60 ?

[phkpr]

Thanks for picking it up.

1. White on white problem is also on Configure Pluging page in Domoticz. Selecting another Theme does not fix it. But selecting all fields with Left-mouse--> Move down shows the values. That's not working for screen in capture nr. 2 By the way, I tested with a value lower than 60. But no result.

2. No tampering at my side. The ConbeeII stick was not touched physically I saw the tampering flag too and thought it maybe was due to the API key. Earlier I had seen a warning from the system that I had 64 API keys. I retrieved a new API key (nr. 65) and removed the other 64 keys. However it did not make any difference.

3. The same day I bought a Lidl SilverCrest On/Off Switch (Smart Plug) , installed it 15 minutes before the Motion sensor, without any errors.

4. By the way: All existing devices present in Phoscon keep working correctly.

5. To see if it is an API-key problem I now removed the device in Phoscon, rebooted Domoticz. Checked if it was completely removed and re-installed the Motion Sensor. Result: Same error.

[Smanar]

Mimix have made tries yesterday with his device

Normal situation

"state": {
        "lastupdated": "2022-02-23T16:46:54.330",
        "lowbattery": false,
        "presence": true,
        "tampered": false
    },

With the backplate removed:

    "state": {
        "lastupdated": "2022-02-23T16:47:47.804",
        "lowbattery": false,
        "presence": true,
        "tampered": true
    },

So on his device the value can move, you are sure you have not a problem on the backplate ?

The API key is an issue, to avoid them, when you log to phoscon, put the page in bookmark after the login. Else everytime you log you will create a new api key for phoscon.

I can make a setting to ignore tampering, will be usefull for you, but you will never see if someone tamper the device.

You are using defaut theme ? With wich one domoticz version ? I can't have same result than you.

For the duration try with highter value, 60 is probably the minimum.

[phkpr]

So on this device the value can move, you are sure you have not a problem on the backplate ? That was indeed the problem, I thought you metioned tamparing the Phoscon stick. I gave no attention to the backplate, just an item to easily fix or remove the motion sensor. :-) So this problem is solved.

You are using defaut theme ? With wich one domoticz version ? I can't have same result than you. Domoticx Version: 2022.1 Stable. I tested all themes: The only theme that shows the DECONZ / TOOLS page correctly is.the Darke-th3me. So a minor problem for me, now I know this.

Thanks Smanar ( + Mimix) ,

[Smanar]

Strange, on defaut theme, I have this result on my side.

[phkpr]

This is at my side also correct on most Themes: It's merely the Configuring Plugin that doesn't shows the values some themes

---

Below on default Theme (partly screenprint)

Below on Element-light Theme

[Smanar]

Ok, right, but have made a try, the issue is not from me, but from the domoticz CCS. Try on domoticz / devices / select a device , then "rename", you will have same result.

BTW, the duration is working if you use a value > 60 ? or still have issue ?

[phkpr]

Hi Try on domoticz / devices / select a device , then "rename", you will have same result. No CSS problem at my side, I can see the name of the device.

BTW, the duration is working if you use a value > 60 ? or still have issue ?

Changing the duration did work yesterday but I did not notice any effect. THe value 60 gave a motion detection duration of about 66 seconds. The same about 66 seconds came up when I used 20 or 80

Today (this evening ) I cannot change the value anymore. Strange! ( I don't trust yesterdays test anymore)

In the end:

I can live with these 2 issues, so you may close this issue #127 If you want me to do more testing that's no problem at all! Thnx

[Smanar]

But you miss a part, white on white

Changing the duration did work yesterday but I did not notice any effect.

I don't understand all the issue https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5423 But I m not sure this device use "duration".

[phkpr]

I. The white on white problem: Indeed I cannot see the name .

2. Duration: I read the #5423 issue. Quite a long read.

Not configurable is my conclusion.

I see the problem, but my device gives an On and Off signal in Domiticz. I can also extend the On period by waving my hand in front of the sensor. This waving does not give any renewed On signal.

I have a Neon Coolcam sensor. It has a motion detection blind time, during which it is insensitive for new motion. After that it gives a new On signal even if it is within the configured duration. The Silvercrest is missing all of this.

[Smanar]

I see the problem, but my device gives an On and Off signal in Domiticz. I can also extend the On period by waving my hand in front of the sensor. This waving does not give any renewed On signal.

It seem normal for me, it s presence sensor, not a mouvement detection, but strange the duration can't be increased, I m asking on discord, no answer yet.

I have a Neon Coolcam sensor. It has a motion detection blind time, during which it is insensitive for new motion. After that it gives a new On signal even if it is within the configured duration.

Even if it detect presence ? Not sure it s the correct working mode. I know better the xioami one, when it detect a presence it go to "true" and stop working during 60s, so it's for that the minimum duration is 90s, the device don't return to false itself, need to use a timer (with 30s after the not working state), the lidl one send a true and a false.

[phkpr]

Thanks!
You can close the Issue if you want, or do you want to keep it open for the question you have open on Discord"

It seem normal for me, it s presence sensor, not a mouvement detection, but strange the duration can't be increased, I m asking on discord, no answer yet.

[Smanar]

I have still no more return on discord ^^ Even the guy on the issue don't remember how it was working. Will make a new try today.