Closed marcelopalermo closed 4 years ago
I believe id=3 is not right. The Id numbers are independent between devices. Therefore, in your second accessory try id=1 and set it as primary since it’s the only accessory for this device.
Thanks for your response @peros550 . I believe that I have already tried this combination but I will redo it and will post results here.
Sent with GitHawk
I've tested with id=1 and primary and confirmed the issue persists. Thanks
Sent with GitHawk
First, I recommend using a single accessory definition and just grouping all services inside of it. Second, stop talking about .primary=true
, it has nothing to do with it.
While having both of them connected, can you ping each of them? What does dns-sd -B _hap._tcp local
(command is for macOS) say?
Hi Colleagues,
When I have two flashed ESP8266 within the same WIFi network, HomeKit enters in conflict when adding second one. Due to my house physical reasons, I can't add all the accessories I need under one ESP8226, only.
Details below:
I've got two ESP8266 NodeMCU chips flashed with esp-homekit-demo under the same WiFi network.
It sounds like the two ESP8266 have the very same identity, from Apple HomeKit standpoint. I believe that if HomeKit understands the two ESP8266 chips as different accessories/identities then Apple HomeKit would understand them as independent accessories and would allow adding both ESP8266 #1 and #2. Is this assumption correct?
ESP8266 #1 contains the following code -- before that please notice the following:
ESP98266 #2 has the following code (below at end of this thread), with one accessory only, and .id=3 and primary=false:
I've also tested ESP8266 #2 with .id=1 and .primary=true but issue persists. I've tried other sequences like below (all of them leading to the same issue again):
I'm pretty sure I am missing something on the process and/or architecture. Any help/hints would be much appreciated.
Thanks in advance Regards Marcelo