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

Keep getting messages about no longer having a state class etc #706

Open
letsstartbeinganon opened this issue Nov 21, 2024 · 6 comments
Open

Comments

@letsstartbeinganon
Copy link

Version of the custom_component

I'm using v1.12.2

Configuration

Not sure how to do this but I've attached the debug logs below.

Describe the bug

Every or multiple times per day if I clear I get a repair listed in Home Assistant saying that an entity no longer has a state class or that the unit has changed. It doesn't appear to be doing anything that breaks the functionality but not sure how I'd know it is. I do use this integration to help charge/discharge my battery at certain times of day so want assurance this bug isn't harming that.

Debug log

home-assistant_foxess_modbus_2024-11-21T11-50-04.216Z.log

home-assistant_foxess_modbus_2024-11-19T16-20-34.679Z.log

Screenshot_1
Screenshot_2

@letsstartbeinganon
Copy link
Author

Is there likely to be any assistance with this?

@letsstartbeinganon
Copy link
Author

Still having this issue. Could it be something to do with PredBat, which I also have running?

@canton7
Copy link
Collaborator

canton7 commented Jan 31, 2025

Can you go to Developer tools -> States and filter by sensor.bms_charge_rate? It should look like this:

Image

@letsstartbeinganon
Copy link
Author

letsstartbeinganon commented Jan 31, 2025

Here's mine:

Image

@canton7
Copy link
Collaborator

canton7 commented Jan 31, 2025

I'm not sure where all of the attributes have gone. They're definitely properly defined in foxess_modbus. Do you have a template or something which is trying to provide that entity? Can you see "BMS Charge Rate" in the list of entities provided by foxess_modbus?

@bfayers
Copy link

bfayers commented Feb 1, 2025

This looks like the behaviour of incorrectly configured predbat (it happened to me too).

At the moment predbat doesn't properly support setting charge power in kW rather than watts (springfall2008/batpred#1717)

Personally, I made two input_number helpers for force charge (watts) and force discharge (watts) then use an automation to sync those values to the ones in this integration (here's a gist with that automation: https://gist.github.com/bfayers/82f5a45155281d187f2758c66872c162)

In predbat you then just set the charge_rate and discharge_rate to those input_numbers

  charge_rate:
    - input_number.force_charge_power_watts
  discharge_rate:
    - input_number.force_discharge_power_watts

This seems to all work fine for me.

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

3 participants