Closed itn3rd77 closed 1 year ago
Just doublechecked it here... works without problems:
First the command topic changes to 89 then after a little bit the status topic. If not even the cmd topic is changing, the problem is most likley between your HA installation and your MQTT broker. Are you using ACLs in your broker? Has the user with which your HA installation connects to the broker write permissions to the specific topic?
Thanks again for the quick reply. Double check ACL and permissions but did not find an issue. As you confirmed it is working I removed the cmd topic and and now it is working - crazy shit. Double checked after a restart of HA and MQTT broker. Still working. Don't know what was wrong with the cmd topic, but now it works without flaws.
Thanks and best regards!
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 wanted to change the Limit via Home Assisitant but it seems neither the sliders entities for relative limit adjustment nor the number entities for absolute limit adjustment have any functionality.
I changed the values and watched the topics via MQTT Explorer but nothing changes. Is this a bug or intentional feature and the sliders and number entities are only for representation?
To Reproduce Bug
In the device page of the auto detected device in Home Assistant move the slide e.g. for "Limit NonPersistent Relative" and check the result via openDTU UI or MQTT Explorer. Nothinfg happend and after the next update the slider is back at 100%.
Expected Behavior
Changing the values via automation or UI in Home Assistant should result in an actial change of the desired limit.
Install Method
Pre-Compiled binary from GitHub
What git-hash/version of OpenDTU?
9681ede
Relevant log/trace output
No response
Anything else?
No response