ah, so the original .js file? as in the original documentation?
No The one from that pull request.
1 Like
i give up, deleted the script, tried with easy names, tried with *
dont get it up and running anymore, always verification issue OR the script just doesnt load
i have it now like below:
no more verfiication, but also the script doesnt connect to the devices
maybe it has todo with the .local stuff? i dont have anywhere local
The leading dot in the Name is part of the regular expression. If you replace the asterisk with your HA hostname, you should also remove the leading dot.
So, in your last screenshot, this:
.homeassistant\._home-assistant\._tcp\.local
would be
homeassistant\._home-assistant\._tcp\.local
That is, assuming the Name field is relevant to the issue, which is not yet clear… after all, it is still working locally for me 
ok, back in business, as test i used now
.+\._home-assistant\._tcp\.local
ah , thx @Davidy , makes sense
thats why .+\._home-assistant\._tcp\.local is now also working?
whats the difference between + and * ?
A regular expression followed by a plus sign ( + ) matches one or more occurrences of the one-character regular expression . If there is any choice, the first matching string in a line is used. A regular expression followed by a question mark ( ? ) matches zero or one occurrence of the one-character regular expression.
- matches all types of characters
I’m not sure why you guys are adding a leading ‘_’.
It should be
homeassistant\._home-assistant\._tcp\.local
ok, lets try rebooting, and giving back an space in the name …
is a + also valid for a space ?
In regular expressions like this, a dot is a wildcard that means any character and the asterisk means zero or more times, which would match pretty much anything. The plus sign means one or more times, so it would match anything except an empty string.
The backward slash \ is used to “escape” to prevent using the following character as a wildcard, in this case is used so the other dots are interpreted as literals.
As for why it works now in your case, I have no idea 
1 Like
ok, give my instance back a space , like “Home Assistant” with this value : .+\._home-assistant\._tcp\.local
didnt survive a reboot
gonna try now back without a space
Nope, just a single instance…
For the guys with device verficiation error…
Got it again working, change Name Field to : .*._home-assistant._tcp.local , so removed all the \ in that string, before it was like : .*\._home-assistant\._tcp\.local
EDIT: seems the one with \ is still working, i got it to work just by saying “sync my devices” i think that cleared the verification error
Here is new js file:
It should looke like below when you inspect devices
chrome://inspect/#devices
1 Like
waiting 24 hours and then ‘sync devices’ is what initially addressed mine when it was broken as well a while ago. There was something with the waiting a long period of time though because I had done sync devices a number of times before waiting.
Yes, I think the sync devices did also the trick for me, not sure why, maybe Somekind of ID change
Thanks a lot Fabio,
now it’s working without error 
(grazie neeee)
Denis
yeah, but after a restart of HA, it fails again, i then receive unregistered webhooks
everytime i restart HA, i also need to restart the google devices or do a sync
You shouldn’t have to. I’ve restarted my HA dozens of times without issue.