Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Two indentical coordinators conflict #24

Open
ajunio3 opened this issue Jan 18, 2023 · 2 comments
Open

Two indentical coordinators conflict #24

ajunio3 opened this issue Jan 18, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@ajunio3
Copy link

ajunio3 commented Jan 18, 2023

I'm using 2 LAN POE coordinators in my 2 Z2M instances. Changed their hostnames and topics, but the ESP32 MQTT monitor is under conflict because it claims the device is already conected (see the broker log)

It seems it keeps using the standard device name "ZigStarGW-7348" for both disregarding the change in hostnames

image

First coordinator
image
image

Second one
image
image

@ajunio3
Copy link
Author

ajunio3 commented Jan 19, 2023

Doing some resarch, looks its the MQTT Client ID introduced in FW 0.6.0. But it seeems uses the same for both coordinators, disregarding the hostnames (nor the MQTT topic) inputs

image

@xyzroe
Copy link
Owner

xyzroe commented Jan 19, 2023

Indeed, according to this line, 4 characters from the MAC address are used to determine the ID, but not the last two blocks, but before the last ones. In your case, both coordinators use MAC addresses that differ only in the last block, which is not used.
I'll fix it in the next update.

@xyzroe xyzroe added the bug Something isn't working label Jan 19, 2023
Repository owner deleted a comment from medjaiiii Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants