search

pgerke / homebridge-freeathome-local-api

A Homebridge plugin that allows controlling you free@home setup using the local API provided by the System Access Point
MIT License
18 stars 2 forks source link

500 internal server error on startup #33

Closed korneliuscode closed 2 years ago

korneliuscode commented 2 years ago

hi, I installed and configured the plugin and tried with 2 different users. The result is the same. I get this error when booting homebridge. Any ideas?

My sysAP is on 3.1.0 Rev 9754.

[27/11/2022, 22:35:59] [My free@home Setup] Received HTTP 500 status code unexpectedly: <html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
</body>
</html>

[27/11/2022, 22:36:00] [My free@home Setup] Device discovery failed Error: Received HTTP 500 status code unexpectedly: <html>
<head><title>500 Internal Server Error</title></head>
<body>
<center><h1>500 Internal Server Error</h1></center>
</body>
</html>

    at s.<anonymous> (/var/lib/homebridge/node_modules/homebridge-freeathome-local-api/node_modules/freeathome-local-api-client/dist/cjs/webpack:/freeathome-local-api-client/src/system-access-point.ts:388:15)
    at Generator.next (<anonymous>)
    at u (/var/lib/homebridge/node_modules/homebridge-freeathome-local-api/node_modules/freeathome-local-api-client/dist/cjs/index.js:1:161693)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
pgerke commented 2 years ago

Hi, the error message you sent indicates your SysAP responded with a HTTP 500 error to a request the plugin is sending to retrieve the device configuration. Can you confirm you have a second generation System Access Point and local API is enabled? The firmware version is fine, I'm running the same one.

korneliuscode commented 2 years ago

Actually the local api was the issue. Fixed it by enabling it and using the username given for the API. Thanks for the hint!!

pgerke commented 2 years ago

Perfect, I'm happy to hear your issue is resolved!

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.