Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in the evening #251

Open
4noxx opened this issue May 15, 2024 · 3 comments
Open

Error in the evening #251

4noxx opened this issue May 15, 2024 · 3 comments

Comments

@4noxx
Copy link

4noxx commented May 15, 2024

i added this addon. works fine on day (with sun).

but in the evening lovelace shows errors....

image

Die Entität ist nicht-numerisch
entity isnt numeric

  1. FoxESS - FeedIn Power
  2. FoxESS - Energy Generated
@FozzieUK
Copy link
Collaborator

Which inverter is it ?

If it’s a solar only inverter the datalogger will go off-line once the sun goes down, the sensor.foxess_inverter will show the inverter status as ‘off-line’ and all the entities will show ‘unknown’ as there is no state being reported.

@4noxx
Copy link
Author

4noxx commented May 16, 2024

Inverter: T10-G3

but everything is there in the cloud. why can't i use this data?

image

@FozzieUK
Copy link
Collaborator

If there is feed in power showing in the cloud then you would expect the inverter to be on-line and it should be showing the same information as the cloud - the Fox OpenAPI has been having some problems (Fox are aware and are working on the problem) so it could be that is causing that problem.

But if the inverter goes into standby overnight, it shuts down the datalogger and the cloud will show it as off-line, when this happens there are no values being returned and so all the sensors become ‘unknown’ - you can click on them and they will still show their history. As soon as the inverter returns on-line it will start sending data and the sensors will start to show the most recent data.

For the energy_generated sensor you can handle this by creating a utility meter and use the energy_generated sensor as it’s source. The utility meter will retain the value even when the energy_generated sensor goes off-line, that’s why utility meters are often used for long term statistics.

The yaml code for your configuration would look something like this-

utility_meter:
  generated_energy:
    source: sensor.foxess_energy_generated_2
    cycle: daily
    always_available: true

Most HA cards can deal with ‘unknown’ or ‘unavailable’ states, but if they cannot you can use templates to create ‘filtered’ sensors that deal with it to return a ‘known’ numeric state, like this-

template:
  - sensor:
      - name: "Filtered Feed In Power"
        unit_of_measurement: "kW"
        device_class: power
        state: "{{ states('sensor.foxess_feedin') if states('sensor.foxess_feedin')|is_number else 0 }}"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants