Comments (6)
@catalinbordan thx for the insight.
@zeputt the ACCESS_FREQUENCY_IS_TOO_HIGH
is not related to the entities. The call updates multiple entities if it receives data. The call is per device type, so the call also handles multiple devices at once.
I have created a Pull Request that takes the disabled devices into account. This will not request the information for the disabled devices.
from homeassistant-fusionsolar.
I don't get it. In Home Assistant you can decide which entities to show in a dashboard.
from homeassistant-fusionsolar.
@zeputt I assume you have added the full widget to your dashboard? If so: you can edit the dashboard and remove the items you don't want to see.
Feel free to reopen the issue if you think this is a problem within the integration. But at this point the integration just exposes the data that is coming from the Huawei Fusion Solar API.
from homeassistant-fusionsolar.
@tijsverkoyen Sorry for not coming back sooner ;)
I know that you can select what to show and I only use the datapoints that makes sense in Node-Red and don't really use them in the UI.
My thought was if it's useful to be able to supress the datapoints that's not useful to you in order to mitigate this:
This error originated from a custom integration.
Logger: custom_components.fusion_solar.sensor
Source: custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py:158
Integration: Fusion Solar (documentation, issues)
First occurred: February 7, 2023 at 14:29:36 (89 occurrences)
Last logged: 08:41:50Unexpected error fetching FusionSolarOpenAPIStationYearKpi data: Access frequency to high. failCode: 407, message: ACCESS_FREQUENCY_IS_TOO_HIGH
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 239, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 195, in _async_update_data
return await self.update_method()
File "/config/custom_components/fusion_solar/sensor.py", line 655, in async_update_station_year_kpi_data
response = await hass.async_add_executor_job(api.get_kpi_station_year, station_codes)
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 92, in get_kpi_station_year
response = self._do_call(url, json)
File "/config/custom_components/fusion_solar/fusion_solar/openapi/openapi_api.py", line 158, in _do_call
raise FusionSolarOpenApiAccessFrequencyTooHighError(
custom_components.fusion_solar.fusion_solar.openapi.openapi_api.FusionSolarOpenApiAccessFrequencyTooHighError: Access frequency to high. failCode: 407, message: ACCESS_FREQUENCY_IS_TOO_HIGH
I'm aware that it's depending on the way that the call is written but this was the reason way I raised the issue :)
from homeassistant-fusionsolar.
Hmm, would be a good idea.
But I don't see a good way to implement this in the interface. Maybe something in the config flow that grabs all devices and let you select which ones to include. Will need to think about this. For probably not something that will be included very soon.
from homeassistant-fusionsolar.
Hi,
Could be a solution to disable the sensors from HA? Maybe would not be pulled by integration?
from homeassistant-fusionsolar.
Related Issues (20)
- Entities not Updating in Kiosk Mode HOT 8
- All sensors unavailable (Kiosk) HOT 5
- Half of entities are unavailable HOT 4
- Unexpected error fetching FusionSolarOpenAPIDeviceRealKpiType data: 'NoneType' object is not iterable HOT 15
- No more entities provided HOT 63
- User/pass is output to log file. HOT 4
- Always disconnecting HOT 3
- Lifetime energy does not recover after Kiosk max retries. HOT 10
- Energy dashboard showing wrong values HOT 2
- Wrong device_class? HOT 1
- Steps in cumulative quantities. (open api) HOT 1
- Kiosk mode: SyntaxWarning: invalid escape sequence '\?' HOT 2
- Question: have you ever considered using APIs from the web portal? HOT 5
- Error requesting FusionSolarKiosk data HOT 1
- Not in coordinator data HOT 5
- Some numerical sensors do not allow to be used completely in the statistics cards HOT 6
- New entities created when updating kiosk URL HOT 1
- sensor.solar_total_lifetime_energy unknown HOT 6
- Some sensors take previous values at midnight HOT 2
- Not all kiosk sensors are present in Home assistant HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from homeassistant-fusionsolar.