Sensor config.on not implemented?

[ebaauw]

When I set a sensor's config.on attribute to false, it's state continues to be updated. On the Hue bridge, setting config.on to false blocks updates to the sensor state. This is used by the Hue app to disable the Hue motion sensor.

[manup]

Added to the todo list. Currently this is only possible by disabling the rules. The config.on makes sense and simplifies the task.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ebaauw]

Still on the list, I hope.

[manup]

I thought this is already working :) need to check, so basically rules shouldn't be processed when the sensor is off. Should web socket events also be stopped?

[ebaauw]

If memory serves, the Hue bridge sets the state attributes to 0 or null or "none" or something and no longer accepts PUTs to CLIP sensors state.

[manup]

Ok guess this should be compared in more detail, can be handy to disable some automations without messing too much with the existing rules.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ebaauw]

Bump

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ebaauw]

Bump

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ebaauw]

Not solved.

[ebaauw]

I suppose we just need to document that setting config/on only disables firing of rules.