Replies: 3 comments 13 replies
-
is it always the case that no data is coming? Can you check with WeConnect-cli if data is coming? |
Beta Was this translation helpful? Give feedback.
9 replies
-
I fixed the python issues. ping heise.de works fine, so probably not a network problem I reinstalled requests and urllib3 but with no succes.
|
Beta Was this translation helpful? Give feedback.
3 replies
-
I was sure I had done an upgrade when installing, so was surprised the version was not good.Good you have the insight in version management.MQTT control messages don't work with my car. But they do work with weconnect-cli. So not realy a problem.As a little positive feedback for what I am using your applications for. We have a solar and wind powered house. With the coming of an electric car and a heat pump energy management is very important. I build an home automation system in Node Red. Most electricity intense appliances are monitored and controlled so we can use as much electricity we produce ourselves.With weconnect-mqtt/cli the charging power for tje car can be changed or pauzed. So I don't need to install an expensive dynamic charging station.With a smart household we can make the world a bit better.Verzonden vanaf mijn Galaxy
-------- Oorspronkelijk bericht --------Van: Till Steinbach ***@***.***> Datum: 6/09/2023 22:48 (GMT+01:00) Aan: tillsteinbach/WeConnect-mqtt ***@***.***> Cc: dwindey1 ***@***.***>, Author ***@***.***> Onderwerp: Re: [tillsteinbach/WeConnect-mqtt] connection error (Discussion #249)
You are welcome! I now understand what happened. When you had python 3.7 pip downloaded the last version that was available with 3.7 support. But that version is not working anymore with the VW servers.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have logged in with this command
weconnect-mqtt --username xxxx@xxxl.com --password mysecretpas --mqttbroker 192.168.0.156 --prefix weconnect&
in MQTT there are first 6 or 7 messages at startup. One of them is weconnectconnected with payload true
Then at an interval of 5 minutes 2 error messages arrive
error/code with payload -6
error/message with payload "Retrieval error during update. Will try again after configured interval of 300s"
When retrieving the journalctl it looks like weConnect-mqtt stopped ?
pi@theone:~ $ journalctl -u weconnect-mqtt
-- Logs begin at Sat 2023-09-02 13:30:33 CEST, end at Sat 2023-09-02 21:32:50 CE
Sep 02 21:20:14 theone systemd[1]: Stopping WeConnect-mqtt...
Sep 02 21:20:14 theone systemd[1]: weconnect-mqtt.service: Main process exited,
Sep 02 21:20:14 theone systemd[1]: weconnect-mqtt.service: Succeeded.
Sep 02 21:20:14 theone systemd[1]: Stopped WeConnect-mqtt.
I also tried to send a write message without result. And also no trace (that I know of) that is has been send to the server.
weconnect/0/vehicles/WVGZZZE20PP0xxxx/controls/climatisation with payload start
I also had the program running from systemd.
There it is active, but with the same error code and message in MQTT
lines 1-9/9 (END)...skipping...
● weconnect-mqtt.service - WeConnect-mqtt
Loaded: loaded (/etc/systemd/system/weconnect-mqtt.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2023-09-02 21:49:08 CEST; 9h ago
Main PID: 22237 (python3)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/weconnect-mqtt.service
└─22237 /usr/bin/python3 -m weconnect_mqtt --username xxx@xxx.com --password mypassword --mqttbroker 192.168.0.156 --prefix weconnect --republish-on-update
Any ideas ?
Beta Was this translation helpful? Give feedback.
All reactions