-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat/captor data periodic flux #20
base: develop
Are you sure you want to change the base?
feat/captor data periodic flux #20
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current UI is adapted to live data transmission, not at all to periodic transmission:
- on first connection, application displays "waiting for data" while it's downloading history from sensor;
- once history download is done, indicators appear on screen, but they don't move (since there's no live data reception)
I feel like user should have the choice between live and periodic transmission; I'm open to chat about this.
I'm agree with this, I think we can add a button in settings view to change the transmission mode. |
Are you using same influxDB version as Apolline backend: https://github.com/Apolline-Lille/apolline-backend-ng ?
To begin, we can display last data point on screen; we should display a message that tells that we're waiting X minutes to sync with sensor, so that people do not think the app crashed. |
Yes I am using it and I didn't change anything from the docker image.
I see, I'll try to do this. |
…s are superior than thresholds
Live data transmission mode replaced by a periodic data transmission mode.
Warning: during the time between step 2 and 3 we can loose 1 or 2 seconds of data.