Amcrest Sensor Scan Interval

Configuration
1

I was trying to troubleshoot my issue with my Amcrest Cameras today, again, and came up with an error I have not seen before but that is due to the fact I decided to add the Amcrest IP Camera Sensor so I could pick up the motion detection and SD card usage. Anyway, I was using that as part of the troubleshooting just to see if I could get the crazy stuff to show up and saw the following error:

17-03-18 02:11:31 ERROR (MainThread) [homeassistant.bootstrap] Invalid config for [sensor.amcrest]: expected int for dictionary value @ data['scan_interval']. Got datetime.timedelta(0, 10). (See ?, line ?). Please check the docs at https://home-assistant.io/components/sensor.amcrest/

Now, the documentation says the default scan interval is 10 seconds but I have always been taught with respect to writing code or configurations for that matter, to set things explicitly rather than relying on the defaults where possible. So I added the scan_interval setting and set it to the default.

It ‘appears’ to be pointing to the integer value, so I assume it does not like the default value being explicitly set? Or is there something else going on.

2

Anyone seen this issue before or know what is going on?

3

It looks like there’s a bug in the code.

The system keeps formatting the input 10, “10”, ‘10’, etc. as a datetime format.

I had to explicitly specify the type as integer for it to work.
Someone should submit a bug report, but I don’t have time right now.

See my config (and binary_sensor template to convert this sensor to true binary!)

sensor:
  - platform: amcrest
    host: !secret cam_ip
    username: !secret cam_user
    password: !secret cam_pass
    scan_interval: !!int 10
    monitored_conditions:
      - motion_detector

binary_sensor:
  - platform: template
    sensors:
      lr_motion:
        value_template: "{{ states('sensor.amcrest_motion_detected') == True }}"
        friendly_name: "Living Room Motion"
        device_class: motion
        entity_id: sensor.amcrest_motion_detected
1 Like
4

@mike1237

I’m looking into this issue.

5

@mike1237 thanks for much for reporting this problem.

The issue was when passing the scan_interval it was not being recognized as timedelta value. It was a bug in the code.

The PR#6685 - https://github.com/home-assistant/home-assistant/pull/6885 fixes the issue.

Please let me know if that works for you.
mmello