Error from Osram Motion sensor

[thomasbaetge]

Hi,

I have a strange error in my Domoticz log every minute from my Osram motion sensor (despite the device operation is normal).

Code: Select all

2020-05-08 15:32:12.415 Error: (Zigbee) ###### Device with hardware defaut : {'e': 'changed', 'id': '2', 'r': 'sensors', 'state': {'lastupdated': '2020-05-08T13:32:12', 'lowbattery': False, 'presence': False, 'tampered': True}, 't': 'event', 'uniqueid': '00:0d:6f:00:0f:83:fc:9e-01-0500'}

my setup is RPI with 2020.2 stable, deCONZ stick and plugin.
I had this error since I got the sensor, so it does not seem to be related to my domoticz version.
When I run the device over node-red, the errormessage is the same.

Any idea what could be wrong ??

Thanks for your help!

[Thorgal789]

Hello, you have explanation here https://github.com/dresden-elektronik/d ... ssues/2672

The modification have been validated, but It will be in deconz version 2.05.76

If you are bored with it, you can edit the plugin.py file search the line

Code: Select all

if tampered or lowbattery:

and replace it by

Code: Select all

if lowbattery:

But it will be a little bit more complicated to update the plugin after, github will see the file was modified and can cause problem at next "git pull", you probably will need to delete the folder.

[thomasbaetge]

Cool, thank you very much!!

[waaren]

But it will be a little bit more complicated to update the plugin after, github will see the file was modified and can cause problem at next "git pull", you probably will need to delete the folder.

If you do a

Code: Select all

git stash 

before

Code: Select all

git pull

The pull will work. After the pull

Code: Select all

git stash apply

will re apply the changes. Check if the change was successful can be done with

Code: Select all

git diff 

[thomasbaetge]

Thanks again

[Thorgal789]

Yeah thx a lot @waarren.

I can't try now, but I have so much problem with github, and I have never used "stash"

[thomasbaetge]

quick update on this one:
the issue got resolved with the phoscon / deCONZ update as promised.

no more silly messages