Using the bounjour browser the entity looks pretty good.
Not sure what the problem is you are trying to explain…
Have you added “default_visibility”: “visible” to your configuration after the upgrade?
Hello @frenck! How are you today my friend?
Since this morning, after update to version 1.0.3 the home assistant accessory (bridge) has become unavailable:
Another thing is that devices updated from the HA webui does not replicate on my Home app.
Any idea why?
Thanks!!!
I’m not sure why it is unavailable. Have you restarted the addon? Did you notice anything strange in the logs?
For the second problem: Devices added/updated/changed in the HA configuration won’t show that way in Homebrige. This is a limitation of the Homebridge software the addon uses and is documented.
1 Like
exactly the same issue @Schneider has, Home assistant (bridge) is no longer available. I can’t see it when adding an accessory in the iOS Home app. Updated to 1.0.3, removed persist folder and added “default_visibility”: “visible”. Nothing working. Homebridge logs show everything working as normal.
I found this in the GitHub repository of Homebridge:
This was added/discussed after the upgrade of Homebridge.
Quote from the issue tracker:
Regarding the “Not Responding” situation, if force closing the app isn’t enough then try the following before deleting anything in “persist”. Note that when you delete anything in the “persist” directory, you’ll have to setup Homebridge from scratch (i.e. delete the home from within the Home app and go through the pairing/setup process all over again, losing all of your scenes/automations/rooms/etc.).
- Stop Homebridge
- Force close Home app
- Delete “cachedAccessories” from “accessories” folder in Homebridge directory
- Restart Homebridge
- Reopen Home app
I’m sorry, I might not have expressed myself correctly: the second problem is when I toggle a switch using the native web ui on HA, switch that is already configured and showing in Home app, the status of the same switch does not sync on my iPhone as before.
And yes! I’ve restarted homebridge…
Aah ok, that would be a result of not being connected to the Homebridge of course…
1 Like
The weird thing is that even if Homebridge is unavailable, I can turn on things using Home app and it replicates on HA webui hehe
Tried and still not showing home assistant ‘bridge’ in home app.
I’m sorry I just guess here now. I can’t debug your setup from a remote location.
Please provide me:
- Startup and some event logs.
- Your config.json (remove passwords!)
- Your addon configuration
Please also try Bounjour Browser to check if the service is actually showing on your network.
Info sent, thanks 
Here are my logs:
Logs
starting version 3.2.2
[ADD-ON] Ensuring old PID files are absent
[ADD-ON] Ensuring D-Bus unique ID exists
[ADD-ON] Starting D-Bus daemon
[ADD-ON] Starting Avahi daemon
Found user ‘avahi’ (UID 86) and group ‘avahi’ (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.6.32 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Successfully called chroot().
Successfully dropped remaining capabilities.
Loading service file /services/sftp-ssh.service.
Loading service file /services/ssh.service.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.80.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::28b3:2cff:fee2:ed15 on veth88c8cbc..
Registering new address record for fe80::2c89:8eff:fe35:19e8 on vethe466355..
Registering new address record for fe80::d014:cfff:fe2d:b5a1 on veth3d794bc..
Registering new address record for fe80::42:75ff:fedf:3f25 on docker0..
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::326f:bcf8:940d:70be on eth0.*.
Registering new address record for 192.168.2.80 on eth0.IPv4.
Server startup complete. Host name is hassio.local. Local service cookie is 2905888832.
[ADD-ON] Applying HAP NodeJS IPV6 HOTFIX
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[ADD-ON] Starting Homebridge
*** WARNING *** The program ‘node’ uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program ‘node’ called ‘DNSServiceRegister()’ which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
[8/22/2017, 5:21:53 PM] Loaded plugin: homebridge-homeassistant
[8/22/2017, 5:21:54 PM] Registering platform ‘homebridge-homeassistant.HomeAssistant’
[8/22/2017, 5:21:54 PM] —
[8/22/2017, 5:21:54 PM] Loaded config.json with 0 accessories and 1 platforms.
[8/22/2017, 5:21:54 PM] —
[8/22/2017, 5:21:54 PM] Loading 1 platforms…
[8/22/2017, 5:21:54 PM] [HomeAssistant] Initializing HomeAssistant platform…
[8/22/2017, 5:21:54 PM] [HomeAssistant] Fetching HomeAssistant devices.
[8/22/2017, 5:21:54 PM] Loading 0 accessories…
[8/22/2017, 5:21:54 PM] [HomeAssistant] Received event: ping
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Ar condicionado da suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Display ar da sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Display ar do quarto’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Ar condicionado da sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Ar condicionado do quarto’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Display ar da suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Temperatura externa’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz da TV da suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz do banheiro da suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz do corredor’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz do banheiro social’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz principal do quarto’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz principal da sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz da mesa de jantar’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz da entrada’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz principal da cozinha’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz do balcão da cozinha’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz principal da suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luz da TV da sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Garagem de dentro do trabalho’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Garagem de casa’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Garagem da rua do trabalho’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Persiana quarto’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Tv LG suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Tv LG quarto’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Tv LG sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Humidade na sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Luminosidade sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Temperatura na sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Temperatura na suíte’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Alarme da casa’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Desktop’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘Home Theater sala’…
[8/22/2017, 5:21:55 PM] [HomeAssistant] Initializing platform accessory ‘alarme casa’…
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 123-45-678 │
└────────────┘
[8/22/2017, 5:21:55 PM] Homebridge is running on port 51826.
This platform accessory ‘alarme casa’ is totally new, I have no idea what it is and can not find on my YAML files…
No problem @frenck! I really appreciate you work here. I will try to uninstall and reinstall everything again when I get home. Thanks my friend!
1 Like
Any update on why homebridge isn’t showing up in the home app?
Did you check to see if it is started?
Not joking. I restarted my Pi yesterday after the update, and when I did Homebridge stopped working. After some digging, I found out that even with auto start selected, it did not boot and I had to start it manually.
Been working like a champ since, but still…
Yes all started. @frenck is aware of the issue as it’s effecting a few of us but he wasn’t sure what was causing it. Still happening running latest version of HASSIO (0.52) and homebridge add-on (1.0.3).
Ok, I did not check all the way through the thread; thanks. Nice to know it’s not just 0.52 issue then.
Confirming empty Home app for me too (Homebridge addon 1.0.3, HassIO 0.52. I have config.json with “default_visibility” set to “visible”
“platforms”: [
{
“platform”: “HomeAssistant”,
“name”: “HomeAssistant”,
“host”: “http://172.17.0.1:8123”,
“password”: “”,
“default_visibility”: “visible”,
“supported_types”: [ “binary_sensor”, “climate”, “cover”, “device_tracker”, “fan”, “group”, “input_boolean”, “light”, “lock”, “media_player”, “scene”, “sensor”, “switch” ], …
I even set:
customize_domain: switch: homebridge_hidden: false
to configuration.yaml but I still have "homebridge_hidden": true for every element in Homebridge logs.