516 rfxcom problems

[mhwlng]

my motion detectors send their state 5 times,

I always see errors in some of the commands :

------------------
B1:ON
B1:ON
B1:ON
B1:ON
>>>>> Error decoding block No matching handler for a block with 33bits
Attempting resync from 7
Attempt 2 partition data 70 8F 00 FF 00 p�.ÿ.
--------------------
B1:OFF
B1:OFF
Not a 1-wire
>>>>> Error decoding block nil
Attempting resync from 12
Attempt 2 partition data 70 8F 20 DD p� Ý
>>>>> Error decoding block No matching handler for a block with 112bits
Attempting resync from 2
Attempt 2 partition data 70 8F 20 DF p� ß

-----------------------

Also, my power meter data is not parsed properly :

this device also sends the same data 5 times, and this is the result :

Internal serial number = 00 F0 31 64 00 86 .ð1d.†
Internal serial number = 00 F0 30 BC 00 86 .ð0¼.†
Internal serial number = 00 C8 18 A6 00 43 .È.¦.C
Internal serial number = 00 F0 30 3C 00 21 .ð0<.!
Internal serial number = 00 F0 31 78 01 0C .ð1x..

-------------------------

one difference between your code and mine is, that you initialise the rfxcom with : F041

and I use mode F02C....

I don't know if this matters...

------------

also, what does the X10 RF Transmitters component do ?

I don't see any different with or without this component enabled ?


Marcel

[Rob H]

The RFXCOM component is in a transitional state at the moment and doesn't currently interact with the X10RFTransmitters class or the RFXCOMTransmitters class, but that should be sorted soon. Once this has been fixed then the RFXPower should work (I don't have one of these to test against but Mike does).

Re the errors - I see these quite often myself, and I assume that they are due to RF interference corrupting the signal. The RFXCOM component attempts to resync, but that doesn't work all that often. The X10RFTransmitters component should take care of the repetition of events.

I initialise with F041 because I want the variable length data for Visonic sensors while still receiving X10 - I'm still not clear whether I need to initialise the X10 side first to get the full length data from X10 security devices - I've noticed using the example code from RFXCOM that there seems to be a difference in X10 output depending on the initialisation order.

[Promixis]

Marcel,

too clarify - we have separated the RF devices into Tx and Rx.

Rx we will support are the W800RF32 and RFXCOM

TX we will support are X10 Standard and Security, RFXCOM devices, and Some Visonic +/- others

[mhwlng]

I still have problems with 518

I have x10 motion detectors that work fine
rfxcom power meter data is not parsed properly :

B10:OFF
B10:OFF
B10:OFF
B10:OFF
B10:OFF
Internal serial number = 00 F0 8E 7A 02 07 .ðŽz..

after the rfxcom power meter data is received (sent every 30 min.), also the x10 motion detectors stop working..

Marcel

[Rob H]

Looking at this now - my code attempts to resync if it finds unexpected data in the buffer, but this doesn't appear to work as well as I'd like.

[Rob H]

Can you try this replacement for RFXCOMReceivers.lua (goes in the lua\Components folder).

[mhwlng]

when the power meter data comes in, I get results in attached :

the x10 motion detectors still work afterward (I'm not sure if some motion detector events were lost during the resync process..)....

Marcel

[Rob H]

You shouldn't lose any motion detector events during a resync - I have however seen it produce an occasional spurious result e.g. I got an L13 ON while testing this version and I don't have any such device.

I may change the way that this is handled, e.g. just throwing away any block that doesn't have valid data.

Not sure about the power meter data - I don't have one of these devices to test with which makes it a bit tricky.

[mhwlng]

Not sure about the power meter data

ok, I'll revert back to my old rfxcom component.....

If you need me to test something in the future, let me know...

thanks,

Marcel

[Rob H]

Mike has one though