-
Notifications
You must be signed in to change notification settings - Fork 0
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
Reasonable preset of MQTT topics #6
Comments
Support starting from an empty, existing file.
Thanks for providing this info as a hint on how the json data looks like. Unfortunately, Home Assistant auto discovery is not working for me (even as I see the server sending data to the homeassistant/# topic). |
The autodiscovery works for me (tm). |
Thank you for checking this one as well. :)
However, I saw in another issue that this last line is holding homeassistant back from publishing the discovered device: Edit: Nevermind. The fans are not shown as MQTT devices, but the entities are published correctly in the entity view. Looks like all features are working! 🎉 Thank you so much for creating this. The fans were literally the last dumb (non-homeassistant-controllable) parts of our home. |
Nice to know that there is another running installation :-). I feedback for others: the current version of the code is now running for more than 6 months without any issues. Issues with the MQTT server sometimes require a restart of the server. This never happened without a reason like playing around with the MQTT config if IOBroker. |
After I moved my installation to docker containers I almost gave up because I did not get it working. Reason for the system not working was wrong strings in the MQTT. After installation lots of settings like e.g. speed come with "(null)". If you do not change these to the expected values the server will not accept any changes from MQTT at all.
Is it possible to directly set all MQTT topics to a working preset?
The text was updated successfully, but these errors were encountered: