MG MQTT #9811

sanwaldx6x · 2023-09-09T12:21:43Z

sanwaldx6x
Sep 9, 2023

Describe the bug

The Vehicle Load status is not screened in evcc.
I always get alarm:
vehicle soc: saic/mail/vehicles/vin/drivetrain/soc outdated: 10s

09 14:02:32 evcc evcc[527]: [mqtt ] DEBUG 2023/09/09 14:02:32 saic/mail/vehicles/vin/drivetrain/soc wait for initial value
Sep 09 14:02:42 evcc evcc[527]: [lp-1 ] ERROR 2023/09/09 14:02:42 vehicle soc: saic/mail/vehicles/vin/drivetrain/soc outdated: 10s

If I check vehicle configuration it semms it reads alwys only 6 Datas and reconnect.

For me it seems evcc always reconnecct less then a second to mgtt, that there is no time to get all Datas.

Do you have any idea or advice whats to check?

Steps to reproduce

Always

...

Configuration details

sponsortoken: ...

network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: ....

interval: 10s # control cycle interval

loadpoints:
  - title: Carport
    charger: Wallbox_1
    mode: pv # charge mode (off, now, minpv, pv)
    vehicle: mg_zs_ev

meters:
- type: template
  template: sungrow-hybrid
  id: 1
  host: 192.168.201.22
  port: 502
  usage: grid
  modbus: tcpip
  name: grid1
- type: template
  template: sungrow-hybrid
  id: 1
  host: 192.168.201.22
  port: 502
  usage: pv
  modbus: tcpip
  name: pv2
- type: template
  template: sungrow-hybrid
  id: 1
  host: 192.168.201.22
  port: 502
  usage: battery
  modbus: tcpip
  name: battery3

chargers:
  - name: Wallbox_1
    type: template
    template: heidelberg
    modbus: rs485tcpip
    id: 1
    host: 192.168.202.150
    port: 502

site:
  title: my home
  meters:
    grid: grid1
    pv:
    - pv2
    battery:
    - battery3

mqtt:
  broker: 192.168.202.26
  topic: evcc
  clientid: evcc
  user: .....
  password: .....

vehicles:
  - name: mg_zs_ev
    type: template
    template: mg2mqtt
    title: MG ZS EV
    user: .....
    vin: ......
    capacity: 51 # Akkukapazität in kWh (optional)
    phases: 1
    maxcurrent: 3.8
    icon: car

Log details

