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

Insteon: Log Output if PLM Parser Drops a Duplicate Messages #193

Merged
merged 3 commits into from
May 21, 2013

Conversation

krkeegan
Copy link
Collaborator

As discovered by @peloy, the PLM Parser was silently dropping duplicate messages sequentially received in the same pass.

This adds a debug3 message to the log when such messages are dropped.

Partial fix for #186

As discovered by @peloy, the PLM Parser was silently dropping duplicate messages sequentially received in the same pass.

This adds a debug3 message to the log when such messages are dropped.

Partial fix for hollie#186
…eived at the Same Time

PLM Decoder will not decode each message if multiple are received in one check data request.

The only place that could create a hiccup, is if the PLM Parser has a bug.  Since we now rely on the PLM Parser to first identify a valid message before asking the decoder to decode it, we rely on the PLM Parser to accurately discover messages.

We still display the raw message, so the information is not lost, but we will not have a nice display of the message.  I don't see this as a big deal, if the PLM Parser is missing messages we would likely have other problems anyways.

Fixes the remainder of hollie#186
Conflicts:
	lib/Insteon_PLM.pm
krkeegan added a commit that referenced this pull request May 21, 2013
Insteon: Log Output if PLM Parser Drops a Duplicate Messages
@krkeegan krkeegan merged commit 2ba7b63 into hollie:master May 21, 2013
@krkeegan krkeegan deleted the fix_issue_186 branch May 21, 2013 04:04
@hollie hollie mentioned this pull request Jun 15, 2013
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.

2 participants