Page 14 of 36
Re: RFXtrx
Posted: Mon Dec 03, 2012 7:23 am
by b_weijenberg
Paul,
Do you use the latest RFXtrx433 firmware?
It is known that older firmware versions can produce a single "00" byte. This should be solved in the latest firmware.
Best regards, Bert
Re: RFXtrx
Posted: Tue Dec 04, 2012 11:13 am
by krambriw
I have tried your workaround and I fear this may cause some unnecessary loss of messages. Sometimes it seems, at least in my case, that I get the first byte of the message first (the byte that tells the packet length) and in the next round, I get the remaining bytes.
So I would propose the following modification instead:
Code: Select all
if pl>3 and len(str(out))==pl+1:
if self.bDebug:
print "Debug Info: ", data
self.HandleChar(data)
else:
if not (data == '00' and self.tmpMessage == ''):
self.PartialMessageHandler(data)
out = ''
Please try this out if it also works fine for you.
Best regards, Walter
Re: RFXtrx
Posted: Tue Dec 04, 2012 1:54 pm
by pavlouis
Good day gents, I upgraded the firmware, thinking that was the original problem, when I first got the unit back in Sept. I've put in your code and it looks like it is working well, I appear to be getting a lot of "Message could not be repaired", but that was fairly common before as well.
Cheers and thanks again!
Paul
Re: RFXtrx
Posted: Tue Dec 04, 2012 4:28 pm
by krambriw
Paul, you could paste the content of some of them "Message could not be repaired" in here for analyze. Just to be sure I did not create a bug
BR
Re: RFXtrx
Posted: Wed Dec 05, 2012 2:18 am
by pavlouis
I don't think your fix created any of the below as I'm pretty sure I was getting them even before I even asked you for assistance. By the way, do you guys ever get the below with the 1 degree? I just tend to filter out the erroneous ones as I figured the signal is being corrupted during the transmission:
17:00:28 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +1.0 deg C humidity: 82 %RH status: comfort signal: 15 battery: 15'
17:01:07 Decoding of message failed: ['0a', '52', '01', 'ff', '70', '01', '00', '5d', '0a', '52', '01']
17:01:45 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +9.3 deg C humidity: 65 %RH status: normal signal: 5 battery: 9'
19:32:49 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +9.7 deg C humidity: 65 %RH status: normal signal: 5 battery: 9'
19:37:19 Decoding of message failed: ['0a', '52', '01', 'e9', '70', '01', '00', '61', '41', '0a', '52']
19:37:58 Message could not be repaired 0a5201f1
19:38:01 Message could not be repaired 0a5201f1700100
19:38:39 Decoding of message failed: ['0a', '52', '01', 'f1', '70', '0a', '52', '01', 'f1', '70', '01']
19:39:17 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +1.0 deg C humidity: 82 %RH status: comfort signal: 15 battery: 1'
20:03:07 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +1.0 deg C humidity: 82 %RH status: comfort signal: 1 battery: 4'
20:33:57 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +9.8 deg C humidity: 65 %RH status: normal signal: 5 battery: 9'
20:37:48 Decoding of message failed: ['0a', '52', '0a', '52', '01', '43', '70', '01', '00', '62', '41']
20:39:46 Decoding of message failed: ['0a', '52', '01', '4b', '70', '0a', '52', '01', '4b', '70', '01']
20:41:02 Message could not be repaired 0a52
20:41:03 Message could not be repaired 0a52014b7001006241
20:55:48 RFXtrx.Type: THGN122/123, THGN132, THGR122/228/238/268 id: 28673 ' temperature: +9.8 deg C humidity: 65 %RH status: normal signal: 0 battery: 10'
20:57:04 Decoding of message failed: ['0a', '52', '01', '53', '70', '01', '0a', '52', '01', '53', '70']
20:57:42 Message could not be repaired 0a5201537001
20:57:43 Message could not be repaired 0a52015370
20:58:20 Decoding of message failed: ['0a', '52', '01', '53', '70', '01', '00', '62', '0a', '52', '01']
20:58:59 Message could not be repaired 5959520153700100624102
20:59:38 Message could not be repaired 5952015370010062410259
21:00:18 Message could not be repaired 5952015370010062410259
21:00:56 Message could not be repaired 5952015370010062410259
21:01:35 Message could not be repaired 5952015370010062410259
21:02:12 Message could not be repaired 5952015370010062410259
21:02:50 Message could not be repaired 5952015370010062410259
21:03:28 Message could not be repaired 5952015370010062410259
Cheers
Paul
Re: RFXtrx
Posted: Wed Dec 05, 2012 7:47 am
by krambriw
Looks not good, I only have "Message could not be repaired" very, very seldom.
- Try to check that ÔÇ£undec onÔÇØ is really disabled.
- Change back to the old timeout setting of 0.4 in
Code: Select all
#Schedule the new resetting task
self.pmh = eg.scheduler.AddTask(0.4, self.ClearTempMessage)
It looks as if your messages are partly correct and then partly overwritten by the same...
Like this
19:38:39 Decoding of message failed: ['0a', '52', '01', 'f1', '70', '0a', '52', '01', 'f1', '70', '01']
'0a', '52', '01', 'f1', '70', is a correct start but then the same is repeated as '0a', '52', '01', 'f1', '70', '01'
Currently no more ideas...
Best regards, Walter
Re: RFXtrx
Posted: Thu Jan 03, 2013 6:35 pm
by Pastis
Hello
thanks for this wonderful plugin
I just can't get any message from my ati remote wonder II why?
and with RFXmngr.exe I only get a code when turning "undec on" mode on :\
Re: RFXtrx
Posted: Thu Jan 03, 2013 7:00 pm
by krambriw
Hi,
If it does not show messages in RFXmngr, it can unfortunately not show in EG either. This is where the issue needs to be resolved first.
BR Walter
ATI Remote Wonder II (only available in hardware version 1.0)
Re: RFXtrx
Posted: Thu Jan 03, 2013 7:54 pm
by Pastis
I got this code with "undec on" checked:
------------------------------------------------
07030C03143A2540
Packettype = UNDECODED RF Message
UNDECODED NEC:143A2540
------------------------------------------------
Re: RFXtrx
Posted: Fri Jan 04, 2013 2:29 pm
by b_weijenberg
This RW II is probably not yet decoded in the RFXtrx433.
Please contact RFXCOM support for an update.
Re: RFXtrx
Posted: Fri Jan 04, 2013 4:43 pm
by Pastis
thank you,
problem solved! their support is really fast ^^
Re: RFXtrx
Posted: Sun Jan 06, 2013 4:41 pm
by Pallantir
My system's been chugging nicely along for a while now, but suddenly I'm getting a few of these:
Code: Select all
17:16:25 Main.Lost contact with sensor: Type: Viking 02811 id: 60928
The weird thing is that it actually gets signals again pretty soon (maybe the next send), so I can't say that it's really lost contact. Does anybody have any idea what this can be?
Re: RFXtrx
Posted: Sun Jan 06, 2013 7:17 pm
by krambriw
Yes, it means that it has passed more than 10 minutes since the sensor was last seen. Maybe the battery is getting weak or you have some other interference. For sure it indicates that the signal is not able to reach all the time, the sensor sends about once per minute.
You could make a quick change if you like, just change the value '600' to something else (seconds) in line 1017, save and restart EG:
Code: Select all
self.monitor_050_mem[base_msg] = self.eventMonitor(
mon_param,
decode_param,
base_msg,
600.0
)
Re: RFXtrx
Posted: Sun Jan 06, 2013 7:22 pm
by Pallantir
Thanks! Yeah, there can be interference from the 433 mHz Next Generation IR Remote extender. Thanks for that tip! I'll set it to 300, I think.
Re: RFXtrx
Posted: Sun Jan 06, 2013 7:29 pm
by krambriw
300 would mean you are increasing the sensitivity and will get alerts more frequently.
900 would mean 15 minutes before you will get notified if the sensor is lost