Error in log related to Ohme EV charger dns name resolution

[PauloGoncalves86]

Describe the bug
A clear and concise description of what the bug is.

Expected behaviour
A clear and concise description of what you expected to happen.

Predbat version

Describe the bug
I configured prebat and have it in monitor mode.
I configured both grid load and backup loads on apps.yaml
I also configured the Ohme EV charger:
ohme_login: "YYYY@gmail.com"
ohme_password: "XXX"
ohme_automatic: true

In the logs, see an error related to Ohme:

aiohttp.client_exceptions.C lientConnectorDNSError: Cannot connect to host api.ohme.io:443 ssl:default [Temporary failure in name resolution] -- 763 | raise ClientConnectorDN SError(req.connection_key, exc) from exc 732 | socket.gaierror: [Errno -3] Temporary failure in name resolution 710 | 2025-12-18 20:06:22.738248: Error: Traceback (most recent call last): 709 | 2025-12-18 20:06:22.712696: Error: OhmeAPI: Cannot connect to host api.ohme.io:443 ssl:default [Temporary failure in name resolution]

Expected behaviour
I was not expecting the error

Predbat version

v8.29.13

Environment details

Inverter and battery setup
Inverter is solis hybrid 8kw. I have no PV
battery is 16 kwh, I get the stats via a solis modbus integration.
Standard HAOS installer or Docker
HAOS on mini pc (HA supported configuration with docker containers)
Anything else?
I also have the solis control and solis inverter integrations configured.

Screenshots
If applicable, add screenshots to help explain your problem. The most useful ones can be your battery chart, the Predbat HTML plan and your current settings in HA.

Log file
Can you capture a log file from the time of the issue, debug mode is not normally required.

You can download the logfile from the WebUI on the Dash tab select predbat_debug.log

predbat (1).log

Predbat debug yaml file
This is important for any plan related issues.

Once you have captured the issue go to the Web UI, in the Dash tab click on predbat_debug.yaml and wait 30 seconds for it to download. Select 'keep' if your Web Browser thinks the file is dangerous.

Rename the download file to predbat_debug.yaml.txt and upload it to GitHub. This will allow your plan to be reproduced and also stores all your settings for review.

[gcoan]

this points to a problem with your home assistant not being able to access the site api.ohme.io:443

try it from something else on your network and see if you can connect

otherwise it looks like a temporary problem. You could try restarting home assistant to see if that cures the connection problem

from the logs I see this message appearing at 11:55 for a while, then the logs appear clear, then at the end a different message:

2025-12-19 18:10:18.603582: Ohme API: Started
2025-12-19 18:10:18.730207: Error: OhmeAPI: Incorrect credentials

looks like there was a temporary connection issue to Ohme which is now resolved but your login details are now incorrectly set in apps.yaml

[springfall2008]

This works for me, so it seems to be related to your connection

[PauloGoncalves86]

Thanks, I will have another look. I think I activated passkey login to Ohme so I am not 100% sure what I need to set! I also switched broadband provider recently, perhaps the current provider has some DNS limitation. I tried that address form a browser and seemed to have done a redirect without issues.

…

On Fri, 19 Dec 2025 at 18:58, Geoffrey Coan ***@***.***> wrote: *gcoan* left a comment (springfall2008/batpred#3081) <#3081 (comment)> this points to a problem with your home assistant not being able to access the site api.ohme.io:443 try it from something else on your network and see if you can connect otherwise it looks like a temporary problem. You could try restarting home assistant to see if that cures the connection problem from the logs I see this message appearing at 11:55 for a while, then the logs appear clear, then at the end a different message: 2025-12-19 18:10:18.603582: Ohme API: Started 2025-12-19 18:10:18.730207: Error: OhmeAPI: Incorrect credentials looks like there was a temporary connection issue to Ohme which is now resolved but your login details are now incorrectly set in apps.yaml — Reply to this email directly, view it on GitHub <#3081 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQWZFN6KXRDA52263FXFAZL4CRDGDAVCNFSM6AAAAACPSEDRXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZWGE3DOMJZHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>