You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have appended an organizing string to the basic MQTT topic, i.e., from solar/ to solar/baga/.
Now, setting the limits via the cmd topic does not work anymore. Previously, the topic to write to was solar/<invnr>/cmd/limit_nonpersistent_relative, now, it should be solar/baga/<invnr>/cmd/limit_nonpersistent_absolute. However, writing to it does not change the limit. If I reset the basic topic to solar/, it works again.
I've also tried to publish to the original topic, but this doesn't work either.
No matter, if relative or absolute limit is used.
To Reproduce Bug
Change the basic topic.
Try to write a new limit.
Expected Behavior
The written limit should be applied.
Install Method
Pre-Compiled binary from GitHub
What git-hash/version of OpenDTU?
v24.5.6
Relevant log/trace output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.
What happened?
I have appended an organizing string to the basic MQTT topic, i.e., from
solar/
tosolar/baga/
.Now, setting the limits via the
cmd
topic does not work anymore. Previously, the topic to write to wassolar/<invnr>/cmd/limit_nonpersistent_relative
, now, it should besolar/baga/<invnr>/cmd/limit_nonpersistent_absolute
. However, writing to it does not change the limit. If I reset the basic topic tosolar/
, it works again.I've also tried to publish to the original topic, but this doesn't work either.
No matter, if relative or absolute limit is used.
To Reproduce Bug
Expected Behavior
The written limit should be applied.
Install Method
Pre-Compiled binary from GitHub
What git-hash/version of OpenDTU?
v24.5.6
Relevant log/trace output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: