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 am not finding "Mosquitto broker" in the HACS search (now the only way to interface with HACS in HA). What happened to it? How to proceed?
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Other (e.g., Raspbian/Raspberry Pi OS/Fedora)
Which add-on are you reporting an issue with?
CEC Scanner
What is the version of the add-on?
HACS, latest
Steps to reproduce the issue
Click on HACS in the upper left side menu items.
Start typing in the search bar: "Mosq", as soon as the 'q' is typed, there no search hits, regardless of what is typed after it.
(btw, your issue template links should open in new tab/window, not in this tab.)
System Health information
System Information
version
core-2024.4.2
installation_type
Unsupported Third Party Container
dev
false
hassio
false
docker
true
user
abc
virtualenv
false
python_version
3.12.2
os_name
Linux
os_version
5.10.0-28-amd64
arch
x86_64
timezone
America/New_York
config_dir
/config
Home Assistant Community Store
GitHub API
ok
GitHub Content
ok
GitHub Web
ok
GitHub API Calls Remaining
4989
Installed Version
1.34.0
Stage
running
Available Repositories
1399
Downloaded Repositories
1
HACS Data
ok
Home Assistant Cloud
logged_in
false
can_reach_cert_server
ok
can_reach_cloud_auth
ok
can_reach_cloud
ok
Dashboards
dashboards
2
resources
0
views
1
mode
storage
Recorder
oldest_recorder_run
April 25, 2024 at 3:18 AM
current_recorder_run
April 28, 2024 at 10:53 AM
estimated_db_size
4.59 MiB
database_engine
sqlite
database_version
3.44.2
Anything in the Supervisor logs that might be useful for us?
N/A
Anything in the add-on logs that might be useful for us?
2024-04-28 10:53:31.618 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-28 10:55:56.498 WARNING (MainThread) [homeassistant.data_entry_flow] custom_components.hacs.config_flow::HacsFlowHandler calls async_show_progress without passing a progress task, this is not valid and will break in Home Assistant Core 2024.8. Please report it to the custom integration author
2024-04-28 10:58:41.070 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
Additional information
I see the need for full info for an issue, but this is so not user friendly.
The text was updated successfully, but these errors were encountered:
I just faced the same trivial issue, spent a lot of time but the solution is very easy. You probably searched the Mosquitto as Integration, but it is an Addon.
BR, Timo
Describe the issue you are experiencing
I am not finding "Mosquitto broker" in the HACS search (now the only way to interface with HACS in HA). What happened to it? How to proceed?
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Other (e.g., Raspbian/Raspberry Pi OS/Fedora)
Which add-on are you reporting an issue with?
CEC Scanner
What is the version of the add-on?
HACS, latest
Steps to reproduce the issue
(btw, your issue template links should open in new tab/window, not in this tab.)
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
I see the need for full info for an issue, but this is so not user friendly.
The text was updated successfully, but these errors were encountered: