Skip to content
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

MQTT Featurerequest: One-Time publish of devcontrol Topics #191

Closed
BernhardLinz opened this issue Aug 22, 2022 · 0 comments
Closed

MQTT Featurerequest: One-Time publish of devcontrol Topics #191

BernhardLinz opened this issue Aug 22, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@BernhardLinz
Copy link

In User_Manuel.md is the Active Power Limit via MQTT described.
I have just try to help another user to create the correct Topics in MQTT:

topic payload active power limit in Condition
<CHOOSEN_TOPIC_FROM_SETUP>/devcontrol/<INVERTER_ID>/11 OR <CHOOSEN_TOPIC_FROM_SETUP>/devcontrol/<INVERTER_ID>/11/0 [0..65535] Watt not persistent
<CHOOSEN_TOPIC_FROM_SETUP>/devcontrol/<INVERTER_ID>/11/256 [0...65535] Watt persistent
<CHOOSEN_TOPIC_FROM_SETUP>/devcontrol/<INVERTER_ID>/11/1 [2...100] % not persistent
<CHOOSEN_TOPIC_FROM_SETUP>/devcontrol/<INVERTER_ID>/11/257 [2...100] % persistent

For Example, Tasmota have also separate Topics for publish (stat, tele) and subscription (cmnd). But the Tamota Firmware is initialize the cmnd Topic with one item cmnd/devicename/POWER

It would be helpfull if ahoy would do the same after establishing the first connection to the MQTT Broker.
First publish the ../devcontrol/0/11/0 to ../devcontrol/0/11/257 and, if configured, ../devcontrol/1/11/0 / ../devcontrol/2/11/0
and then start to subscribe

One Time after each reboot with empty values should be sufficient

Maybe also do the same for DevControlCmdType

@stefan123t stefan123t added documentation Improvements or additions to documentation ESP ESP8266 / ESP32 related labels Aug 30, 2022
@stefan123t stefan123t removed the ESP ESP8266 / ESP32 related label Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants