-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[rfxcom] Add support for receiving RAW messages #10833
Conversation
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
switch (channelId) { | ||
case CHANNEL_RAW_MESSAGE: | ||
if (type instanceof StringType) { | ||
// TODO: Check the raw message for validity (length, no more than 124 shorts, multiple of 4 bytes in |
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.
There is a TODO, what should be done and can it be completed before merging the PR?
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.
This is really a TODO for when I implement tx, which is next. There is value in merging rx.
|
||
case CHANNEL_RAW_PAYLOAD: | ||
if (type instanceof StringType) { | ||
// TODO: Check the payload for validity (no more than 124 shorts, multiple of 4 bytes |
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.
There is a TODO, what should be done and can it be completed before merging the PR?
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.
This is really a TODO for when I implement tx, which is next. There is value in merging rx.
@@ -145,6 +145,7 @@ | |||
private static final ThingTypeUID THING_TYPE_POWER = new ThingTypeUID(BINDING_ID, "power"); | |||
private static final ThingTypeUID THING_TYPE_RADIATOR1 = new ThingTypeUID(BINDING_ID, "radiator1"); | |||
private static final ThingTypeUID THING_TYPE_RAIN = new ThingTypeUID(BINDING_ID, "rain"); | |||
private static final ThingTypeUID THING_TYPE_RAW = new ThingTypeUID(BINDING_ID, "raw"); |
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.
Just out of curiosity what is the difference with undecoded
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.
UNDECODED is where the RFXCOM understands the type, but just hasn't broken it down into values. RAW is where the RFXCOM has received an RF message and hasn't tried to do anything to it at all, so the values are the ms pulse timings that would need to be processed into stable bytes before they could even be decoded.
Does it make to wait with merging until the tx support is added? |
I would merge it, it adds value as is. Not sure when exactly I'll find time to do the tx side. |
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com> Signed-off-by: Luca Calcaterra <calcaterra.luca@gmail.com>
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com> Signed-off-by: Luca Calcaterra <calcaterra.luca@gmail.com>
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com> Signed-off-by: Luca Calcaterra <calcaterra.luca@gmail.com>
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
This is a new feature in the Pro firmwares that provides the real raw RF pulse lengths as shorts. Good for being able to parrot switches that aren't otherwise supported, once we add the tx support as well. Signed-off-by: James Hewitt <james.hewitt@uk.ibm.com>
This is a new feature in the Pro firmwares that provides the real raw RF
pulse lengths as shorts. Good for being able to parrot switches that aren't
otherwise supported, once we add the tx support as well.
Signed-off-by: James Hewitt james.hewitt@uk.ibm.com