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
[1.9.x] - MaxPriceForCharging (awattar) should use "config / get" and "config / set" mqtt paths #2803
Comments
All topics are separated in to |
Found this issue exactly for the same purpose: Feed a new max price threshold to the openWB. So I guess it's up to someone creating a pull request? Unfortunately I have no experience at all (incl. OpenWB ruleset) on how to extend and modify the MQTT structure Setting the existing topic via MQTT is shown in the display / OpenWB front end, but is overwritten to the previous value shortly after EDIT: Maybe I am writing nonsense here - I guess I have to first activate the MQTT bridge bidirectionally? |
@ChristophCaina Enabling TLS for Mosquito on Home Assistant side seems to be an endeavor in itself. Can you confirm, that the openWB initiated bridge and "enable external control" will allow to modify the max charging price? Or can I save the effort, as it's not working anyway? |
Sorry, I can't confirm this. I haven't continued to try the above Information since I don't use this Feature by myself and didn't had the time to Work on the Integration |
Thanks, but I am highly confused right now anyway... Somehow I found a way to set the MaxPriceForCharging, but didn't find the option before in the MQTT Exporer. This one works just using the always on MQTT server of the wallbox: openWB/set/awattar/MaxPriceForCharging |
ok - now I could have a look into the whole thing again. the problem here is, that the SET Topic has a different structure / path. For example, here's the code to Send a number to the OpenWB and get it:
but it would require a complete change of this code to catch, if you want to set a new value for the awattar price... I would need to read the while all other relevant changes would still use the same I might be able to adapt this - but the idea was, that the openWB should use a 'standard' for everything ... |
This is in fact the standard for openWB. In |
When you enable the Price based charging in your Wallbox, you can set the 'MaxPriceForCharging' from the Display.
The topic for this is:
openWB/global/awattar/MaxPriceForCharging
The Topic should rather be use the /config/get (get the current value) and /config/set (set the current value) paths like:
openWB/config/get/global/MaxPriceForCharging
openWB/config/set/global/MaxPriceForCharging
This would make it easier to expose / use it externaly without using the Display, for example for integrations such as
https://github.com/a529987659852/openwbmqtt
The text was updated successfully, but these errors were encountered: