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

Cannot reset CC2531 remotely #414

Open
rcarmo opened this Issue Sep 27, 2018 · 13 comments

Comments

Projects
None yet
5 participants
@rcarmo
Copy link

rcarmo commented Sep 27, 2018

I have been having some weird crashes I'm assuming are the result of the soft reset mechanism triggering. However, when I restart the daemon, I get this:

2018-9-27 20:21:57 - error: Press the reset button on the stick (the one closest to the USB) and start again
2018-9-27 20:21:57 - error: Failed to start Error: request timeout
    at CcZnp.<anonymous> (/home/user/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:255:22)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at CcZnp.emit (events.js:211:7)
    at Timeout.<anonymous> (/home/user/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:234:18)
    at ontimeout (timers.js:498:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:290:5)

Since I have the dongle inside a case, the most effective way to fix it is walk up to the machine and unplug it. Is there any documented way to force a reset?

@Koenkk

This comment has been minimized.

Copy link
Owner

Koenkk commented Sep 28, 2018

This soft reset brings the CC2531 in a strange situation.

For now I would recommend the fix from: #274 (comment)

Soon I will provide an option to complete disable this soft reset behavior.

@rcarmo

This comment has been minimized.

Copy link
Author

rcarmo commented Oct 1, 2018

I'm having some erratic behaviour (sensors dropping out of the network and failing to update until re-paired), and keep wondering if this has something to do with it.

@lolorc

This comment has been minimized.

Copy link
Contributor

lolorc commented Oct 2, 2018

@rcarmo could you check your logs and see if the panId is still the same. I'm having that kind of issues here, and this is because the panId has changed.

@stale

This comment has been minimized.

Copy link

stale bot commented Dec 1, 2018

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.

@stale stale bot added the stale label Dec 1, 2018

@rcarmo

This comment has been minimized.

Copy link
Author

rcarmo commented Dec 1, 2018

Logs show no changes... it keeps happening.

@stale stale bot removed the stale label Dec 1, 2018

@Koenkk

This comment has been minimized.

Copy link
Owner

Koenkk commented Dec 1, 2018

Soft reset mechanism is disabled in the latest version, do you still have this problem?

@Morphy99

This comment has been minimized.

Copy link

Morphy99 commented Jan 12, 2019

I'm having this issue after rebooting my RPi 3 running HASS.IO. The dongle lights up after boot then goes off. I've tried pressing the reset button which lights the LED again however it still won't connect even after restarting the zigbee2mqtt addon. In fact it then goes to another state where even pressing the reset button does nothing.

To resolve before I had to power off the pi, remove the dongle and press the reset button before powering on again. Now even this doesn't seem to work :/ This is the log from boot:

[Info]
Configuration file found. Will overwrite configurable fields with values from add-on configuration
[Info] Configuration written to /share/zigbee2mqtt/configuration.yaml
2019-01-12T11:00:19: PM2 log: Launching in no daemon mode
2019-01-12T11:00:20: PM2 log: App [npm:0] starting in -fork mode-
2019-01-12T11:00:20: PM2 log: App [npm:0] online
zigbee2mqtt@1.0.1 start /app
node index.js
zigbee2mqtt:info 2019-1-12 11:00:29 Logging to directory: /share/zigbee2mqtt/log/2019-01-12.11-00-29
zigbee2mqtt:info 2019-1-12 11:00:31 Starting zigbee2mqtt version 1.0.1 (commit #9191788)
zigbee2mqtt:info 2019-1-12 11:00:31 Starting zigbee-shepherd
zigbee2mqtt:info 2019-1-12 11:00:34 Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds)
zigbee2mqtt:info 2019-1-12 11:01:34 Starting zigbee-shepherd
zigbee2mqtt:error 2019-1-12 11:01:37 Error while starting zigbee-shepherd!
zigbee2mqtt:error 2019-1-12 11:01:37 Press the reset button on the stick (the one closest to the USB) and start again
zigbee2mqtt:error 2019-1-12 11:01:37 Failed to start
{"message":"request timeout","stack":"Error: request timeout\n at CcZnp. (/app/node_modules/cc-znp/lib/ccznp.js:255:22)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at CcZnp.emit (events.js:211:7)\n at Timeout. (/app/node_modules/cc-znp/lib/ccznp.js:234:18)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)"}

@Morphy99

This comment has been minimized.

Copy link

Morphy99 commented Jan 12, 2019

So I swapped the USB port and it seems to work now but after rebooting the same issue happens again and I have to shutdown and remove.
Now none of my devices are registered 👎
EDIT: Panic over, its just a couple of IKEA tradfri bulbs which have changed ID's for some reason.

@rcarmo

This comment has been minimized.

Copy link
Author

rcarmo commented Jan 13, 2019

FYI, I'm still having the same issue as initially reported.

@Koenkk

This comment has been minimized.

Copy link
Owner

Koenkk commented Jan 13, 2019

@rcarmo when does this happen?

@msadeghz

This comment has been minimized.

Copy link

msadeghz commented Jan 19, 2019

So I swapped the USB port and it seems to work now but after rebooting the same issue happens again and I have to shutdown and remove.
Now none of my devices are registered 👎
EDIT: Panic over, its just a couple of IKEA tradfri bulbs which have changed ID's for some reason.

I got this problem.
but when I removed the IEEE address of the dongle in configuration.yaml, it goes OK.
but in the next time when I want remove the IEEE address from the file, I can't find it.
edit: so, how can I force zigbee2mqtt to forget the dongle? I remove database and IEEE addresses from configuration.yaml in data directory, but the issue is not solved.

@Morphy99

This comment has been minimized.

Copy link

Morphy99 commented Jan 19, 2019

I think I removed everything from zigbee2mqtt directory. Uninstalled add-on and also mosquitto. Removed mqtt entries from core.device_registry and core.entity_registry. Deleted mqtt broker in integrations as well then restarted the server. Once I installed everything again it all seemed to work ok again. Oh I updated the firmware of the cc2531 as well as I was one release behind.

@msadeghz

This comment has been minimized.

Copy link

msadeghz commented Jan 20, 2019

So I swapped the USB port and it seems to work now but after rebooting the same issue happens again and I have to shutdown and remove.
Now none of my devices are registered 👎
EDIT: Panic over, its just a couple of IKEA tradfri bulbs which have changed ID's for some reason.

I got this problem.
but when I removed the IEEE address of the dongle in configuration.yaml, it goes OK.
but in the next time when I want remove the IEEE address from the file, I can't find it.
edit: so, how can I force zigbee2mqtt to forget the dongle? I remove database and IEEE addresses from configuration.yaml in data directory, but the issue is not solved.

today, I've run the firmware and the problem is not seen!! I don't know the source of the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment