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

Detecting changed messages #16

Merged
merged 1 commit into from
Jul 20, 2019
Merged

Detecting changed messages #16

merged 1 commit into from
Jul 20, 2019

Conversation

syspart
Copy link
Contributor

@syspart syspart commented Jul 11, 2019

With adding date&time to the header, the device knows a newer message has been send.
So you don't have to remove the device when sending a new message.

With adding date&time to the header, the device knows a newer message has been send. 
So you don't have to remove the device when sending a new message.
@s-light
Copy link
Collaborator

s-light commented Jul 17, 2019

where did you get the meanings for the fields from?
are there any resource i don't know of? ;-)

and what exactly means

So you don't have to remove the device when sending a new message.
→ would this fix #13 ??

@syspart
Copy link
Contributor Author

syspart commented Jul 18, 2019 via email

@jnweiger
Copy link
Owner

Nice reverse engineering. Thanks!

I have to try that! It sounds like it could solve #10 ?

@syspart
Copy link
Contributor Author

syspart commented Jul 19, 2019

@s-light: If you send a new message to the badge, it looks like something has happend. But nothing changed and the old messages are shown.

@jnweiger
Copy link
Owner

The exact conditions when a new message would not appear without this fix, are still unclear to me. Merging, it seems to make sense anyway.

@jnweiger jnweiger merged commit 47ffd0c into jnweiger:master Jul 20, 2019
@syspart syspart deleted the patch-3 branch July 22, 2019 20:02
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

Successfully merging this pull request may close these issues.

3 participants