phev-remote / phevctl Goto Github PK

Hello,
When building the Docker image on the Raspberry, the following error message appears:

`Step 8/13 : RUN cd /src/phevcore && mkdir build && cd build && cmake .. && make && make install
---> Running in e8f1923886ab
-- The C compiler identification is GNU 11.3.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
CMake Error at CMakeLists.txt:3 (include):
include could not find requested file:

splint.cmake

CMake Error at CMakeLists.txt:38 (add_splint):
Unknown CMake command "add_splint".

-- Configuring incomplete, errors occurred!
See also "/src/phevcore/build/CMakeFiles/CMakeOutput.log".
The command '/bin/sh -c cd /src/phevcore && mkdir build && cd build && cmake .. && make && make install' returned a non-zero code: 1`

Unfortunately I can't do anything with this.
greeting
Michael

Phevctl works good for me, at least when the connection is ok. But when I been away with the car and gets home again, the connection is lost. When I run phevctl commands there is no respons, it just reads "Wait...".
Does anyone has any idea how to fix this? "/etc/init.d/networking restart" or "wlan0 down && wlan0 up" doesn't work.

Using phevctl to set the aircon mode (heating/cooling/windshield) works fine, but regardless of whether I set 10, 20 or 30 minutes for the duration, my car (MY15) seems to stop after 10 minutes.

After some hours of fiddling with the registration of my MY15, I discovered that for the register command to actually perform a registration, the WiFi MAC address must be provided as an option.

My suggestion is to make this option mandatory when phevctl register is invoked; other commands still seem to work fine without the MAC option.

I need to build it as I anned to run on a reapsberry using ARM

I get build error
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
ARGP_LIB
linked by target "phevctl" in directory /home/pi/test/phevbuild/external/phevctl

I have no clue on how to proceed

First off, great work!

Do you know if it is possible to turn on the heater or perhaps enable AC with some temperature?

Step 10/12 : RUN mkdir -p build && cd build && cmake .. && make
---> Running in e62222329c13
-- The C compiler identification is GNU 8.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /src/phevctl/build
Scanning dependencies of target phevctl
[ 50%] Building C object CMakeFiles/phevctl.dir/main.c.o
/src/phevctl/main.c: In function 'main_eventHandler':
/src/phevctl/main.c:280:14: error: 'PHEV_START' undeclared (first use in this function); did you mean 'PHEV_STARTED'?
case PHEV_START:
^~~~~~~~~~
PHEV_STARTED
/src/phevctl/main.c:280:14: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [CMakeFiles/phevctl.dir/build.make:63: CMakeFiles/phevctl.dir/main.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:73: CMakeFiles/phevctl.dir/all] Error 2
make: *** [Makefile:84: all] Error 2
The command '/bin/sh -c mkdir -p build && cd build && cmake .. && make' returned a non-zero code: 2

docker version
Client: Docker Engine - Community
Version: 19.03.1
API version: 1.40
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:32:16 2019
OS/Arch: linux/arm
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.1
API version: 1.40 (minimum version 1.12)
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:26:16 2019
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.2.6
GitCommit: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
runc:
Version: 1.0.0-rc8
GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f
docker-init:
Version: 0.18.0
GitCommit: fec3683

I am unable to complete the register step on my MY18. phevctl does connect to to car as it is able to fetch the VIN and other data, but then nothing happens. I tried setting msg-core/logger.h log level to debug, but seems I can't get debug from phevcore. Here's what I have:
out.log

MY2019 PHEV will not heat once the car door is opened while the heating is on. After this phevctl aircon on -command will result to "Operation successful" message but the heater is not turned on.

The heater will start to work again only by opening the official "Remote ctrl" app and confirming the message pop ups for "heating was cancelled because of opening doors...".

I tried to use phevctl monitor -command and see if this would affect same way but without success.

Any ideas could I run some command with phevctl which would confirm this "error" and allow heating again?

Cheers for great work on this. It has made my PHEV AC control truly remote. I'm running this on android -phone with termux and ubuntu installed on it and I trigger the phevctl scripts with Tasker by sending SMS or by home automation MQTT -messages. Thank you!

I have a raspberry pi configured to connect to my laptop over SSH on the raspberry pi's ethernet port and a wireless adapter on the raspberry pi connecting to the vehicle on the correct IP address. I am using the -m command to spoof the same MAC address as my vehicle registered android device.

I have enabled verbose logging in the msg-core and this is the following output when running phevctl, any ideas what could be causing the issue.

pi@raspberrypi:~/automate/Outlander/phevctl/build $ ./phevctl -m 92:a6:82:d3:e7:7c battery
Mitsubishi Outlander PHEV Remote CLI - Designed and coded by Jamie Nuttall 2020
MIT License

Type 'x' then enter to quit.
DEBUG - MSG_CORE: Setting incoming handler to 0x15d04
DEBUG - MSG_CORE: Setting ougoing handler to 0x15ce0
DEBUG - MSG_CORE: Setting incoming handler to 0x229f4
DEBUG - MSG_CORE: Setting ougoing handler to 0x22b18
VERBOSE - MSG_PIPE: START pipe
DEBUG - MSG_PIPE: Calling inbound subscribe
DEBUG - MSG_PIPE: Addr of subscribe 0x20b08
DEBUG - MSG_PIPE: Calling outbound subscribe
DEBUG - MSG_PIPE: Calling input start
DEBUG - MSG_PIPE: Calling input connect
VERBOSE - MSG_PIPE: START - in connect
VERBOSE - MSG_PIPE: Calling in connect 0x207b8
VERBOSE - MSG_PIPE: END - in connect
DEBUG - MSG_PIPE: Calling output start
DEBUG - MSG_PIPE: Calling output connect
VERBOSE - MSG_PIPE: START - out connect
VERBOSE - MSG_PIPE: Calling out connect 0x228b8
VERBOSE - MSG_TCPIP: START - connect
DEBUG - MSG_TCPIP: Context Host 192.168.8.46 Port 8080
ERROR - MSG_TCPIP: Failed to connected to server : -1
VERBOSE - MSG_TCPIP: END - connect
VERBOSE - MSG_PIPE: END - out connect
VERBOSE - MSG_PIPE: END - pipe
Starting *main_thread ...
VERBOSE - MSG_PIPE: START - out connect
VERBOSE - MSG_PIPE: Calling out connect 0x228b8
VERBOSE - MSG_TCPIP: START - connect
DEBUG - MSG_TCPIP: Context Host 192.168.8.46 Port 8080
ERROR - MSG_TCPIP: Failed to connected to server : -1
VERBOSE - MSG_TCPIP: END - connect
VERBOSE - MSG_PIPE: END - out connect
VERBOSE - MSG_PIPE: START - out connect
VERBOSE - MSG_PIPE: Calling out connect 0x228b8
VERBOSE - MSG_TCPIP: START - connect
DEBUG - MSG_TCPIP: Context Host 192.168.8.46 Port 8080
ERROR - MSG_TCPIP: Failed to connected to server : -1
VERBOSE - MSG_TCPIP: END - connect
VERBOSE - MSG_PIPE: END - out connect
VERBOSE - MSG_PIPE: START - out connect
VERBOSE - MSG_PIPE: Calling out connect 0x228b8
VERBOSE - MSG_TCPIP: START - connect
DEBUG - MSG_TCPIP: Context Host 192.168.8.46 Port 8080

I started to look into the protocol and could need some help with logs to find the nasty details of the currently unknown XOR algorithm and registration process - I've posted all the details at buxtronix/phev2mqtt#16 maybe someone want's to join...