-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
API keeps crashing #22
Comments
Are you sure that you can reach the system access point with the IP set in the configuration file? |
Yes, it is reachable and I managed to get it to work by commenting out line 33 in appRunner.js. |
It should also run on a Pi Zero. I thought of a race condition in the code but couldn't find anything. Please enable debug logging and post a log again. |
I'm on a trip this week and I can't access the device from here, so I'll post the log when I'm back next monday. |
So here is the full log
|
Hmm that doesn't look right. Have you created a separate user for the API? If so, what permission does it have? |
Yes I have, it has "Operation" level but I've tried an "Installation" account as well and the results were the same. |
Hi, mine is set to "Operation" too. Do you use special characters (including umlauts) in your username or password? |
No. As I said when I comment out line 33 in appRunner.js it is working fine. The only issue I have then is that accessories turn "not reachable" in the home app when sending too many commands at once (I am using your homebridge plugin as well). Not sure if that is normal, it's probably because of the jabber based protocol that creates a lot of overhead and noise on the socket. |
Sorry, I forgot that you mentioned it. Please also include a log with the line commented out. |
|
Hmm. I'm not sure how to fix it. We could ignore the EPIPE error and let it reconnect automatically, however that would probably be bad in case a real error occurs. The API should exit properly when an error occurs so systemd can restart it (for example). We need to to implement some error handling to automatically reconnect. I may consider this for a future update but at the moment I won't fix this. I think the real issue is a race condition in the XMPP library so even a fix from my side would just be a workaround. |
I am running SysAp v. 2.4.0 and the API keeps crashing.
Any ideas?
The text was updated successfully, but these errors were encountered: