Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to interpret: weconnect/0/vehicles/xxxxx/domains/charging/chargingSettings/maxChargeCurrentAC : msg.payload : string[0] #385

Open
Domoberry opened this issue Jan 13, 2025 · 2 comments

Comments

@Domoberry
Copy link

Hi Forum,

I'm using some Node-RED flows as glue-logic between WeConnect-mqtt and Domoticz. I have noted in some cases an incoming value (payload) which I did not yet anticipate.

Example: weconnect/0/vehicles/xxxxx/domains/charging/chargingSettings/maxChargeCurrentAC
This typically has values 'reduced' or 'maximum', indicating the maximum charge rate (it is a writable topic as well).
However, I have recently noted that the received payload of the this mqtt message can temprary be 'empty', e.g. 'string[0]' as well.

How should I handle this? Or, what is the meaning of this empty mesage?
(perhaps the overarching question is: does an overview of all weconnect-mqtt topics and there possible/allowed values exists somewhere?)

@tillsteinbach
Copy link
Owner

An empty payload is indicating that the topic should be deleted. This happens when the property is not present in the message from the VW server anymore.

@Domoberry
Copy link
Author

Thanks for the reply.
Per today, the same topic provides its normal values again. This 'empty' message happened few times, one time I captured the actual source message (string[0]) from weconnect, two other times I was not able to trace it back to the actual message from weconnect (not aware of logging there), my nodeRED translates anything other than the two known messages into 'unknown value' :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants