Homekit: did not remove an accesssory from homekit (after removing homekit metada)

1

@yfre hi, will you be so kind and help me to get rid of an accessory in homekit which was earlier removed from openhab. My homekit app is freezing showing not-responding items (all of them). Put when i click them one after another all of them works. But closing and opening the app gives me the same. The problem is that homekit is requesting a removed accessory 21:04:49.711 [WARN ]

[r.impl.json.CharacteristicsController] - Accessory 1362381210 has no characteristics or does not exist. Request: /characteristics?id=933082717.9,806591347.9,1362381210.13,1362381210.9,1964532893.10,1964532893.12,1263468315.12,1263468315.10,881892342.9,1939556017.9
21:04:49.715 [WARN ] [r.impl.json.CharacteristicsController] - Accessory 1362381210 has no characteristics or does not exist. Request: /characteristics?id=933082717.9,806591347.9,1362381210.13,1362381210.9,1964532893.10,1964532893.12,1263468315.12,1263468315.10,881892342.9,1939556017.9

when the problem appeared after removing and accessorygroup tag from a group conteinig two Lighing.Brightness items.

There were some problem in GUI do remove the metadata but after a while and openhab restart it’s ok but homekit app somehow is still requesting the accessory - and probably this is the reason of not responding items..

2

Hi Jacek,

hm. looks like home app still expects that item, but we dont have it.

we could better handle it.

try following:

  • add new homekit item, e.g. add homekit tag to an existing item without it, or create just any OH item and tag it. this would inform home app that the list of accessories has been change
  • you can remove that items afterwards

if the issue still exist, then it is cached by Homekit bridges, e.g. Apple TV, homepad, switch them off and try the steps above.

3

Thank you, indeed adding new items somehow resolved the issue in homekit app, not sure what was the final solution but it’s ok now and the accessory list in the app is the same as in openhab right now

1 Like
4

basically, for some reasons, Homekit binding has missed the changes you did and therefore has not informed Home app about it. so, the proper fix would be fix this root cause.

or as workaround, if we get request for an item we dont have, we should inform home app about changes.

5

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.