Closed dimdedmid closed 7 years ago
scan_interval
work on every platform. The hardcodec is only for default value... But I think the trouble need to fix on api with a data cache.
Thank you @pvizeli . I will try using scan_interval
. The only request left would be
Could you also set dependency version of somecomfort python module to 0.4.1. Now it is 0.3.2.
I too am having this problem.
Just to be clear I understand correctly, we should be adding scan_interval: 500
to the configuration.yaml
file?
To platform yes. @dimdedmid can you make a PR with pump version to 0.4.1 after you have test it?
Please submit a PR to add a SCAN_INTERVAL
value to the Honeywell platform. We are already on somecomfort 0.4.1
Ok, I am taking off my request to add SCAN_INTERVAL
since the generic scan_interval
parameter applicable to any component does the job. I have this config running for 2 days and it doesn't cause errors in the log. I will try to test with scan_interval: 300
a bit later.
climate:
platform: honeywell
username: !secret thermostat_username
password: !secret thermostat_password
region: us
scan_interval: 600
I would really appreciate if someone can
make a PR with pump version to 0.4.1 after you have test it
because I am a newbie here.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍
Home Assistant release (
hass --version
): 0.36.1 Python release (python3 --version
): 3.5.2 Component/platform: climate/honeywell Dependency: Somecomfort 0.4.1 Description of problem:I have a regular honeywell configuration that works for about a day or two. Then the component starts throwing error "somecomfort.client.APIRateLimited: You are being rate-limited. Try waiting a bit." every 2 minutes. Since then it doesn't work any more. I can't set or get current temperature or do anything else. When I restart HASS, everything comes back to normal until the next day.
HA Climate component is polling Honeywell API every minute and that parameter is hardcoded. Honeywell API FAQ states that status requests should be every 5 minutes per hour.
As a workaround I opened
"..\Python\Python35\Lib\site-packages\homeassistant\components\climate\__init__.py"
, increased SCAN_INTERVAL to 300 seconds and restarted HASS. The issue is gone but next update will bring original code back.Expected: Please, make SCAN_INTERVAL configurable in yaml rather than hardcoded to 60sec and add scan_interval parameter to yaml for climate component to be able to meet API rate limitation. Could you also set dependency version of somecomfort python module to 0.4.1. Now it is 0.3.2.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info: