-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Feature Request: Rest-Api call to get result of adjust power level #553
Comments
IMHO the two call(s) should remain async as the REST API would otherwise be blocked not only until the |
|
added SH1106 to automatic build added IP address to MQTT (version, device and IP are retained and only transmitted once after boot) #556 added `set_power_limit` acknowledge MQTT publish #553 changed: version, device name are only published via MQTT once after boot added `Login` to menu if admin password is set #554 added `development` to second changelog link in `index.html` #543 added interval for MQTT (as option). With this settings MQTT live data is published in a fixed timing (only if inverter is available) #542, #523 added MQTT `comm_disabled` #529
Will check this soon, thank you! |
for me the acknowledge works as expected, the field |
Hardware
Modelname: Any
Retailer URL: n.a.
nRF24L01+ Module
n.a.
Software
Version / Git SHA:
Version: any next version
From Discord discussion:
Mo had a question about the statement
"http:https://192.168.0.142/api/ctrl"
and there the payload
{"id": "0", "cmd": "limit_persistent_absolute", "val": "30"}
must be POSTed as content type
application/json
:Q (Mo): Is there an immediate return code from which one can see whether the HM understood and implemented the command?
A (lumapu): Yes, it is read back and the value is then also transmitted via MQTT, but it feels like it takes about a minute. I don't know the exact MQTT path at the moment
Q (Mo): It would be nice to also have a rest-api call for this, then you can process the order and the check via the same interface (and maybe don't have to wait up to 1 minute?).
The text was updated successfully, but these errors were encountered: