Get Data via MQTT

[Werner1000]

WICAN works fine with Car Scanner App via BT and WIFI, so I was able to collect the SoC PID for my VW E-UP via the logging function on MQTT:
wican/xxxxxxxxxxxx/elm327 {"bus":"0","type":"tx","ts":35144,"frame":[{"id":2016,"dlc":8,"rtr":false,"extd":false,"data":[3,34,22,24,170,170,170,170]}]}
wican/xxxxxxxxxxxx/elm327 {"bus":"0","type":"rx","ts":35146,"frame":[{"id":2024,"dlc":8,"rtr":false,"extd":false,"data":[5,98,22,24,37,88,85,85]}]}

To request the SoC via MQTT I sent this request:
mosquitto_pub -h 192.168.xx.x -p 1883 -u wican -P wican -t wican/xxxxxxxxxxxx/can/tx -m "{"bus":"0","type":"tx","frame":[{"id":2016,"dlc":8,"rtr":false,"extd":false,"data":[3,34,22,24,170,170,170,170]}]}"

There is absolutely no reponse from the WICAN, even if I try several proposals / different PIDs available from different online-sources. My WICAN is functional connected to my MQTT Broker, the ONLINE- and OFFLINE messages are published as the logging-functions. WICAN SW-Version is the actual 3.28.

Any ideas whats wrong with my approach? Any hints are welcome!
Best regards
Werner

[cr0i]

WICAN works fine with Car Scanner App via BT and WIFI, so I was able to collect the SoC PID for my VW E-UP via the logging function on MQTT: wican/xxxxxxxxxxxx/elm327 {"bus":"0","type":"tx","ts":35144,"frame":[{"id":2016,"dlc":8,"rtr":false,"extd":false,"data":[3,34,22,24,170,170,170,170]}]} wican/xxxxxxxxxxxx/elm327 {"bus":"0","type":"rx","ts":35146,"frame":[{"id":2024,"dlc":8,"rtr":false,"extd":false,"data":[5,98,22,24,37,88,85,85]}]}

To request the SoC via MQTT I sent this request: mosquitto_pub -h 192.168.xx.x -p 1883 -u wican -P wican -t wican/xxxxxxxxxxxx/can/tx -m "{"bus":"0","type":"tx","frame":[{"id":2016,"dlc":8,"rtr":false,"extd":false,"data":[3,34,22,24,170,170,170,170]}]}"

There is absolutely no reponse from the WICAN, even if I try several proposals / different PIDs available from different online-sources. My WICAN is functional connected to my MQTT Broker, the ONLINE- and OFFLINE messages are published as the logging-functions. WICAN SW-Version is the actual 3.28.

Any ideas whats wrong with my approach? Any hints are welcome! Best regards Werner

Elm Logging must be disabled again.
Perhaps you can try with ignition on?
That was a problem as I tried the first times, but without HA.

[meatpiHQ]

@Werner1000 I've just created a vehicle profile for e-up, please update to the latest firmware and try it

https://github.com/meatpiHQ/wican-fw/releases
https://github.com/meatpiHQ/wican-fw?tab=readme-ov-file#getting-started-guide

[Werner1000]

Just updated to 3.30 plus new profile, made automation settings and - magic - two PIDs are automatically published via MQTT:
wican/xxxxxxxxxx/can/rx {"bus":"0","type":"rx","ts":203,"frame":[{"id":2029,"dlc":8,"rtr":false,"extd":false,"data":[6,65,0,152,24,0,1,170]}]}
wican/xxxxxxxxxx/can/rx {"bus":"0","type":"rx","ts":206,"frame":[{"id":2024,"dlc":8,"rtr":false,"extd":false,"data":[6,65,0,128,8,0,17,0]}]}
Exactly what I'm looking for.

PID 2029 is continueously published, even after switching off the ignition, PID 2024 only when ignition is switched on.

Was not shure about automation settings, with these ones it worked well for me:

Based on this I will continue to implement it to my environment.
Thanks guys!

[meatpiHQ]

@Werner1000 you should receive the SoC value in this format {"SOC": "xx"}

The profile is only sending one parameter, where is the other one coming from? Do you have a custom PID?

[Werner1000]

Sad to say, seems to have been a dayfly yesterday. meatpi was switched off overnight, today same procedure as before with ver 2.98.: Only 2 MQTT-messages came when reboot/start ('MQTT elm327 log' disabled) - nothing else:
wican/xxxxxxxxxxxx/can/status {"status": "offline"}
wican/xxxxxxxxxxxx/can/status {"status": "online"}

and if MQTT elm327 log is enabled and Car Scanner is active:
wican/xxxxxxxxxxx/elm327 {"bus":"0","type":"rx","ts":20961,"frame":[{"id":2029,"dlc":8,"rtr":false,"extd":false,"data":[6,65,64,224,128,0,0,170]}]}
wican/xxxxxxxxxxx/elm327 {"bus":"0","type":"rx","ts":20965,"frame":[{"id":2024,"dlc":8,"rtr":false,"extd":false,"data":[6,65,64,196,195,128,33,0]}]}
wican/xxxxxxxxxxx/elm327 {"bus":"0","type":"tx","ts":21596,"frame":[{"id":2015,"dlc":8,"rtr":false,"extd":false,"data":[2,1,96,170,170,170,170,170]}]}

2 questions to the 'Automate' settings:

• is 'Destination Topic:' in automate settings the full MQTT topic or only an addition to the general MQTT-settings?
• for pure MQTT-publishing without HA usage is 'Home Assistant Discovery:' disabled sufficiant?

Do I have any possibilty to get more detailed logs ?

Best regards
Werner

[cr0i]

With Automate Settings it seems to be necessary that the Initialisation string sets the Header (ID) for the Request/Response.
Because in the moment only one Initialisation string is possible I only can get one value published.
I was wondering, why you could store the settings without Destination Topic, it was mandatory at me.
When you use Automate (With AutoPID Protokoll), then you don´t send the tx frame from your system, the wican publishes the MQTT Topic itself.

Based on my Init String, try changing yours in the car Profile to something like that:
ATSP6;ATST96;ATSH7E5;ATCP18;ATCRA7ED;ATFCSH7E5;ATFCSD300000;ATFCSM1;
(I´m not sure if all are compatible at you, but I think important would be: ATSH7E5;ATCRA7ED;ATFCSH7E5;)
Then give an Destination Topic, under this topic should a new topic SOC be published if Protokoll changed to AutoPID and the wican is rebooted.
So I got it working.

[meatpiHQ]

@Werner1000 what firmware version are you running?

[Werner1000]

Again thanks to you both, now it looks good. I get these MQTT-Messages at v3.30 (hopefully permanently...)

wican/xxxxxxxxxx/can/rx {"bus":"0","type":"rx","ts":40414,"frame":[{"id":2029,"dlc":8,"rtr":false,"extd":false,"data":[4,98,2,140,233,170,170,170]}]}
wican/xxxxxxxxxx/can/SoC {"SOC":93.2}

Only these two adaptions have been made at my side, no need for the proposals from cr0i. Everything works as default.

• Change the Settings/Protocol from elm327 to Autopid (my error, read the f... manual). Consequence: Car Scanner needs elm327, has to be changed when in use.
• add the full MQTT topic at Automate/destination Topic: wican/xxxxxxxxx/can/SoC, otherwise it will publish to complete different topic out of my focus. Proposal for future versions: why not use default values similar to these at Settings/MQTT?
• and of cause: disable Settings/elm327 logging

[meatpiHQ]

@Werner1000 alright so we can say that E-Up profile works.

Proposal for future versions: why not use default values similar to these at Settings/MQTT?

if you leave destination empty, where does it publish? It's suppose to send to the default topic if left empty.

[Werner1000]

Yes, for me E-Up profile now works. I emptied Automate/Destination path and now it publishes as you desripted along settings/MQTT . wican/xxxxxxxxxxxx/can/SoC {"SOC":95.6}
Thats fine, maybe note it somewhere visible - it was not clear to me what's needed.

Remark: calculated SoC is too low: Real 100% SoC is published as 95,6%. Not a problem for me, I multiply the value with 1,046 and thats sufficiant for me.