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

Allow CLI to retrieve more than 100 000 events #7

Closed
uhppoted opened this issue Dec 14, 2021 · 4 comments
Closed

Allow CLI to retrieve more than 100 000 events #7

uhppoted opened this issue Dec 14, 2021 · 4 comments
Assignees

Comments

@uhppoted
Copy link
Owner

Hi there,

I have been using uhppote-cli to connect to some controllers and I thought I would share with you my findings on the 100,000 event log buffer of these devices.
I have a device that is currently at 111,545 events and still working, so I have been modifying the ROLLOVER variable in –cli in a fork in an attempt to work out the actual behaviour of the device, at the moment I can still access all events from 1 through 111545 from CLI or the web interface.
I don’t know whether this is specific to a board version but this controller is running V7.70.61227
I do have other boards with different versions of the firmware but they are not at 100,000 events yet.

twystd added a commit that referenced this issue Dec 14, 2021
twystd added a commit to uhppoted/uhppote-core that referenced this issue Dec 15, 2021
twystd added a commit that referenced this issue Dec 16, 2021
twystd added a commit to uhppoted/uhppoted-rest that referenced this issue Dec 24, 2021
twystd added a commit to uhppoted/uhppoted-mqtt that referenced this issue Dec 24, 2021
twystd added a commit to uhppoted/uhppoted-app-s3 that referenced this issue Dec 24, 2021
twystd added a commit to uhppoted/uhppoted-app-sheets that referenced this issue Dec 24, 2021
twystd added a commit to uhppoted/uhppoted-app-wild-apricot that referenced this issue Dec 24, 2021
twystd added a commit to uhppoted/uhppoted-httpd that referenced this issue Dec 24, 2021
@uhppoted
Copy link
Owner Author

From experimentation, it appears that the on-device event buffer is approximately 200 000 events:

Fri Dec 24 14:16:01 PST 2021
EVENTS:  423187757  1  186809
FIRST:   423187757  1      2019-02-10 07:12:01 6154410      3 false 6
LAST:    423187757  186809 2021-12-24 14:16:01 3922570474   4 true  44

Fri Dec 24 17:15:49 PST 2021
EVENTS:  423187757  2049  206817
FIRST:   423187757  2049   2021-12-17 11:42:55 3922570474   4 true  44
LAST:    423187757  206817 2021-12-24 17:15:48 3922570474   4 true  44

Once the on-device event buffer is full, events are dropped in chunks of 2048 events and the first event index updated accordingly i.e. the event index does not wrap around but continues to increment:

Fri Dec 24 17:15:49 PST 2021
EVENTS: 423187757  2049  206817
FIRST:  423187757  2049   2021-12-17 11:42:55 3922570474   4 true  44
LAST:   423187757  206817 2021-12-24 17:15:48 3922570474   4 true  44

Fri Dec 24 17:19:37 PST 2021
EVENTS: 423187757  2049   2021-12-17 11:42:55 3922570474   4 true  44
FIRST:  423187757  206825 2021-12-24 17:19:37 3922570474   4 true  44
LAST:   423187757  2049  206825

@uhppoted
Copy link
Owner Author

events.log

twystd added a commit to uhppoted/uhppote-simulator that referenced this issue Dec 30, 2021
twystd added a commit to uhppoted/uhppote-simulator that referenced this issue Dec 31, 2021
twystd pushed a commit to uhppoted/uhppoted that referenced this issue Dec 31, 2021
twystd added a commit to uhppoted/uhppoted-app-s3 that referenced this issue Jan 5, 2022
twystd added a commit to uhppoted/uhppoted-app-sheets that referenced this issue Jan 5, 2022
twystd added a commit to uhppoted/uhppoted-app-wild-apricot that referenced this issue Jan 6, 2022
twystd added a commit to uhppoted/uhppoted-nodejs that referenced this issue Jan 10, 2022
twystd added a commit to uhppoted/node-red-contrib-uhppoted that referenced this issue Jan 11, 2022
@uhppoted
Copy link
Owner Author

Reworked throughout - pending release of 0.7.2

@uhppoted
Copy link
Owner Author

Closing - fixed in release v0.7.2

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

No branches or pull requests

2 participants