-
Notifications
You must be signed in to change notification settings - Fork 17
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
Getting timestamp failed. Web Socket not running #172
Comments
I have the same problem. I get all errors except the last one. I noticed that when I log out from the server in the app and log back in, then I have a connection and can edit data but after about a minute the errors mentioned occur. After a night sleep it might work again but only for a minute or so. To give some system context for my installation: homeassistant:
IOS app:
MacOS app:
As an example, here is the IOS App log after logging out of the server, logging back in and editing some data until it doesn't work anymore:
|
I am trying to use the Grocy app, however I keep getting errors. I have installed the Grocy add-on in the Home Assistant OS, the web interface works fine.
In the iOS app, I often get white screens or products can't be saved, always with one of the following error messages:
Getting timestamp failed. Message: hassError(error: Grocy_Mobile.APIError.errorString(description: "Web Socket not running."))
or this:
Product edit failed. Message: hassError(error: Grocy_Mobile.APIError.errorString(description: "Web Socket not running."))
or this:
Getting timestamp failed. Message: ErrorDomain=kNWErrorDomainPOSIX Code=57 "Socket is not connected" UserInfo={NSDescription=Socker is not connected}
or this:
Getting timestamp failed. Message: internalError
Version: 3.3.2
Releasedatum: 12.11.2022
PHP Version: 8.1.19
SQLite Version: 3.41.2
The text was updated successfully, but these errors were encountered: