RESTful sensor does not respect scan_interval configuration

[mountainsandcode]

The problem

The RESTful sensor keeps polling every 30 seconds, even when using the scan_interval key

Environment

• Home Assistant Core release with the issue: 0.115.6
• Last working Home Assistant Core release (if known): ?
• Operating environment (OS/Container/Supervised/Core): Docker
• Integration causing this issue: rest
• Link to integration documentation on our website: https://www.home-assistant.io/integrations/rest/

Problem-relevant configuration.yaml

- platform: rest
  name: "My Sensor 1"
  resource: "[URL]"
  value_template: >-
    {{ value_json[0] }}
  headers:
    User-Agent: "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0"
  scan_interval: 600

Traceback/Error logs

Additional information

[tkacikdominik]

@mountainsandcode I try the RESTful sensor on my HA

My configuration.yaml

sensor:
  - platform: rest
    name: rest_sensor
    resource: <ip>
    username: user
    password: pass
    authentication: basic
    value_template: '{{ value_json.Do4 }}'
    scan_interval: 600

I try it with scan_interval above 30 and also with scan_interval below 30,
and it works in both case.

Environment

• HA core 0.115.6
• Operating environment (OS/Container/Supervised/Core): Docker

[theorician]

I can confirm that I'm also not seeing scan intervals respected.

[theorician]

Was there perhaps a new upper limit implemented? No matter what I try (above 60), it always scans every 60 seconds.

[mbrrg]

I could not reproduce this issue on 0.117.0.dev0. Tried with 120 seconds scan interval, calls are made with correct interval.

[jaap-stack]

Running Version 0.118.5 of Home Assistant (not sure if this corresponds to the Core version nr).

My REST configuration included:
scan_interval: 3600

However, I noticed that requests were done on a much higher frequency (minutes but I only see the value changes),
I quickly stopped my integration since I was polling an external source and I don't want to be blocked or receive complaints.

So I can confirm that the scan_interval in my case definitely was not set to 3600 (one hour).

If this issue still persists I will probably go for the SCRAPE sensor, but that one seems a bit more elaborate to setup.

[bdraco]

Could not repro on 2020.12.2. This appears to be fixed.