My Mitsubishi PHEV integration, via MQTT

cookiebot · September 7, 2021, 3:44pm

Hey, sorry I feel stupid but need to make sure that I got it right.

If I have my home-assistant instance installed on the raspberry, can I still use this on the same raspberry device, or do I need to get another one?

And if it is possible, could you elaborate a bit on the process how to get the broker compiled onto it? If I have understood now correctly, I should download the GO compiler on the rasberry device, download the archive and then compile it on the device itself?

matti · September 8, 2021, 8:55am

Thank you for the awesome work!

I’m looking to integrate this a bit different way than with raspi. I’m going with old mobile phone running termux because I wan’t mobile connectivity and good battery life for my “PHEV remote” and to have the mobile as my car phone / navigator at the same time.

I’ve succesfully gotten phev2mqtt running now and I can get Tasker to handle the wifi switching etc. so that I will be able to use phev2mqtt over 4G/LTE.

Now my problem is that I won’t be able to use mqtt abilities because of the 4G/WIFI switching and running with Tasker. Well I might be able to achieve this by using rooted phone and by configuring ip routes to correct network interfaces but my phone at the moment is unrootable (Blackberry).

I would like to use phev2mqtt client set commands for now. I’m trying to understand how to set the climate (acmode, heat/windscreen…, duration). I’m inspecting the mqtt file from cmd folder:

else if strings.HasPrefix(msg.Topic(), m.topic("/set/climate/")) {
		topic := msg.Topic()
		payload := strings.ToLower(string(msg.Payload()))

		modeMap := map[string]byte{"off": 0x0, "OFF": 0x0, "cool": 0x1, "heat": 0x2, "windscreen": 0x3, "mode": 0x4}
		durMap := map[string]byte{"10": 0x0, "20": 0x10, "30": 0x20, "on": 0x0, "off": 0x0}
		parts := strings.Split(topic, "/")
		state := byte(0x02) // initial.
		mode, ok := modeMap[parts[len(parts)-1]]
		if !ok {
			log.Errorf("Unknown climate mode: %s", parts[len(parts)-1])
			return
		}
		if mode == 0x4 { // set/climate/mode -> "heat"
			mode = modeMap[payload]
			payload = "on"
		}
		if payload == "off" {
			mode = 0x0
		}
		duration, ok := durMap[payload]
		if mode != 0x0 && !ok {
			log.Errorf("Unknown climate duration: %s", payload)
			return
		}
		if mode == 0x0 {
			state = 0x1
		}
		if err := m.phev.SetRegister(0x1b, []byte{state, mode, duration, 0x0}); err != nil {
			log.Infof("Error setting register 0x1b: %v", err)
			return

So for heat 20 minutes I use command “phev2mqtt client set 0x1b,0x02,0x2,0x10,0x0” am I correct?

Just want to make this sure so I don’t break anything at the PHEV…

droetker · September 25, 2021, 6:59am

with regards to 2… I have implemented the following code in my configuration.yaml and use this new “sensor.phev_battery2” for my gauge.

platform: template
sensors:
phev_battery2:
unit_of_measurement: ‘%’
friendly_name: “Car Battery”
value_template: >
{% if states(‘sensor.phev_battery’) in [‘unknown’, ‘unavailable’, ‘None’] %}
0
{% elif states(‘sensor.phev_battery’)|float >94 %}
{{(states(‘sensor.phev_battery2’)|float *1)}}
{% else %}
{{(states(‘sensor.phev_battery’)| float /0.94) |round(0) }}
{% endif %}

nigotiator · October 11, 2021, 12:44pm

Any advice on this. So I have RaspberryPi where phev2mqtt is installed.
I have USB WIFI dongle and set to connect to the car.
I have LAN connected to home network via router.
But I guess every time the connection is made to car my SSH connection dies and after that I’m not able to connect to the Pi.
When I remove the USB WIFI dongle I’m able to make the connection again.
Operating in headless so not able to say if the connection to car really works.
Topics on mqtt broker are not updated (only shows )

phev/available

10/11/2021 2:19:24 PM 
offline

I guess this is some kind of configuration/routing issue…

strict · December 2, 2021, 6:52pm

Hi,
this is exactely what I am searching for my Outlander PHEV 21, it looks so promessing!!!
I so hope to get it running…
It took me some hours… but now I get some data from the car.

But I am stuck now.
./phev2mqtt client mqtt --mqtt_server tcp://IP:1883 [–mqtt_username XXX] [–mqtt_password XXX]
It does not work, I always get “Error: not Authorized”
Any ideas?
Thanks, Michael

kris10an · December 2, 2021, 7:43pm

I was setting up this earlier today and got the same error. I was using the mqtt user for the Mosquitto broker add-on, but when I added a dedicated PHEV MQTT user to HA it worked.

It works very well so far and seems very responsive, great work! Running in a container on my Proxmox host and using an old wireless D-link router with dd-wrt as a wireless bridged from the Outlander to my cabled network.

I keep getting a lot of errors, but it re-connects, so still works fine:

kristian@phev2mqtt ~$ sudo systemctl status phev2mqtt
[sudo] password for kristian: 
* phev2mqtt.service - phev2mqtt
   Loaded: loaded (/etc/systemd/system/phev2mqtt.service; disabled; vendor preset: enabled)
   Active: active (running) since Thu 2021-12-02 11:58:02 CET; 8h ago
 Main PID: 1686 (phev2mqtt)
    Tasks: 5 (limit: 4915)
   Memory: 10.0M
   CGroup: /system.slice/phev2mqtt.service
           `-1686 /usr/local/bin/phev2mqtt client mqtt --mqtt_server tcp://<hassip>:1883/ --mqtt_username phevmqtt --mqtt_password MySecretPassword -v info

Dec 02 19:40:39 phev2mqtt phev2mqtt[1686]: time="2021-12-02T19:40:39+01:00" level=error msg="Disconnecting due to too many errors"
Dec 02 19:40:40 phev2mqtt phev2mqtt[1686]: time="2021-12-02T19:40:40+01:00" level=info msg="%PHEV_TCP_CONNECTED%"
Dec 02 19:45:56 phev2mqtt phev2mqtt[1686]: Short msg
Dec 02 19:46:07 phev2mqtt phev2mqtt[1686]: time="2021-12-02T19:46:07+01:00" level=error msg="Disconnecting due to too many errors"
Dec 02 19:46:08 phev2mqtt phev2mqtt[1686]: time="2021-12-02T19:46:08+01:00" level=info msg="%PHEV_TCP_CONNECTED%"
Dec 02 19:56:35 phev2mqtt phev2mqtt[1686]: time="2021-12-02T19:56:35+01:00" level=error msg="Disconnecting due to too many errors"
Dec 02 19:56:36 phev2mqtt phev2mqtt[1686]: time="2021-12-02T19:56:36+01:00" level=info msg="%PHEV_TCP_CONNECTED%"
Dec 02 20:01:59 phev2mqtt phev2mqtt[1686]: Short msg
Dec 02 20:02:03 phev2mqtt phev2mqtt[1686]: time="2021-12-02T20:02:03+01:00" level=error msg="Disconnecting due to too many errors"
Dec 02 20:02:04 phev2mqtt phev2mqtt[1686]: time="2021-12-02T20:02:04+01:00" level=info msg="%PHEV_TCP_CONNECTED%"

strict · December 5, 2021, 10:36am

Thanks for your reply. I don’t use HA I use another smart home system (Loxone with Loxberry), but have mqtt running. I tried to connect to my already running mqtt Mosquitto broker/server. Maybe that is the problem. I will try to make a second Mosquitto broker/server or use a docker container for HA, but as far as I have read, it uses an external Mosquitto broker/server as well, right?
Thanks, Michael

jampez77 · March 15, 2022, 8:55pm

I’m getting this error, did you ever find a solution?

My Github issue, for context:

github.com/buxtronix/phev2mqtt

Getting timed out waiting for start once connected.

opened 10:24AM - 24 Jan 22 UTC

jampez77

I have followed this installation guide, i think accurately from what I can tell…. I'm using a Raspberry Pi 3 Model B Rev 1.2 When I run the MQTT connection command I get the following response on the pi: ``` pi@raspberrypi:~ $ ./phev2mqtt-master/phev2mqtt client mqtt --mqtt_server tcp://192.168.1.101:1883/ --mqtt_username username --mqtt_password password INFO[0000] %PHEV_TCP_CONNECTED% ERRO[0020] timed out waiting for start INFO[0021] %PHEV_TCP_CONNECTED% ERRO[0041] timed out waiting for start ERRO[0172] dial tcp 192.168.8.46:8080: connect: connection timed out INFO[0173] %PHEV_TCP_CONNECTED% ``` The MQTT broker on HA shows the following related logs: ``` 1643018628: New client connected from 192.168.1.115 as phev2mqtt (p2, c1, k30, u'username'). 1643018742: Socket error on client phev2mqtt, disconnecting. ``` I've double checked my MQTT details and they're correct. I've also ran `iwconfig` and the WiFi is connected to the cars SSID. I've also spoofed the MAC Address of my mobile phone to the `wlan0` of the Pi. UPDATE: I've run the mqtt command with the `debug` tag: ``` INFO[0000] %PHEV_TCP_CONNECTED% DEBU[0000] %%PHEV_START_AWAIT%% DEBU[0001] %PHEV_TCP_RECV_MSG%: [00] START RECV18 (orig 5e0c0001619c8b691d04691501fc) DEBU[0001] %PHEV_TCP_SEND_MSG%: [00] START SEND (orig ) DEBU[0001] %PHEV_TCP_RECV_MSG%: [ae] REGISTER NTFY (reg 0x1d data 5e000003) DEBU[0001] %PHEV_TCP_RECV_MSG%: [a4] REGISTER NTFY (reg 0x1e data 0000) DEBU[0002] %PHEV_TCP_RECV_MSG%: [1d] REGISTER NTFY (reg 0x1f data 000000) DEBU[0002] %PHEV_TCP_RECV_MSG%: [e5] REGISTER NTFY (reg 0x21 data 00) DEBU[0003] %PHEV_TCP_RECV_MSG%: [a5] REGISTER NTFY (reg 0x22 data 000000000000) DEBU[0020] %%PHEV_START_TIMEOUT%% ERRO[0020] timed out waiting for start INFO[0021] %PHEV_TCP_CONNECTED% DEBU[0021] %%PHEV_START_AWAIT%% DEBU[0021] %%PHEV_TCP_READER_ERROR%%: EOF DEBU[0021] %PHEV_TCP_READER_CLOSE% DEBU[0041] %%PHEV_START_TIMEOUT%% ERRO[0041] timed out waiting for start INFO[0057] %PHEV_TCP_CONNECTED% DEBU[0057] %%PHEV_START_AWAIT%% DEBU[0058] %PHEV_TCP_RECV_MSG%: [00] START RECV18 (orig 5e0c0001507a3f5072b63f580184) DEBU[0058] %PHEV_TCP_SEND_MSG%: [00] START SEND (orig ) DEBU[0058] %PHEV_TCP_RECV_MSG%: [c4] REGISTER NTFY (reg 0xc0 data 30303630303330303030100100) DEBU[0059] %PHEV_TCP_RECV_MSG%: [15] REGISTER NTFY (reg 0x01 data 0102) DEBU[0060] %PHEV_TCP_RECV_MSG%: [0c] REGISTER NTFY (reg 0x02 data 02000000) DEBU[0060] %PHEV_TCP_RECV_MSG%: [6d] REGISTER NTFY (reg 0x03 data 011573) DEBU[0061] %PHEV_TCP_RECV_MSG%: [e8] REGISTER NTFY (reg 0x04 data 00ffff0300ffff0300ffff0300ffff0300ffff03) DEBU[0077] %%PHEV_START_TIMEOUT%% ERRO[0077] timed out waiting for start INFO[0078] %PHEV_TCP_CONNECTED% DEBU[0078] %%PHEV_START_AWAIT%% DEBU[0078] %%PHEV_TCP_READER_ERROR%%: EOF DEBU[0078] %PHEV_TCP_READER_CLOSE% ``` FURTHER UPDATE: I ran client watch and got this ``` INFO[0000] %PHEV_TCP_CONNECTED% panic: timed out waiting for start goroutine 1 [running]: github.com/buxtronix/phev2mqtt/cmd.Run(0x7871c0, {0xae8288, 0x0, 0x0}) /home/pi/phev2mqtt-master/cmd/watch.go:50 +0x520 github.com/spf13/cobra.(*Command).execute(0x7871c0, {0xae8288, 0x0, 0x0}) /home/pi/golib/pkg/mod/github.com/spf13/[email protected]/command.go:860 +0x644 github.com/spf13/cobra.(*Command).ExecuteC(0x786f30) /home/pi/golib/pkg/mod/github.com/spf13/[email protected]/command.go:974 +0x414 github.com/spf13/cobra.(*Command).Execute(...) /home/pi/golib/pkg/mod/github.com/spf13/[email protected]/command.go:902 github.com/buxtronix/phev2mqtt/cmd.Execute() /home/pi/phev2mqtt-master/cmd/root.go:55 +0x20 main.main() /home/pi/phev2mqtt-master/main.go:22 +0x14 ```

BunpGhost · March 16, 2022, 1:10pm

Hi @buxtronix.
I want to say that I have a PHEV’14 since 2019 and only recently I have found this work of yours.
After several hours I finally got it working with my HA.
I had several connections issues… what worked for me was getting my Pi closer to the Car

Congratulations on this and Thank you very much. I would like to help in any way I can. I’m not familiar with GO but I can give it try. If not that then for count with me for testing

I have a question:

What is the refresh rate of the client? I mean, how long between updates?

BunpGhost · March 16, 2022, 1:13pm

Do you still have this? What worked for me was not using brackets

Wouty · March 30, 2022, 1:21pm

Is this possible?
Reading the Mitsubishi with the same computer you run home assistant and MQTT broaker on?

And does someone have an easy way to integrate this in HA?
Something like a blueprint.

thnx.

cmmore · April 14, 2022, 10:16am

Hello.

Anyone have a YouTube movie for this?
Never done this and a newbi

BunpGhost · April 20, 2022, 2:14pm

Yes it is possible.
That is what I have.
I had to bring my raspberry closer to the PHEV in order for it to communicate correctly.

There is no easier way then the one mentioned in the github page of this component.
The author also shares a lovelace config yaml that helps to understand how view the data in HA.
It toke me a couple of hours to get it done.
There are still a couple of bugs but we have to have hope they will get fixed.

I created a daemon service on the pi, so that this “program” runs all the time and also starts at reboot.
I also created an HA restCommand so that I could restart this service in case of lost connection (it happens sometimes)
It could also help you

Good Luck,
Any questions, post here, we will try to answer

Wouty · May 2, 2022, 9:47am

I’m running on debian.
Is that also possible?

I’m not that good in programming, but will give it a try and probably wil have some questions again.

thnx.

BunpGhost · May 2, 2022, 2:52pm

I’m running debian also, so yes it is possible.
Setting up is also fun

Wouty · May 3, 2022, 10:58am

Do you have a how to install under debian?

BunpGhost · May 3, 2022, 1:54pm

Have you already tried the instructions in here: GitHub - buxtronix/phev2mqtt: Mitsubishi PHEV to MQTT gateway ??

JustGeus · May 3, 2022, 9:44pm

Is your climate also working?

JustGeus · May 3, 2022, 9:53pm

Did you find a way to use this?

Wouty · May 4, 2022, 5:16pm

I’m stuck on * Download the phev2mqtt archive
Where do i download it, i can’t find it in the Github?