You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since motion state is intended to be an "event," i.e. only "detected" will be sent on motion and never "clear," can the retained message on the motionStatus message sent in sendMotionStatus() be sent with the retainedmessage flag set to "false" instead of "true?" That way, when a integration is restarted or forced to reconnect/resubscribe to the MQTT topics, it won't pickup the last motion "event" that probably occurred some time ago.
This was discussed as an alternative in another issue, but the issue got closed without having a chance to discuss or consider.
The text was updated successfully, but these errors were encountered:
Since motion state is intended to be an "event," i.e. only "detected" will be sent on motion and never "clear," can the retained message on the motionStatus message sent in sendMotionStatus() be sent with the retainedmessage flag set to "false" instead of "true?" That way, when a integration is restarted or forced to reconnect/resubscribe to the MQTT topics, it won't pickup the last motion "event" that probably occurred some time ago.
This was discussed as an alternative in another issue, but the issue got closed without having a chance to discuss or consider.
The text was updated successfully, but these errors were encountered: