Home Assistance devices not exposed in HomeKit (everything is installed)

Hello ppl,

I am new to Home Assistant and Homebridge, but I do have an extensive tech background. So half-noob here.
Please help me to figure this out:

I bought and configured Rasbery Pi 3. I have both latest Home Assistant and Homebridge installed and configured and running from autostart as daemons. HomeAssistant runs as “homeassistant” account and Homebridge as “homebridge” account.

HomeAssistant works and I can see my Sonos system and Android TV on it and I can start stop Sonos and TV from Home Assistant.

Homebridge also works I can install “homebridge” plugins and also I have paired “homebridge” with my HomeKit and it showing up on my iPhone in HomeKit (HomeApp) in “Default Room”

Last, I installed and configured home-assistant-homebridge plugin for HomeAssistant: https://github.com/home-assistant/homebridge-homeassistant. This integration also works as I can see logs on both sides and below are logs of my Homebridge receiving events from HomeAssistant.

So everything seem working as far as installation is concerned.

THE PROBLEM:

MY devices from HomeAssistant (Sonos and Android TV), do not show up in my HomeKit app on iPhone. The plugin has NO instructions on how to add those devices as “light switch” (for media player). It just states that they (devices) will “automatically” show up in HomeKit exposed as “light switch”

So my assumption is that the phrase “it exposes” it as a light switch means I do NOT need to add any configuration changes in my Homebridge. ?? The MediaPlayer (Sonos) should just “appear” on my iPhone as a switch.
But this does not happen. Neither TV or Sonos show up.

Please help with any ideas of what can be wrong and what I need to do to make it happen?

Thank you very much in advance for your help. I promise soon to become useful contributor to this forum. But at this moment, I am still somewhat lost :slight_smile:

My Homebridge config file in: /var/lib/homebridge/config.json

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
    },

    "platforms": [
     {
    "platform": "HomeAssistant",
    "name": "HomeAssistant",
    "host": "http://localhost:8123",
    "password": "xxxxxxxx.",
    "supported_types": ["binary_sensor", "climate", "cover", "device_tracker", "fan", "group", "input_boolean", "light", "lock", "media_player", "scene", "sensor", "switch"],
    "logging": true
    }
    ]
}

Logs of HomeAssistant sending events to Homebridge. (logs are from HomeBridge Side ):_

May 07 08:47:02 HomeControl homebridge[710]: [5/7/2017, 8:47:02 AM] [HomeAssistant] Received event: {"origin": "LOCAL", "time_fired": "2017-05-07T00:47:02.590054+00:00", "data": {"new_state": {"attributes": {"media_content_id": "Alaake", "media_position": 0, "media_position_updated_at": "2017-05-07T00:45:15.209189+00:00", "media_title": "Alaake", "media_artist": "Deep Forest", "supported_features": 31295, "media_album_name": "Deep Africa", "source_list": ["BBC Radio 4", "BBC World Service News", "Bloomberg Radio", "Chill", "FOX News Talk", "Long Ambients1: Calm. Sleep.", "NPR Program Stream", "Ocean by Ocean", "Radio Kansas", "Sleep Sounds", "WAMU", "WNPR", "\u041d\u0430\u0448\u0435 \u0420\u0430\u0434\u0438\u043e", "Line-in", "TV"], "friendly_name": "Living Room", "media_content_type": "music", "entity_picture": "/api/media_player_proxy/media_player.living_room?token=e25a9b2458463e65f7d1e334113e64307bc967c0d4ccbb5a5c01543942056587&cache=232ce", "media_duration": 221, "is_coordinator": true, "is_volume_muted": false, "volume_level": 0.31}, "last_changed": "2017-05-07T00:46:55.610427+00:00", "state": "paused", "last_updated": "2017-05-07T00:47:02.589885+00:00", "entity_id": "media_player.living_room"}, "old_state": {"attributes": {"media_content_id": "Alaake", "media_position": 0, "media_position_updated_at": "2017-05-07T00:45:15.209189+00:00", "media_title": "Alaake", "media_artist": "Deep Forest", "supported_features": 31295, "media_album_name": "Deep Africa", "source_list": ["BBC Radio 4", "BBC World Service News", "Bloomberg Radio", "Chill", "FOX News Talk", "Long Ambients1: Calm. Sleep.", "NPR Program Stream", "Ocean by Ocean", "Radio Kansas", "Sleep Sounds", "WAMU", "WNPR", "\u041d\u0430\u0448\u0435 \u0420\u0430\u0434\u0438\u043e", "Line-in", "TV"], "friendly_name": "Living Room", "media_content_type": "music", "entity_picture": "/api/media_player_proxy/media_player.living_room?token=e25a9b2458463e65f7d1e334113e64307bc967c0d4ccbb5a5c01543942056587&cache=d849d", "media_duration": 221, "is_coordinator": true, "is_volume_muted": false, "volume_level": 0.31
May 07 08:47:02 HomeControl homebridge[710]: }, "last_changed": "2017-05-07T00:46:55.610427+00:00", "state": "paused", "last_updated": "2017-05-07T00:46:55.610427+00:00", "entity_id": "media_player.living_room"}, "entity_id": "media_player.living_room"}, "event_type": "state_changed"}
May 07 08:47:02 HomeControl homebridge[710]: [5/7/2017, 8:47:02 AM] [HomeAssistant] Received event: {"origin": "LOCAL", "time_fired": "2017-05-07T00:47:02.590054+00:00", "data": {"new_state": {"attributes": {"media_content_id": "Alaake", "media_position": 0, "media_position_updated_at": "2017-05-07T00:45:15.209189+00:00", "media_title": "Alaake", "media_artist": "Deep Forest", "supported_features": 31295, "media_album_name": "Deep Africa", "source_list": ["BBC Radio 4", "BBC World Service News", "Bloomberg Radio", "Chill", "FOX News Talk", "Long Ambients1: Calm. Sleep.", "NPR Program Stream", "Ocean by Ocean", "Radio Kansas", "Sleep Sounds", "WAMU", "WNPR", "\u041d\u0430\u0448\u0435 \u0420\u0430\u0434\u0438\u043e", "Line-in", "TV"], "friendly_name": "Living Room", "media_content_type": "music", "entity_picture": "/api/media_player_proxy/media_player.living_room?token=e25a9b2458463e65f7d1e334113e64307bc967c0d4ccbb5a5c01543942056587&cache=232ce", "media_duration": 221, "is_coordinator": true, "is_volume_muted": false, "volume_level": 0.31}, "last_changed": "2017-05-07T00:46:55.610427+00:00", "state": "paused", "last_updated": "2017-05-07T00:47:02.589885+00:00", "entity_id": "media_player.living_room"}, "old_state": {"attributes": {"media_content_id": "Alaake", "media_position": 0, "media_position_updated_at": "2017-05-07T00:45:15.209189+00:00", "media_title": "Alaake", "media_artist": "Deep Forest", "supported_features": 31295, "media_album_name": "Deep Africa", "source_list": ["BBC Radio 4", "BBC World Service News", "Bloomberg Radio", "Chill", "FOX News Talk", "Long Ambients1: Calm. Sleep.", "NPR Program Stream", "Ocean by Ocean", "Radio Kansas", "Sleep Sounds", "WAMU", "WNPR", "\u041d\u0430\u0448\u0435 \u0420\u0430\u0434\u0438\u043e", "Line-in", "TV"], "friendly_name": "Living Room", "media_content_type": "music", "entity_picture": "/api/media_player_proxy/media_player.living_room?token=e25a9b2458463e65f7d1e334113e64307bc967c0d4ccbb5a5c01543942056587&cache=d849d", "media_duration": 221, "is_coordinator": true, "is_volume_muted": false, "volume_level": 0.31
May 07 08:47:02 HomeControl homebridge[710]: }, "last_changed": "2017-05-07T00:46:55.610427+00:00", "state": "paused", "last_updated": "2017-05-07T00:46:55.610427+00:00", "entity_id": "media_player.living_room"}, "entity_id": "media_player.living_room"}, "event_type": "state_changed"}

I managed to find a work around… To make things work I basically just moved “media_plugin” to be first in the list. And things started working…

So from this:

"platforms": [
     {
    "platform": "HomeAssistant",
    "name": "HomeAssistant",
    "host": "http://localhost:8123",
    "password": "YOURPASSWORD.",
    "supported_types": [ "binary_sensor", "climate", "cover", "device_tracker", "fan", "group", "input_boolean", "light", "lock","scene", "media_player", "sensor", "switch"],
    "logging": true
    }
    ]

It became this: (note how “media_player” moved to the front of the list)

"platforms": [
     {
    "platform": "HomeAssistant",
    "name": "HomeAssistant",
    "host": "http://localhost:8123",
    "password": "YOURPASSWORD.",
    "supported_types": ["media_player", "binary_sensor", "climate", "cover", "device_tracker", "fan", "group", "input_boolean", "light", "lock","scene", "sensor", "switch"],
    "logging": true
    }
    ]
1 Like

hi there,

I’m experiencing a similar issue too. I don’t see any exposed service either. May I ask, did you do any further action in order to flush the configuration onto homekit?

thanks

If you still cannot use homebridge. I will post my config this evening. I use hassbian and raspbian not hass.io

I assume that setting shoud be the same. the different is the way to install.

If your homebridge run successfully but no device expose from HA which you are not sure that from homebridge side or from HA side. check your config.json whether you have this option.

"platforms": [{
"platform": "HomeAssistant",
"name": "HomeAssistant",
"host": "http://homeassistantipaddress:8123",  <== can be local ip address or dynamic name by duckdns can be https if you use let's encrypt
"password": "passwordofhomeassistant",
"supported_types": ["alarm_control_panel", "automation", "binary_sensor", "climate", "cover", "device_tracker", "fan", "group", "input_boolean", "light", "lock", "media_player", "remote", "scene", "script", "sensor", "switch", "vacuum"],  all domain that homebridge knows
"default_visibility": "visible",  <==== change this part from hidden to visible
"logging": true,
"verify_ssl": false  <== if you didn't use let's encrypt / if use let's encrypt change to true
   },

on HA part. configuration.yaml in customize:

homeassistant:
  customize:
    switch.kitchen_aircon:
      friendly_name: Kitchen Aircon
      homebridge_hidden: true  <== true to hide false to show
    switch.kitchen_light_2:
      friendly_name: Kitchen Light
      homebridge_hidden: true  <== true to hide false to show

Thanks a million! Will review it and get back. Many thanks

I still can’t make this to work. I wonder how to narrow down where the source of the problem is, either on HA or on Homebridge. I’ve reviewed my configuration and it pretty much matches what you indicate, therefore my question.

I would appreciate your feedback

Have you mange homebridge to run?
If you can run homebridge already, then next proceed is to expose devices from HA to homebridge by customize platform from HA

I manage to go as far as to see in the Home app on my iPhone a device called Home Assistant. It sits right there and I can tap on it, but it won’t do a thing. I did replicate your configuration where I think it makes sense in hass.io, and the customize part goes into the file customize.yaml, which configuration.yaml uses. Not sure how to troubleshoot this.

in config.json did you put these in, if you put in without customize in ha it should be able to see accessories in homekit.
“supported_types”: [“alarm_control_panel”, “automation”, “binary_sensor”, “climate”, “cover”, “device_tracker”, “fan”, “group”, “input_boolean”, “light”, “lock”, “media_player”, “remote”, “scene”, “script”, “sensor”, “switch”, “vacuum”],
“default_visibility”: “visible”,

in customize platform on HA side. This to customize the name to be seen in homebridge and whether to be seen in homebridge.

By doing both mentioned above you have to stop homeassistant and stop homebridge then start all again.

Thanks for that. I’m at work and can’t access HA from my work computer. I believe I’ve done everything above. I will paste here the different configuration files, but as I’m running hass.io, locations definitely differ from yours. I’ll do it when I’m back home tonight.

hello, this is my configuration:

core-ssh:~# cat /config/homebridge/config.json 
{
  "bridge": {
    "name": "Home Assistant",
    "username": "xx:yy:ee:jj:cc:ee",
    "port": 51826,
    "pin": "xxx-xx-xxx"
  },
  "description": "Homebridge for Home Assistant",
  "accessories": [],
  "platforms": [
    {
      "platform": "HomeAssistant",
      "name": "HomeAssistant",
      "host": "http://hassio/homeassistant",
      "password": "",
      "default_visibility": "hidden",
      "supported_types": [
        "cover",
        "scene",
        "switch",
        "media_player",
        "automation",
        "binary_sensor",
        "climate",
        "device_tracker",
        "fan",
        "group",
        "input_boolean",
        "light",
        "lock",
        "remote",
        "script",
        "sensor",
        "vacuum"
      ],
      "logging": true,
      "verify_ssl": true
    }
  ]
}

configuration.yaml:

core-ssh:~# cat /config/configuration.yaml
homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: xx.4846
  longitude: yy.---5
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: ---
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here:
  List_of_tz_database_time_zones
  time_zone: Europe/---
  # Customization file
  customize: !include customize.yaml

and customize.yaml:

core-ssh:~# cat /config/customize.yaml 
    zwave.dinning_room_shutter:
      friendly_name: Persiana menjador
      homebridge_hidden: false

I really think it very much matches your configuration in terms of content, right?

thanks

from your config.json
username as to be in Capital letter “username”: “xx:yy:ee:jj:cc:ee” if doesn’t change it.
default_visibility change from hidden to visible “default_visibility”: “visible”,
“host”: “http://hassio/homeassistant”, <== since you didn’t use let’s encrypt. change “verify_ssl”: true to false / also don’t forget to put port 8123. http://hassio/homeassistant:8123

from ha. your configuration and customize look fine.
the zwave.dinning_room_shutter is the cover? and you put this under which platform in HA?

Many thanks, I’ve review and corrected where applicable. It still does not work and I’m having trouble with pairing this now with my Home.app on my iPhone. Not sure what is happening. There may be a problem with HomeKit itself, I don’t know… Let’s just assume it is not my fault but a temporary problem when registering new devices.
If I go to the homebridge log output displayed in hass.io, I see this:

Server startup complete. Host name is hassio.local. Local service cookie is 307084472.
*** 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>
[2018-2-1 22:28:36] Loaded plugin: homebridge-homeassistant
[2018-2-1 22:28:36] Registering platform 'homebridge-homeassistant.HomeAssistant'
[2018-2-1 22:28:36] ---
[2018-2-1 22:28:36] Loaded config.json with 0 accessories and 1 platforms.
[2018-2-1 22:28:36] ---
[2018-2-1 22:28:36] Loading 1 platforms...
[2018-2-1 22:28:36] [HomeAssistant] Initializing HomeAssistant platform...
[2018-2-1 22:28:36] [HomeAssistant] Fetching HomeAssistant devices.
[2018-2-1 22:28:36] Loading 0 accessories...
[2018-2-1 22:28:36] [HomeAssistant] Received event: ping
[2018-2-1 22:28:36] [HomeAssistant] 'cover.dinning_room_shutter_level' is a cover but does not have a 'homebridge_cover_type' property set. You must set it to either 'rollershutter' or 'garage_door' in the customize section of your Home Assistant configuration. It will not be available to Homebridge until you do. See the README.md for more information. The attributes that were found are: {"current_position":0,"friendly_name":"Dinning room shutter Level","new_entity_id":"cover.dinning_room_shutter_level","node_id":2,"old_entity_id":"cover.dinning_room_shutter_level_2_0","power_consumption":0,"supported_features":15,"value_id":"72057594076299265","value_index":0,"value_instance":1}

I think there is something missing in customize.yaml. I’ve been online for a while looking for the answers and adding this to that file, does not address the issue either.

core-ssh:~# cat /config/customize.yaml 
    zwave.dinning_room_shutter:
      friendly_name: Persiana menjador
      homebridge_cover_type: rollershutter
      homebridge_hidden: false

Back to your last question, yes it is a zwave rollershutter by Fibaro.

Any thoughts on this? thanks a lot :slight_smile:

[quote=“kitus, post:15, topic:17249, full:true”]
It still does not work and I’m having trouble with pairing this now with my Home.app on my iPhone. Not sure what is happening. There may be a problem with HomeKit itself, I don’t know… [/quote]

Just found this on the log output:

[2018-2-1 22:29:26] [HomeAssistant] Received event: ping
[2018-2-1 22:29:30] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.21, "azimuth": 294.54, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:28:30.878346+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.38, "azimuth": 294.79, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:29:30.878027+00:00"}}, "origin": "LOCAL", "time_fired": "2018-02-01T21:29:30.878173+00:00"}
[2018-2-1 22:30:20] [HomeAssistant] Received event: ping
[2018-2-1 22:30:30] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.38, "azimuth": 294.79, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:29:30.878027+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.55, "azimuth": 295.05, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:30:30.878483+00:00"}}, "origin": "LOCAL", "time_fired": "2018-02-01T21:30:30.878621+00:00"}
[2018-2-1 22:31:20] [HomeAssistant] Received event: ping
[2018-2-1 22:31:30] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.55, "azimuth": 295.05, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:30:30.878483+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.72, "azimuth": 295.3, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:31:30.879247+00:00"}}, "origin": "LOCAL", "time_fired": "2018-02-01T21:31:30.879407+00:00"}
[2018-2-1 22:32:20] [HomeAssistant] Received event: ping
[2018-2-1 22:32:30] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.72, "azimuth": 295.3, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:31:30.879247+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2018-02-02T06:33:33+00:00", "next_dusk": "2018-02-02T17:37:12+00:00", "next_midnight": "2018-02-02T00:05:26+00:00", "next_noon": "2018-02-02T12:05:23+00:00", "next_rising": "2018-02-02T07:02:51+00:00", "next_setting": "2018-02-02T17:07:54+00:00", "elevation": -48.89, "azimuth": 295.56, "friendly_name": "Sun"}, "last_changed": "2018-02-01T21:23:26.128661+00:00", "last_updated": "2018-02-01T21:32:30.878912+00:00"}}, "origin": "LOCAL", "time_fired": "2018-02-01T21:32:30.879059+00:00"}

any idea what is going on?

thanks

If your device is binary_sensor or cover you can put device_class in customize
from this setting add device_class:
To see what can be put in device_class look here

I have installed the addon 2 days and reinstalled again today and I confirm it is working so it is certain that it is your fault.

In Homebridge folder change the configuration from:
"default_visibility": "hidden",
to:
"default_visibility": "visible",

Save and delete both folders leaving only the configuration.
In Hassio reboot the addon and pray hard it works :stuck_out_tongue:

@Kitus:

I’m not sure how far you are into Home Assistant or how many devices you’ve added to it. I’m guessing not many at all since you’ve now set default_visiiblity to visible, which will send all of your entities to Homebridge. You should be seeing something like a light or something at least if any exist in your system. Anyhow, moving forward, as you add more devices, this probably isn’t the best approach since it’s going to expose everything and I’m sure you don’t want a cluttered Home app. Better is to set default_visibility to hidden, and then expose per entity in customize.yaml as you’ve done (homebridge_hidden: false).

Moving on to the current problem. The reason your roller shutter isn’t appearing is because you’re customizing zwave.dinning_room_shutter with homebridge_cover_type but you should instead be customizing cover.dinning_room_shutter (as the Homebridge logs told you!). “Zwave” entities are created by the Zwave component as information type devices but the Zwave component will also create the correct type of entity depending on the device, in this case a cover (on your entities page you’ll also find cover.dinning_room_shutter - this is the entity that you should use to control your device).

Add homebridge_cover_type: rollershutter to cover.dinning_room_shutter in customize.yaml, restart Home Assistant, then restart Homebridge. I’m sure it will appear.

If you’re still having problems pairing Homebridge with your Home app, try incrementing the username, port, and pin in your Homebridge config.json. HomeKit is terrible about caching and sometimes won’t re-pair if you’ve already paired several times.

Thank you so much for trying to help me. I’m attaching a snapshot of what I see in my dev tools. The entity_id seems to be that, right?

Do you see any information valuable on it?
thanks a lot,

You got me! :slight_smile: I installed hass.io last weekend and haven’t had the chance to play with it much. I guess my questions gave me away :slight_smile:

well yes, that and also that was one of the settings I changed out of desperation to be honest. I thought, well, let’s just see if I get to see at least all of the items, and once I’m there, I will start filtering out what I don’t want to see

thanks for the tip. Will definitely follow your advice.

I promise I’ve tried as many combinations I come to think of, but still I can’t have my rollershutter to be shown in the Home app.

Agreed. Thanks for that too. As I said, I’ve tried several combinations (changed customize.yaml to cover.dinning_room_shutter and restarted homebridge → nothing. changed it to cover.dinning_room_shutter_level and restarted HA and homebrig → nothing. changed it to cover.dinning_room_shutter and restarted HA and hombredige → nothing.

core-ssh:/# cat /config/customize.yaml
    cover.dinning_room_shutter:
      homebridge_cover_type: rollershutter
      friendly_name: Persiana menjador
      homebridge_hidden: false

I don’t know what it is but Hombredige keeps complainig

[2018-2-2 23:55:05] [HomeAssistant] 'cover.dinning_room_shutter_level' is a cover but does not have a 'homebridge_cover_type' property set. You must set it to either 'rollershutter' or 'garage_door' in the customize section of your Home Assistant configuration.

Here you hit the nail on its head. I needed to change all these values or I would be able to re-pair it.

I feel a little dumb asking for further help, but I’m kind of lost after testing all these things. Would appreciate your help.