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

Most Solax entities stay unknown after updating to 2024.5.3 #117302

Closed
davosje opened this issue May 12, 2024 · 2 comments
Closed

Most Solax entities stay unknown after updating to 2024.5.3 #117302

davosje opened this issue May 12, 2024 · 2 comments

Comments

@davosje
Copy link

davosje commented May 12, 2024

The problem

After updating to 2024.5.3 from 2024.5.0 my Solax integration stopped working partially. Only the Solax (SERIAL) PV1 Current (sensor.solax_(serial)_pv1_current) is giving a value the other stay on unknown. Anybody else experience this as well?

Still able to curl the device and get values:
{"type":"X1-Boost-Air-Mini","SN":"*SERIAL*","ver":"2.033.20","Data":[7.7,0.0,113.1,0.0,3.4,230.8,797,44,2.1,3354.2,0,875,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0.00,0.00,0,0,0,0,0,0,0,50.03,0,0,0,0,0,0,0,0,0,0.00,0,0,0,0,0.00,0,0,2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"Information":[1.500,4,"X1-Boost-Air-Mini","*DIFFERENT SERIAL*",1,1.17,0.00,1.14,0.00]}

What version of Home Assistant Core has the issue?

core-2024.5.3

What was the last working version of Home Assistant Core?

core-2024.5.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

SolaX Power

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

`ValueError: Sensor sensor.solax_total has device class 'energy', state class 'measurement' unit 'kWh' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'unknown' (<class 'str'>)
2024-05-12 12:51:44.408 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/solax/sensor.py", line 160, in async_refresh
    sensor.async_schedule_update_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1258, in async_schedule_update_ha_state
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1006, in async_write_ha_state
    self._async_verify_state_writable()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 974, in _async_verify_state_writable
    raise RuntimeError(f"Attribute hass is None for {self}")`

Additional information

The device is connected to the router with static ip.

@home-assistant
Copy link

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

Code owner commands

Code owners of solax can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign solax Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


solax documentation
solax source
(message by IssueLinks)

@davosje
Copy link
Author

davosje commented May 13, 2024

Hi, for everybody that experience the same issue. I just deleted the integration and added it again. Values are back!

@davosje davosje closed this as completed May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant