Project

General

Profile

Feature #845

Ability to log Insteon PLM events

Added by Luke Murphey over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Luke Murphey
Target version:
0.5
Start date:
10/12/2014
Due date:
% Done:

100%

History

#1 Updated by Luke Murphey over 9 years ago

  • Status changed from New to In Progress

#2 Updated by Luke Murphey over 9 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

#3 Updated by Luke Murphey over 9 years ago

  • Status changed from Closed to In Progress
  • % Done changed from 100 to 60

Seems like I'm only getting acknowledgements at the current time.

#4 Updated by Luke Murphey over 9 years ago

The issue might be in run() where it checks to see if the first byte is 0x02. Not sure why it does that though. Does the modem not pass on all messages?

I might just need to move the callback up further in the call stack.

#5 Updated by Luke Murphey over 9 years ago

Apparently, the messages are preceded with an Insteon Command Code.

  1. run():
    1. gets the first byte and verifies it is a modem command
    2. uses the second byte to determine the modem command and response size
  2. Calls associated callback

I'm not sure how the second byte can be used to identify extended messages because this appears to be the first part of the from address.

#6 Updated by Luke Murphey over 9 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 60 to 100

This seems to be working. It appears as if the PLM doesn't include its own requests in the feed. Other device requests do show up though.

Also available in: Atom PDF