-
Notifications
You must be signed in to change notification settings - Fork 3
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
Constant Status 504 - Gateway Timeout errors - is this normal? #885
Comments
Someone had a similar issue with my NodeRED module here and for reasons I cannot explain, an uninstall/reinstall fixed the issue for them. Maybe try the same with the add-on? BigThunderSR/node-red-contrib-onstar2#311 |
Unfortunately, uninstalling and reinstalling did not work for me. I am still experiencing 504 Gateway Timeouts every 30 minutes. |
Both of my vehicles are ICE and the best chances that I get data from both vehicles is if the data is requested while the engines have been running for several minutes with the ignition actually on (remote start doesn't count). Beyond that, it is very much a roll of the dice on what the GM side decides to do. |
I have a Bolt EV, and I have tried running the engine and driving around, but I am still getting 504 errors most of the time. I wonder if it could possibly be the version of the OnStar plan that I have. The EVs come with EV Access and Connected Access OnStar plans included, but I did not purchase any additional OnStar plan. I guess it is possible this is the issue, but as I noted previously, the add-on was working fine prior to the TOTP requirement - and I am getting data sometimes, just not most of the time. |
Gotcha. Unfortunately, I don't have any other suggestions since I'm not able to replicate the same with mine. |
I am having a problem where I am getting Status 504 - Gateway Timeout errors most of the time. If I have the refreshInterval set at 1800000, meaning that the API is pinged 48 times a day, on average I am seeing a Status 504 error at least 47 of those 48 times. I do get the good data from the API about once per day on average, so I think everything is generally configured correctly.
I read the "Helpful Usage Notes" section and I know that the API is temperamental, but I don't think this is normal and I was wondering if anyone had any insights as to what is going on here. As another data point, before the API required the TOTP codes, I was only getting the Status 504 error maybe once or twice per day instead of most of the time.
I have tried increasing the refreshInterval, but that does not seem to have made a difference. I have also tried generating a new v4 uuid, but that doesn't seem to have done anything either.
Does anyone have any thoughts as to what I might be doing wrong? I have included my logs below (VIN, IP addresses, etc. are redacted). I just restarted the add-on before taking this log, but if the pattern holds, I will receive the same "error: ..." line every 30 minutes.
Thanks in advance for any help.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[08:04:24] INFO: Starting OnStar2MQTT for Vehicle 1...
The text was updated successfully, but these errors were encountered: