Open GamEased opened 9 months ago
Hi, Same here, but my integration was working allready until yesterday 11:48. Looks like there are problems with the API at SAIC site and maybe there are some changes comming as well?
Lucky me then timin wise :D
I read something about an API 2.0 or the new iSmart 2 App - tbh, my App got a big rework a few weeks ago so maybe they did some changes there and those brilliant people of this community need time to figure out :) I'm sure either way they will get it to work. THanks to everyone putting their time and effort in those things.
It is solved - you just have to refresh your car in the I smart app once. After that it works. Don't ask me why please^^
I think it is a server problem. I used the app yesterday evening, but also after that the gateway won't work.
Did you try a complete scan of the car?
Yes, to make sure the car was locked.
It is solved - you just have to refresh your car in the I smart app once. After that it works. Don't ask me why please^^
yes thanks, also it works here again. And thanks developers ! for the good work to create this functionality for contact with the EV !
I constantly see in my logging errors from my Tyre pressure. It looks like i have an issue with my sensor. Don't think this has nothing to do with the API. @GamEased, Do you have also messages in the logging, like this? 2024-01-27 19:30:58,208 [ INFO ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:31:57 CET)" executed successfully - apscheduler.executors.default 2024-01-27 19:31:57,493 [ INFO ] Running job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" (scheduled at 2024-01-27 19:31:57.485003+01:00) - apscheduler.executors.default 2024-01-27 19:31:57,945 [ INFO ] 5 messages received - main 2024-01-27 19:31:57,947 [ INFO ] ID: 21845378, Time: 2024-01-17 15:53:03, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: xxxxx- main 2024-01-27 19:31:57,947 [ INFO ] ID: 21842441, Time: 2024-01-17 15:17:23, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: xxxxx- main 2024-01-27 19:31:57,948 [ INFO ] ID: 21839010, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: xxxxx- main 2024-01-27 19:31:57,949 [ INFO ] ID: 21839009, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: xxxxx- main 2024-01-27 19:31:57,949 [ INFO ] ID: 21008018, Time: 2024-01-09 15:03:46, Type: 801, Title: Abnormal Alarm, Content: The Tyre Pressure of your vehicle (***498) is abnormal, please check the vehicle in time to ensure the safety., Status: unread, Sender: TBOX, VIN: xxxxx- main 2024-01-27 19:31:57,950 [ INFO ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" executed successfully - apscheduler.executors.default
I constantly see in my logging errors from my Tyre pressure. It looks like i have an issue with my sensor. Don't think this has nothing to do with the API. @GamEased, Do you have also messages in the logging, like this? 2024-01-27 19:30:58,208 [ INFO ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:31:57 CET)" executed successfully - apscheduler.executors.default 2024-01-27 19:31:57,493 [ INFO ] Running job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" (scheduled at 2024-01-27 19:31:57.485003+01:00) - apscheduler.executors.default 2024-01-27 19:31:57,945 [ INFO ] 5 messages received - main 2024-01-27 19:31:57,947 [ INFO ] ID: 21845378, Time: 2024-01-17 15:53:03, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXX - main 2024-01-27 19:31:57,947 [ INFO ] ID: 21842441, Time: 2024-01-17 15:17:23, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXXX - main 2024-01-27 19:31:57,948 [ INFO ] ID: 21839010, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De bandendruk van uw voertuig (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXXX - main 2024-01-27 19:31:57,949 [ INFO ] ID: 21839009, Time: 2024-01-17 14:36:43, Type: 801, Title: Abnormaal alarm, Content: De status van uw linkerachterband (498) is abnormaal. Laat het voertuig op tijd controleren in verband met de veiligheid., Status: unread, Sender: TBOX, VIN: XXXXXXXXX - main 2024-01-27 19:31:57,949 [ INFO ] ID: 21008018, Time: 2024-01-09 15:03:46, Type: 801, Title: Abnormal Alarm, Content: The Tyre Pressure of your vehicle (*498) is abnormal, please check the vehicle in time to ensure the safety., Status: unread, Sender: TBOX, VIN: XXXXXXXXX - main** 2024-01-27 19:31:57,950 [ INFO ] Job "Check for new messages (trigger: interval[0:01:00], next run at: 2024-01-27 19:32:57 CET)" executed successfully - apscheduler.executors.default
The issue is I have this alarm active right now because of the cold my tire pressure on the tires are often a little too low until I get going - so I guess I am not able to tell false positives apart, sorry about that.
Just a tip - next time better cover your VIN as this is the identification Number for your car.
@GamEased ok, thanks!
I just checked again because it is a little warmer right now. MG App on my phone says tire pressure is fine.
MQTT Log indeed says as well:
2024-01-27 20:18:00,368 [ INFO ] ID: 22058415, Time: 2024-01-19 17:56:19, Type: 801, Title: Abnormal Alarm, Content: The Tyre Pressure of your vehicle (***367) is abnormal, please check the vehicle in time to ensure the safety., Status: unread, Sender: TBOX, VIN: XXXXXXXXX - __main__
So I guess it's some form of bug.
Hey all,
I just installed this add-on (I used python). My Gateway is mosquitto. Add-On Version is 0.4.6 The Sensors (HA Discovery) get created but after a while this error comes up and no values are pulled:
I am not a programmer but it seems like some variables have the wrong declaration of datatype - or the API sends information to the wrong places
I already tried reinstalling it as well as tested the Java Add-On - this gave me another error which I didnt really looked into as I planned to use python regardless.
My HA is on versions: Core 2024.1.5 Supervisor 2023.12.1 Operating System 11.4 Frontend 20240104.0
Thank yall