-
Notifications
You must be signed in to change notification settings - Fork 23
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
Frequently "not available" error since some days (HA update 2022.10?) #35
Comments
I have exactly the same issues... now i just added a cronjob to home assitant that it will be automaticall restarted every night .....But the root cause is on the addon i am pretty sure |
Meanwhile I have the feeling that this is somehow linked to a fragile network cable connection. |
Could you share the logs and detailed error messages you get? You should have something if the sensors are not available? I do not experience any problems even with latest HA, so it's hard for me to judge. |
I'm having the same issue here. Since a few HA updates, the integration says "not available". Where can I find some debug logouts which could help to find the source of the problem? |
lately it seems to be more stable again. I'm on the current HA 2023.3.6 version. |
I am currently getting the same issue in the version 2023.8.1.
|
For me the problem seems to be solved locally. |
I have no issues with the integration running the latest HA Version 2023.8.3 Running like a charm (except that the battery is again in 70% conditioning mode 😢 ) |
Anyone an idea how to validate the issue? Looks for me, that the response of the API Call returns an unexpected character. Does anyone knows the exact API call? |
@klaus1956 Why did you closed this issue? Looks like the problem does still exist? |
I think I opened it due to a specific issue (on my side) which is solved |
Hello
I ran the intergartion some months now w/o problems on a modified timedelta of 20 seconds instead of the original 60 seconds. More or less since the HA-update to 2022.10 I got frequently not available errors . Even after re-adjusting timedelta to 60 secondes the measurement data are not available for more than 50% of the time.
PV-Car charging is not possible under these conditions :(
Has anyone else the same issue?
The text was updated successfully, but these errors were encountered: