no more mqtt messages coming in - suggestions appreciated

[Domoberry]

Dear Forum,
I’m setting up weconnect-mqtt for my ID.3 on Domoticz, using Node-RED in between and Mosquitto as mqtt broker. All is running on an RPI4. On my PC. I’m using mqtt.fx as monitoring tool. First results were encouraging. I received data every 300 secs on subscribed topics like SoC, Remaining Range, Charge Power and alike. All correctly showing up in Domoticz. Also, using write-topics, able to set target-SoC and Reduce Charge Current using the related write-topics.
However, around mid December, no more updates are coming in and similarly setting Target SoC or Reduced Charge Current fails. The only topic that currently arrives every 300 secs is weconnect/0/mqtt/weconnectUpdated. This is consistent with what I see in the mqtt.fx monitoring tool. On accasion I noted a parking position (lon/lat/timestamp) coming in. Once with correct coordinates, once without coordinates.
I have tried restarting, ensuring latest versions of weconnect-python (0.59.5) and weconnect-mqtt (0.48.3), etc. I must have missed something or changed something unintentionally (I added a user in the ID.3 and removed it again later).
Any tips, for example on:

• Suggestion on what to check or were to look? Log-files? Install and try with weconnect-cli?
• Any pre-requirements on settings in the car itself? S-Pin? Reset the ID.3?
• A recommended ‘round-trip’ sequence I could use for testing (e.g. publish to write-topic ABC payload PQR then expect to receive a reply on topic DEF a payload XYZ)

would be appreciated to figure out were I made a mistake.
Thanks in advance.

Update: in the meantime, I have reset the ID3 to factory defaults and reconnected it to the services and mobile app, new spin, etc. Received a correct location and topic list and the regular weconnect/0/mqtt/weconnectUpdated timestamps, yet not information like SoC, range, etc.

[Domoberry]

Update: I have installed weconnect-cli on a separate RPI3b. With this command line tool, I'm able to retrieve information, including current SoC, which does not show up anymore in my weconnect-mqtt setup:

`pi@rpi3Lite64:~ $ weconnect-cli --username [email protected] --password 1234567890 shell
Welcome! Type ? to list commands
xxx@yyyyy.zzz@weconnect-sh:/$cd /vehicles/WVWxxxxxxxxxxxxxx/domains/charging/batteryStatus/currentSOC_pct
xxx@yyyyy.zzz@weconnect-sh:/vehicles/WVWxxxxxxxxxxxxxx/domains/charging/batteryStatus/currentSOC_pct$cat

78`

So, there seems nothing wrong between the car and the weconnect server to weconnect-cli. I must have messed up something with my weconnect-mqtt setup, which stops it from reporting SoC (among others) yet continues to provide update timestamps.

[Domoberry]

Update: after succesfully obtianing information from my ID3 using weconnect-cli on a separate RPI3, focussed on the failing RPI4 setup. Careful conclusion is that I had managed to create a weconnect-mqtt.service file to start weconnect-mqtt as a service, which in some way conflicted with the .netrc file. Strictly adhering to suggestions made in this Github repository (always a good idea :-)) created a working setup again.
I added the --verbose option and noticed some repeating warnings (which I also noted using weconnect-cli). In case someone has more insights, your feedback would be appraciated! See below:

weconnect-mqtt.service - WeConnect-mqtt
Loaded: loaded (/etc/systemd/system/weconnect-mqtt.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-01-10 14:12:19 CET; 1h 10min ago
Main PID: 770 (python)
Tasks: 2 (limit: 3933)
CPU: 3.270s
CGroup: /system.slice/weconnect-mqtt.service
└─770 /usr/bin/python -m weconnect_mqtt --username [email protected] --password ppppppppp --mqttbroker 192.168.0.179 --no-capabilities --convert-times Europe/Berlin --verbose

Jan 10 15:14:12 rpi4domoticz python[770]: 2024-01-10T15:14:12+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute repetitionDays with value ['tuesday', 'thursday']
Jan 10 15:14:12 rpi4domoticz python[770]: 2024-01-10T15:14:12+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/climatisationTimers/climatisationTimersStatus/timers/2/singleTimer: Unknown attribute targetDateTime with value 1999-12-31T23:00:00Z
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/automation/climatisationTimer/timers/1/recurringTimer: Unknown attribute targetTime with value 06:00
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/automation/climatisationTimer/timers/1/recurringTimer: Unknown attribute repetitionDays with value ['tuesday', 'thursday']
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/automation/climatisationTimer/timers/2/singleTimer: Unknown attribute targetDateTime with value 1999-12-31T23:00:00Z
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:generic_status:/vehicles/WVWvvvvvvvvvvvvvv/domains/automation/chargingProfiles: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'invalid'}
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:generic_status:/vehicles/WVWvvvvvvvvvvvvvv/domains/chargingProfiles/chargingProfilesStatus: Unknown attribute nextChargingTimer with value {'id': 0, 'targetSOCreachable': 'invalid'}
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute targetTime with value 06:00
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/climatisationTimers/climatisationTimersStatus/timers/1/recurringTimer: Unknown attribute repetitionDays with value ['tuesday', 'thursday']
Jan 10 15:19:27 rpi4domoticz python[770]: 2024-01-10T15:19:27+0100:WARNING:timer:/vehicles/WVWvvvvvvvvvvvvvv/domains/climatisationTimers/climatisationTimersStatus/timers/2/singleTimer: Unknown attribute targetDateTime with value 1999-12-31T23:00:00Z
~