homekit | Home Assistant | Page 1

livid pewter Aug 9, 2021, 9:06 AM

#

no i don’t. almost all zwave stuff

#

i need to sleep now (4am) and i’ll play w a new HA instance / new home instance when i’m less exhausted.

chrome mantle Aug 9, 2021, 9:08 AM

#

all right

livid pewter Aug 9, 2021, 9:09 AM

#

but from what i can tell it’s something in our setups like you’ve found since there are other issues ppl are reporting on 8.* w homekit other than “it’s not connecting” lol

chrome mantle Aug 9, 2021, 9:09 AM

#

hmm

#

I'll check the forums

#

https://community.openhab.org/t/homekit-accessory-out-of-compliance-3-1-0m2/118294

#

maybe this is somehow related

abstract dragon Aug 10, 2021, 12:55 AM

#

I have just updated to core-2021.8.4 and am experiencing unusual stuff via the HomeKit integration. I use LocalTuya and have created a number of lightgroups. All of these have been working as expected including colour control. After updating I have gained a bunch of new devices in homekit. The old devices now result in unexpected colours (and brightness) when selected, and result in some of the new devices (which appear to relate to colour and brightness of individual lights) but do not behave sanely. I have rolled back to the previous version but would appreciate any pointers to debug so I can update.

sharp jacinth Aug 10, 2021, 1:52 AM

#

hmm im having homekit issues in 8.4 aswell

#

completely broken after update, restoring snapshot of 7.4 fixed it immediately

abstract dragon Aug 10, 2021, 1:53 AM

#

Even the exclude part of the homekit integration seems to have no effect

#

Also noticed a delay on activating / deactivating devices in homekit

sharp jacinth Aug 10, 2021, 1:54 AM

#

interesting, my bridge doesnt even connect after 8.4 update

#

tested 8.0 as well, same behavior

#

restoring snapshot of 7.4 immediately fixes it, tested many times no progress on a solution though

livid pewter Aug 10, 2021, 2:03 AM

#

abstract dragon I have just updated to core-2021.8.4 and am experiencing unusual stuff via the H...

there is a thread in one of the hass github issues about this - the 8. something added a temperature and color panel which made homekit see it as two devices... it sounds like it will get rolled back at some release?

#

re: total HK fail i'm going to try to see if i can create a second HASS on another machine and try to connect it to a new Home

sharp jacinth Aug 10, 2021, 2:08 AM

#

Gotcha, I've tried a number of things, nothing relevant in the debug logs -- tested a bunch of mDNS stuff because I did also swap my firewall a while ago -- it is interesting that it works immediately perfectly after restoreing a 7.4 snapshot

livid pewter Aug 10, 2021, 2:08 AM

#

are you running os / supervised or plain core?

sharp jacinth Aug 10, 2021, 2:08 AM

#

os /docker on esxi

livid pewter Aug 10, 2021, 2:09 AM

#

i am running a core only on macos so i never know if its that setup or what causing issues

sharp jacinth Aug 10, 2021, 2:09 AM

#

fortigate fg60f with multicast setup and appearing to be working

abstract dragon Aug 10, 2021, 2:09 AM

#

homekit integration seems to ignore the excludes. I am on a RPI4 Supervised

livid pewter Aug 10, 2021, 2:10 AM

#

hmmmm... i cannot even get a fresh install of 8.4 to run w/o any of my old config

livid pewter Aug 10, 2021, 2:57 AM

#

n/m i am eejit and forgot to install some python libs on this new machine

#

when 7.4 failed to start fresh i knew i had borked

livid pewter Aug 10, 2021, 3:48 AM

#

i think it has something to do with some zeroconf errors i'm seeing on 8.4 and not on 7.4

#

Traceback (most recent call last):
  File "/usr/local/Cellar/python@3.9/3.9.6/Frameworks/Python.framework/Versions/3.9/lib/python3.9/asyncio/selector_events.py", line 1056, in sendto
    self._sock.sendto(data, addr)
OSError: [Errno 65] No route to host```

#

with debug logging turned on for zeroconf i got this:

#

2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] Created socket <socket.socket fd=20, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 5353, 0, 0)>
2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] Adding (('', 0, 0), 0) (socket 20) to multicast group
2021-08-09 22:43:20 INFO (MainThread) [zeroconf] Address not available when adding (('', 0, 0), 0) to multicast group, it is expected to happen on some systems
2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] Adding '0.0.0.0' (socket 20) to multicast group
2021-08-09 22:43:20 INFO (MainThread) [zeroconf] Interface of 0.0.0.0 does not support multicast, it is expected in WSL
2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] Listen socket <socket.socket fd=20, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 5353, 0, 0)>, respond sockets [<socket.socket fd=20, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_DGRAM, proto=0, laddr=('::', 5353, 0, 0)>]
2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] offsets = questions=0, answers=0, authorities=0, additionals=0
2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] lengths = questions=37, answers=0, authorities=0, additionals=0
2021-08-09 22:43:20 DEBUG (MainThread) [zeroconf] now offsets = questions=37, answers=0, authorities=0, additionals=0

#

oh. nvm digging in and now i found this github error that is being worked on... https://github.com/home-assistant/core/issues/54196

#homekit