Right, I’ve seen the stale thing, though I didn’t remember the details. But for “needs more info” tag the process could be a bit different and faster. I could even imagine the bug to be marked as closed within a week of having “needs more info” without any activity - with the option for the author to reopen it when they add missing info. Anyway, just a suggestion.
Eh, people still ignore the needs more info tag. And only contributors can add the tag. I.e. the user needs to fill out the form correctly so that it’s triaged in the correct place, then the codeowner needs to issue the commands to add the tag.
So, assuming there’s a code owner and the user filled out the information, everything should work as intended. But speaking from experience, most issues that get the flag needs more info, the issuer ingores that and it just goes stale.
In regards to my integrations, I’ve only had to issue it a few times and people respond with proper information. However, every now and then I search all the issues and apply tags to incorrectly created issues and many of those get needs more info and go stale.
Right, I understand that. But then with my proposition those bugs would go away much faster, they woudn’t stick around for another 3 months after you added the needs more info tag.
1 Like
Eh, I’m not sure it makes a difference. We use filter to filter out needs more info so we know not to focus on them until the tag is removed.
Core does exactly this already, I think it accelerates it to ~2 weeks instead of 3 months.
2 Likes
Interesting, never noticed that
For the record, I had a couple of issues in core with “needs more info” tag where users (like me) asked several times very politely an assigned developer about “what info should be added?”.
And then users had to repeatedly un-stale issues with both “up” or “I experience same issue” (every 2 weeks).
And there were no reaction from a developer within more than a year, so no wonder that I myself lost my patience.
Means - both sides should follow some moral etc principles.
4 Likes
I pulled all issues ever logged against the project from GitHub and plotted created vs resolved issues (not only bugs). I tried to use the bug label, but it doesn’t seem reliable, so let’s just stick with all issues being problems of sorts. At this moment there’s been 63,156 issues logged against the core, with 2,649 open at the moment. Feature requests are minimal, so I just ignored that.
This is the monthly view:
And here’s the cumulative monthly view:
Yes, perhaps there is a marginal increase in the number of unresolved issues, but here are also the lines of code stats for the project:
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 8505 203321 104334 941140
JSON 3851 18 0 242679
YAML 466 992 825 30105
Text 1 38 0 191
Markdown 3 52 2 77
XML 1 8 0 30
TOML 2 2 0 8
CSV 1 0 0 5
-------------------------------------------------------------------------------
SUM: 12830 204431 105161 1214235
-------------------------------------------------------------------------------
So, 2.6k issues over 1.2m LOC gives a bug density of about 54 bugs per KLOC (1000 LOC).
Where does this rank?
| Software type | Bugs/KLOC (typical) | Notes |
| ------------------------------------ | ------------------- | ------------------------- |
| High-reliability (avionics, medical) | 0.1–0.5 | Very strict |
| Enterprise backend | 1–10 | Java/.NET, internal teams |
| Large Python/JS OSS | 20–50 | User-facing apps |
| Complex plugin-heavy OSS | 50–200 | Like Home Assistant Core |
For transparency, this table was generated by ChatGPT for convenience’s sake. I work in the industry, and these numbers are typical, so I can verify it at least in part. For some online references, see https://stackoverflow.com/questions/2898571/basis-for-claim-that-the-number-of-bugs-per-line-of-code-is-constant-regardless and Defect density benchmarks and industry standards.
Considering the fact that HA is a very large project with (as Petro said) 3,000 volunteers and a high number of integrations, I’d categorically say the project is in a healthy state. The core (excluding branded integrations) seems very stable.
If I filter for integration-related issues, I get 2,117 open issues, which means the remainder is 532. I can probably go filter the LOC stats to exclude components, but keep in mind automations, scripts, templates, etc. are actually all components and are probably considered more core (all the domains and platforms) than some component that supports the devices from a certain brand, or integration with some online service.
Issue counts for all domains:
Domain Count
-------------------------------
alarm_control_panel 0
automation 13
binary_sensor 0
calendar 0
camera 1
climate 1
counter 2
cover 1
device_tracker 0
fan 0
group 9
humidifier 0
input_boolean 0
input_datetime 0
input_number 0
input_select 0
input_text 1
light 2
lock 0
media_player 1
notify 3
number 0
person 4
plant 0
remote 10
scene 6
script 4
select 0
sensor 3
switch 30
timer 1
vacuum 0
water_heater 0
zone 0
-------------------------------
total 92
One overall blindspot here would be the libraries used by integrations which must architecturally sit outside of the core (typically the client libraries that handle the comms with devices and services).
15 Likes
Does that differentiate between actually resolved and closed as stale?
Many people just give up.
For example I have had to keep this core integration issue open for over two years:
I have four other issues that have been open for well over one year. All fully documented. No requests for furter info.
4 Likes
“Lies, damned lies, and statistics”
It really is disheartening to look through the issues in github looking for one that might be related to a current problem before reporting it. The majority of issues are closed as “stale” without any indication that anyone has ever looked at them.
3 Likes
It doesn’t. It was a bit of a manual effort to create these stats. I think stale issues goes two ways though: Lots of stale issues will be resolved indirectly, and some will just die while remaining an issue. I can maybe repeat this excluding all stale issues, and do something for the rate at which stale issues are closed. I naturally used the “created vs resolved” phrase from the (hateful) Jira world, where resolved means basically the same as closed, but you’d have a reason (a specific resolution) accompanying it (fixed, won’t do, not a bug, etc.). GitHub’s issue tracking isn’t the most advanced.
I’ve made an honest attempt at providing some concrete numbers, so please bring yours. I had no idea what I would find when I did this last night.
5 Likes
Pieter, an interesting survey. Does it account duplicates? Sometimes we have several duplicates of the same issue… Of course, not every issue has a duplicate, but at least we can estimate them like “3% of closed issues are duplicates” )))
(sorry for an offtopic)
There are 21k closed issues with the stale label in HA core.
I really don’t think there is any point to try to get valuable information from the data github provides, in the context discussed. It’s garbage in, garbage out. You could justify the exact opposite views using the same data, because it’s such imprecise. Partially because github doesn’t seem to mark some details like reason to close issues (closed is not the same as resolved), partially because anyone can create an entry, so there are bound to be a lot of incorrect entries, duplicates, not real bugs etc.
For example, you could both argue that 21k stale is good, because it’s only 21k out of 150k total closed. Or that it’s bad, because it’s 21k extra open bugs in the software.
1 Like
This is frustrating, and I have a couple of those too (on the frontend side too). I’m just careful to generalise that bugs aren’t attended to (I’m not saying you are, but some other replies here have illustrated that). I too don’t know why there isn’t feedback on quality logged issues.
Thanks Ildar. I could attempt this by employing some AI, but it would be hard to verify this (I try to use AI agents only where I can verify the output to some extent). Some spot checks might help. What would also be tricky would be to identify returning issues (was a bug, got fixed, broke again).
What’s the alternative? I agree there are caveats, and some of it has been noted, but that doesn’t mean one cannot get some useful data out of it. I have no agenda here and really thought posting this would generate more ideas for trying to get a better view, point out blind spots, etc. Honestly, in my 6 years here I haven’t seen such an analysis, even as basic as mine. What I would really like to hear are your suggestions for tackling some of the issues you’ve mentioned.
(Mods, if you feel this is too much off topic, feel free to migrate this to a new topic.)
2 Likes
Not sure how the number of volunteers can implicitly influence healthiness evaluation. It’s either healthy or not.
If latter, then the number of volunteers might be taken as justification (BTW are those all-time volunteers or active ones?).
What hit me immediately, seeing the graph, is its shape. Nobody mentioned it, but it looks like exponential. And in my opinion is dangerous. Especially, it’s obvious that resolving issues is lagging behind.
For a project being developed for 10 years (ie mature one), I would expect it to be stabilized to a pretty linear function
The question is how the lag would change if automatically closed issues did not contribute to resolved ones. Would it be negligible?
Please keep in mind that there is no severity distinction. We don’t know the ratio between critical issues vs trivial ones. So, indeed hard to tell which one remains unresolved.
Anyway, thank you, Parautenbach, for the analysis. It is a great picture.
The alternative to one action does not need to be another action, it could be inaction. My point here is that I don’t think the data is very useful. I didn’t want to suggest you had an agenta or that you misused the data somehow, just that I think the data you work on cannot give us all that useful information.
I think either way there is some space for improvement (even if we could say for sure that it’s already very good). There are plenty people here with a lot of knowledge of how things are being done currently (and, crucially, why) that probably have some good ideas what could be improved.
I think this is an incorrect conclusion. HA is growing both in terms of its code, supported features, and user base. Why would number of reported issues not grow as well? In fact, I was rather surprised by the fact it did stabilize in the last year or two.
1 Like
You might be right. For some reason, I thought it was the velocity, not the cumulative number of issues.
You have Pieter, and I am sorry if you thought my comment was aimed at you personally. Rather, I am critical of Github’s implication that “closed” means “resolved”.
Like Tom_I and Lidar_Gabdullin, I have had my share of issues which I have repeatedly marked as still an issue - until I gave up. What frustrates me personally most, is the lack of feedback that any developer has even looked at the issue 
The effect is to discourage users from reporting issues.
As you pointed out, HA is a large and primarily volunteer project; and I accept that volunteer developers are under no obligation to look at and fix every issue that is raised. As a former programmer myself, I appreciate both user and developer points of view. I still get a definite “by developers, for equally skilled developers” vibe from HA and ESPHome - particularly in github and ESPHome documentation - and feel that the main developers don’t frequent this community forum … creating a two-tier support system for users vs developers.
Possibly HA could use a helpdesk type app for users to report issues, and have some Nabu Casa staff to vet them, help users to provide additional information, and prioritise before passing them to github.
8 Likes
Thanks. My export doesn’t include all the fields. I extracted these fields using the GH CLI and it takes about 15 min: key, title, state, createdAt, closedAt, labels. One could do more with descriptions and comments too, I suppose. For getting the maintainers though, one needs to inspect the repo.
I got 1353 components with 394 without codeowners.
Here’s the full list.
integration,has_codeowner
abode,yes
acaia,yes
accuweather,yes
acer_projector,no
acmeda,yes
acomax,no
actiontec,no
actron_air,yes
adax,yes
adguard,yes
ads,yes
advantage_air,yes
aemet,yes
aep_ohio,no
aep_texas,no
aftership,no
agent_dvr,yes
ai_task,yes
air_quality,yes
airgradient,yes
airly,yes
airnow,yes
airos,yes
airq,yes
airthings,yes
airthings_ble,yes
airtouch4,yes
airtouch5,yes
airvisual,yes
airvisual_pro,yes
airzone,yes
airzone_cloud,yes
aladdin_connect,yes
alarm_control_panel,yes
alarmdecoder,no
alert,yes
alexa,yes
alexa_devices,yes
alpha_vantage,no
altruist,yes
amazon_polly,yes
amberelectric,yes
ambient_network,yes
ambient_station,yes
amcrest,yes
amp_motorization,no
ampio,no
analytics,yes
analytics_insights,yes
android_ip_webcam,yes
androidtv,yes
androidtv_remote,yes
anel_pwrctrl,no
anova,yes
anthemav,yes
anthropic,yes
anwb_energie,no
aosmith,yes
apache_kafka,yes
apcupsd,yes
api,yes
apollo_automation,no
appalachianpower,no
apple_tv,yes
application_credentials,yes
apprise,yes
aprilaire,yes
aprs,yes
apsystems,yes
aquacell,yes
aqualogic,no
aquostv,no
aranet,yes
arcam_fmj,yes
arest,no
arris_tg2492lg,yes
artsound,no
aruba,no
arve,yes
arwn,no
aseko_pool_live,yes
assist_pipeline,yes
assist_satellite,yes
asuswrt,yes
atag,yes
aten_pe,yes
atlanticcityelectric,no
atome,yes
august,yes
aurora,yes
aurora_abb_powerone,yes
aussie_broadband,yes
autarco,yes
auth,yes
automation,yes
avea,yes
avion,no
awair,yes
aws,no
aws_s3,yes
axis,yes
azure_data_explorer,yes
azure_devops,yes
azure_event_hub,yes
azure_service_bus,yes
azure_storage,yes
backblaze_b2,yes
backup,yes
baf,yes
baidu,no
balay,no
balboa,yes
bang_olufsen,yes
bauknecht,no
bayesian,yes
bbox,no
beewi_smartclim,yes
bge,no
binary_sensor,yes
bitcoin,no
bizkaibus,yes
blackbird,no
blebox,yes
blink,yes
blinksticklight,no
bliss_automation,no
bloc_blinds,no
blockchain,no
blue_current,yes
bluemaestro,yes
blueprint,yes
bluesound,yes
bluetooth,yes
bluetooth_adapters,yes
bluetooth_le_tracker,no
bluetooth_tracker,no
bmw_connected_drive,yes
bond,yes
bosch_alarm,yes
bosch_shc,yes
brandt,no
braviatv,yes
brel_home,no
bring,yes
broadlink,yes
brother,yes
brottsplatskartan,yes
browser,no
brunt,yes
bryant_evolution,yes
bsblan,yes
bt_home_hub_5,no
bt_smarthub,yes
bthome,yes
buienradar,yes
burbank_water_and_power,no
button,yes
caldav,no
calendar,yes
cambridge_audio,yes
camera,yes
canary,no
cast,yes
ccm15,yes
cert_expiry,yes
chacon_dio,yes
channels,no
cisco_ios,yes
cisco_mobility_express,yes
cisco_webex_teams,yes
citybikes,no
clementine,no
clickatell,no
clicksend,no
clicksend_tts,no
climate,yes
cloud,yes
cloudflare,yes
cmus,no
co2signal,yes
coautilities,no
coinbase,yes
color_extractor,yes
comed,no
comed_hourly_pricing,no
comelit,yes
comfoconnect,yes
command_line,yes
compensation,yes
compit,yes
concord232,no
coned,no
config,yes
configurator,yes
constructa,no
control4,yes
conversation,yes
cookidoo,yes
coolmaster,yes
counter,yes
cover,yes
cppm_tracker,no
cpuspeed,yes
cribl,no
crownstone,yes
currencylayer,no
cync,yes
daikin,yes
danfoss_air,no
datadog,no
date,yes
datetime,yes
ddwrt,no
deako,yes
debugpy,yes
deconz,yes
decora_wifi,no
decorquip,no
default_config,yes
delijn,yes
delmarva,no
deluge,yes
demo,yes
denon,no
denonavr,yes
derivative,yes
devialet,yes
device_automation,yes
device_sun_light_trigger,no
device_tracker,yes
devolo_home_control,yes
devolo_home_network,yes
dexcom,yes
dhcp,yes
diagnostics,yes
dialogflow,no
diaz,no
digital_ocean,yes
directv,no
discogs,yes
discord,yes
discovergy,yes
dlink,yes
dlna_dmr,yes
dlna_dms,yes
dnsip,yes
dominos,no
doods,no
doorbird,yes
dooya,no
dormakaba_dkey,yes
dovado,no
downloader,yes
dremel_3d_printer,yes
drop_connect,yes
droplet,yes
dsmr,yes
dsmr_reader,yes
dublin_bus_transport,no
duckdns,no
duke_energy,yes
dunehd,no
duotecno,yes
duquesne_light,no
dwd_weather_warnings,yes
dynalite,yes
eafm,yes
eastron,no
easyenergy,yes
ebox,no
ebusd,no
ecoal_boiler,no
ecobee,no
ecoforest,yes
econet,yes
ecovacs,yes
ecowitt,yes
edimax,no
edl21,no
efergy,yes
egardia,yes
eheimdigital,yes
eight_sleep,no
ekeybionyx,yes
electrasmart,yes
electric_kiwi,yes
elevenlabs,yes
elgato,yes
eliqonline,no
elkm1,yes
elmax,yes
elv,yes
elvia,yes
emby,yes
emoncms,yes
emoncms_history,yes
emonitor,yes
emulated_hue,yes
emulated_kasa,yes
emulated_roku,no
energenie_power_sockets,yes
energie_vanons,no
energy,yes
energyzero,yes
enigma2,yes
enocean,no
enphase_envoy,yes
entur_public_transport,yes
environment_canada,yes
envisalink,no
ephember,yes
epic_games_store,yes
epion,yes
epson,yes
eq3btsmart,yes
escea,yes
esera_onewire,no
esphome,yes
etherscan,no
eufy,no
eufylife_ble,yes
event,yes
evergy,no
everlights,no
evil_genius_labs,no
evohome,yes
ezviz,yes
faa_delays,yes
facebook,no
fail2ban,no
familyhub,no
fan,yes
fastdotcom,yes
feedreader,yes
ffmpeg,no
ffmpeg_motion,no
ffmpeg_noise,no
fibaro,yes
fido,no
file,yes
file_upload,yes
filesize,yes
filter,yes
fing,yes
fints,no
fire_tv,no
firefly_iii,yes
fireservicerota,yes
firmata,yes
fitbit,yes
fivem,yes
fixer,no
fjaraskupan,yes
fleetgo,no
flexit,no
flexit_bacnet,yes
flic,no
flipr,yes
flo,yes
flock,no
flume,yes
flux,no
flux_led,yes
folder,no
folder_watcher,no
foobot,no
forecast_solar,yes
forked_daapd,yes
fortios,yes
foscam,yes
foursquare,no
frankever,no
free_mobile,no
freebox,yes
freedns,no
freedompro,yes
fritz,yes
fritzbox,yes
fritzbox_callmonitor,yes
fronius,yes
frontend,yes
frontier_silicon,yes
fujitsu_anywair,no
fujitsu_fglair,yes
fully_kiosk,yes
futurenow,no
fyta,yes
gaggenau,no
garadget,no
garages_amsterdam,yes
gardena_bluetooth,yes
gaviota,no
gc100,no
gdacs,yes
generic,yes
generic_hygrostat,yes
generic_thermostat,no
geniushub,yes
geo_json_events,yes
geo_location,yes
geo_rss_events,yes
geocaching,yes
geofency,no
geonetnz_quakes,yes
geonetnz_volcano,yes
gios,yes
github,yes
gitlab_ci,no
gitter,no
glances,yes
go2rtc,yes
goalzero,yes
gogogate2,yes
goodwe,yes
google,yes
google_assistant,yes
google_assistant_sdk,yes
google_cloud,yes
google_drive,yes
google_generative_ai_conversation,yes
google_mail,yes
google_maps,no
google_photos,yes
google_pubsub,no
google_sheets,yes
google_tasks,yes
google_translate,no
google_travel_time,yes
google_wifi,no
govee_ble,yes
govee_light_local,yes
gpsd,yes
gpslogger,no
graphite,no
gree,yes
greeneye_monitor,yes
greenwave,no
group,yes
growatt_server,yes
gtfs,no
guardian,yes
habitica,yes
hardkernel,yes
hardware,yes
harman_kardon_avr,no
harmony,yes
harvey,no
hassio,yes
havana_shade,no
haveibeenpwned,no
hddtemp,no
hdmi_cec,yes
heatmiser,yes
heicko,no
heos,yes
here_travel_time,yes
hexaom,no
hikvision,yes
hikvisioncam,yes
hisense_aehw4a1,yes
history,yes
history_stats,no
hitron_coda,no
hive,yes
hko,yes
hlk_sw16,yes
holiday,yes
home_connect,yes
home_plus_control,no
homeassistant,yes
homeassistant_alerts,yes
homeassistant_connect_zbt2,yes
homeassistant_green,yes
homeassistant_hardware,yes
homeassistant_sky_connect,yes
homeassistant_yellow,yes
homee,yes
homekit,yes
homekit_controller,yes
homematic,yes
homematicip_cloud,yes
homewizard,yes
homeworks,no
honeywell,yes
horizon,no
hp_ilo,no
html5,yes
http,yes
huawei_lte,yes
hue,yes
huisbaasje,yes
humidifier,yes
hunterdouglas_powerview,yes
hurrican_shutters_wholesale,no
husqvarna_automower,yes
husqvarna_automower_ble,yes
huum,yes
hvv_departures,yes
hydrawise,yes
hyperion,yes
ialarm,yes
iammeter,yes
iaqualink,yes
ibeacon,no
icloud,yes
idasen_desk,yes
idteck_prox,no
ifttt,no
iglo,no
igloohome,yes
ign_sismologia,yes
ihc,no
image,yes
image_processing,yes
image_upload,yes
imap,yes
imeon_inverter,yes
imgw_pib,yes
immich,yes
improv_ble,yes
incomfort,yes
indianamichiganpower,no
inels,yes
influxdb,yes
inkbird,yes
input_boolean,yes
input_button,yes
input_datetime,yes
input_number,yes
input_select,yes
input_text,yes
inspired_shades,no
insteon,yes
integration,yes
intellifire,yes
intent,yes
intent_script,no
intesishome,yes
iometer,yes
ios,yes
iotawatt,yes
iotty,yes
iperf3,yes
ipma,yes
ipp,yes
iqvia,yes
irish_rail_transport,yes
irm_kmi,yes
iron_os,yes
isal,yes
iskra,yes
islamic_prayer_times,yes
ismartwindow,no
israel_rail,yes
iss,yes
ista_ecotrend,yes
isy994,yes
itach,no
itunes,no
ituran,yes
izone,yes
jellyfin,yes
jewish_calendar,yes
joaoapps_join,no
juicenet,no
justnimbus,yes
jvc_projector,yes
kaiser_nienhaus,no
kaiterra,yes
kaleidescape,yes
kankun,no
keba,yes
keenetic_ndms2,yes
kef,yes
kegtron,yes
kentuckypower,no
keyboard_remote,yes
keymitt_ble,yes
kira,no
kitchen_sink,yes
kiwi,no
kmtronic,yes
knocki,yes
knx,yes
kodi,yes
konnected,yes
konnected_esphome,no
kostal_plenticore,yes
kraken,yes
krispol,no
kulersky,yes
kwb,no
lacrosse,no
lacrosse_view,yes
lamarzocco,yes
lametric,yes
landisgyr_heat_meter,yes
lannouncer,no
lastfm,yes
launch_library,yes
laundrify,yes
lawn_mower,yes
lcn,yes
ld2410_ble,yes
leaone,yes
led_ble,yes
lektrico,yes
letpot,yes
lg_netcast,yes
lg_soundbar,no
lg_thinq,yes
libre_hardware_monitor,yes
lidarr,yes
life360,no
lifx,yes
lifx_cloud,no
light,yes
lightwave,no
limitlessled,no
linak,no
linkedgo,no
linkplay,yes
linksys_smart,no
linode,no
linux_battery,yes
linx,no
litejet,yes
litterrobot,yes
livisi,yes
llamalab_automate,no
local_calendar,yes
local_file,no
local_ip,yes
local_todo,yes
locative,no
lock,yes
logbook,yes
logentries,no
logger,yes
london_air,no
london_underground,yes
lookin,yes
loqed,yes
lovelace,yes
luci,yes
luftdaten,yes
lunatone,yes
lupusec,yes
lutron,yes
lutron_caseta,yes
lw12wifi,no
lyric,yes
madeco,no
madvr,yes
mailgun,no
manual,no
manual_mqtt,no
martec,no
marytts,no
mastodon,yes
matrix,yes
matter,yes
maxcube,no
maytag,no
mazda,no
mcp,yes
mcp_server,yes
mealie,yes
meater,yes
medcom_ble,yes
media_extractor,yes
media_player,yes
media_source,yes
mediaroom,yes
melcloud,yes
melissa,yes
melnor,yes
meraki,no
message_bird,no
met,yes
met_eireann,yes
meteo_france,yes
meteo_lt,yes
meteoalarm,yes
meteoclimatic,yes
metoffice,yes
mfi,no
microbees,yes
microsoft,no
microsoft_face,no
microsoft_face_detect,no
microsoft_face_identify,no
miele,yes
mijndomein_energie,no
mikrotik,yes
mill,yes
min_max,yes
minecraft_server,yes
mini_connected,no
minio,yes
mjpeg,no
moat,yes
mobile_app,yes
mochad,no
modbus,no
modem_callerid,yes
modern_forms,yes
moehlenhoff_alpha2,yes
mold_indicator,no
monarch_money,yes
monessen,no
monoprice,yes
monzo,yes
moon,yes
mopeka,yes
motion_blinds,yes
motionblinds_ble,yes
motioneye,yes
motionmount,yes
mpd,no
mqtt,yes
mqtt_eventstream,no
mqtt_json,no
mqtt_room,no
mqtt_statestream,no
msteams,yes
mullvad,yes
music_assistant,yes
mutesync,yes
mvglive,no
my,yes
mycroft,no
myq,no
mysensors,yes
mystrom,yes
mythicbeastsdns,no
myuplink,yes
nad,no
nam,yes
namecheapdns,no
nanoleaf,yes
nasweb,yes
national_grid_us,no
neato,no
nederlandse_spoorwegen,yes
neff,no
neo,no
ness_alarm,yes
nest,yes
netatmo,yes
netdata,yes
netgear,yes
netgear_lte,yes
netio,no
network,yes
neurio_energy,no
nexia,yes
nextbus,yes
nextcloud,yes
nextdns,yes
nfandroidtv,yes
nibe_heatpump,yes
nice_go,yes
nightscout,yes
niko_home_control,yes
nilu,yes
nina,yes
nintendo_parental_controls,yes
nissan_leaf,yes
nmap_tracker,no
nmbs,no
no_ip,no
noaa_tides,yes
nobo_hub,yes
nordpool,yes
norway_air,no
notify,yes
notify_events,yes
notion,yes
nsw_fuel_station,yes
nsw_rural_fire_service_feed,yes
ntfy,yes
nuheat,yes
nuki,yes
numato,yes
number,yes
nut,yes
nws,yes
nx584,no
nyt_games,yes
nzbget,yes
oasa_telematics,no
obihai,yes
octoprint,yes
oem,no
ogemray,no
ohmconnect,yes
ohme,yes
ollama,yes
ombi,yes
omnilogic,no
onboarding,yes
oncue,no
ondilo_ico,yes
onedrive,yes
onewire,yes
onkyo,yes
onvif,yes
open_meteo,yes
open_router,yes
openai_conversation,no
openalpr_cloud,no
openerz,yes
openevse,no
openexchangerates,yes
opengarage,yes
openhardwaremonitor,no
openhome,yes
openrgb,yes
opensensemap,no
opensky,yes
opentherm_gw,yes
openuv,yes
openweathermap,yes
opnsense,yes
opower,yes
opple,no
oralb,yes
oru,yes
oru_opower,no
orvibo,no
osoenergy,yes
osramlightify,no
otbr,yes
otp,no
ourgroceries,yes
overkiz,yes
overseerr,yes
ovo_energy,yes
owntracks,no
p1_monitor,yes
palazzetti,yes
panasonic_bluray,no
panasonic_viera,no
panel_custom,yes
paperless_ngx,yes
peblar,yes
peco,yes
peco_opower,no
pegel_online,yes
pencom,no
pepco,no
permobil,yes
persistent_notification,yes
person,no
pge,no
pglab,yes
philips_js,yes
pi_hole,yes
picnic,yes
picotts,no
pilight,no
pinecil,no
ping,yes
pioneer,no
piper,no
pitsos,no
pjlink,no
plaato,yes
plant,no
playstation_network,yes
plex,yes
plugwise,yes
plum_lightpad,no
pocketcasts,no
point,yes
pooldose,yes
poolsense,yes
portainer,yes
portlandgeneral,no
powerfox,yes
powerwall,yes
private_ble_device,yes
probe_plus,yes
profiler,yes
profilo,no
progettihwsw,yes
proliphix,no
prometheus,yes
prosegur,yes
prowl,no
proximity,yes
proxmoxve,yes
proxy,no
prusalink,no
ps4,yes
pse,no
psoklahoma,no
pterodactyl,yes
pulseaudio_loopback,no
pure_energie,yes
purpleair,yes
push,yes
pushbullet,yes
pushover,yes
pushsafer,no
pvoutput,yes
pvpc_hourly_pricing,yes
pyload,yes
python_script,no
qbittorrent,yes
qbus,yes
qingping,yes
qld_bushfire,yes
qnap,yes
qnap_qsw,yes
qrcode,no
quadrafire,no
quantum_gateway,yes
qvr_pro,yes
qwikswitch,yes
rabbitair,yes
rachio,yes
radarr,yes
radio_browser,yes
radiotherm,yes
rainbird,yes
raincloud,yes
rainforest_eagle,yes
rainforest_raven,yes
rainmachine,yes
random,yes
rapt_ble,yes
raspberry_pi,yes
raspyrfm,no
raven_rock_mfg,no
rdw,yes
recollect_waste,yes
recorder,yes
recovery_mode,yes
recswitch,no
reddit,no
refoss,yes
rehlko,yes
rejseplanen,no
remember_the_milk,no
remote,yes
remote_calendar,yes
remote_rpi_gpio,no
renault,yes
renson,yes
reolink,yes
repairs,yes
repetier,yes
rest,no
rest_command,yes
rflink,yes
rfxtrx,yes
rhasspy,yes
ridwell,yes
ring,yes
ripple,no
risco,yes
rituals_perfume_genie,yes
rmvtransport,yes
roborock,yes
rocketchat,no
roku,yes
romy,yes
roomba,yes
roon,yes
route53,no
route_b_smart_meter,yes
rova,no
rpi_camera,no
rpi_power,yes
rss_feed_template,yes
rtorrent,no
ruckus_unleashed,yes
russound_rio,yes
russound_rnet,yes
ruuvi_gateway,yes
ruuvitag_ble,yes
rympro,yes
sabnzbd,yes
saj,yes
samsam,no
samsungtv,yes
sanix,yes
satel_integra,yes
scene,yes
schedule,yes
schlage,yes
schluter,yes
scl,no
scrape,yes
screenaway,no
screenlogic,yes
script,yes
scsgate,no
search,yes
season,yes
select,yes
sendgrid,no
sense,yes
sensibo,yes
sensirion_ble,yes
sensor,yes
sensorpro,yes
sensorpush,yes
sensorpush_cloud,yes
sensoterra,yes
sentry,yes
senz,yes
serial,yes
serial_pm,no
sesame,no
seven_segments,yes
seventeentrack,yes
sfr_box,yes
sftp_storage,yes
sharkiq,yes
shell_command,yes
shelly,yes
shodan,yes
shopping_list,no
sia,yes
siemens,no
sigfox,no
sighthound,yes
signal_messenger,yes
simplefin,yes
simplepush,yes
simplisafe,yes
simu,no
sinch,yes
siren,yes
sisyphus,yes
sky_hub,no
sky_remote,yes
skybeacon,no
skybell,yes
slack,yes
sleep_as_android,yes
sleepiq,yes
slide,yes
slide_local,yes
slimproto,yes
sma,yes
smappee,yes
smarla,yes
smart_blinds,no
smart_home,no
smart_meter_texas,yes
smart_rollos,no
smartthings,yes
smarttub,yes
smarty,yes
smhi,yes
smlight,yes
smtp,no
smud,no
snapcast,yes
snmp,yes
snoo,yes
snooz,yes
solaredge,yes
solaredge_local,yes
solarlog,yes
solax,yes
soma,yes
somfy_mylink,no
sonarr,yes
songpal,yes
sonos,yes
sony_projector,no
soundtouch,yes
spaceapi,yes
spc,no
speedtestdotnet,yes
spider,no
splunk,yes
spotify,yes
sql,yes
squeezebox,yes
srp_energy,yes
ssdp,no
starline,yes
starlingbank,no
starlink,yes
startca,no
statistics,yes
statsd,no
steam_online,yes
steamist,yes
stiebel_eltron,yes
stookwijzer,yes
stream,yes
streamlabswater,no
stt,yes
subaru,yes
suez_water,yes
sun,yes
sunricher_dali,yes
sunweg,no
supervisord,no
supla,yes
surepetcare,yes
swepco,no
swiss_hydrological_data,yes
swiss_public_transport,yes
swisscom,no
switch,yes
switch_as_x,yes
switchbee,yes
switchbot,yes
switchbot_cloud,yes
switcher_kis,yes
switchmate,yes
symfonisk,no
syncthing,yes
syncthru,yes
synology_chat,no
synology_dsm,yes
synology_srm,yes
syslog,no
system_bridge,yes
system_health,no
system_log,no
systemmonitor,yes
tado,yes
tag,yes
tailscale,yes
tailwind,yes
tami4,yes
tank_utility,no
tankerkoenig,yes
tapsaff,yes
tasmota,yes
tautulli,yes
tcp,no
technove,yes
ted5000,no
tedee,yes
telegram,no
telegram_bot,yes
tellduslive,yes
tellstick,no
telnet,no
temper,no
template,yes
tesla_fleet,yes
tesla_wall_connector,yes
teslemetry,yes
tessie,yes
text,yes
tfiac,yes
thermador,no
thermobeacon,yes
thermopro,yes
thermoworks_smoke,no
thethingsnetwork,yes
thingspeak,no
thinkingcleaner,no
thomson,no
thread,yes
threshold,no
tibber,yes
tikteck,no
tile,yes
tilt_ble,yes
tilt_pi,yes
time,yes
time_date,yes
timer,no
tmb,yes
tod,no
todo,yes
todoist,yes
togrill,yes
tolo,yes
tomato,no
tomorrowio,yes
toon,no
torque,no
totalconnect,yes
touchline,no
touchline_sl,yes
tplink,yes
tplink_lte,no
tplink_omada,yes
tplink_tapo,no
traccar,yes
traccar_server,no
trace,yes
tractive,yes
tradfri,no
trafikverket_camera,yes
trafikverket_ferry,yes
trafikverket_train,yes
trafikverket_weatherstation,yes
transmission,yes
transport_nsw,no
travisci,no
trend,yes
triggercmd,yes
tts,yes
tuya,yes
twentemilieu,yes
twilio,no
twilio_call,no
twilio_sms,no
twinkly,yes
twitch,yes
twitter,no
ubiwizz,no
ublockout,no
ubus,no
uk_transport,no
ukraine_alarm,yes
ultraloq,no
unifi,yes
unifi_direct,yes
unifiled,yes
unifiprotect,yes
universal,no
upb,yes
upc_connect,yes
upcloud,yes
update,yes
upnp,yes
uprise_smart_shades,no
uptime,yes
uptime_kuma,yes
uptimerobot,yes
usage_prediction,yes
usb,yes
usgs_earthquakes_feed,yes
utility_meter,yes
uvc,no
v2c,yes
vacuum,yes
vallox,yes
valve,yes
vasttrafik,no
vegehub,yes
velbus,yes
velux,yes
venstar,yes
vera,no
verisure,no
vermont_castings,no
versasense,yes
version,yes
vesync,yes
viaggiatreno,no
vicare,yes
victron_remote_monitoring,yes
vilfo,yes
vivotek,yes
vizio,yes
vlc,no
vlc_telnet,yes
vodafone_station,yes
voicerss,no
voip,yes
volkszaehler,no
volumio,yes
volvo,yes
volvooncall,yes
w800rf32,no
wake_on_lan,yes
wake_word,yes
wallbox,yes
waqi,yes
water_heater,yes
waterfurnace,no
watergate,yes
watson_tts,yes
watttime,yes
waze_travel_time,yes
weather,yes
weatherflow,yes
weatherflow_cloud,yes
weatherkit,yes
webdav,yes
webhook,yes
webmin,yes
webostv,yes
websocket_api,yes
weheat,yes
wemo,yes
whirlpool,yes
whisper,no
whois,yes
wiffi,yes
wilight,yes
wirelesstag,yes
withings,yes
wiz,yes
wled,yes
wmspro,yes
wolflink,yes
workday,yes
worldclock,yes
worldtidesinfo,no
worxlandroid,no
ws66i,yes
wsdot,no
wyoming,yes
x10,no
xbox,yes
xeoma,no
xiaomi,no
xiaomi_aqara,yes
xiaomi_ble,yes
xiaomi_miio,yes
xiaomi_tv,yes
xmpp,yes
xs1,no
yale,yes
yale_smart_alarm,yes
yalexs_ble,yes
yamaha,no
yamaha_musiccast,yes
yandex_transport,yes
yandextts,no
yardian,yes
yeelight,yes
yeelightsunflower,yes
yi,yes
yolink,yes
youless,yes
youtube,yes
zabbix,yes
zamg,yes
zbox_hub,no
zengge,yes
zeroconf,yes
zerproc,yes
zestimate,no
zeversolar,yes
zha,yes
zhong_hong,no
ziggo_mediabox_xl,no
zimi,yes
zodiac,yes
zondergas,no
zone,yes
zoneminder,yes
zwave_js,yes
zwave_me,yes
1 Like