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

No battery status after firmware upgrade #311

Open
robin13 opened this issue May 12, 2023 · 5 comments
Open

No battery status after firmware upgrade #311

robin13 opened this issue May 12, 2023 · 5 comments
Labels
bug Something isn't working question Further information is requested

Comments

@robin13
Copy link

robin13 commented May 12, 2023

Since upgrading RCT Power Storage 10.0 (PS 10.0 B59G) to latest firmware 2.3.5661 there are no values for the RCT Power battery device...

@weltenwort
Copy link
Owner

hm, I can't reproduce that. It seems to work for me on that same version. By "no values" you mean the entities are gone? Or they just don't receive new values?

@weltenwort weltenwort added bug Something isn't working question Further information is requested labels May 12, 2023
@robin13
Copy link
Author

robin13 commented May 12, 2023

All the entities under the device storage battery are unavailable.
I don't see anything related in the logs... Is there something I can do to get more insight into what is missing?

@weltenwort
Copy link
Owner

Sorry for the delay in answering 🙈 You could try to increase the log level to debug for the integration by setting this in your Home Assistant configuration.yaml:

logger:
  default: info
  logs:
    custom_components.rct_power: debug

@robin13
Copy link
Author

robin13 commented Jun 15, 2023

I tried enabling the debugging, but did not see anything there that helped me understand. The only slightly off thing I noticed was:

2023-06-11 19:19:26.098 DEBUG (MainThread) [custom_components.rct_power.lib] Decoded data for object 959930bf (battery.soc): 0.5
2023-06-11 19:19:26.286 DEBUG (MainThread) [custom_components.rct_power.lib] Decoded data for object 959930bf (battery.soc): 0.9671242237091064

This is strange that it seems to be reading both an invalid SOC (first line) and an invalid one...

In any case... I deleted the devices and created them new. With the newly created ones, the battery state is again visible. It would be great if you can identify something in the logs to avoid this happening again, as it was quite a bother to change the entity ids in all the automations etc. that refer to these.

Uploading rct_power_debug.log.gz…

@weltenwort
Copy link
Owner

Interesting, it almost looks like the inverter responded to the query with two different values 🤔

Thanks for enabling the debug logging. Unfortunately the upload didn't quite work, apparently. 😬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants