8000 Youless: power_total is non_numeric in Energy config · Issue #58234 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Youless: power_total is non_numeric in Energy config #58234

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

Closed
BarBaar44 opened this issue Oct 22, 2021 · 2 comments · Fixed by #58333
Closed

Youless: power_total is non_numeric in Energy config #58234

BarBaar44 opened this issue Oct 22, 2021 · 2 comments · Fixed by #58333

Comments

@BarBaar44
Copy link

The problem

Added a Youless LS110 (firmware 1.2.2-el) to Home Assistant and set power_total as Grid Consumption in the Energy dashboard.

The following error appears:

Entity has non-numeric state The following entities have a state that cannot be parsed as a number: sensor.power_total (40064,145)

The 40064,145 comes from Youless as the current value of the energy meter, as configured in the Youless interface (Meterstand).

What is version of Home Assistant Core has the issue?

2021.10.6

What was the last working version of Home Assistant Core?

Unknown

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Youless

Link to integration documentation on our website

https://www.home-assistant.io/integrations/youless

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@probot-home-assistant
Copy link

Hey there @gjong, mind taking a look at this issue as it has been labeled with an integration (youless) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)


youless documentation
youless source
(message by IssueLinks)

@gjong
Copy link
Contributor
gjong commented Oct 24, 2021

This is a known issue with the LS110 that is already fixed in the library that Home Assistant uses. However this library with the fix still needs to be released and after that the integration updated.

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

Successfully merging a pull request may close this issue.

2 participants
0