I’ve moved a Osram Smart+ Motion Sensor from Alexa (Zigbee with Echo Studio) to Phoscon (iobroker on RaspberryPi) , an the behavoir is quite different here:
-Alexa routine triggers presence=true with the first move in the sensor area and delays sending the presence=false until there is no more movement or at least after 40sec.
-With Phoscon the sensor triggers presence=true with the first move in the sensor area and is forcing sending the presence=false ALWAYS after 40sec duration, no matter if there’s any more movement or not. then the sensor is paused for about 1min until it can be triggered again.
The pairing works well in both szenarios, also the tempature sensor is shown at both worlds.
Whats going wrong here ?? How can I make the sensor behave the same way in both worlds? i want to get rid of Alexa zigbee to make the sensors independent of web access.
EDIT: did some testing in deconz/ Cluster Info of the device. The attribute 0x0000 Occupancyseems to behave exactly as expected, and what I’ve seen at Alexa. How can I subscribe to this attribute from JS/Blockly?
After checking, this device (at least on his DDF) don’t use the cluster 0x0406 but the cluster 0x0500, so I have a doubt on your try with the attribute 0x0000
It works! Tested it more than an hour yesterday, when mowing your hand in the sensor area you see the behavoiur after pressing the [read] button in 0x0406 every 10 seconds. So why not using 0x0406 instead!?
I also do not understand this fundamental malfunction in deconz, especially that the sensor is freezed for a minute or more after the 40 seconds.
Did some more general investigations at Google to understand whats the use case:
-for occupancy with high sensitivity (0x0406) for motion
-and for security alarm with a lower sensitivity (0x0500), so I understand the freezing after the 40sec’s.
So deconz uses the alarm attribute, which is definitely WRONG for light purposes.
It seem the sensor was working previously on the cluster 0x0406 and after a time switched to use the IAS cluster 0x0500.
But even using the IAS cluster, the working mode is not correct.
Edit:
Z2M is using the IAS cluster too.
I don’t have motion sensor that use the IAS cluster on my side to test if the problem is specific or general.
Device:
–Press and hold the grey button
– Insert the battery (btw I use 3.6V CR2 accus (USB-C loading, with battery mgmt, shows always 100% and switches off when empty, no more malfunction with empty bat.!)
– after 1-2s release the button, should light green after 5s
Phoscon:
– wait until it says “Device ready” (?, I use the German one)
– go to the settings page of the new sensor and try while watching the men icon
—does it extend the on-time while you keep moving?
—does it react immediately after stop moving > 40s > icon off > start moving?
—all = yes! congrats, it works like expected! > END
—all = no! GOTO 3
@manup@Smanar Thanks for the quick reply on Easter!
I have more than 10 of these devices bought over 5 yrs, most of them working properly on Alexa. in case I can help testing let me know
right now 2 of them I have directly connected to Phoscon not extending the time while mowing (as described above).
Hope the update helps to solve.
@manup@Smanar
Found this on Deconz Toolboxusing 0406-Snippet, published
2 months ago (10.2.2025), BETA, file motion-sensor-a-598551ca27.ddb (can’t upload here): (haven’t tried yet, waiting until reply from you)
Lol, so If you doing tests it’s fine, but not possible to ask users to do same ^^, too much stuff, realy need to make something, but now we know it’s possible.
And BTW I realy like your captures and all the job you are done, realy nice tutorial (“Goto 3”, long time passed on Basic too ? ^^)
But seriously for me there is 3 situations possibles.
You have a version that work better with the Presence cluster, the 0x0406, I can make a DDF for you that will use it, but if we have done a change to use the IAS cluster (and other application too) I think there is a reason.
There is something to improve on the DDF, because the deconz core is able to done all you have done manually.
But you are lucky, If @manup have the device, he can make tries on his side.
For information, all you are seing on cluster 0x0500 need to be done by deconz.
So you can compare this cluster (the capture on step 5) on a working and a not working device to see what is missing.
Edit:
After reflexion, it seem you have exaclty the same issue the link I have used in this post, the user have problem to include water sensor using IAS cluster. And some days ago was someone on the ikea sensor, the enrollement fail every time (mean the attribute 0x0010 on the cluster 0x0500 don’t display the Mac adress).
@Smanar thanks for the update and your comments, (yes I startet long ago with BASIC on a C64 )
In between got 4 devices running fine, surviving after a reboot of my Raspi.
@manup I recognize that the man icon shown in Phoscon is not always showing what Deconz is showing, means prompt reaction on Deconz, but no reaction of the icon, may a core issue as mentioned above?
At the moment i do more testing with the 4 devices and awaiting on the input of @manup.
And again many thanks for your input, I really appreciate that
The sensor fires the IAS Zone Status Notification event, and after approx. 35 seconds another one to notify the motion is over. So far so good, now I need to make some tests what happens when motion is active for more than this grace period.
The bug was that the config/duration caused a auto reset to false, while the sensor was still in motion state. The config/duration should only be used for sensors which trigger the motion: true but not the no-motion events.
Yes only the config/duration entry needs to be removed from the DDF. In my little test I only restarted deCONZ after that and observed if the sensor presence stayed true while waving in front of it for 2 minutes (which it didn’t before) that worked.
To be sure the change is applied the REST-API presentation { "config": { "duration": 40 } } shouldn’t be there anymore. In my test this worked without delete + repairing.
)
)
