Hey guys, hoping someone can help me out here. I don’t have any Apple/Homekit devices, and will not be purchasing any, yet HA constantly is autodiscovering (via zeroconf, from my reading?) my Rachio sprinkler system (which I already have integrated with HA under that component) as an Apple homekit accessory.
My question is how on earth do I get rid of this notification permanently without completely disabling discovery or zeroconf or whatever? It’s driving me crazy as it’s constantly recurring every time I reboot HA or whatever. I don’t see any option in the discovery component to ignore ‘homekit’, and I don’t even have the ‘zeroconf:’ entered anywhere in my configuration.yaml file. I don’t see any related entity that I can ignore either. See attached pics for what I’m seeing if I hit “check it out” then “configure”. What can I do here?
Done! Really stupid that there’s no solution for such a seemingly simple item Hopefully something comes of it. Thanks!
EDIT: Figured it out with the help of a kind individual on Reddit. I didn’t have zeroconf: or anything explicitly enabled in my config, but I did have default_config: entered so it was getting added through that. I removed that and added only the things I wanted from it, and the blasted notification has vanished! Whooohoooo!
Thanks tom_l. I don’t use github but this issue is rather important to me. I’ll lurk that thread but it seems jc2k has already covered my gripes.
I’m an equal opportunity hater. While I hate apple and anything they touch, I also can’t stand microsoft. Since MS bought out github, all of my coding has been moved over to my own private server.
I have no HomeKit devices, but do have a Lutron Bridge that I control locally. I got tired of the constant, persistent notification, so I did as follows:
forked and downloaded the Home Assistant source from github.
copied zeroconf folder to custom_components directory within .homeassistant directory (/config for hassio).
edited init.py (two undersores before and after init), and added “return True” as first line after “def handle_homekit(hass, info) -> bool:”
restarted hass
That worked for me, and seems to have no complications. However, I’m not a developer, and do not claim that I know what I am doing.
Don’t forget to remove the custom component if the real developers resolve this and change zeroconf.
Yea! Now I can trust Home Assistant to tell me when there’s something I need to be notified about, instead of always assuming it just wants to set up my Rachio again, using homekit this time.
@tom_l nice idea! But, I have a similar niggling problem, since it turns out my LG television in a late model and LG are not fully supporting Homekit in that model. It turns out your television is detected but won’t connect - really annoying. When I pulled the thread, I found a petition site where people with the later models of LG televisions can petition LG to sort address this pain.
Just in case anyone still has this issue (like myself) here is automation that automatically discards persistent notifications that are matching text pattern:
alias: discard notification
description: ""
trigger:
- platform: persistent_notification
update_type:
- added
condition:
- condition: template
value_template: >-
{{ 'in the Home App, scan the QR code or enter the following code' in
trigger.notification.message }}
action:
- service: persistent_notification.dismiss
data:
notification_id: "{{ trigger.notification.notification_id }}"
In my case I wanted to ignore notifications about adding devices of HA into Homekit, but you can change the value_template string to anything you need
Presumably because I’m already using the Rachio component maybe?