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

ZWave controller should be reset at start of program? #74

Closed
dhylands opened this issue May 15, 2017 · 3 comments
Closed

ZWave controller should be reset at start of program? #74

dhylands opened this issue May 15, 2017 · 3 comments

Comments

@dhylands
Copy link
Contributor

If the app crashes while the zwave dongle is inclusion mode, and you then restart the app, the dongle seems to still be in a state where many devices will timout. I observed that my Leviton devices all got timeouts.

Unplugging and replugging the dongle seemed to resolve this.

We might need to do a controller (dongle) reset. Ideally we'd detect the state that the controller is in and get it out of that state, and only reset the controller if absolutely required.

@mrstegeman
Copy link
Contributor

@dhylands Is this still an issue?

@dhylands
Copy link
Contributor Author

I think so. If the Pi happened to get reset while the gateway was in the middle of sending data, I think that's its possible for the dongle to get into a confused state. I've definitely seen cases where unplugging and plugging in the zigbee dongle made things work again.

On some of the RPis it is apparently possible to power cycle some of the USB ports.

@mrstegeman
Copy link
Contributor

Moved: WebThingsIO/zwave-adapter#32

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

No branches or pull requests

2 participants