ssjoholm / rfxcmd Goto Github PK

Hi Sebastian,

Can you help me letting rfxcmd recognise WIND& and TH 14 packages?

rfxcmd - log outputs:

Received = 10 56 07 01 2E 01 01 3B 00 00 00 04 02 1C 00 00 59
Date/Time = 2015-06-12 13:58:09
Packet Length = 10
2015-06-12 13:58:09,401 - MainThread - rfxcmd:3828 - DEBUG - Decode packet
2015-06-12 13:58:09,402 - MainThread - rfxcmd:594 - DEBUG - Verify incoming packet
2015-06-12 13:58:09,403 - MainThread - rfxcmd:3700 - DEBUG - Test message: 10 56 07 01 2E 01 01 3B 00 00 00 04 02 1C 00 00 59
2015-06-12 13:58:09,404 - MainThread - rfxcmd:3740 - DEBUG - Message OK
2015-06-12 13:58:09,404 - MainThread - rfxcmd:601 - DEBUG - Verified OK
2015-06-12 13:58:09,405 - MainThread - rfxcmd:607 - DEBUG - PacketType: 56
2015-06-12 13:58:09,406 - MainThread - rfxcmd:611 - DEBUG - SubType: 07
2015-06-12 13:58:09,406 - MainThread - rfxcmd:615 - DEBUG - SeqNbr: 01
2015-06-12 13:58:09,407 - MainThread - rfxcmd:619 - DEBUG - Id1: 2E
2015-06-12 13:58:09,407 - MainThread - rfxcmd:623 - DEBUG - Id2: 01
Packettype = Wind sensors
2015-06-12 13:58:09,408 - MainThread - rfxcmd:642 - DEBUG - Verify correct packet length
2015-06-12 13:58:09,409 - MainThread - rfxcmd:2767 - DEBUG - Decode packetType 0x56 - Start
2015-06-12 13:58:09,410 - MainThread - rfxcmd:3832 - ERROR - Error: unrecognizable packet (10 56 07 01 2E 01 01 3B 00 00 00 04 02 1C 00 00 59) Line: [read_rfx:3832]
Error: unrecognizable packet
2015-06-12 13:58:09,411 - MainThread - rfxcmd:4113 - DEBUG - Processed: 105607012E01013B00000004021C000059

Using RFXmngr for windows, the console outputs:

Packettype = UNDECODED RF Message
UNDECODED ARC:33FFFE77B5AB4240
Packettype = WIND
subtype = WIND7 - Alecto WS3500,WS4500
Sequence nbr = 6
ID = 11777
Direction = 270 degrees W
Average speed = 0.2 mtr/sec = 0.72 km/hr = 0.45 mph
Wind gust = 0.2 mtr/sec = 0.72 km/hr = 0.45 mph
Signal level = 5
Battery = OK

The same as unable to decode a TH14 package:
rfxcmd log:
-----------------------------------------------
Received = 0A 52 0E 03 2E 01 01 2E 14 02 59
Date/Time = 2015-06-12 13:58:40
Packet Length = 0A
2015-06-12 13:58:40,252 - MainThread - rfxcmd:3828 - DEBUG - Decode packet
2015-06-12 13:58:40,252 - MainThread - rfxcmd:594 - DEBUG - Verify incoming packet
2015-06-12 13:58:40,253 - MainThread - rfxcmd:3700 - DEBUG - Test message: 0A 52 0E 03 2E 01 01 2E 14 02 59
2015-06-12 13:58:40,254 - MainThread - rfxcmd:3740 - DEBUG - Message OK
2015-06-12 13:58:40,255 - MainThread - rfxcmd:601 - DEBUG - Verified OK
2015-06-12 13:58:40,255 - MainThread - rfxcmd:607 - DEBUG - PacketType: 52
2015-06-12 13:58:40,256 - MainThread - rfxcmd:611 - DEBUG - SubType: 0E
2015-06-12 13:58:40,256 - MainThread - rfxcmd:615 - DEBUG - SeqNbr: 03
2015-06-12 13:58:40,257 - MainThread - rfxcmd:619 - DEBUG - Id1: 2E
2015-06-12 13:58:40,258 - MainThread - rfxcmd:623 - DEBUG - Id2: 01
Packettype = Temperature and humidity sensors
2015-06-12 13:58:40,258 - MainThread - rfxcmd:642 - DEBUG - Verify correct packet length
2015-06-12 13:58:40,259 - MainThread - rfxcmd:2434 - DEBUG - Decode packetType 0x52 - Start
2015-06-12 13:58:40,260 - MainThread - rfxcmd:2447 - DEBUG - Print data stdout
2015-06-12 13:58:40,261 - MainThread - rfxcmd:3832 - ERROR - Error: unrecognizable packet (0A 52 0E 03 2E 01 01 2E 14 02 59) Line: [read_rfx:3832]
Error: unrecognizable packet
2015-06-12 13:58:40,262 - MainThread - rfxcmd:4113 - DEBUG - Processed: 0A520E032E01012E140259

RFXmngr outputs:

Packettype = TEMP_HUM
subtype = TH14 - Alecto WS3500,WS4500
Sequence nbr = 7
ID = 11777
Temperature = 29.9 °C
Humidity = 20
Status = Dry
Signal level = 5
Battery = OK

The link to google code seems dead.

The website in the readme http://www.rfxcmd.eu/ is no longer working.

I have a Byron MP001 doorbel which is support by RFXCOM but only transmit, not receive.

Via the Windows RFXCOM Manager I can ring the doorbel via the "Chimes" tab.

Is there any way I can do this by the commandline on my raspberry ?

Since receiving is not supported, I cannot listen to it to get it's ID

In datatype 57 (UV sensors), the message[7] shall be used instead of message[6] for temperature high bits.

Hi,

When running rfxproto.py to enable the "Undecoded" protocol using:
/usr/src/rfxcmd/rfxcmd# ./rfxproto.py -d /dev/ttyUSB0 -p 0 -s on -D -V

The script exits and returns the following error:
rfxproto:210 - DEBUG - Error: Send failed, error: zero length field name in format

This situation also occurs when trying to enable or disable other protocols.
I`ve validated the correct protocol number using the "-l" switch ( # 0 - Undecoded - Disabled)

i`m running Firmware version 240
Can you reproduce this issue?

Here`s rfxproto.py debug output:

2015-06-08 17:42:44,834 - MainThread - rfxproto:544 - DEBUG - Logger started
2015-06-08 17:42:44,834 - MainThread - rfxproto:545 - DEBUG - Version: 0.1 (566)
2015-06-08 17:42:44,835 - MainThread - rfxproto:546 - DEBUG - Date: Date: 2013-11-22 21:43:41 +0100 (Fri, 22 Nov 2013)
2015-06-08 17:42:44,835 - MainThread - rfxproto:549 - DEBUG - Print version
RFXPROTO Version: 0.1 (566)
Date: 2013-11-22 21:43:41 +0100 (Fri, 22 Nov 2013)
2015-06-08 17:42:44,836 - MainThread - rfxproto:554 - DEBUG - Serial device: /dev/ttyUSB0
2015-06-08 17:42:44,836 - MainThread - rfxproto:564 - DEBUG - Protocol num: 0
2015-06-08 17:42:44,837 - MainThread - rfxproto:565 - DEBUG - Protocol state: on
2015-06-08 17:42:44,837 - MainThread - rfxproto:409 - DEBUG - Serial extension version: 1.35
2015-06-08 17:42:44,838 - MainThread - rfxproto:417 - DEBUG - Device: /dev/ttyUSB0
2015-06-08 17:42:44,838 - MainThread - rfxproto:424 - DEBUG - Open Serialport
2015-06-08 17:42:44,848 - MainThread - rfxproto:434 - DEBUG - Serialport flush output
2015-06-08 17:42:44,848 - MainThread - rfxproto:436 - DEBUG - Serialport flush input
2015-06-08 17:42:44,849 - MainThread - rfxproto:440 - DEBUG - Send RFX reset
2015-06-08 17:42:45,851 - MainThread - rfxproto:445 - DEBUG - Serialport flush output
2015-06-08 17:42:45,852 - MainThread - rfxproto:447 - DEBUG - Serialport flush input
2015-06-08 17:42:45,852 - MainThread - rfxproto:450 - DEBUG - Send message
2015-06-08 17:42:46,854 - MainThread - rfxproto:457 - DEBUG - Wait for the reply
2015-06-08 17:42:46,864 - MainThread - rfxproto:465 - DEBUG - Timestamp: 2015-06-08 17:42:46
2015-06-08 17:42:46,865 - MainThread - rfxproto:466 - DEBUG - SerWaiting: 14
2015-06-08 17:42:46,865 - MainThread - rfxproto:468 - DEBUG - Byte: 0D
2015-06-08 17:42:46,866 - MainThread - rfxproto:478 - DEBUG - Message: 0D 01 00 00 02 53 F0 02 08 27 00 01 02 00
2015-06-08 17:42:46,867 - MainThread - rfxproto:502 - DEBUG - Close serial port
2015-06-08 17:42:46,869 - MainThread - rfxproto:505 - DEBUG - Serial port closed
2015-06-08 17:42:46,870 - MainThread - rfxproto:177 - DEBUG - Result: 0D 01 00 00 02 53 F0 02 08 27 00 01 02 00
2015-06-08 17:42:46,871 - MainThread - rfxproto:210 - DEBUG - Error: Send failed, error: zero length field name in format
Error: Could not send message: zero length field name in format
2015-06-08 17:42:46,871 - MainThread - rfxproto:595 - DEBUG - Exit

regards,

Erik

Hello.

Its not really a issue but more a question. Im trying to use AC (under signal printout 0×11 – Lightning2) command and i suppose i need to use rfxsend.py. Is there an example on how to use this in this scenario?

Thanks