Amcrest Motion Detection won't clear after upgrade to HA 2021.5

Has anyone else run into this problem after the upgrade to HA 2021.5. The motion detection on my Amcrest Cameras will hardly ever clear now and is always on. This is an issue because I use this detection to run the Doods intergration. I thought maybe it was the cameras themselves but I’ve done many reboots both hard and soft and I am now pretty sure it’s HA. Any insight would be helpful. Thank you.

amcrest:
  - host: !secret camera_host1
    username: admin
    password: !secret camera_password
    stream_source: mjpeg
    name: Garage
    binary_sensors:
      - motion_detected
      - online
    sensors:
      - sdcard
model_name: IP3M-943W
brand: Amcrest
motion_detection: true
audio: 'off'
motion_recording: 'on'
color_bw: auto
friendly_name: Garage
entity_picture: >-
  /api/camera_proxy/camera.garage?token=depricated
supported_features: 3

my cameras binary_sensor.camera_motion_detected all show ON 24hrs now.
I not use this sensor anymore so I not notice when it occur but definately between 2021.4.6 and 2021.5.1

Have either of you turned on debug and checked the logs? There is an issue here that may be related… Amcrest Camera failing with 400 error · Issue #50264 · home-assistant/core · GitHub
the fix mentioned at the bottom is related to event monitor

you can fix this issue with this automation… for now!

- id: 'clear_motion'
  alias: Reset Motion Detection
  initial_state: 'on'
  trigger:
  - entity_id: binary_sensor.entrance_motion_detected
    platform: state
    to: 'on'
  action:
  - alias: Clear Motion
    repeat:
      sequence:
      - delay: 00:00:05
      - service: homeassistant.update_entity
        target:
          entity_id: binary_sensor.entrance_motion_detected
      until:
        - condition: state
          entity_id: binary_sensor.entrance_motion_detected
          state: 'off'

It’s fixed in latest update Fix amcrest detection of sensor reset by FrnchFrgg · Pull Request #50249 · home-assistant/core · GitHub

Update 2021.5.2 was finally pushed to me today, looks like it came out yesterday. So far it looks to have fixed the bug.