#Now it's at value 1

1 messages · Page 1 of 1 (latest)

tired bridge
#

Best start a thread or its going to get a bit hard to follow

#

Is HA now showing it as discovered?

vague dawn
#

Home assistant now has it discovered as a Home kit device. And the strip is connected to my Thread

tired bridge
#

and if you follow the prompts in HA to add it? does it work?

#

if not, im guessing there will be an error in the log and i'll need that error

vague dawn
#

Inside of home assistant there is just the error of M5: Not an error or a proof.

I will get the logs on a sec

tired bridge
#

ok thats no good

#

i've helped a bunch of people with this device; it should work. And M5 is pretty much one of the last steps.

#

can you also check if sf has flipped back to 0?

vague dawn
#

It's back at 0

tired bridge
#

can you reset and try again, but this time turn on logging for aiohomekit in your configuration.yml

#

logger:
default: critical
logs:
aiohomekit: debug

#

something like that

vague dawn
tired bridge
#

i think i need more logs

#

do you have other homekit over thread devices?

vague dawn
#

no, but there were old entries of the same strip, which should be gone by now

tired bridge
#

this is weird

#

2024-08-16 12:44:20.792 DEBUG (MainThread) [aiohomekit.controller.ip.connection] Starting reconnect loop to ['172.24.0.1', '172.17.0.1', '172.18.0.1', '172.19.0.1', '172.21.0.1', '172.22.0.1', '192.168.178.70', '192.168.178.20', 'fd76:38d8:52f:5b5:ed08:9ea0:282c:d93b', 'fd76:38d8:52f:5b5:4b37:9980:bfa0:ef4f']:51235

#

(its homebridge, and not related, but its weird that its advertising on so many networks)

vague dawn
#

this looks like it tried some of the network modules the container has available cause the first 6 are all bridges and the next 2 are lan and wlan and the ipv6 idk

tired bridge
#

so... it kinda looks like it worked in these logs

#

i can see it polling a thread device once a minute at the end

vague dawn
#

funny thing, id did work, the device is inside of HA

#

idk when it appeared but now it did

tired bridge
#

weird

vague dawn
#

but at least it worked.
i will watch out if anything weird will appear, cause there are some things i wanted to test, but for now it seems to be doing fine

tired bridge
#

👍

vague dawn
#

and of course thanks for the time and support of trying to find whats wrong

tired bridge
#

hoping it was just a blip in the device

#

the nanoleaf thread firmware before matter and before a couple months ago was not great