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
never been that fooled in 50 years. i search weeks from verify operation => how to make a subscription for a regulator.
Dumb people install a shitload of tools on the fly without care about security, resources... and maybe get it run. not an option 4 me.
It was already a stonehenge kinda work to verify mqtt operation as there is no logfile, status info, ..... Debugging is not what i had in mind, but was the only way to get infos at all, without external tools. This is like" rm -rf /var/log/*" what a great job
now i give up to map (subscribe) a published sensor value to another device using it as input. Even jackaudio or subscribe a newsletter is easier to handle. most the yaml, ... examples are nice but never found a mapping/subscribe that should generally faaaaaar easier
ha runs on raspi, mqtt inside as container aap
Hey there @emontnemery, @jbouwh, @bdraco, mind taking a look at this feedback as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of mqtt can trigger bot actions by commenting:
@home-assistant close Closes the feedback.
@home-assistant rename Awesome new title Renames the feedback.
@home-assistant reopen Reopen the feedback.
@home-assistant unassign mqtt Removes the current integration label and assignees on the feedback, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.
Feedback
Hola
never been that fooled in 50 years. i search weeks from verify operation => how to make a subscription for a regulator.
Dumb people install a shitload of tools on the fly without care about security, resources... and maybe get it run. not an option 4 me.
It was already a stonehenge kinda work to verify mqtt operation as there is no logfile, status info, ..... Debugging is not what i had in mind, but was the only way to get infos at all, without external tools. This is like" rm -rf /var/log/*" what a great job
now i give up to map (subscribe) a published sensor value to another device using it as input. Even jackaudio or subscribe a newsletter is easier to handle. most the yaml, ... examples are nice but never found a mapping/subscribe that should generally faaaaaar easier
ha runs on raspi, mqtt inside as container aap
URL
https://www.home-assistant.io/integrations/mqtt/
Version
2025.4.4
Additional information
No response
The text was updated successfully, but these errors were encountered: