Someone on the MG forums suggested changing the picture to monochrome with a picture editor, which I had a little trouble doing to get a dark enough grey from the original orange but they posted one they created, so I flipped that to portrait and have this so far:
I think portrait mode gives a bit more room to place info icons on the phone screen. I might add a couple of extra things, e.g. the range estimate, odometer.
Iām trying to run the mqtt gateway via docker. My MQTT container is in the same stack.
Everything can connect to the mqtt container such as zigbee2mqtt and other docker containers but I canāt get this gateway to connect even if I run under host mode.
Iām mqtt is anonymous. Logs just suggest connection refused.
The car (MG4) refuses to charge after the EVSE (Wallbox Pulsar Plus) has been on āPauseā for a while.
I run an automation on the EVSE to start charging when the Solar inverter (SMA) voltage rises too high. This to prevent the solar system from shutting down. With my Polestar connected this works great, during a two week vacation it prevented dozens of solar system shutdowns.
However with the MG4 it does not (always) work. When the EVSE has been on āPauseā for a wile, then when the automation kicks in and wants to car to charge, the car does not accept a charge, the EVSE status goes into āWaiting for car demandā.
What is causing this behavior, what could a work around be?
charging from 12:10 to 12:18 (based on solar inverter voltage)
paused from 12:18 to 16:03, at 16:03 charge initiated, but not starting
waiting for demand from 16:03 on, charging not accepted by the car
PS
This behavior also makes that the scheduled charge automation does not always work.
The only way to start charging again that I could find is to physically disconnect the car and reconnect it again (hard to do from 1000 miles away). Also forcing a refresh does not re-enable charging.
I would agree. Not the MG integration, not the EVSE integration, not the HA automation. It seems to be the reaction of the car to the EVSE switching on and off (more precisely in and out of āpausedā).
I canāt figure out what causes this. Sometimes it works fine a whole day, sometimes it fails after the the first switch. Just wondering if anybody else has seen this work or fail and if there is a fix.
There is a power sensor and a sensor for plugged-in.
You should be able to feed the power sensor to a utility meter when ever the plugged-in sensor is āonā
ODB plug is not required
Yes.
There are settings for Target SOC, current adjustment for 6/8/16 and Max amps, a toggle to start and stop charging, start and stop times, and a selection for charge till target SOC or till stop time.
