What happened to /api/error_log?

Configuration
1

Anyone know what happened to the error log API?
It’s still listed in the official documentation as /api/error_log. I know the physical log was deprecated, but nothing is documented about the API going away (logs are still accessible in the UI).

I only get a 404 now.

2

I have the same issue. I assumed it was me not managing my post or making a mistake but it seems to just nog be there

3

I'd like OpenClaw to watch the log and suggest corrections - best way is to use the api, maybe the endpoint changed?

4

FYI, Claude taught me how to bypass the apparently-deprecated /api/error_log REST endpoint entirely and instead use this WebSocket approach:

  1. Connect to ws://$HA_HOST:$HA_PORT/api/websocket
  2. Authenticate with your long-lived token
  3. Send the command, {"id":1,"type":"system_log/list"}
  4. Parse the JSON response.

Claude also authored this JSON response parser python script:

import json, datetime
with open('/tmp/ha_ws_log.json') as f:
    lines = f.readlines()
result_line = [l for l in lines if '"type": "result"' in l or '"type":"result"' in l]
d = json.loads(result_line[0])
for e in d['result']:
    ts = e.get('timestamp')
    dt = datetime.datetime.fromtimestamp(ts) if ts else None
    msg = ' '.join(e['message']) if isinstance(e.get('message'), list) else e.get('message', '')
    print(dt, '|', e['name'], '|', e['level'], '| count:', e.get('count'), '|', msg[:200])