-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error network map after pairing GL-C-008-2ID #3623
Comments
Can you share your |
GL-C-008-2ID shown GL-C-007
|
I have the same problem since I upgraded to 0.13.1. It was working fine in 0.13 |
Can you replace |
It's same..
|
I would expect some logging above it this error now. (coming from the |
It's log from start scan to finish scan
|
Can you try replacing |
changing log - at /app/lib/extension/networkMap.js:74:61
|
Can you change it to |
How can I set logger,infor(DEBUG + JSON)??
|
can you try replacing the |
Here is logs.
|
Found the issue, should be fixed in latest dev branch now. Please confirm. |
Okey. Thanks. |
I checked it works good. Thanks~ |
Cool! thanks for confirming. |
Bug Report
What happened
Error network map after device(GL-C-008-2ID) pairing.
zigbee2mqtt:info 2020-05-28 09:52:52: Network scan finished
zigbee2mqtt:error 2020-05-28 09:52:52: Failed to call 'NetworkMap' 'onMQTTMessage' (TypeError: Cannot read property 'map' of undefined
at fingerprintMatch (/app/node_modules/zigbee-herdsman-converters/index.js:75:42)
at Object.findByDevice (/app/node_modules/zigbee-herdsman-converters/index.js:50:21)
at /app/lib/extension/networkMap.js:74:61
at Array.forEach ()
at NetworkMap.graphviz (/app/lib/extension/networkMap.js:60:24)
at NetworkMap.onMQTTMessage (/app/lib/extension/networkMap.js:44:65)
at async Controller.callExtensionMethod (/app/lib/controller.js:352:21))
What did you expect to happen
How to reproduce it (minimal and precise)
It is work when I remove GL-C-008-2ID device.
Debug Info
Zigbee2mqtt version: last-dev
Adapter hardware: CC1352P-2
Adapter firmware version: 20200419
The text was updated successfully, but these errors were encountered: