Ohme Connectivity

[Ashpork]

Describe the bug Ohme now seem to be limiting the connectivity to their API

Expected behaviour Predbat to use the direct ohme connectivity, and successfully identify expected load/time slots

Predbat version v8.27.24

See the discussion on the HA core integration for ohme as it looks like the issue relates to the advancedSettings

Since about 11:30 this morning, predbat is unable to connect to the ohme API and plan calculation fails. See log excerpt below.

65536 | ohme.ApiException: Warn:Ohm e API response error: /v1/chargeDevices/redacted/advancedSettings, 401; {"timestamp":1763411386980,"status":401,"error":"Unauthorized","message":"Unauthorised","path":"/v1/chargeDevices/redacted/advancedSettings"} -- | -- 65535 | raise ApiException(msg) 65534 | File "/config/ohme.py", l ine 543, in _handle_api_error 65533 | await self._handle_api_ error(url, resp) 65532 | File "/config/ohme.py", l ine 571, in _make_request 65531 | ^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 65530 | resp = await self._make _request("GET", f"/v1/chargeDevices/{self.serial}/advancedSettings") 65529 | File "/config/ohme.py", l ine 909, in async_get_advanced_settings 65528 | await self.client.async _get_advanced_settings() 65527 | File "/config/ohme.py", l ine 229, in start