search

SAIC-iSmart-API / saic-java-client

MIT License
7 stars 3 forks source link

no connection to SAIC/MG anymore #120

Open Markus0806 opened 1 month ago

Markus0806 commented 1 month ago

Since August 8, 2024, the gateway can no longer establish a connection to MG (SAIC). The following error message is in the log file:

java[1425]: org.apache.hc.client5.http.ClientProtocolException: Unexpected response status: 429 java[1425]: at net.heberling.ismart.Client.lambda$sendRequest$0(Client.java:37) java[1425]: at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:247) java[1425]: at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:188) java[1425]: at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:162) java[1425]: at net.heberling.ismart.Client.sendRequest(Client.java:40) java[1425]: at net.heberling.ismart.mqtt.SaicMqttGateway.call(SaicMqttGateway.java:264) java[1425]: at net.heberling.ismart.mqtt.SaicMqttGateway.call(SaicMqttGateway.java:67) java[1425]: at picocli.CommandLine.executeUserObject(CommandLine.java:2041) java[1425]: at picocli.CommandLine.access$1500(CommandLine.java:148) java[1425]: at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461) java[1425]: at picocli.CommandLine$RunLast.handle(CommandLine.java:2453) java[1425]: at picocli.CommandLine$RunLast.handle(CommandLine.java:2415) java[1425]: at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273) java[1425]: at picocli.CommandLine$RunLast.execute(CommandLine.java:2417) java[1425]: at picocli.CommandLine.execute(CommandLine.java:2170) java[1425]: at net.heberling.ismart.mqtt.SaicMqttGateway.main(SaicMqttGateway.java:395) systemd[1]: saic-mqtt-gateway.service: Main process exited, code=exited, status=1/FAILURE

villingerh commented 1 month ago

I have the same issue. Trying the following URL in a browser gives me "Blocked by Sentinel (flow limiting)"

https://tap-eu.soimt.com/TAP.Web/ota.mpv30

The Android Phone app still works

gitHost7 commented 1 month ago

i have exact the same problem since days... any hints / solutions available ?

Aug 24 10:51:24 heizung java[14243]: org.apache.hc.client5.http.ClientProtocolException: Unexpected response status: 429 Aug 24 10:51:24 heizung java[14243]: at net.heberling.ismart.Client.lambda$sendRequest$0(Client.java:37) Aug 24 10:51:24 heizung java[14243]: at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:247) Aug 24 10:51:24 heizung java[14243]: at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:188) Aug 24 10:51:24 heizung java[14243]: at org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:162) Aug 24 10:51:24 heizung java[14243]: at net.heberling.ismart.Client.sendRequest(Client.java:40) Aug 24 10:51:24 heizung java[14243]: at net.heberling.ismart.mqtt.SaicMqttGateway.call(SaicMqttGateway.java:256) Aug 24 10:51:24 heizung java[14243]: at net.heberling.ismart.mqtt.SaicMqttGateway.call(SaicMqttGateway.java:69) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine.executeUserObject(CommandLine.java:2041) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine.access$1500(CommandLine.java:148) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine$RunLast.handle(CommandLine.java:2453) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine$RunLast.handle(CommandLine.java:2415) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine$RunLast.execute(CommandLine.java:2417) Aug 24 10:51:24 heizung java[14243]: at picocli.CommandLine.execute(CommandLine.java:2170) Aug 24 10:51:24 heizung java[14243]: at net.heberling.ismart.mqtt.SaicMqttGateway.main(SaicMqttGateway.java:415) Aug 24 10:51:24 heizung systemd[1]: saic-mqtt-gateway.service: Main process exited, code=exited, status=1/FAILURE Aug 24 10:51:24 heizung systemd[1]: saic-mqtt-gateway.service: Service RestartSec=100ms expired, scheduling restart. Aug 24 10:51:24 heizung systemd[1]: saic-mqtt-gateway.service: Scheduled restart job, restart counter is at 4071. Aug 24 10:51:24 heizung systemd[1]: Stopped The SAIC MQTT Gateway. Aug 24 10:51:24 heizung systemd[1]: Started The SAIC MQTT Gateway.

Ove

gitHost7 commented 2 weeks ago

@Markus0806 and @villingerh : did you resolve this issue ?

Markus0806 commented 2 weeks ago

I couldn't solve it with saic-java-client. I'm using saic-python-mqtt-gateway now. Installed it in a docker and it works fine

villingerh commented 2 weeks ago

I also changed to saic-python-mqtt-gateway and used the oportunity to move it into my smal kubernetes setup. But I am not yet finished with my overall setup, because the gateway sometimes misses to record if our MG5 is used.