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

Photon System.sleep(pin, edge, seconds) does not always stay asleep #846

Closed
technobly opened this issue Jan 28, 2016 · 3 comments

Comments

@technobly
Copy link
Member

commented Jan 28, 2016

It's very bizarre... at first I thought I was seeing things.. but it appears to come and go. I was using INPUT_PULLDOWN on D0, with RISING edge... and even with an additional 1k pulldown resistor it still misbehaves. Here's a test app that will connect, wait 5 seconds, publish a message, then sleep for 30 seconds and repeat. It does not always stay asleep for 30 seconds. I also tried jumpering VBAT to 3V3 which is important for some retained variable cases (not that this should affect how long the STOP mode stays asleep).

Tested on latest develop:
04ededb

Test app:
https://gist.github.com/technobly/b64574b0f31e598c1560

If the app doesn't seem to be failing, try doubling the delays and use a clean build.

@technobly

This comment has been minimized.

Copy link
Member Author

commented Mar 4, 2016

  • I tested this recently with #864 and merged #845 on an Electron and sleep stop mode was working.
  • Test with a Photon.
  • Also verify the problem case again with above steps.
  • If anyone else can reproduce any or all of the above that would be helpful :) Lone ranger rides again!
@m-mcgowan

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2016

@technobly - could you complete the remaining test steps please so we can close this issue before the of the week.

@technobly technobly self-assigned this Mar 17, 2016

@technobly

This comment has been minimized.

Copy link
Member Author

commented Mar 17, 2016

@m-mcgowan completed tests, looks good as far as PR #864 and #845 currently sit. We should test again after beta 0.5.0 is out.

@technobly technobly removed their assignment Mar 17, 2016

@technobly technobly closed this Mar 31, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.