You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
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
First coordinator
Second one
The text was updated successfully, but these errors were encountered:
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
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.
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
First coordinator
Second one
The text was updated successfully, but these errors were encountered: