-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Network Map not working #373
Comments
It looks like this is an issue with the Docker latest image tag - the dev version seems to be ok, but latest doesn't seem to be updated to reflect changes in z2m. |
Is this project dead? Because this bug has been present for more than 4 months .. and last activity on Docker Hub was 8 month ago. |
I think it is. The gui in Z2M itself is great! |
Yes, I agree - it was a very cool project! |
@derekoharrow - have you tried with Z2M 1.19.1? Looks like networkmap is working .. but you need to restart Z2MA or you cannot press the "Launch new network scan" (for me it is the Docker version running in K8S). Anyway; just wanted to share the good news. |
Clicking on Launch New Network Scan doesn't seem to trigger a new network scan in Z2M.
Running a manual network scan in Z2M doesn't seem to update Z2MAssistant.
From looking at this code it seems that Z2MAssistant is looking for topics ending with /bridge/networkmap. In my Z2M setup it seems to be responding with /bridge/response/networkmap, hence isn't being picked-up by Z2MAssistant.
Similarly, I assume that Z2MAssistant is not sending to the correct topic, which should be zigbee2mqtt/bridge/response/networkmap I believe (from the documentation here)
Installation
The text was updated successfully, but these errors were encountered: