On what device are u trying to install it? I have it on a pi zero w with a eth0 hat.
Iām installing on a dell wise.
My homeassistant is also running on it.
Iām running under debian.
I think u have to install it in a container, thats why I choose for a extra device. I dont know anything about containers, sorry
No, the climate is not yet supported!
if you want to run it in the same homeassistant machine you have 2 options:
1 - using the addon (but I donāt know if that is working)
2 - having access to the OS of the machine to compile and run the program. This means that you canāt use HomeassistantOS but rather have supervised install insteadā¦ If you have HomeassistantOS then my best advice is to run this program on a separate machine 
I have added instructions in the top level README for how to setup on Raspbian such that it starts on boot. Feel free to send suggestions or PRs to improve the instructions.
U know why? I have user some sniffers to see what the car communicating to the app. But the climate messages are always different 
Great!
Btw, any idea why, if we only restart HASS, the communcation stops? Is ti the mqtt part that canāt reconnect?
when this happens a double restart to phev2mqtt makes it work again!
I have no ideaā¦
Havenāt setup the sniffing part yetā¦
Has anyone had any issues with some entities being orphaned?
The front door entities used to be fine but now appear as unavailable. Iām hoping this is a common problem thatās easily fixed.
Also the climate stuff is unresponsive too.
They were changed recently to use a different mqtt topic as left/right hand drive vehicles differ.
front_left_door is now front_passenger
front_right_door is now driver
You may need to update your dashboard to reflect this.
1 Like
Ahh, right you are. Thatās sorted it! Thanks
R.E the climate, is it expected behaviour for nothing to update when changing / setting it to heat / cool / windscreen? Iāve tried with the dropdown and the switches.
The climate messages are coded and u have to use a sniffer to find the commands. I think the commands use a timestamp but untill now, cant find out how there build.
Oh, are you sure about that?
The way the documentation read I would have thought those commands already work.
I think it depends from wich year the phev is. Mine is from 2015.
All the climate function are nog working with this intergration. But with the Outlander app i can use the climate. I have tried to use a sniffer. But the pcap files are not clear to me.
1 Like
Is it possible to add an entity to HA that simply reports if PHEV2MQTT is connected. Right now all entities are unavailable when the car isnāt connect or if there is a problem with the project.
I think a binary sensor that indicates if the project is online and connected to MQTT would help with determining if I actually need to initiate a reboot.
I see alot of BAD ENCODING in the verbose logging. My car is MY22 I think (or MY21). It goes like this for miles:
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [f9] REGISTER NTFY (reg 0x1d data 5e000103)"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_SEND_MSG%: [f9] REGISTER ACK (reg 0x1d data 00)"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [27] Cmd: 0xcc () (len 6), Register 0xf1, Data: fe"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [27] BAD ENCODING (exp: 0x61)"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [27] REGISTER NTFY (reg 0x24 data 01000000000000000001)"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_SEND_MSG%: [27] REGISTER ACK (reg 0x24 data 00)"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [fe] Cmd: 0xcc () (len 6), Register 0xb0, Data: 61"
time="2022-07-25T09:54:22+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [fe] BAD ENCODING (exp: 0x79)"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [fe] REGISTER NTFY (reg 0x16 data 02161ed701d80100)"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_SEND_MSG%: [fe] REGISTER ACK (reg 0x16 data 00)"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [61] Cmd: 0xcc () (len 6), Register 0x71, Data: 79"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [61] BAD ENCODING (exp: 0x26)"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [61] REGISTER NTFY (reg 0x1d data 5e000103)"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_SEND_MSG%: [61] REGISTER ACK (reg 0x1d data 00)"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [79] Cmd: 0xcc () (len 6), Register 0xb1, Data: 26"
time="2022-07-25T09:54:23+03:00" level=debug msg="%PHEV_TCP_RECV_MSG%: [79] BAD ENCODING (exp: 0xe1)"
Iām going to check the code on my vacation . Iāve never viewed nor developed Go, but how hard can it be 
Did anybody create an addon for this yet?
1 Like
Hello,
I tried the program with the Mitsubishi Eclipse Cross PHEV - the connection to the hotspot works, PING to 192.168.8.46 also works.
pi@phev:~/phev2mqtt $ ./phev2mqtt client watch
INFO[0000] %PHEV_TCP_CONNECTED%
ERRO[0000] %PHEV_TCP_WRITER_ERROR%: write tcp 192.168.8.48:43522->192.168.8.46:8080: use of closed network connection
panic: timed out waiting for start
goroutine 1 [running]:
github.com/buxtronix/phev2mqtt/cmd.Run(0x84aaa0, {0xbac84c, 0x0, 0x0})
/home/pi/phev2mqtt/cmd/watch.go:50 +0x554
github.com/spf13/cobra.(*Command).execute(0x84aaa0, {0xbac84c, 0x0, 0x0})
/home/pi/go/pkg/mod/github.com/spf13/[email protected]/command.go:860 +0x688
github.com/spf13/cobra.(*Command).ExecuteC(0x84b398)
/home/pi/go/pkg/mod/github.com/spf13/[email protected]/command.go:974 +0x40c
github.com/spf13/cobra.(*Command).Execute(...)
/home/pi/go/pkg/mod/github.com/spf13/[email protected]/command.go:902
github.com/buxtronix/phev2mqtt/cmd.Execute()
/home/pi/phev2mqtt/cmd/root.go:61 +0x20
main.main()
/home/pi/phev2mqtt/main.go:22 +0x14
Obviously, the Eclipse Cross protocol has changed so that communication does not work.
Maybe you can make appropriate changes for the vehicle based on the existing software.
Best regards
Michael