Motion sensor presence commands have changed. Request update.
Posted: Sat Aug 03, 2019 12:01 pm
## Intro
It appears that Philips has recently changed some of the Motion sensor presence conditions. I request the All4Hue app be updated to support the new form of these Motion sensor presence conditions; and deprecate the old conditions.
I've observed the change through experiment and interrogating the hue bridge. That is, by creating presence rules via the Official Philips Hue app, observing those rules via the API; then creating presence rules in All4Hue, and observing those rules via the API.
Additionally, when I observe from All4Hue the relevant presence rules that have been created in the Official Philips Hue app, this will show up as an "Unsupported" condition.
So it's not from anything in the official documentation https://developers.meethue.com/develop/hue-api/ that I come by this. Indeed I can't find anything in that documentation that stipulates what the presence conditions should be (perhaps I'm missing it).
There are the following conditions to think about:
* Presence updated (has changed)
* Presence updated with delay (has changed)
* Presence detected; or Presence not detected. (Unchanged)
The Philips hue bridge works with any of the following conditions. However it would be a good idea to keep up with where the official Philips code base has shifted to; and to see, in All4Hue, support for all conditions created by Philips (these are the only conditions that All4Hue doesn't support, as far as I've seen).
## My Environment
As at 2019-08-02 I'm up to date:
Philips hue bridge. BSB002 | 1933087030 (The square bridge, with rounded corners)
Motion sensors. SML001 | 6.11.27575
## Presence updated
* All4Hue currently creates:
* Philips official app creates:
## Presence updated with delay
* All4Hue currently creates:
* Philips official app creates:
## Presence detected; or Presence not detected
Unchanged. Both the Philips official app and All4Hue app create the same sort of command.
Edit: Corrected "address": "/sensors/66/state/status" to "address": "/sensors/66/state/presence".
It appears that Philips has recently changed some of the Motion sensor presence conditions. I request the All4Hue app be updated to support the new form of these Motion sensor presence conditions; and deprecate the old conditions.
I've observed the change through experiment and interrogating the hue bridge. That is, by creating presence rules via the Official Philips Hue app, observing those rules via the API; then creating presence rules in All4Hue, and observing those rules via the API.
Additionally, when I observe from All4Hue the relevant presence rules that have been created in the Official Philips Hue app, this will show up as an "Unsupported" condition.
So it's not from anything in the official documentation https://developers.meethue.com/develop/hue-api/ that I come by this. Indeed I can't find anything in that documentation that stipulates what the presence conditions should be (perhaps I'm missing it).
There are the following conditions to think about:
* Presence updated (has changed)
* Presence updated with delay (has changed)
* Presence detected; or Presence not detected. (Unchanged)
The Philips hue bridge works with any of the following conditions. However it would be a good idea to keep up with where the official Philips code base has shifted to; and to see, in All4Hue, support for all conditions created by Philips (these are the only conditions that All4Hue doesn't support, as far as I've seen).
## My Environment
As at 2019-08-02 I'm up to date:
Philips hue bridge. BSB002 | 1933087030 (The square bridge, with rounded corners)
Motion sensors. SML001 | 6.11.27575
## Presence updated
* All4Hue currently creates:
Code: Select all
"conditions": [
{
"address": "/sensors/66/state/lastupdated",
"operator": "dx"
},
Code: Select all
"conditions": [
{
"address": "/sensors/66/state/presence",
"operator": "dx"
},
* All4Hue currently creates:
Code: Select all
"conditions": [
{
"address": "/sensors/66/state/lastupdated",
"operator": "ddx",
"value": "PT00:00:05"
},
Code: Select all
"conditions": [
{
~~"address": "/sensors/66/state/status",~~
"address": "/sensors/66/state/presence",
"operator": "ddx",
"value": "PT00:00:05"
}
],
Unchanged. Both the Philips official app and All4Hue app create the same sort of command.
Edit: Corrected "address": "/sensors/66/state/status" to "address": "/sensors/66/state/presence".