[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/soc
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/chargerConnected
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/charging
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/range
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/mileage
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/climate/remoteClimateState
[mqtt  ] ERROR 2023/09/09 14:11:37 tcp://192.168.202.26:1883 connection lost: EOF
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 connected
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/chargerConnected
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/charging
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/range
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/mileage
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/climate/remoteClimateState
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/soc
[mqtt  ] ERROR 2023/09/09 14:11:37 tcp://192.168.202.26:1883 connection lost: EOF
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 connected
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/charging
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/range
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/mileage
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/climate/remoteClimateState
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/soc
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 subscribe saic/daniel-lai@web.de/vehicles/vin/drivetrain/chargerConnected
[mqtt  ] ERROR 2023/09/09 14:11:37 tcp://192.168.202.26:1883 connection lost: EOF
[mqtt  ] DEBUG 2023/09/09 14:11:37 tcp://192.168.202.26:1883 connected







log from MQTT:
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58038 as evcc (p2, c1, k30, u'daniel').
1694261497: New connection from 192.168.201.21:58044 on port 1883.
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58044 as evcc (p2, c1, k30, u'daniel').
1694261497: New connection from 192.168.201.21:58048 on port 1883.
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58048 as evcc (p2, c1, k30, u'daniel').
1694261497: New connection from 192.168.201.21:58062 on port 1883.
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58062 as evcc (p2, c1, k30, u'daniel').
1694261497: New connection from 192.168.201.21:58068 on port 1883.
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58068 as evcc (p2, c1, k30, u'daniel').
1694261497: New connection from 192.168.201.21:58078 on port 1883.
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58078 as evcc (p2, c1, k30, u'daniel').
1694261497: New connection from 192.168.201.21:58086 on port 1883.
1694261497: Client evcc already connected, closing old connection.
1694261497: New client connected from 192.168.201.21:58086 as evcc (p2, c1, k30, u'daniel').

What type of operating system are you running?

Linux

Version

evcc version 0.119.5

andig · 2023-09-09T12:31:26Z

andig
Sep 9, 2023
Maintainer

Would be good if other users of MG could verify this

3 replies

c1olli Sep 9, 2023

That`s my solution.
The saic-java-mqtt-gateway sends the Data to ioBroker (my mqtt broker)

`vehicles:

name: MG 4
type: custom
title: MG 4
capacity: 64 # kWh
onIdentify:
targetSoc: 80
soc: # %
source: http
uri: http://192.168.178.115:8087/getPlainValue/0_userdata.0.autobatt
method: GET
cache: 15m
range: # km
source: http
uri: http://192.168.178.115:8087/getPlainValue/0_userdata.0.autoweit
method: GET
`

Bitmage77 Nov 23, 2023

Hello c1olli,
I am running an intel nuc with linux. I have a MG4 and I would like to get the data via MQTT in my IOBroker.

This is what I found so far: https://github.com/SAIC-iSmart-API
Sadly, I dont find the saic-java-mqtt-gateway. Only one with python.
Could you help me get it running? I am very new to this but willing to learn.

Bitmage77 Nov 23, 2023

Okay, I found this one now: https://github.com/SAIC-iSmart-API/saic-java-client/tree/main/saic-java-mqtt-gateway
I will work onto it.

datOlle · 2023-09-11T17:51:02Z

datOlle
Sep 11, 2023

Hi,
In evcc documentation it says the VIN is optional.
but it only works with VIN

I got the same Error without VIN

1 reply

sanwaldx6x Sep 11, 2023
Author

Hi,
I have used the VIN, I just replaced with vin due Data Sercurity.

sanwaldx6x · 2023-09-11T19:07:49Z

sanwaldx6x
Sep 11, 2023
Author

I got a temporary solution which is working now thanks to @c1olli for inspiration:

vehicles:
  - name: mg_zs_ev
    type: custom
    title: MG ZS EV
    capacity: 50 # kWh
    onIdentify:
      maxcurrent: 3.8
    soc: # %
      source: mqtt
      topic: mg_saic/[mail]/vehicles/[vin]/drivetrain/soc
      timeout: 5m
    range: # km
      source: mqtt
      topic: mg_saic/[mail]/vehicles/[vin]/drivetrain/range
      timeout: 5m

But I'm not complete satisfied, because the basic issue is not solved.
I think I have a basic problem with MQTT to EVCC, it has nothing to do with just with the mggateway, because this is basically working.
On HAAS I can see all Informaitons form the Gateway.

Maybe as next I will try to install another MQTT Broker, just to be sure, that the issue do not come from there, even everything else is running with the actual MQTT broker. But this needs time.

1 reply

BaxPlay360 Jan 17, 2024
Sponsor

I need help with my MG ZS EV. I can't manage to use an mqtt broker and have my car displayed on evcc.

can someone help me? best in German but English is also possible.

BaxPlay360 · 2024-01-17T15:04:43Z

BaxPlay360
Jan 17, 2024
Sponsor

I need help with my MG ZS EV. I can't manage to use an mqtt broker and have my car displayed on evcc.

can someone help me? best in German but English is also possible.

14 replies

BaxPlay360 Jan 17, 2024
Sponsor

@c1olli können Sie mir helfen und mit mir schritt für schritt durch gehen. natürlich fürn kasten bier

c1olli Jan 18, 2024

Ich würde gerne helfen, aber wie eine virtualbox mit debian reagiert weiß ich nicht.
Das einfachste ist ein Raspberry pi, oder ein Docker System.
Es benötigt aber auch einen MQTT Broker, um die Daten abzugreifen.
Ich hab mir das auch nur angelesen und bin nur einfacher User.
Auf welchem System läuft denn EVCC?

BaxPlay360 Jan 18, 2024
Sponsor

Mit Docker habe ich es auch versucht, aber da habe ich mich nicht all zu lange beschäftigt. Was ich nicht nicht weiß, wie man Docker genau benutzt.

BaxPlay360 Jan 19, 2024
Sponsor

so ich gebe es auf mosquitto eingerichtet und getestet. aber saic-ismart-mqtt refused immer die connection. es geht einfach nicht bei mir. aber dieses phänomen hab ich immer: wenn alle sagen das das einfach ist, habe ich damit probleme. ich schreibe hin und wieder mal eigene apks oder ändere diese aber das bekomme ich nicht hin

BaxPlay360 Jan 19, 2024
Sponsor

@c1olli evcc läuft auf windows

Uh oh!

Uh oh!

MG MQTT #9811

Uh oh!

Uh oh!

sanwaldx6x Sep 9, 2023

Describe the bug

Steps to reproduce

Configuration details

Log details

What type of operating system are you running?

Version

Replies: 4 comments · 19 replies

Uh oh!

andig Sep 9, 2023 Maintainer

Uh oh!

c1olli Sep 9, 2023

Uh oh!

Bitmage77 Nov 23, 2023

Uh oh!

Bitmage77 Nov 23, 2023

Uh oh!

datOlle Sep 11, 2023

Uh oh!

sanwaldx6x Sep 11, 2023 Author

Uh oh!

sanwaldx6x Sep 11, 2023 Author

Uh oh!

BaxPlay360 Jan 17, 2024 Sponsor

Uh oh!

BaxPlay360 Jan 17, 2024 Sponsor

Uh oh!

BaxPlay360 Jan 17, 2024 Sponsor

Uh oh!

c1olli Jan 18, 2024

Uh oh!

BaxPlay360 Jan 18, 2024 Sponsor

Uh oh!

BaxPlay360 Jan 19, 2024 Sponsor

Uh oh!

BaxPlay360 Jan 19, 2024 Sponsor

sanwaldx6x
Sep 9, 2023

Replies: 4 comments 19 replies

andig
Sep 9, 2023
Maintainer

datOlle
Sep 11, 2023

sanwaldx6x Sep 11, 2023
Author

sanwaldx6x
Sep 11, 2023
Author

BaxPlay360 Jan 17, 2024
Sponsor

BaxPlay360
Jan 17, 2024
Sponsor

BaxPlay360 Jan 17, 2024
Sponsor

BaxPlay360 Jan 18, 2024
Sponsor

BaxPlay360 Jan 19, 2024
Sponsor

BaxPlay360 Jan 19, 2024
Sponsor