Skip to content
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

Errors after update #1760

Closed
stanislavmerts opened this issue Jul 21, 2019 · 6 comments
Closed

Errors after update #1760

stanislavmerts opened this issue Jul 21, 2019 · 6 comments
Labels
stale Stale issues

Comments

@stanislavmerts
Copy link

stanislavmerts commented Jul 21, 2019

Hello! I use Hass.io addon. Today i update addon from 1.4.0 to 1.5.1 and got a lot of problems.
Firstly, when i try to start addon I saw in the message log as in issue # 1756. I add in config line with "network_key": [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13]. And it succesfully started.
Then I encountered the following problem. I see what my Aqara sensors and Lamp is connected, but I don't get information from them. I tried reconnect my sensors and lamp but no result.
As for the lamp, I see some additional errors:

7/21/2019, 9:35:38 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.","meta":{"entity":{"ID":"0x00158d0002d39c50","type":"device","friendlyName":"0x00158d0002d39c50"},"message":"{"state": "ON"}"}}'

zigbee2mqtt:error 7/21/2019, 10:23:31 PM Failed to ping 0x00158d0002d39c50

I tried downgrade to version 1.4.0 from my backup but the result is exactly the same.
Please help me. I use CC2531

@Koenkk
Copy link
Owner

Koenkk commented Jul 21, 2019

Did you change your network key? Because that requires repairing all devices

@stanislavmerts
Copy link
Author

What i need to do? I reapairing all my sensors and lamp (it's Xiaomi Aqara). I click button on sensor for 5 second, then blue LED flashing tripple. For a lamp I turn power off and on 5 times and the bulb blink twice. In log i see what finding new device.
Now my config in version 1.4.0 is:
{
"data_path": "/share/zigbee2mqtt",
"homeassistant": true,
"permit_join": false,
"mqtt_base_topic": "zigbee2mqtt",
"mqtt_server": "mqtt://192.168.0.4:1883",
"serial_port": "/dev/ttyACM0",
"devices": [],
"network_key": [],
"mqtt_user": "user",
"mqtt_pass": "password"
}
Now the lamp in front of me on the table, disconnected from the power supply. But in hass.io my lamp is online.

@anrada73
Copy link

I have the same problems

@stanislavmerts
Copy link
Author

stanislavmerts commented Jul 22, 2019

Ok, I solved my problem.
I change config on version 1.4.0
Before: "network_key": [],
After: "network_key": [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13]
Next I repair all the sensors. After this i remove aqara lamp. When i try pairing lamp, in log i see errors:
zigbee2mqtt:warn 7/22/2019, 1:51:56 PM Device with modelID 'undefined' is not supported.
zigbee2mqtt:warn 7/22/2019, 1:51:56 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html
zigbee2mqtt:error 7/22/2019, 1:52:16 PM Cannot get the Node Descriptor of the Device: 0x00158d0002d39c50 (Error: Timed out after 10000 ms)
First and second pairing unsuccessful, but in third time pairing is successful.

@flatsiedatsie
Copy link
Contributor

Perhaps related, I'm also getting zigbee2mqtt:error 2019-8-1 08:27:26 Cannot get the Node Descriptor of the Device: 0x00158dxxxxxxx (Error: Timed out after 10000 ms) on an Aqara cube. At the same time an Aqara magnetic contact sensor (V2) works just time.

@stale
Copy link

stale bot commented Sep 30, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale issues
Projects
None yet
Development

No branches or pull requests

4 participants