-
Notifications
You must be signed in to change notification settings - Fork 10
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
Decoding of payload for tag TAG_WB_EXTERN_DATA_ALG #100
Comments
It would be interesting what firmware version is on your E3DC and Wallbox. |
I'm currently running S10_2022_022 on the S10. |
To my knowledge, our E3/DC WB is connected via some sort of (S?)bus to the S10 system. I'm not aware that it has its own IP address. |
The decoding of the tag |
I can confirm that we have an E3/DC original wallbox installed but it's a rather old pre-Easy Connect wallbox (installed in 2016). |
Thanks for supplying information about your installation. Yet I am a bit frustrated that an original E3/DC wallbox seems to deliver data not matching the tag list documentation. Currently, I have no idea how to solve this cleanly, unless it turns out that all E3/DC wallboxes - or at least a clearly defined subset - behave like your model. Please refer to the official E3/DC tag list provided with the sample application. I do not want to post it here due to copyright considerations. Note that the tag list is not complete, not up-to-date, and, obviously, also not correct in every detail. |
By doing some experiments with my S10 system and the E3/DC Wallbox I figured out that the decoding of the tag
TAG_WB_EXTERN_DATA_ALG
as specified inRscpTags.json
is probably wrong.I observed the following mapping of the
EXTERN_DATA
payload:(Byte 1: uint8, PreCharge in [%])
Byte 2: uint8, Anzahl akt. Phasen [0-3]
Byte 3: uint8, 0x10 : Auto lädt, 0x20: Type2 verriegelt
Byte 4: uint8, Ladestrom [A]
Byte 5: uint8, 0x40: Sonnenmode, 0x00: Mischbetrieb
(Byte 6: uint4 low, 1: Schuko belegt / uint4 high, 1: Schuko an)
(Could not verify the mapping for the bytes in brackets)
This might be relevant if this decoding is or will be available in the ioBroker (which I can't tell).
The text was updated successfully, but these errors were encountered: