search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.59k stars 29.91k forks source link

New devices not shown in Homekit-Controller #68063

Closed badewanne1234 closed 2 years ago

badewanne1234 commented 2 years ago

The problem

I have several cover entities controlled via Homekit-Controller. The covers are paired with the Somfy Tahoma Gateway and the latter is paired to Homekit-Controller. Recently, I have added a Velux Window and a Velux Window-Shutter to my environment. Both are HomeKit compatible.

After I added them to the Somfy Tahoma Box, the two devices were instantly added to HA in the Overkiz integration, but unfortunately not in the HomeKit-Controller integration.

I restarted the HK integration as well as HA itself, without luck. The two devices are also not listed in the entity-map of HK (.storage) I also reloaded the HK integration without luck.

What can I do to add have the two devices visible in HK?

I tried it with HA 2022.2.x and now upgraded to HA 2022.3.3 but that did not solve the problem either.

What version of Home Assistant Core has the issue?

core-2022.3.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

homekit_controller

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit_controller

Diagnostics information

There is nothing (new) in the entity-map and nothing in the standard logs

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

homekit_controller documentation homekit_controller source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

bdraco commented 2 years ago

AFAIK these boxes only support limited set of devices via HomeKit. It's likely your new devices aren't supported by the gateway.

Jc2k commented 2 years ago

I don't know anything about that particular gateway but if it's not in the entity map there's nothing we can do. The entity map has every characteristic, service and accessory the gateway exports. If it's not in there then the gateway isn't telling us about it.

The API we use to fetch that map is pretty much all of nothing, it's not like we are mishandling something, what you see is pretty much what was returned by the device.

The only things you could try are (a) using an iOS device to prove it's a problem with the gateway or (b) backup and delete the entity map. Restart HA. That will force HA to refresh the map. This will only help if the map was stale, and it probably isn't going to do anything based on what you've said.

badewanne1234 commented 2 years ago

Thanks for the quick responses. When I delete the entity-map, does that mean it will be regenerated on the next reload/reboot automatically?

Regardless, obviously there is a compatibiliy list by Somfy: https://service.somfy.com/downloads/fr_v5/tahoma-homekitcompatibilitylist_general_en.pdf

Velux Stuff is not listed there, thanks for the hint @bdraco I will revert back to Somfy to double-check and, because the list is from Nov 2020. Will get back to this thread with the feedback.

Jc2k commented 2 years ago

Yes, the entity map is really just a cache of what the API returns. If it's not there HA will fetch the latest one at startup.

On a functioning deployment it won't help because the gateway should broadcast when the entity map needs refreshing, so it should already be up to date. This is how when i pair a new device with one of my Hue or Aqara gateways the new device instantly pops up in the devices list.

It will only change anything if your router was blocking zeroconf traffic for example or if your gateway wasn't following the spec and wasn't broadcasting an entity map change.

iMicknl commented 2 years ago

As far as I know, Velux devices are not exposed via the HomeKit interface unfortunately.

badewanne1234 commented 2 years ago

Checked with Somfy, answer was straight away: no devices from other brands than Somfy are supported, and its not planned at this stage either (not even all Somfy products are supported, they stated). I will get a KLG 300 gateway from Velux to add them to HomeKit.

Thanks for the help and clarification, much appreciated.

badewanne1234 commented 2 years ago

Just FYI. I got the Velux KIG-300 gateway and was able to pair the Velux window and shutter, they are now exposed via that gateway in HA/Homekit-controller. Be aware, if you paired the Velux window/shutter already with the Tahoma Box, you cant pair them with the Velux Gateway straight away, since a security key has already been assigned to the window and shutter by Tahoma.

Instead, you need to send the key from the Tahoma Box and set the Velux Gateway into receiving mode (press the button with a pen, next to the key-sign on the back of the gateway).

As a bonus, all Somfy io blinds have been added to the Velux Gateway too, and are exposed in HA/Homekit. So, you could get rid of the Tahoma Box unless you have RTS stuff in place.

iMicknl commented 2 years ago

@badewanne1234 great to hear! By the way, would it be possible for you to (temporarily) configure the Overkiz integration in core? I would love to see an export of your Overkiz diagnostics, to see how the Velux gateway is added.

badewanne1234 commented 2 years ago

@iMicknl sure, not a problem. I have Overkiz installed, but its connected with the Tahoma box. I tried to create a second instance, but there is no Velux to select from the hub list?

iMicknl commented 2 years ago

@iMicknl sure, not a problem. I have Overkiz installed, but its connected with the Tahoma box. I tried to create a second instance, but there is no Velux to select from the hub list?

Just the TaHoma diagnostics. I thought you said that your Velux box was connected to the TaHoma box, thus I did wonder if that would be different in the diagnostics. We try to gather the different (and especially exotic) setups.

badewanne1234 commented 2 years ago

@iMicknl sure, not a problem. I have Overkiz installed, but its connected with the Tahoma box. I tried to create a second instance, but there is no Velux to select from the hub list?

Just the TaHoma diagnostics. I thought you said that your Velux box was connected to the TaHoma box, thus I did wonder if that would be different in the diagnostics. We try to gather the different (and especially exotic) setups.

Oh, no that is a misunderstanding. I edited my post above: I was referring to the Velux window and shutter, which was firstly linked to the Tahomabox. I was now able to link them to the Velux Gateway too.

What I can provide is the Velux Shutter data, that one is still linked to the Tahomabox - would that help?