Replies: 2 comments 2 replies
-
Hi Sandor, Thank you for your kind words and interest in the project! Currently, the software does support setting the default system output power and configuring charging/discharge limits, so those aspects of battery management are indeed possible through the existing implementation. To do this send a MQTT message to
If you want to change the upper charging or lower discharge limit you have to include both, {
"output_power_w": 500
} Keep im mind, if you have set a schedule, it will always overwrite the default system output power. However, setting the operation mode of the battery is a bit more complex. As of now, it's only possible to set the operation mode by configuring a schedule, but unfortunately, the feature to set schedules is not yet supported in the software. Regarding your question about intercepting HTTP calls made by the app, yes, that is one of the methods used to understand and replicate the communication between the app and the battery system. I hope this answers your questions! If you have any more suggestions or need further assistance, feel free to ask. Best regards, |
Beta Was this translation helpful? Give feedback.
-
I also wanted to thank you for the great software. Picking up the discussion from a year ago. Is there any plan for the future to implement the setting of operation mode using schedules? |
Beta Was this translation helpful? Give feedback.
-
Hi Markus,
this is really great projekt!
What do you think? Is is possible to implement sending configuration to the battery (change operation modes of the battery, standard power output, etc) via your SW?
are you somehow intercepting the http calls made by the APP?
Thanks,
Regards,
Sandor
Beta Was this translation helpful? Give feedback.
All reactions