Open mabunixda opened 9 months ago
you can send this message:
{"type":"requestFullStatus"}
Thanks ... having problems on the actual evcc implementation of the wattpilot implementations that if the car stops the charging process, some updates seem not to be send ( or are not processed correctly ).
alw
just tells if the car is allowed to charge, but is there any other flag known if the car is actual still charging ( except making a code descission if any power is on the cable ) ?
@peterpoetzi
Is there a way to send this message through the mqtt topics, like using .../messages/send/... or something? Somehow the last "fullStatus" I received is months old, maybe Fronius changed the system here, or for whatever reason it is not send automatically anymore.
Wattpilotshell itself seems to receive it properly, it "knows" the car state, when the shell is started after the car was connected.
However, it is not exported on mqtt it seems. Maybe it is received and processed before the mqtt connection is established. (Set env variable MQTT_MESSAGES to "fullStatus deltaStatus" to no success)
At least the order of log entries seems to indicate that wattpilot connection is made before Mqtt is setup:
INFO:wattpilot:Wattpilot None initialized
INFO:wattpilot.wattpilotshell:Automatically connecting to Wattpilot ...
INFO:wattpilot:Wattpilot connected
INFO:websocket:Websocket connected
INFO:wattpilot:Connected to WattPilot Serial xxxxxxxxxxxxx
INFO:wattpilot:Authentication successful
INFO:wattpilot.wattpilotshell:Connecting to MQTT host mqtt.ad.xxxxxxxx.de on port 1883 ...
Is there any known implementation to force a fullStatus message?